confirguring an internal certificate to our Virtual enviornment.

Configuring a Certificate for Virtual Machine Connection in Hyper-V or thru SCVMM internally.  to migrate host away from one of the Hyper-V machines and then perform the actions above. Once he has successfully validated it then he can perform the changes on each HV host in the same manner.
A change request needs to be raised but the impact is minimal as the HV cluster is designed for such live maintenance. He put the HV host in maintenance mode before performing the blog.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

btanExec ConsultantCommented:
For the configuring of the Hyper-V host, this article can be useful. In short, either self-signed or installed CA issued certificate that you have. By default no cert found, the self-signed is generated by the host. The article shared how to deploy a certificate issued by a CA use a server. in short to do this, you would need to follow these steps:
1. Disable the automatic generation of self-signed certificates on the Hyper-V host.
2. Delete the existing self-signed certificates.
3. Request a new server authentication certificate for your Hyper-V host from your enterprise CA.
4. Install and configure this new certificate on your Hyper-V host.

This forum has also discussed steps in exporting the host
Hyper-V has a Feature buildin to Export the VM with its configuration. So the right steps would be:
1. Shutdown the VM on the current physical Server
2. Export the VM to an external drive
3. Copy to the new physical Server
4. Import the VM in Hyper-V on the new Server
5. Boot the VM on the new Server
6. After testing the VM on the new Server delete the VM on the old Server

“Virtual Domain Controller Considerations”, which it mentioned “Do not clone, export, copy or use a VHD file to seed a new virtual domain controller. This will create problems in USN and possibly lead to a damaged AD database.”

....just done an sbs2011 with 2nd dc, RDS server and a few other from xenserver to hyper-v migration. I used disk2vhd physical to virtual conversion in the end and cloned the DC's. You could use this tool to clone your 2nd DC first THEN clone/migrate the SBS LAST. Then leave your live domain alone running.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.