Upgrading SCSM and SCO to 2016 - anything to be aware of?
Leigh_Kilday
Member Ninja IT Monkey ✭✭✭✭
Are there any dependencies on upgrading SCSM and SCO? Is there an ideal sequence, and why?
0
Best Answers
-
Adrian_Paech
Customer Advanced IT Monkey ✭✭✭
We have done both.
No issues I can think of on the top of my head.
I would probably recommend upgrading your database to SQL 2016 if you can, as SQL 2016 seems to give improved performance (in conjunction with the enhancements of SCSM 2016.).
5 -
Adam_Dzyacky
Product Owner Contributor Monkey ✭✭✭✭✭
I've been following this page for updates - https://technet.microsoft.com/en-us/system-center-docs/get-started/upgrade-to-system-center-2016
A similar write-up existed for 2012, to 2012 SP1, and then to 2012 R2.5 -
Tom_Hendricks
Customer Super IT Monkey ✭✭✭✭✭
I am just chiming in to support @Adrian_Paech's and @Adam_Dzyacky's comments.
We have also done both (and the rest of the stack), and have also upgraded to SQL 2016 (latest). I have done the SQL 2016 upgrade before SCORCH and SCSM, and I have done it shortly after. The result was basically the same (note that our DB's are still in 2012 compat mode for the moment--you can always move up, but not back).
Also, I cannot stress enough that you need to follow the technet article that Adam cited. It's the "supported" way of performing the upgrade, and it does a good job of explaining the pre-reqs and the order for the whole System Center stack.
5
Answers
We have done both.
No issues I can think of on the top of my head.
I would probably recommend upgrading your database to SQL 2016 if you can, as SQL 2016 seems to give improved performance (in conjunction with the enhancements of SCSM 2016.).
A similar write-up existed for 2012, to 2012 SP1, and then to 2012 R2.
We have also done both (and the rest of the stack), and have also upgraded to SQL 2016 (latest). I have done the SQL 2016 upgrade before SCORCH and SCSM, and I have done it shortly after. The result was basically the same (note that our DB's are still in 2012 compat mode for the moment--you can always move up, but not back).
Also, I cannot stress enough that you need to follow the technet article that Adam cited. It's the "supported" way of performing the upgrade, and it does a good job of explaining the pre-reqs and the order for the whole System Center stack.
I prefer migrating without doing any in-place upgrade.
I'm planning to spin up new servers for all, but, I'm not sure if I'm able to restore backup from SQL 2012 on SQL 2016, maybe clean it up like this really old guide from MS and install 2016 SM MS.
I have no idea if that will work, any ideas or suggestions?
Not sure why I didn't see this earlier. Microsoft now supports SCSM 2016 with SCO 2012.