The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Windows 2003 Server Logon Scripts not running

    Discussion in 'Windows OS and Software' started by BRPCADMIN, Jun 2, 2008.

  1. BRPCADMIN

    BRPCADMIN Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    So we decided to setup a server here at work since our needs are growing. We built a computer and installed Windows 2003 Server Standard Edition with SP2. I installed active directory, dhcp, and dns with the nifty wizard at setup. We have several different departments with different mapings for printers. So I setup two different OUs lets just call one North and the other South. To test them out i made a simple logon.bat file which consisted of

    @echo Hello World!!
    @pause


    which would show me that it was working as I had to hit any key to continue. I went and setup a GPO for the OU But to no avail I cant get it to work. I even put the logon.bat in their profile it still doesnt run. I added the maping to the default gpo for the entire domain and still nothing!! Here is what I used to help me out

    Logon scripts can also be configured in Group Policy. However, Group Policy only applies to clients with Windows 2000 or above. The setting in Group Policy is “User Configuration”, “Windows Settings”, “Scripts (Logon/Logoff)”, “Logon”. Best practice is to copy the file you want for the Logon script to the Windows clipboard, open the “Logon” setting in the Group Policy editor, press the “Show Files...” button, and paste the desired file in the dialog. You can select the file and edit it in this dialog as well. This is easier than navigating in Windows Explorer to the folder where Group Policy Logon scripts are saved. However, if you do have to navigate to the folder, the path on the Domain Controller is:

    %SystemRoot%\sysvol\sysvol\<domain DNS name>\<policy GUID>\user\scripts\logon

    This server has nothing else done to it or setup other than what I have said. This is driving me nuts as it should be something so simple. The clients are Windows 2000 and Windows XP. Please help!! :)
     
    BRPCADMIN, Jun 2, 2008
    #1
  2. gerryf19

    gerryf19 I am the walrus

    Reputations:
    2,275
    Messages:
    3,990
    Likes Received:
    0
    Trophy Points:
    105
    gerryf19, Jun 2, 2008
    #2
  3. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    All i can say is make sure the policy is linked to the correct OU and that the users who should be affected by it are in the correct OU as well.....i really never did any tweaking with startup/logon scripts so i don't know much about it....

    Oh, and a gpupdate /force command always help. And a gpresult will show u all the policies applied on the server.....
     
    makaveli72, Jun 2, 2008
    #3
  4. BRPCADMIN

    BRPCADMIN Newbie

    Reputations:
    0
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    5
    well i figured it out myself after messing around under the user, administrative templates,system, scripts i had to enable run logon scripts synchronously, run log on scripts visible. Once i did this it worked like a charm!!
     
    BRPCADMIN, Jun 2, 2008
    #4
  5. makaveli72

    makaveli72 Eat.My.Shorts

    Reputations:
    1,235
    Messages:
    2,108
    Likes Received:
    0
    Trophy Points:
    55
    Great i learnt something!
     
    makaveli72, Jun 2, 2008
    #5
  6. surfasb

    surfasb Titles Shmm-itles

    Reputations:
    2,637
    Messages:
    6,370
    Likes Received:
    0
    Trophy Points:
    205
    yeah, you have to turn on a GPO that displays the output of the logon script. That gets people.
     
    surfasb, Jun 2, 2008
    #6