Windows Forum

Ask something
Discussion Locked

Win 98 login scripts

0 helpful
3 replies

by joemoran

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Folks, I need some help here.

I just created several simple login scripts, which contain a handful of net use drive mappings.

The problem I am having is with Windows 98 users who are using these scripts. The scripts are executing, but when they do, they invariably map drive Z to the NETLOGON share of whatever BDC the user is logging on to. This is happening with two seperate scripts on two seperate servers, although only with Windows 98 clients. NT/2000 clients are not exhibiting the samebehavior.

Needless to say, I am not explicitly mapping drive Z to that share or any other one, and there aren't any residual mappings of that share on the client, so I am at a loss to explain this?

I've heard of this happening before, but cannot recall the resolution. Anyone have any ideas? Thanks.

3 replies

by nettek

Because the Netlogon folder is a shared folder and the logon script is executing from the folder, I suspect that Windows is automatically mapping the drive to the shared folder. If you have Office installed, this could be a result of having FindFast running (a utility that is more problems than it is worth). Delete Find Fast from the Startup folder. Then go to Control Panel -> FindFast and delete the Indexes. Then from Index on the toolbar, select Close and Stop.

Another way to remove the drive mapping is to place the following at the end of your loging script:
IF "%OS%" == "Windows_NT" goto end
NET USE Z: /DELETE
:end
This will delete the drive mapping on the Win9x clients after it is created, and the users will never know the difference.

This discussion is closed to new replies.