Jump to content


Sign in to follow this  
jonrowe81

Moving Main SCCM Server from VMWare to Hyper-V : Convert or Rebuild?

Recommended Posts

Everyone,

 

I have an SCCM Server that is currently running in VMware, but we're moving all our environment over to Hyper-V. We have moved everything over by using the Microsoft Virtual Machine Converter Tool, and so far have had 0 issues. It scares me to mess with my SCCM server, but we're going to have to get it over to Hyper-V one way or another.

 

My question to you all, do we convert and move or back-up and rebuild?

 

My environment is very basic. Single site, and one server (the one being moved) that houses all roles (site server/database/reporting/management point/etc). This is a school district, and we have 4 remote campuses throughout our town, and we have distribution points setup. That's the extent of our SCCM Infrastructure.

 

I have a feeling the best route would be to back-up and rebuild the server from scratch. If that's the case, can someone point me in the right direction for best practices for that process?

 

I'm open to any suggestion(s) for this.

 

I appreciate any and all input, thank you!

Share this post


Link to post
Share on other sites


Hello fellow school master of tech... I got nothing.

IMO, SCCM has gotten to the point that it's easier to just backup and rebuild than it is to worry about some "P2V" converter screwing something up, at least for smaller setups like the one I maintain. But then again, if you have the capability of converting to a test machine, checking with the SCCM Toolkit to verify everything was transferred correctly, it's worth a shot.

Please note, what follows is what worked for me, not necessarily best practice or recommended, but this worked for the most part so I'm sticking with it.

If you do decide to do the backup and nuke, what I did recently was go through the Assets & Compliance and Software Library workspaces and exported anything that I valued (collections, Compliance Settings, Applications, Packages, Driver Packages, Task Sequences). SCCM will export anything it needs for them to the location you specified, you can skip exporting the content assuming you will rebuild the server with the same shares.

Once everything is exported, build the new SCCM server w/ any required fixings.

Once the new SCCM server is up and running, migrate the files from the old server to the new and setup the necessary shares. Go through the workspaces and import the exported items. When it comes to the Collections, SCCM tends to derp and has no error checking on if it is using a user collection in a device collection and will cause a bad day, if you run into this, check what I did to fix it https://www.windows-noob.com/forums/topic/14002-imported-device-collection-using-user-collection-as-limit/#entry53677.

 

This is in no way a bullet proof method, there are some things that I am still cleaning up like some imported packages are not being distributed correctly, but re-making the packages manually fixes that.

 

Hope this helps, if you need more help, let me know, us school admins need to stick together!

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
Sign in to follow this  

×
×
  • Create New...