Putting login scripts on a none DC in AD environment.
Posted on 2005-04-06
Good day everyone. I have a question about implementing login scripts on 2003 server in AD environment to map shared drives when the user logs in. The problem that I am having is, the company that I am working for has a DC at each site, but only our central office has the control of the DC's and they won't give anyone else access because we just migrated recently to AD and they want to make sure that nothing goes wrong at this point in time. Now I am switching our Novell file server to 2003 server, and I wanted to create login scripts for the shares to be mapped automatically as the users log in, but since I don't have access to the DC I can’t do this using GPO’s or VBScripts. So since I don't have access to the DC and to get the headquarters to do any of this for me is pretty much impossible, I was wondering if it's possible to create a basic batch file login script, create a share on this new file server that's not a DC/BDC just a basic 2003 files server, and store these scripts in the share. Then in AD under user properties, profile tab point the profile path to the share that the login scripts are located on \\servername\share, and under the logon script tab put the login script name xxxx.bat.
I created a basic batch file and I placed it in the startup folder of my machine just to make sure that the script is ok and everything was fine, the shares were mapped with no problems, and I even put a basic net send command just to make sure that I see the .bat file execute. When I did all this under my users properties profile tab in AD and tried to log in nothing happened, but I was getting an popup when login out about "not being able to copy roaming profile" So is it even possible to store the login scripts on a none DC server? And then point to them by using the Profile tab under user properties? And if not, any other options that I might have?
I know the easiest thing to do, would be store the scripts on DC and use VBScripts or GPO’s, but like I said that's not an option in this strange case of mine, take way to long to coordinate any of this with head office IT staff.
Help would be appreciated,