Question Locked

logon script under Profile tab?

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

hello,
I would like to make a logon script for a user under Windows Server 2003. I made a folder named "scripts" under the C drive(C:\scripts) and shared it out with a name Netlogon. With "net share" command i can see the C:\scripts shared out as Netlogon. However, my logon script is not found when the user logs in(he has all the necessary rights to access Netlogon folder). I think i have entered wrong information under "Profile path" and "Logon script" fields. Under "Logon script" field I entered the name of my bat file ant under the "Profile path" I entered \\127.0.0.1\Netlogon Did I do something wrong?

5 replies

by granthb2001

You should use "net use" not "net share". Also, you should
probably put the script in the netlogon folder in the
Windows directory.
Good luck.

by maniacman

What you're doing is all wrong and redundant. When you have a domain controller, there already is a default share on the server called Netlogon and that's where you place your login script. You don't need to create it and share it out because it's already there. Go to a command prompt and type Net Share and you'll see the Netlogon share should be there. On the profile tab of the user, for login script, enter \\servername\netlogon\scriptname. Do not use localhost because from the workstation's point of view, localhost refers to itself, so how will the client refer to itself to run a login script? You need to specify the servername explicitly.

Regards,
R.Z., MCSE, MCDST

by ghummad

Hi RZ.You are absolutely right in that there is indeed a built in share folder for loging scripts. So, there is no need to create one, nor is it necessary to point it in the profile path of the user profile window.

I have one question for you though. My users have terminal services session with the Domain Controller. They run apps, IE, prit, etc. using Terminal services. I have a logon scrip residing in the sysvol\sysvol\scripts folder of Windows. Recently I made changes to the UNC of mapped drive. it used to be NET USE Q:\SERVER-A\SHARE_NAME_A. I changed it to NET USE Q:\SERVER-B\SHARE_NAME_B. I saved the logon script is saved in a batch file named logon.bat, which is used in User Profile window. After making changes, I rebooted the server, and all the workstations so the latter can point the Q drive to the new UNC. But the workstations in Terminal Services sessions still retained the old UNC of the Q drive and they all indicate "disconnected" drive under "My Computer". One more thing, users are not allowed to map drives using terminal services. Care to explain why this is happening and suggest a solution?

by ghummad

Hi, in my post above the syntax should read:

NET USE Q: \\SERVER-B\SHARE_NAME_B

and the location of the logon.bat script is in:

C:\WINDOWS\sysvol\sysvol\domain.local\scripts

which is simply entered as LOGON.BAT in the User Profile window under in Logon Scripts. No Proflie Path entry was made.

This discussion is closed to new replies.