Changed domain controller still using login script off old one

I added a 2008 server and made it a domain controller and them transferred the FMSO roles to it. I'm trying to make an adjustment to the login scripts and it wasn't working. I ran %logonserver%\netlogon and it shows the path as looking toward the old domain controller. its still online for the moment I have some file shares to move off of it. how to I get the PC's to look to the new DC for the login scripts?
LVL 2
Axis52401Security AnalystAsked:
Who is Participating?
 
MaheshConnect With a Mentor ArchitectCommented:
Are both servers in same site?
Just run %logonserver% on client machines and new DC itself and check to which server they are pointing as a logon DC
may be they can point to old server as both servers in same site.
In that case you can add GPO on OU containing users with mentioning new DC path for logon script
For Ex: \\newDC\netlogon\xyz.bat

Or
else you can try by pasting above path in all user properties logon script path.
I have not tested this. Please try on one user 1st.

Mahesh
0
 
Axis52401Security AnalystAuthor Commented:
Yes they are both at the same office
Running %logonserver% on the new server gives itself
Running it on  PC gives the old domain controller thats what I'm trying to figure out how to change before I take out the old server

I don't know much about creating GPOs so I don't know how to create and link one to mention the new path.
0
 
MaheshArchitectCommented:
You must be having OU that contains all required users

Check below links to create logon script GPO
http://homepages.ius.edu/JHOLLY/a247/labs/LogonScript.htm
http://www.youtube.com/watch?v=5E34QVxdcGQ

Do not forget to set script path as I suggested in earlier comment.

OR

just try below
Go to user properties \ profiles tab and in "logon script" paste path mentioned above.
Check if it allow to do so.
If it works, then select all users and right click and go to properties \ profiles Tab and in "logon script" paste path mentioned above.

Mahesh
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
Axis52401Security AnalystAuthor Commented:
I know how to create a login script we already have that done. In fact all the stations are using that script but its pulling it from  the Old server. What I'm trying to do is get the machines to utilize the script from the new DC or login server so I can shut down the old server.
0
 
MaheshArchitectCommented:
You cannot stop clients from getting old server as logon server, since both servers are in same site.

just change the logon script path to reflect new server as my earlier comment may be through GPO

Mahesh
0
 
Axis52401Security AnalystAuthor Commented:
Yes but I don't know how to add GPO on OU containing users with mentioning new DC path for logon script
For Ex: \\newDC\netlogon\xyz.bat

What does that mean? I can add a GPO but where in those settings do I make that setting to get them to see the new server for the login script.
0
 
MaheshArchitectCommented:
In new GPO when you are trying to add logon script, in user configuration, instead of browsing the script path, just type path of script manually
Ex: \\newdcname\netlogon\scriptname

Mahesh
0
 
Axis52401Security AnalystAuthor Commented:
Ye thats the way I did it and its not applying
0
 
compdigit44Commented:
Here are a copy of points.

1) In AD all DC's are equal members meaning they can service log on request for clients in their given subnet. Just because to transferred FSMO roles from server to the other will not stop client from connecting to the old server since it is still hosting AD and the Sysvol share.

2) When you want to apply a GP you need to assigned it to the OU that contains the target user or computer accounts. You can also apply GP at the domain level.

3) Even if you change the path of the login script to run from the new server clients still may be authenticated by the old server but then run the script from the new server.

Are you trying to retire the old server. IF so why not run dcpomo on it and make it a regular member server. I would suggest buying an addtional server though since your should always have two DC's for redundancy.
0
 
SandeshdubeySenior Server EngineerCommented:
How have you applied the script is it on user properties/OU/domain etc.You need to check the same and point the UNC path to new DC.To get the clear view can you post the screenshot of the policy.Also change the dns setting preferred dns setting on client computer to new DC this may be in DHCP or TCP/IP setting.
0
 
compdigit44Commented:
If you are still having problems can you upload the following information.
1) Screen shot of your GP login script settings including script path
2) Screen shot of GP placing in AD structure
3) TCP/IP settings on the server
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.