|
I figured this was one of the better threads to ask, but feel free to redirect me if I'm wrong. I'm a CJ / developer for my small company. We have two Hyper-V hosts that have a few Win2k3 VMs that we haven't gotten around to upgrading (ain't broke, don't fix, etc, etc). I'm now ready to replace our main virtual file server from 2k3 to 2012 (for a number of reasons). Rather than deal with the butthurt of peoples UNC shortcuts changing and mapped drives breaking, can I do an in-place switch over a weekend and keep the same hostname (lets call it fs01). I'd rather do a fresh install of 2012 rather than in place upgrade. Lots of cruft on that 2003 box.... i.e. - Create new 2012 VM but don't join to domain - Kick everyone off on a Friday night - Remove 2003 machine from AD and shutdown - Rename 2012 machine to the new hostname (fs01). - Join 2012 VM to AD - Attach VHD from 2003 machine to 2012 machine as readonly (temporarily) - Copy files to new VHD on 2012 machine - Re-share all the folders viola....everything works on Monday? \\fs01\butts will work the same? Or is there some AD / kerberos stuff I'm not aware of and it will all blow up in my face when people can't get to their butts?
|
# ¿ Oct 3, 2013 08:54 |
|
|
# ¿ Apr 26, 2024 05:48 |
|
Agrikk posted:The way I've done file server migrations (P2V, P2P, V2V) without mucking with VHDs: Thanks! Share information and permissions are not particularly important, there's only two shares (which I can recreate). And permissions I can reapply manually if need be. I just wasn't sure how gracefully AD handles a new server with the same name as an old (albeit removed) server.
|
# ¿ Oct 4, 2013 00:14 |