This content has been marked as final. Show 10 replies
moving machines between databases is not really supported - it can be done but it's expensive in terms of time and effort, and also very risky. You can't move users between systems at all - that's simply impossible due to the crypto. If you want to do this you need to buy a few days of professional services to work it all out.
If your databases are related (if you started off with a fragment architecture), then of course moving is entirely possible.
WOW. We did one yesterday. We moved one test machine from the PROD environment to the test environment. I just didn't get to see how it was done by the guy who did it.
chances are it will blow up pretty soon. It would only work if the two db's were almost identical - ie in their out-of-box guise.
certainly he would not have been able to move the users, or files etc with the machine.
The DB's are identical. All settings, etc.
This is for testing purposes only. I am surprised that you would recommend professional services for a test environment. I have destroyed that server four times and reloaded without a problem. I just need one more machine that has 4.2.15 client on it so I can watch it upgrade the client to EEM.
What I am getting is error 5c020004 Authentication signature is not valid.
If someone could explain to me what that means that would be awesome!
it means the server keys of the currently running server, and the server keys built into the install package, are not the same.
when you moved the machine between databases, how did you point it at the new database server?
Using the SDMCFG.ini file. I am re-building the server right now and imaging the machine back to the original state. Once done, I will install 4.2.15 and make identical to our prod environment. Once that is done, I will create an installation set for 4.2 and install it on the test machine. After that, I will upgrade to 5500 and create one group called "no upgrade" and another group called upgrade. I will have both machines ready.
There is method to my madness. What I want to do to deploy the clients is to have several machine subgroups and only do one at a time.
I hope to God this goes well. sad
this seems like a really crazy long-way round to me. I'd have said you should update the current server to the last version of 4 (for the database update), then install 5.1.x on the new server and over-write the database folder with the one from the old server.
Then i'd leave my exiting group with 4.x client files, and select a few machines to move to the new group. If the server on the original is set up using IP rather than DNS, then i'd replace the SDMCFG.ini file with one created on a new client from the new server, so the 4 machines can sync. If it's set up by DNS, then it's a simple case of publishing the appropriate forward record...
if you did it your way, chances our machines would never sync properly again - machines sync based on version number, so the copy of the database you made would have earlier entries than the DB you are moving from, thus the machines would think there was nothing to do.