Startup Scripts

Topic

New Reply

I’m trying to use group policy to distribute a startup .vbs script that will map network drives. On most of the pc’s that I have applied the scripts to, the scripts work fine. On others, though, I get the following error message: An attempt was made to remember a device that had previously been remembered, Error: 800704b2. I have disconnected the drive letters that are causing the problem before I restart the pc, but it still gives the error after it comes back up. I can login in to these pc’s, after receiving the error, and execute the scripts manually and they work. I have reinstalled windows on one of the pc’s that didn’t work before and that fixed the problem. The pc seems to think that the drive letter is in use even though it’s not. Any suggestions?

Reply | Quote

Replies

Is it being mapped in the user logon script?

Joe

--Joe

Reply | Quote

Is it being mapped in the user logon script?

Joe

--Joe

Reply | Quote

No it’s being mapped in the computer settings. I think that it might have something to do with the path of the mapped drive being changed.

Reply | Quote

Have you disconnected the network drives and rebooted without having you script run? If so, what happens?

Joe

--Joe

Reply | Quote

Nothing happens. No errors, no drives get mapped. I did find out that if I change the .vbs script path to the original path in the batch file, I don’t get the error. Persistent connections was originally turned on, but now it’s somehow remembering the old path even though it doesn’t get mapped and persistent connections is turned off.

Reply | Quote

Nothing happens. No errors, no drives get mapped. I did find out that if I change the .vbs script path to the original path in the batch file, I don’t get the error. Persistent connections was originally turned on, but now it’s somehow remembering the old path even though it doesn’t get mapped and persistent connections is turned off.

Reply | Quote

BTW, what win2k service pack are you running?

Joe

--Joe

Reply | Quote

SP4, all critical updates ar installed.

Reply | Quote

Well, have you tried disabling ‘file & print sharing’ and/or ‘client for microsoft networks’ and then re-enabling. That may clear out any local caching. You could also try an uninstall and re-install of these network client/services.

Joe

--Joe

Reply | Quote

Yes, that didn’t work.

Reply | Quote

Yes, that didn’t work.

Reply | Quote

Well, have you tried disabling ‘file & print sharing’ and/or ‘client for microsoft networks’ and then re-enabling. That may clear out any local caching. You could also try an uninstall and re-install of these network client/services.

Joe

--Joe

Reply | Quote

SP4, all critical updates ar installed.

Reply | Quote

BTW, what win2k service pack are you running?

Joe

--Joe

Reply | Quote

Have you disconnected the network drives and rebooted without having you script run? If so, what happens?

Joe

--Joe

Reply | Quote

No it’s being mapped in the computer settings. I think that it might have something to do with the path of the mapped drive being changed.

Reply | Quote