We have a Windows Server 2003 R2 file server on VMWare, called OldFS01, which used to be a physical server.
We've built a Windows Server 2008 R2 Standard file server, called NewSRV01, also on VMWare but built from scratch and on a new MUCH faster SAN, to replace it.
Most (all?) shares, drive mappings and so on refer to the old server using an alias, 'SRV01'.
The new server currently has no data and so none of the shares.
Also, the old server is member of a few DFS Namespaces and Replication Groups to replicate data to/from our Hong Kong and New York offices, Some data (such as a ‘Software’ namespace) only replicates out from OldFS01.
This weekend we're migrating from the old to the new, choosing the approach of copying the VMDK file of the E: drive on OldFS01 (which contains all the data/shares) to the LUN on the new SAN to attach to NewSRV01.
Here's my plan so far:
1. Export the shares (registry key) from OldVFS01
2. Shut down OldVFS01
3. Copy the E: disk file to the new LUN for NewSRV01
4. Add the disk as E: to NewSRV01 in VMWare then Windows.
5. Import the shares
6. Change the SRV01 alias to point to NewSRV01
7. Make DFS changes
8. Test drive mappings, DFS Namespaces
9. Power-up and rename OldFS01 (OldFS01ol?)
10. Power down (or disconnect from the network) OldFS01ol
11. Create OldVFS01 alias, pointing to NewSRV01 (to capture any OldFS01 host name references out there)
Have I missed anything? Step 7 seems a bit vague at the moment, for instance...
Is there something that you came across in a similar situation that I should watch out for?