Domain Controller Issues?

Question

I am having trouble running logon scripts on my windows 2003 DC. I have put the batch files in Active Directory MMC and I have put the path for the domain user as follows:

C:\WINDOWS\SYSVOL\sysvol\domain name\SCRIPTS\newfile.bat

So far all efforts are unsuccessful. Now when I hit the server through the network and execute the scripts from there a command prompt comes up with the following:

\\192.168.3.49\netlogon

CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory.

Then it executes the script. I have the script to connect to a mapped network drive and execute an app. update from there. Does anybody know what I'm doing wrong?

Answer 1

I can't tell for sure since the UNC path was trunkated by "Answers", but I think either you've got the wrong directory (yes, I know the documentation told you that one) or you don't have the share permissions correct.
Our login.bat file is contained in C:\windows \sysvol \sysvol \domain_name \scripts (note one additional level of sysvol. This is different than what the documentation tells you). This may be unique to SBS 2003, but I don't think so.

Additionally, we have that folder shared as "NETLOGON", share permissions for everyone are "read", file permissions for authenticated users are read & execute, list folder contents and read.

I'd check your directory structure to make sure your script is actually in the right directory. If so, I'd create the share exactly as I've indicated. We have scores of 2003 DC's (mostly SBS) and we set them all up this way for the logon scripts. Never had an issue.

You also have to point your users to the script in Active directory, of course...

Answer 2

"even as the 2003 server is down, we are no longer in a position to get admission to the community for jiffy" - is smart, even as the server's down - the resources on it are down too. you'd be needing to describe issues a touch more desirable, as what you've provide is smart (except the username and password container, that could want to come from everywhere... help us out the following).