rikhavshah
New Member
- Messages
- 1
- Reaction score
- 0
- Points
- 1
I am required to migrate existing SCCM onto new server with new hardware and new SQL server.
Existing Setup :
1) SCCM 2012 recently upgraded to 1606 on Windows Server 2012 R2 (SMS Site code MIS) -
2) SQL Server 2012 on separate Windows Server 2012 R2.-
The new setup would be following :
1) SCCM Server 1606 on Server 2016 with site code (possibly use the same site code : MIS)- new host name and new ip
2) SQL Server 2016 on Server 2016 - new host name and new ip
In my lab I did new setup with SMS site code as PRI and run the migration wizard and did some migration of packages. What I found is the migration was successful but the package retained the old site code in the package ID ,i.e MIS00232 and not PRI00232.
I am planning to deploy new SCCM server in the lab and this time I plan to use same site code as on existing system i.e. MIS.
Please advise if this is possible and doing so wont cause any issue post migration ?
If not, and if I have to use new site code, is there a way to change the package Id post migration so that it matches the new site code ?
We would really like to retain and use the existing site code.
Thank You in advance.
Existing Setup :
1) SCCM 2012 recently upgraded to 1606 on Windows Server 2012 R2 (SMS Site code MIS) -
2) SQL Server 2012 on separate Windows Server 2012 R2.-
The new setup would be following :
1) SCCM Server 1606 on Server 2016 with site code (possibly use the same site code : MIS)- new host name and new ip
2) SQL Server 2016 on Server 2016 - new host name and new ip
In my lab I did new setup with SMS site code as PRI and run the migration wizard and did some migration of packages. What I found is the migration was successful but the package retained the old site code in the package ID ,i.e MIS00232 and not PRI00232.
I am planning to deploy new SCCM server in the lab and this time I plan to use same site code as on existing system i.e. MIS.
Please advise if this is possible and doing so wont cause any issue post migration ?
If not, and if I have to use new site code, is there a way to change the package Id post migration so that it matches the new site code ?
We would really like to retain and use the existing site code.
Thank You in advance.
Last edited: