Unmapping Novell Drives
- From: "Rodney Scott" <rodney_a_scott@xxxxxxxxxxx>
- Date: Fri, 2 May 2008 00:05:42 -0500
We are currently in the process of migrating from Novell to Windows 2k3. We are also consolidating data servers to central locations. On the week-end, we move the data from the local Novell Server to the centrally located Windows. After the data is copied, we shut off the Novell Servers. On Monday morning, when the user logs in, the Login Script is suppose to find any persistently mapped drives to Novell servers, and switch them to the new server\share. This works fine while the Novell Server is up, but with the server off, you get disconnected drives. The wshNet.EnumerateNetworkDrives does not pick them up, neither does a WMI query. However, when you run net use from the cmd prompt, they show up. So, I found in the registry the persistently mapped drives, and attempt to cycle through those to switch the path. Again, this works fine as long as the Novell server is up. It does make the change for the drives, but not during the current session. The user has to log off and back on. Unfortunately this is not acceptable to the customer. Does anyone have any suggestion?
.
- Follow-Ups:
- Re: Unmapping Novell Drives
- From: Alex K. Angelopoulos
- Re: Unmapping Novell Drives
- Prev by Date: Re: Unable to map drives with logon script
- Next by Date: Re: Unable to map drives with logon script
- Previous by thread: Unable to map drives with logon script
- Next by thread: Re: Unmapping Novell Drives
- Index(es):
Relevant Pages
|