migrate JSS address from old domain to new domain

[nelsonpark]

So when we setup our original Casper installation, due to our lack of wisdom and experience of ios management, we named the server a little oddly...
now that we have been using Casper for some time we realise the benefit of having a more meaningful name. I realise that changing the server name (management address) means that all devices have to be re-enrolled and we are recalling all our devices over christmas break for maintenance and thought we would fix it up at the same time.

We currently are running on a windows server, is it as easy as building up an additional virtual machine and installing the casper software. can i just restore a backup of the existing database, etc on the new machine and run both servers side by side?

if possible i would like to be able to run both servers (management URLs) side by side to migrate between the two. im sure that not every device will be returned and so will need to be able to maintain control of the left over devices until the complete migration.

im only running iOS devices, no macs...any suggestions would be great :D
Conor

[bmarks]

I just did this, but we're Mac-only. You'll want to start with a fresh database on the new server since you have to re-enroll everybody anyway. Changing the URL + SSL certificate on an existing database basically breaks everything. Having two servers running side by side won't cause any conflicts since each device is only pointing to one or the other URL and each device will have an MDM profile allowing it to receive APNS data from only one of the servers. I assume since you're considering this that it's not a huge amount of devices.

[nelsonpark]

thanks @bmarks yes only 150 or so devices. While its still a lot of devices, we are ensuring they are all correctly updated to iOS9 at the same time. due to some earlier inconsistencies this might require a complete wipe of the device anyway....what better time than now to also change over to a new MDM server
Conor

[bmarks]

One additional thing that I'll mention (which may or may not apply to your specific environment) would be to plan for your server to be in your DMZ even if you don't have those plans at this time. If your domain is www.example.com, then this won't be an issue. But, if you're like we were, and you have www.corp.example.com and www.internal.example.com (or something similar) you may still want to consider giving your JSS a hostname that's publicly addressable now. Our JSS was initially set up on x.internal.x.x and when we went to put our server into our DMZ years later, we had to change the URL/certificates/etc.

Again, this may not apply to all or even most environments, but I figured I'd mention it anyway. And, by utilizing a publicly addressable hostname now, this will make your migration to a potential cloud service easier too, if ever you were to decide to do that. This would also make it easier down the road to put multiple JSS's behind a load balancer.