Current situation: At this moment we are doing a project of centralizing several branch-offices to a off-site datacenter. One of the branch-offices is using Safeboot so there is a server with Safeboot 5.1 installed. This server will be discontinued when everything is migrated and the project is finished.
Safeboot is licensed to use the AD Connector but I'm not sure whether it is being used or not.
New situation: At the datacenter there will be installed a brand new Windows-domain in an unused IP-range, new hostnames and new hardware. Off course Safeboot needs to become available for the current users in the new network environment.
Question: My question is simple: What's the best practice to move/migrate the current Safeboot configuration "transparently", including all users, objects, licenses (and so on) to this new network environment without disturbing the end-users?
In this post I've read which (simplified) says that I need to copy the SBadmin-folder from the old server to the new server. This post says I need to modify SDMCFG.INI to point the existing SB-users to the new server. Is this an option for my situation?
RE: Moving Safeboot to another network environment
urgh. that's really bad.
the simple answer is you now need to touch every machine and teach it about the new DNS name of the SafeBoot server - if you'd use DNS names to start with you could have just picked up the directory, moved it to the new server and re-assigned the DNS name.
fixed IP's are always bad news.
Personally I'd pay for some professional services if you have more than a handful of active machines. The migration can be done, but doing it without loosing touch with any machines will be hard.