Drives Not Re-Mapping / VBScript Offline Files

[Guest]

I have a logon script (VBScript) that maps drives persistently based on group
membership.

Problem is when a user is moved to a different group (i.e. they no longer
have access to the drive that was mapped persistently), the drive;
• Is not enumerated via EnumNetworkDrives
• Cannot be disconnect via RemoveNetworkDrive, error; drive not found
• Is unable to be replaced via MapNetworkDrive, error; attempt to remember
drive previously remembered

I believe the error is somewhat identified by Microsoft here
(http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q303209&ID=KB;EN-US;Q303209).
I have however found the problem to be not specific to WScript but all drive
mapping tools (NET USE, manual mapping via Explorer).

In an attempt to workaround I would like to;
• Change the persistent status of the drives being mapped at logon (i.e. not
persistent)
• Create a logoff script that makes persistent any network drives that
contains offline files. While this might not be a fix it will help cut down
occurrences of the mapping problem mentioned above to a acceptable level.

My questions;
1. Can anyone identify a solution for the mapping problem mentioned?
2. Is there anyway to interact with Offline Files (list them) with VBScript
via the registry or otherwise?

 

[Pegasus \(MVP\)]

In a batch file environment the problem is easily solved
by making share connections non-persistent. There is
no need anyway to make them persistent, since they are
controlled by a script!

When first making them non-persistent, it may be
necessary to knock out the lot, which will get rid of
remembered but unavailable connections, e.g. like so:

net use /persistent:no
net use * /del /yes
net use s: \\YourServer\YourShare

 

[Guest]

Thanks for your response, however the need for drive persistence comes in
with the Offline Files. As if a user makes a folder in that drive available
offline, they are going to look for that same drive if they are indeed
offline. In which case the script cannot run.

Hence my question to determine which folders are offline, as these alone can
be made persistent.

--
Regards,

- MPAI CITS

In a batch file environment the problem is easily solved
by making share connections non-persistent. There is
no need anyway to make them persistent, since they are
controlled by a script!

When first making them non-persistent, it may be
necessary to knock out the lot, which will get rid of
remembered but unavailable connections, e.g. like so:

net use /persistent:no
net use * /del /yes
net use s: \\YourServer\YourShare