Enterprise Console Upgrade from 3.x to 4.5 accross domains

Hello Mark,

it is not required that the old and new server are in the same domain.

If I understand you correctly you're about to make three changes:

1. Replace SEC 3.1 with SEC 4.5
2. Use a different server (probably with another OS version)
3. Move the server (and eventually the clients) to a new domain

For this to work the clients have to be able to resolve the new server's name correctly and to connect to it. If you also want to use Protect computers you need an account which has sufficient rights on both server and clients. Of course the details depend on the steps you intend to take. If you want to discuss these please post them here.

Christian

Thanks Christian,

1. You are correct. SEC 3.1 to SEC 4.5 (via 4.0 as per the guides)

2. Its likley to be going from Server 2003 x32 to 2008 R2 (x64) so i will need to completed the additional steps as per KB Article 52383

So if i am understanding this correctly my only concern will be DNS accross the domains between the clients and the SEC server?  (with all the domain trusts/account permissions in place already)

oh and one last question :)

Would you recomend upgrading the old 3.1 server to 4.5 and then doing the migration, rather than trying to do the lot all at once?

Mark

I'll leave in a few minutes and don't have a quick answer and tomorrow's a holiday  - so if you can wait ...

Christian

So you do want to keep the database contents. Of course you'd have to change those settings where they refer to you management server.

I don't know what you have in mind when saying trying to do the lot all at once as at one point you'd have to "change servers". As you can't install 3.1 on the 2008R2 it is not simple (didn't say impossible) to do it all at once.

You also have to "replace" EM Library with SUM and adjust the policies accordingly. I'd try to "start" with only SUM and "new" policies on the new server, i.e. perform as many steps as possible on the old one. Be prepared that you need more than "some space" depending on the number of subscriptions.

If you don't care about the clients'  "historical data" and have only a few groups and policies you could also simply set up SEC4.5 on the new server and skip the SEC migration. You'd just create the required groups and policies, then change the updating policies on the old server to use the new CIDs and wait for the clients to switch over.

Christian

"If you don't care about the clients'  "historical data" and have only a few groups and policies you could also simply set up SEC4.5 on the new server and skip the SEC migration. You'd just create the required groups and policies, then change the updating policies on the old server to use the new CIDs and wait for the clients to switch over."

Would like to obtain more information on this process. Looking to move our facility from SECv3.1.0.246 to SECv4.5. No migration needed @ this time. Server side seems straight forward... install SEC4.5 on a new 2003 server. What is the most effective means to reconfigure my workstations so they listen to, and are managed from, the new SEC4.5 server.

Thanks

Hello,

just set up the new server to use the same certificates as the old one (see for example here). Then on the new server copy mrinit.conf from the SAVSCFXP folder to the \rms subfolder and run configcid.exe. Change the updating policies on the old server to point to the CIDs on the new one. Clients will update to 9.5 and also reconfigure RMS to talk to the new server and appear in its Unassigned group. Note this currently works only for Windows clients, not Macs.

Christian

ah ha,  right makes sense now. 

Im going to update to 4.5 on the old server and get it all configured,  then at  a later date migrate SEC to the new server on the new domain.

Assuming i update the SQL instance on the server to SQL Server 2005/2008 express during the upgrade, is it then possible to migrate it to a full blown SQL 2008 instance on a completley seperate server at a later date? (On a different domain, but the SEC 4.5 will also be migrated to a server on the same domain)

Thanks again for the help.

Neither the version (as long as it is one of the supported) nor the location of the database really "matter" as long as you can backup the DB on the one and restore it on the other.  So you can move from one local instance to another, or move it to a dedicated server, or from a server to a local instance.

Christian 

Im going to update to 4.5 on the old server and get it all configured,  then at  a later date migrate SEC to the new server on the new domain.

Good point, thanks for mentioning this. Main reason we are migrating to a new server is because we cannot update the existing SEC, OS will not support it. Based on the results of trolling the forums here, I understand you cannot have two SEC's.

Is it a safe bet that I must move the SEC on the new server and perform any management of the old 3.x server from SEC 4.5?

I understand you cannot have two SEC's.

Depends on what you want them to do. Of course you can't have both to sync with AD and automatically protect the clients but otherwise they can live "side by side". If you are moving to a 2008 R2 the problem is that versions before SEC4.5 are not supported on it. Is this your situation?

Christian