login script not executing

[techie99]

I have a Windows 2003 server. Why is it I can log on to one domain and have the log-in script execute and when I log into another domain I don't have the log-in script execute? In user manager for domains they are pointed to the right place to read the log-in script. Is this simply a group policy setting that has eluded me? The domain where the log-in script is not executing has active directory.

 

[tfg13]

Where have you placed the login script on the 2003 domain? Have you "assigned" this login script to the GP? Also, I noticed that you stated User Manager for Domains. Are you sure it is a script and not a .bat?

 

[techie99]

Thank you for your reply. The login script (bat file) is in the Netlogon share on the 2003 domain, which is where it should be. In User Mgr for Domains, on the profile tab I have the right script name. On a Win 03 machine the bat file will not execute when logging onto 2003 domain but it will when logging onto NT domain. Strangely enough, the login script will execute on the 2003 domain from other PC's, it just won't on the 2003 PC, leading me to believe it is a group policy setting.

I have gone through the group policy settings several times over but have failed or have neglected to see which one pertains to this problem. Any help you can provide would be greatly appreciated.

 

[tfg13]

You have placed it in the Group Policy logon scripts? In your group policy, under User Config, Windows settings, Scripts, logon, a box pops up, does it show the .bat in there? If it does, I would start lolking at the .bat file to make sure that all shares, and/or "settings" are on the 2003 server. Also, make sure that you don't have a loopback setting on the PC that is the problem.

 

[techie99]

Thank you so very much for your reply.

No, I did not place the .bat file in Group policy. The login script (bat file) is in the Netlogon share on the 2003 domain. In User Mgr for Domains on the Profile tab, we specify the Logon Script Name.

In the NT domain we have things set-up the same, but it actually works (the login script runs).

Are you saying that with a 2003 domain things work differently and that I must specify the login script in Group Policy?

 

[tfg13]

Yes. You have to actually assign the .bat to run either for users, or for the machine.

 

[techie99]

Then, why is it when I log onto other PCs (non-Win 03) onto the Windows 2003 domain I get the login script to run? I really would like to understand this.

 

[tfg13]

Is the .bat loaded in the Active Directory? I have found it easier to just make sure that you have it in the domain Group Policy instead of each individual login.

 

[techie99]

I'm not able to edit the default policy on the domain--the edit button is greyed out.

 

[mlichstein]

Putting logon scripts in a GPO is the preferred way to do it in AD, but it isn't necessary. You can still do the "old school" method of putting the .bat file in netlogon and specifying the file name in the properties of the user account.

You might want to enable userenv logging on the problem server and see why it is failing to execute the script.

http://support.microsoft.com/default.aspx?kbid=221833

 

[tfg13]

mlichstein,
I agree that there are multiple ways of getting a script to run within a 2003 domain, I just tried the quick and dirty one.

techie99,
Have you checked to see if this PC does have loopback settings?

 

[techie99]

I figured it out, in AD, in my log-in batch file I had to provide the specific path for the kixtart files. It didn't matter that the login batch file, kixtart files were all in the same netlogon folder in the same directory. As soon as I spelled out the path the login script appeared. In our windows nt domain we didn't have to spell out the path.