Quantcast
Channel: File Services and Storage Forum
Viewing all articles
Browse latest Browse all 1766

File Server Migration question - Best tool AND DC to Non DC question

$
0
0

Hello,

I am preforming my first file server migration, and I'm researching the best tools to use.  So far I think I have it narrowed down to the MS Migration Toolkit and Robocopy.  Pretty straight forward, we are moving data from one FS to another, going to decom the old server once the migration is complete.

Here's the specifics:   

- Server 2003 (VM) to Server 2008 R2 (VM)

- The source File Server is a Print Server and Domain Controller as well as a File Server

- The new File Server will still be a File Server and Print Server, however it WILL NOT be a Domain Controller

- The new file server will have a new name, and mapping I can manage via login script

- I would like to test a tool, then migrate files / test the new server, and then once it's turned up migrate any new / changed files

- This is all done in while in production

The Print server piece I'm not too concerned about.  It's only one or 2 Printers, and I'll most likely have to install new drivers anyway.  I also found an MS article that helps with this.

My real gotcha comes in the tool and permissions.  Looking at the MS Migration Tool, this concerns me:

  • The DFS root server cannot be a domain controller.

We are not using DFS right now, but did and may be again at some point.  Since we were before, can we use this tool w/o any adverse effects.  And alternately, if we choose to again, will using this tool effect our ablity to do so on the new server down the road?

My other, more pressing question, concerns effects on permissions on the shares an server.  What effect will migrating from a Domain Controller to a non DC File Server have on these?  Both local and share related?  I'd like the ACLs to transfer seamlessly.

Thanks in advance




Viewing all articles
Browse latest Browse all 1766

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>