I’m trying to work through our CMS migration from 8.1 RU7 to 8.5. We’ll be moving to new server(s) because our existing install is on 2008r2 servers.
Restoring the database and running NSUpgradeWizard theoretically seems to get us most of the way there (it seems to give us ability to move patches, tasks, and software items), but it seems like the deployment solution part of the suite is not migrated, is that correct?
I understand images need to be updated for the new version of the client (8.5), but typically we’d restore those images, let the client update, and then re-upload the updated image. It seems odd to me that TECH251847 doesn’t mention that images and copy file resources aren’t gathered by the migration wizard/database restore. I assume Deployment tasks and jobs come over but am not sure.
The ITMS Data Migration PDF has DS migration steps (page 30-36) for standalone migration.
If I’m understanding everything above correctly, since most of our machines are getting swapped over the next few months anyway, I’m now leaning towards not migrating anything and instead starting fresh with new win10 machines going to new NS with plan to shut down old NS after our rollout.
My only complication with that is for the few month overlap where we have old machines on one NS and new machines on new NS where we need ability to image on same VLAN. Support suggested we could leave NBS services stopped on the server least used until it’s needed and then swap back and forth stopping/starting services between the 2 services depending on if we’re imaging a new or old machine. I’m assuming there’s no better way to manage 2 iPXE installations on same VLANs?
thanks for any thoughts.