Jump to content

Recommended Posts

Posted (edited)

Since Sp3 has been installed on some client laptops, the logon scripts are not working correctly.

 

The mapped drives not always being mapped.

 

I've tried created them in vbs and use vbs instead of bat files. Still no joy.

 

I dont really want to use a gp logon script as the some users have different logon scripts assigned to their username.

 

Anyone else experiencing this?

Edited by techyphil
Posted

@ECHO OFF

IF EXIST c:\COMMAND.COM GOTO WIN9X

rem **Windows NT/2000/XP Logon**

:WIN2K
rem NET USE G: \\SERVER1\Staff /PERSISTENT:NO
rem NET USE I: \\SERVER1\APPLIC /PERSISTENT:NO
NET USE O: \\SERVER1\SHARED /PERSISTENT:NO
NET USE W: \\SERVER1\WORK /PERSISTENT:NO

NET USE R: \\SERVER1\SHARED_FILES /PERSISTENT:NO

NET USE P: \\SERVER2\PUBLIC /PERSISTENT:NO
NET USE T: \\SERVER2\SME /PERSISTENT:NO
NET USE S: \\SCH4022-5\ADMINDATA
REG IMPORT s:\ram.reg
net time %logonserver% /set /yes
rem SupportIcon.vbs
rem netCheck.exe
rem highContrast.vbs
rem staffInventory.exe

rem \\server1\netlogon\updateto6334632.exe

rem For Managers ONLY - NET USE U: \\SERVER1\USERS$ /PERSISTENT:NO

rem **Start Network Printer Connection Batch File**
CALL \\SERVER1\NETLOGON\PRINT-ST.BAT


GOTO COMMON

rem **Windows 9x/Me Logon**


:COMMON
NET TIME \\SERVER1 /SET /YES



IF NOT EXIST C:\COMMAND.COM GOTO END

rem **Routine to force exit from NT Logon Script**
c:
cd\windows
echo.> c:\windows\lmscript.$$$

:END

 

Thank You, much appreciated!

Posted

Someone else (on these forums) reported the same problem and we isolated it down to the way the home shares were shared and redirected.

 

If you use \\servername\share\username (this seems to cause problems)

 

If you use \\servername\username$ (this seems to work)

 

I use the latter method on XP SP3 with no problems! :)

Posted

Thanks,

 

Well I wish it wasnt just a coincidence but it honestly does only affect SP3 machines. Having said that, it is a custom build CD with lots of reg tweeks. It has to be something on that :(

 

I read that sometimes a slow link detection can cause logon scripts not to be executed as well.

Posted
Someone else (on these forums) reported the same problem and we isolated it down to the way the home shares were shared and redirected.

 

If you use \\servername\share\username (this seems to cause problems)

 

If you use \\servername\username$ (this seems to work)

 

I use the latter method on XP SP3 with no problems! :)

 

The subfolder method works too, you just need to make sure things don't go peculiar by having a read for "this folder only" on the folders that have to be traversed.

Posted
Someone else (on these forums) reported the same problem and we isolated it down to the way the home shares were shared and redirected.

 

If you use \\servername\share\username (this seems to cause problems)

 

If you use \\servername\username$ (this seems to work)

 

I use the latter method on XP SP3 with no problems! :)

 

have had to do that for our mac users and windows clients seem to be fine with it as well.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...