asked on
Hi everyone -
Here's my question: I have a domain file server (called "NAS") that I have just virtualized into my new VMWare environment. I P2V'd the original physical server, disabled the NIC in it, then spun up the virtual copy. Everything is running fine for that new virtualized copy now.
The original physical box still has the same server name ("NAS") that it always did (it just has its NIC disabled, so it's not connected to the LAN). The new virtualized "NAS" 'reconnected' to the Active Directory computer object "NAS" just fine, so it is now NAS as far as A/D is concerned.
Now, I want to re-use the original physical server box for another task. I'd like to avoid having to strip it and rebuild the O/S, so it would be handy if I could just rename it.
However, wouldn't that also rename the active directory computer object "NAS" that is now associated with the new virtual server "NAS", and consequently screw up that machine?
A friend of mine said I should be able to just rename and re-IP the physical box, but it's my belief that that will corrupt/rename the A/D object attached to the virtual NAS. Is he correct in his ascertion maybe because the physical machine's NIC is disabled and it cannot talk to A/D?
Thoughts?
Here's my question: I have a domain file server (called "NAS") that I have just virtualized into my new VMWare environment. I P2V'd the original physical server, disabled the NIC in it, then spun up the virtual copy. Everything is running fine for that new virtualized copy now.
The original physical box still has the same server name ("NAS") that it always did (it just has its NIC disabled, so it's not connected to the LAN). The new virtualized "NAS" 'reconnected' to the Active Directory computer object "NAS" just fine, so it is now NAS as far as A/D is concerned.
Now, I want to re-use the original physical server box for another task. I'd like to avoid having to strip it and rebuild the O/S, so it would be handy if I could just rename it.
However, wouldn't that also rename the active directory computer object "NAS" that is now associated with the new virtual server "NAS", and consequently screw up that machine?
A friend of mine said I should be able to just rename and re-IP the physical box, but it's my belief that that will corrupt/rename the A/D object attached to the virtual NAS. Is he correct in his ascertion maybe because the physical machine's NIC is disabled and it cannot talk to A/D?
Thoughts?
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 2 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.