Posted on 11-18-2013 10:22 PM
For a variety of reasons, I would like to move our installation from its current server, running 8.72, to a newer server running 9.21. I'm thinking of doing a staged migration, bringing groups of clients over gradually until everyone is off the old server. In the process, I hope to clear out some of the older stuff from the package database, policies, etc. and better organize the overall structure of things, as a lot of the landscape has changed since we first implemented our JSS a few years ago.
Just FYI, we're only tracking a few hundred Mac workstations, no mobile devices or Windows machines.
What I would like to do is to re-direct clients to use the newer server, with a new name & IP address. I'm not sure about keeping our old database, or simply enrolling everyone fresh - there may be a value to accessing some of the older records, but on the other hand it may be more difficult to re-configure the existing database to a new primary server. Several of our older machines are not active, and thus we don't really track them; also, they can always be added to the system if they are brought back into service. (It may very well be that they will just be retired in favor of new ones anyway.)
I'm wondering if any of you have gone through something like this, and if there are any tips or other considerations you might share?
Posted on 11-18-2013 10:39 PM
@chris.kemp, I'd create a QuickAdd on the new server & then deploy it from the old.
I've done this before & it works well.
Posted on 11-19-2013 06:21 PM
I second what Ben said but make sure you have a different name for the new server. I tried and it was rough.
Posted on 11-19-2013 11:37 PM
Yeah, that seems reasonable. :~)
Posted on 11-20-2013 05:46 AM
I did exactly the same thing when "upgrading" to v9. I worked well.