This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Enterprise console v3.0 migration issue (cac.pem missing)

Hi folks,

I just migrated my sophos enterprise console v3.0.2321 from old server to a new server(both are win2k OS) and preparing to upgrade it to newest version sophos(v4.5).

However, after I complete the migration, I found that the setup script cannot use again at client side. it will display “cac.pem” is missing in my CID path. I confirm that file is contain at the CID folder and previously is fine at old server. I also tried to remove the CID path and recreate the same CID but failure.

Now I need to manually click setup.exe and input the user name for updating. At the enterprise console, I don't know it is managed or not. :smileysurprised:

This is my script file under the CID path: “setup -mng yes updp \\rsmsophs\InterChk\SAVSCFXP -user SophosEndpointUpdate -pwd rsmnwit -ouser SophosEndpointUpdate -opwd rsmnwit -mngcfg \\rsmsophos\InterChk\SAVSCXP”

following is my migration steps:

- (old server) backup all necessary file.

- (old server) disconnect from network

- (new server) Join same domain and change the same machine name

- (new server) install same version sophos (v3.0.2321)

- (new server) import registry key “certification manager”

- (new server) import em library “emlexp import” command

- (new server) copy old server sql database “SOPHOS3_log.LDF、SOPHOS3.mdf “

- (new server) copy “sophos3” file to c:\program files\sophos\enterprise console\DB

- (new server) use “restoredb sophos3” at DB location

- (new server) change user name "SophosEndpointUpdate" password match my script.

- (new server) reboot

Did my steps have problem? any idea? Thanks

hangie

This thread was automatically locked due to age.

0 jak over 14 years ago

HI,

The first thing I note is the command line: You have obfuscated user and password (ouser and opwd) set as well as plain text user and pwd and they have the same strings which can't be right.

You have to choose either to supply an obfuscated pair or plain text pair. If you wish to use an obfuscated username and password which I'd recommend, you need to use the command line tool obfuscationutil.exe or as I do, deploy to one machine using SEC and copy the deployment string from a windows task scheduler, as the job file is created as this creates the obfuscated version.

Please see the following articles on obfuscationutil and setup.exe:

http://www.sophos.com/support/knowledgebase/article/13094.html

http://www.sophos.com/support/knowledgebase/article/12570.html

Setup.exe is configured by default to copy cac.pem and mrinit.conf to the "remote management system" directory in Programfiles on the machine from the distribution point so the RMS msi picks it up at install. The article on setup.exe shows this:

-mngcfg <RMS config path> <location of Setup.exe> Location of the RMS configuration files.

So you shouldn't need to specify this argument.

I notice that you installed v3 on the new server before importing the certificates, you need to import the cert reg file backup to the new machine first so when you install, the installer spots the key and doesn't create new certificates.

Also, you can only use backupdb/restoredb to export an import SQL backup files, not copies of the mdf and ldf. I would recommend using backupdb to create a backup file before importing it again with restoredb. I wouldn't recommend stopping the SQL server service and moving the mdf and ldf to another server and replacing the files into another SQL instance.

I would suggest going over this with Support it should save you some time.

Thanks,

Jak

:5292
Cancel
Vote Up 0 Vote Down

Cancel