EricTheRedneck
MIS
I have MetaFrame XPa servers with NetWare client 4.83 SP2. The MF servers are running on Windows 2000, SP3. The MetaFrame XPa is at FR3. Most of my MetaFrame users are remote users who access the MetaFrame servers over the Internet, so their PC's are standalone.
When I deliver just a desktop to the user, the NetWare client comes up to allow the user to login both to NDS tree and the AD Domain. The NetWare login scripts run and map certain drives.
When I set up a few published applications, I can access the applications themselves, but I the login uses the Windows client interface rather than the NetWare client. The NetWare client is never invoked, so the drives are not mapped to the NetWare servers. I can log in only to the Domain but not to the NDS tree. Since the apps themselves are on a Windows server, I can use the apps, but I don't have the user's home directory available for saving data since I don't have the NetWare client to map drives to NetWare resources.
What do I need to do to have the published apps use the NetWare client rather than the Windows client?
When I deliver just a desktop to the user, the NetWare client comes up to allow the user to login both to NDS tree and the AD Domain. The NetWare login scripts run and map certain drives.
When I set up a few published applications, I can access the applications themselves, but I the login uses the Windows client interface rather than the NetWare client. The NetWare client is never invoked, so the drives are not mapped to the NetWare servers. I can log in only to the Domain but not to the NDS tree. Since the apps themselves are on a Windows server, I can use the apps, but I don't have the user's home directory available for saving data since I don't have the NetWare client to map drives to NetWare resources.
What do I need to do to have the published apps use the NetWare client rather than the Windows client?