Daniel haddad
asked on
SCCM Primary site server configuration and content migration
Hi all,
I work in a place that is currently running SCCM 1610. This environment is made up of a primary site in the datacenter and 6x distribution points scattered in different states in Australia.
Current setup
PriSCCM01 (Virtualization server running on legacy HP G5 using local disks in front)
- Site code IC1
- Server 2012r2
- local sql 2012
- SUP/WSUS role
- Distribution Point
- Reporting Service Point
- Endpoint protection point
- Disk/Partition - Everything on C: drive (SAN Storage 1tb)
STATENAMEDP01 (x6)
- Distribution Point (WDS and PXE support)
- USMT Storage point
The problem is the primary site server is a shame. It is currently sitting on legacy hardware and just the configuration is unbelievable. Single partition on local disks with absolutely everything on it i.e Host OS , C:\SQL along with WSUS writing to C:\WSUS , the regular SCCM folders SCCMContentlib, smspkg , smspkgc , smspkgsig and smssig etc etc.
I would like to do a massive clean-up and re-configuration of this server however I do not really want to start from scratch with the sccm environment. I have seen many ways to move/migrate sccm to new hardware or VM however they are all focused on the backup and recovery method and all state that the current drives should be identical and to robocopy the data across. If I purely wanted to upgrade the os or virtualize this wouldn't be an issue however I want to fix up the drives and data.
Our company has invested in new infrastructure hardware and as part of the process of moving the legacy VM to the new hardware I would like to make some drastic changes.
Preferred setup
NewPriSCCM01 (Virtualised server running on newer HP G9 and new SAN hardware),
- Site code IC1 / IC2 (TBC)
- Local SQL 2016
- Distribution Point
- Reporting Service Point
- Endpoint protection point
- Disk/Partition
----- C: Host OS (SAN Storage)
----- D: SCCM Content ( SCCMContentlib, smspkg , smspkgc , smspkgsig etc) (SAN Storage)
----- E: SQL MDF location (SAN Storage)
----- F: SQL LDF Location (SAN Storage)
----- G: SQL TempDB location (SAN Storage)
NewPriWSUS01 (Offload SUP/WSUS role to standalone server)
So the questions i have is how do i get from where i am currently (In a crap situation) to the ideal config (my personal opinion)
1) Can I build a secondary site server and associate it my current site IC1. (I.e 2 site servers for the primary site) Migrate all data from my current primary site server to my new one and then decommission the original server retaining my current sccm config (i.e IC1 site), distribution points, content and clients?. This method is basically the way we did Small business server 2003/2008 migrations/upgrades etc)
2) Do i need to create a new SCCM site and import the legacy setup as a subsite (secondary site) within the new one and then migrate from the subsite into the main new parent site? And the reverse of this question is do i create a new SCCM site server as a subsite (secondary site) in the already production IC1 and then migrate across?
3) Can I build a new SCCM site server and in turn a new site (i.e IC2). Can I then migrate all my content, distribution points and config such as boundry groups and admin roles etc to the new site server? Once this has all been migrated across can I then configure the clients to look at the new site server and decommission the old.
3a – If this option is available do I need to build the new site server to SCCM 1610?
3b - Can I build it straight to 1702 instead and effectively complete a upgrade at the same time?.
Any help, advise or links to sites/documentation will be greatly appreciated.
Thanks in Advance,
I work in a place that is currently running SCCM 1610. This environment is made up of a primary site in the datacenter and 6x distribution points scattered in different states in Australia.
Current setup
PriSCCM01 (Virtualization server running on legacy HP G5 using local disks in front)
- Site code IC1
- Server 2012r2
- local sql 2012
- SUP/WSUS role
- Distribution Point
- Reporting Service Point
- Endpoint protection point
- Disk/Partition - Everything on C: drive (SAN Storage 1tb)
STATENAMEDP01 (x6)
- Distribution Point (WDS and PXE support)
- USMT Storage point
The problem is the primary site server is a shame. It is currently sitting on legacy hardware and just the configuration is unbelievable. Single partition on local disks with absolutely everything on it i.e Host OS , C:\SQL along with WSUS writing to C:\WSUS , the regular SCCM folders SCCMContentlib, smspkg , smspkgc , smspkgsig and smssig etc etc.
I would like to do a massive clean-up and re-configuration of this server however I do not really want to start from scratch with the sccm environment. I have seen many ways to move/migrate sccm to new hardware or VM however they are all focused on the backup and recovery method and all state that the current drives should be identical and to robocopy the data across. If I purely wanted to upgrade the os or virtualize this wouldn't be an issue however I want to fix up the drives and data.
Our company has invested in new infrastructure hardware and as part of the process of moving the legacy VM to the new hardware I would like to make some drastic changes.
Preferred setup
NewPriSCCM01 (Virtualised server running on newer HP G9 and new SAN hardware),
- Site code IC1 / IC2 (TBC)
- Local SQL 2016
- Distribution Point
- Reporting Service Point
- Endpoint protection point
- Disk/Partition
----- C: Host OS (SAN Storage)
----- D: SCCM Content ( SCCMContentlib, smspkg , smspkgc , smspkgsig etc) (SAN Storage)
----- E: SQL MDF location (SAN Storage)
----- F: SQL LDF Location (SAN Storage)
----- G: SQL TempDB location (SAN Storage)
NewPriWSUS01 (Offload SUP/WSUS role to standalone server)
So the questions i have is how do i get from where i am currently (In a crap situation) to the ideal config (my personal opinion)
1) Can I build a secondary site server and associate it my current site IC1. (I.e 2 site servers for the primary site) Migrate all data from my current primary site server to my new one and then decommission the original server retaining my current sccm config (i.e IC1 site), distribution points, content and clients?. This method is basically the way we did Small business server 2003/2008 migrations/upgrades etc)
2) Do i need to create a new SCCM site and import the legacy setup as a subsite (secondary site) within the new one and then migrate from the subsite into the main new parent site? And the reverse of this question is do i create a new SCCM site server as a subsite (secondary site) in the already production IC1 and then migrate across?
3) Can I build a new SCCM site server and in turn a new site (i.e IC2). Can I then migrate all my content, distribution points and config such as boundry groups and admin roles etc to the new site server? Once this has all been migrated across can I then configure the clients to look at the new site server and decommission the old.
3a – If this option is available do I need to build the new site server to SCCM 1610?
3b - Can I build it straight to 1702 instead and effectively complete a upgrade at the same time?.
Any help, advise or links to sites/documentation will be greatly appreciated.
Thanks in Advance,
ASKER
Hi David, Thank you for your comment. There is a million things that need to be if i want to try to maintain current server or clean it up. Things that come to mind are
1) Migrate current VM to new hardware
2) inplace upgrade from server 2012 to 2016
3) Upgrade upgrade current sql to 2016, or install sql 2016 on current server as well, move db and then remove sql 2014
4) move wsus content
5) Move all SCCM content from C: drive
6) Removal of all unneeded "tools" and applications that have been added to the server over the years
7) Reconfiguration of file/ntfs permissions (Current server effectively using domain admin for everything)
There is a whole bunch of issues i see with going down this path and trying to bring the current server back to glory
1) Although it is working right now, the server is old and has not been treated with the respect that it should have had from day one. There has been so many applications and tools installed and removed on this server over the years i expect hidden gremlins to show their faces as soon as i start doing installs and/or uninstalls
2) With all the separate components that need to be touched i foresee multiple outages and downtime for what is effectively a current production system.
3) With all the separate cogs in the machine that needs to be manipulated i also foresee a greater risk for things to go wrong
It is for these reasons that i am trying to run up a new server, with the latest OS / SQL and built to best practices. This will allow a clean start from the OS perspective, however it will also hopefully allow me to migrate the SCCM config and content gracefully without causing to much interruption to the current production environment. Hope that makes sence.
##### Note - Since my first post i have run up a new server and have already migrated the WSUS/SUP content and configuration across. This is one less headache i need to worry about in terms of the work however i would really like to clean up and organise this server before something happens in the future and it will mean starting from sratch
1) Migrate current VM to new hardware
2) inplace upgrade from server 2012 to 2016
3) Upgrade upgrade current sql to 2016, or install sql 2016 on current server as well, move db and then remove sql 2014
4) move wsus content
5) Move all SCCM content from C: drive
6) Removal of all unneeded "tools" and applications that have been added to the server over the years
7) Reconfiguration of file/ntfs permissions (Current server effectively using domain admin for everything)
There is a whole bunch of issues i see with going down this path and trying to bring the current server back to glory
1) Although it is working right now, the server is old and has not been treated with the respect that it should have had from day one. There has been so many applications and tools installed and removed on this server over the years i expect hidden gremlins to show their faces as soon as i start doing installs and/or uninstalls
2) With all the separate components that need to be touched i foresee multiple outages and downtime for what is effectively a current production system.
3) With all the separate cogs in the machine that needs to be manipulated i also foresee a greater risk for things to go wrong
It is for these reasons that i am trying to run up a new server, with the latest OS / SQL and built to best practices. This will allow a clean start from the OS perspective, however it will also hopefully allow me to migrate the SCCM config and content gracefully without causing to much interruption to the current production environment. Hope that makes sence.
##### Note - Since my first post i have run up a new server and have already migrated the WSUS/SUP content and configuration across. This is one less headache i need to worry about in terms of the work however i would really like to clean up and organise this server before something happens in the future and it will mean starting from sratch
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Move WSUS https://community.spiceworks.com/how_to/1679-wsus-moving-database-and-content-directory