1 of 1 people found this helpful
if you are in a pinch, just copy the entire SBAdmin directory stuff over - no need to reinstall. If you run up the sbdbserver and start it as a service, it will reinstall all the registry keys.
Yes, once you rename the dns/ip, you should be good to go again - there's nothing in the registry other than connector schedules and window positions that you need to worry about.
Thanks for the advice, I'm going to take the fossil down gracefully next week and bring the new one up after restoring the up to date database, so fingers crossed
Due to OS restrictions and old hardware, I need to move the Safeboot 5.x-based server I'm responsible for as well. I'm also going to backup the sbdata folder and copy/restore it to the new server, the old server will then go down and the new server will be renamed to what the old server was.
What 2 .ini files were you referring to in the SBAdmin folder?
Is there anything else to be done outside of what you've described?
The steps, as I understand them, are this:
- Install admin console on new server
- stop SafeBoot services on original server
- Copy SBdata from original to new
- Copy .ini files from SBAdmin folder (which ones? All of them?)
- Bring down original server
- Rename DNS name/change IP address on new server to match original server (reboot required, right?)
- Start applicable services on new server
- Install Web recovery stuff
Is that correct?
Two other things:
1) when you say "SBAdmin folder" - what folder do you mean? My SBAdmin.exe file is in my Program Files\McAfee\Endpoint Encryption Manager folder
2) I'm going from a 32 bit Win2000 server to 64 bit Win2008 r2 - is that going to screw things up?