Link to home
Start Free TrialLog in
Avatar of kurajesh
kurajesh

asked on

netdom query parameter

i have a windwos 2008 dc and i migrated windows 2008 to windows 2012 now.
both are diff servers. i had completed the fsmo roles shifting and before that netdom query fsmo was showing the 2008 server.

after shifting the roles on 2012 and while giving the same command netdom query fsmo it says " parameter incorrect"

dns on 2008 is an external dns the same has been assigned to 2012 as well.

then i checked the ad users and computers in 2012 - right click the domain and selected properties and error is attached herewith

please revert back as iam in middle of migration with client



"
error.png
Avatar of kurajesh
kurajesh

ASKER

i had just restarted the two servers now , will that cause any issue
Avatar of Radhakrishnan
Hi,

This should work, i suspect that the location you chosen could be wrong, can you bring it to  C:\Users\Administrator\netdom query fsmo

The screen shot shows that it's waiting for the replication to happen and it may take time. If you want you can manually replicate it from AD Sites and Services.
i have given from win 2k12 powershell . the location is correct.

now i just restarted the 2008 server. will that cause any issue . also please let me know the manual steps
now afert restarting 2008 server it is just on "applying computer settings" for a long time.

iam able to ping to ip of win 2008 server
i have started the 2008 server in safe mode and changed the primary ip to 2012 ip and restarted , same issue.

kindly revert asap
Hi,

The similar issue were asked before in EE, please have a look at this thread https://www.experts-exchange.com/questions/26407879/Problem-with-netdom-when-transferring-fsmo-roles.html
ASKER CERTIFIED SOLUTION
Avatar of kurajesh
kurajesh

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hi,

Glad to know that the issue has been resolved. Regarding the DNS query, if the server is acting as DNS then the DNS primary address should point to itself and secondary as other DNS server in the network.
the same solution worked