I obviously dont understand DFS well enough so I'm turning here to EE community to see if I can get some quick assistance.
I have a Windows 2003 Std SP2 member server, that houses several file shares and publishes them through DFS. I thought the seamless approach would be to just rename old file server (A) and bring up new file server (B) with the original name, same set of shares, same ACLs, and DFS would resume.
This was not the case. From what I've read (at 2am last night) DFS gets attached to the system's SID - but maybe I'm wrong.
When I would try to connect to the Root Server, I would get an RPC server unavailable. I did check out this link
but I couldnt find the correct naming context, CN=System, CN=Dfs-Configuration, with ADSIEDIT.
When I tried to just forget the original namespace, I tried recreating new target but I would also receive error message that the root target was not available.
Our namespace reads as such, \\XYZcorp\share however, when I tried to recreate the DFS targets, the namespace now read, \\XYZcorp\xyzcorp\share -- which is not what I wanted. I was trying to keep from having everyone remap their drives. I do have a bat file stuck in GPO in the logon script section, that can just net use delete the old mappings, and then net use the \\netbiosname\share UNC syntax.
if i cant get DFS working, I just have to go that route, but I would prefer to get DFS working as it would make things easier.
Any ideas? Suggestions?