QEMS
asked on
Problem with netdom when transferring fsmo roles
Hi,
I am trying to change our current windows 2k3 server over to 2008 R2, hardware is being replaced at the same time. We have one server for this domain and once the change over is complete I will remove the 2k3 server and have a single 2008 R2 server.
I have got as far as adding the 2008 server to the domain and started to transfer fsmo roles across.
Before transferring any roles I ran "netdom query fsmo" on the new server and all fsmo roles were shown as running on the original server I have transferred RID, PDC and Infrastructure roles and everything appeared to be successful, however when I now run exactly the same command I get the failure message "The parameter is incorrect"
When I check the operations masters in AD users & computers they are shown as being on the new server.
Can anyone offer any advice on why netdom is not showing me all the roles, making no mention of the new server and how to resolve this?
Thanks in advance.
I am trying to change our current windows 2k3 server over to 2008 R2, hardware is being replaced at the same time. We have one server for this domain and once the change over is complete I will remove the 2k3 server and have a single 2008 R2 server.
I have got as far as adding the 2008 server to the domain and started to transfer fsmo roles across.
Before transferring any roles I ran "netdom query fsmo" on the new server and all fsmo roles were shown as running on the original server I have transferred RID, PDC and Infrastructure roles and everything appeared to be successful, however when I now run exactly the same command I get the failure message "The parameter is incorrect"
When I check the operations masters in AD users & computers they are shown as being on the new server.
Can anyone offer any advice on why netdom is not showing me all the roles, making no mention of the new server and how to resolve this?
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks very much for both of your responses, sorry about the delay responding but we have new fibre being connected through the site today as well.
I just wanted to query this before continuing with transferring the remaining two roles.
I just wanted to query this before continuing with transferring the remaining two roles.
ASKER
I have now successfully transferred the remaining roles and used the script from the O'Reilly link which confirms the roles are running on the new server.
The command "dsquery server -hasfsmo <role>" returns an error code regardless of whether I use schema, name, infr, pdc, or rid as the role.
Is there a resolution to the command "netdom query fsmo" not working? Or is this something that will require an update from MS?
The command "dsquery server -hasfsmo <role>" returns an error code regardless of whether I use schema, name, infr, pdc, or rid as the role.
Is there a resolution to the command "netdom query fsmo" not working? Or is this something that will require an update from MS?
If you run the command on the 2008 server, does it yield the same result ?
ASKER
I was always running "netdom query fsmo" on the 2008 (R2) server - that result has stayed the same.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The GUI shows it correctly and the script that is available on the O'Reilly page shows that the roles are on the 2008 server.
I haven't finished moving all the shares and data across yet, is it possible this will resolve itself once i have completed that and removed the 2003 server?
I haven't finished moving all the shares and data across yet, is it possible this will resolve itself once i have completed that and removed the 2003 server?
Yes, most likely.
ASKER
I had to resolve a DNS issue and then this command started working again.
Thanks again for the help.
Thanks again for the help.
Hi,
I'm experiencing exactly the same behaviour as you describe. You are talking about resolving a DNS issue. Could you elaborate on that please ? Maybe thats my problem too.
Thx in advance
I'm experiencing exactly the same behaviour as you describe. You are talking about resolving a DNS issue. Could you elaborate on that please ? Maybe thats my problem too.
Thx in advance
Ok !! solved.
I went on looking for the DNS-issue and I discovered the Server2003 had 2 external DNS-servers in its IP-config. Server2008 had as first DNS-server the server2003 and as second DNS-server server2008. I changed both servers' interfaces as follows :
first DNS-server : itself (Server2008 on the server2008 and ...)
second DNS-server : the other one (Server2003 on the server2008 and ...)
After changing that I guess I just had to wait. Because while looking for more answers on the internet, all of a sudden I got no more errors and the FSMO roles listed up perfectly to the new server.
Thx for getting me in the right direction.
I went on looking for the DNS-issue and I discovered the Server2003 had 2 external DNS-servers in its IP-config. Server2008 had as first DNS-server the server2003 and as second DNS-server server2008. I changed both servers' interfaces as follows :
first DNS-server : itself (Server2008 on the server2008 and ...)
second DNS-server : the other one (Server2003 on the server2008 and ...)
After changing that I guess I just had to wait. Because while looking for more answers on the internet, all of a sudden I got no more errors and the FSMO roles listed up perfectly to the new server.
Thx for getting me in the right direction.
http://support.microsoft.com/kb/324801
Here, you can find how to do that