• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 564
  • Last Modified:

DFS namespace on Server 2012 R2

I get the error Object identifier does not represent a valid object when I try to add Namespace Server on Server 2012 R2 SERVER. I am just trying to move from an existing DFS Namespace to a new server. I have copied the data and when I do the Add Namespace Server it will not create it. It gets through all the checks until the final one to commit changes. That is when I get the error.
0
Wauna_IT
Asked:
Wauna_IT
  • 3
  • 3
1 Solution
 
MaheshArchitectCommented:
You have deleted existing DFS from 2008 \ 2008 R2 and trying to build same name space on 2012 R2?

In that case 1st check if old name space is got deleted completely
https://social.technet.microsoft.com/Forums/windowsserver/en-US/a7724837-b80a-436b-89df-97bb189bcecc/dfs-clean-old-dfs-replication-groups?forum=winserverfiles

Once you clear I out, force AD replication and then try to create name space on new server

In reality you could have simply add 2012 R2 server as DFS name space server in existing DFS
0
 
Wauna_ITAuthor Commented:
I am currently hosting the namespace on a Server 2003 server. I have installed DFS services on a Server 2012 R2 server and I am in the process of trying to decommission the 2003 server. So I thought the suggested method to move it to the new server would be to Add namespace server from the Server 2012 R2 server and delete the namespace from the Server 2003 server. That is when I run into the error. I understand your point to simply add the 2012 R2 server in existing DFS but I am wondering what would happen when I decommission the old server.
0
 
MaheshArchitectCommented:
U have deleted name space from 2003 server, as a fact it is got deleted from active directory itself, since DFS settings are stored in AD, deleting DFS name space had deleted entire DFS from environment
In reality you should add 2012 server as name space server in existing DFS name space and then just remove 2003 server from that name space from 2012 dfs console

The way you are trying to, its could be possible with different way:
U need to export DFS 1st on 2003 server
Then remove dfs from 2003 and replicate changes to AD, ensure there are no stresses left
Then import DFS on 2012 R2 server, this would work
http://blogs.technet.com/b/askds/archive/2008/01/15/migrating-your-dfs-namespaces-in-three-sorta-easy-steps.aspx

Now you have deleted DFS, I don't think you would be able to add it, Now you could build new DFS after clearing out all old dfs stresses as mentioned in 1st comment

OR

else if you have system state backup of 2003 DFS name space server and DC server, you could restore DFS, check article for more info
http://support.microsoft.com/kb/969382
0
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Wauna_ITAuthor Commented:
I called Microsoft and opened a ticket. They had me run the following commands from the new server then I could add the namespace on the new server.
ipconfig /flushdns
nbtstat -RR
dfsutil /pktflush
dfsutil /spcflush
dfsutil /purgeMupcache
I had to run the same commands again before I could disable the old namespace server too.
This blog can be closed. Thanks for responding.
0
 
MaheshArchitectCommented:
I was in a wrong impression that you have deleted DFS from old server and trying to create new DFS name with same name  on new server
Anyways your problem is resolved now, thread will get closed automatically after 3 / 4 days
0
 
Wauna_ITAuthor Commented:
I called Microsoft and opened a technical help ticket.
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.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now