Hello,

Thanks for this post.

The same things for remote database could be great

Hi,

The same process should work even if OME is installed with remote database as well. One thing to note would be instead of using [OMEService] account you will modify whatever account was used to install OME. 

The idea here is the change the password of the account used by OME to access the database. That way OME shows the DB retargeting screen.

The SQL command listed in the post above is for default install option. If you are using custom install, you will modify the command to look something like this.

sqlcmd -E -S " \ " -Q "ALTER LOGIN [ ] with PASSWORD='DummyPassword'"

Regards

Abhijit

This procedure broke my OpenManage Essentials installation :-(

The "DSM Essentials Host Service" works fine with the remote database, but the "DSM Essentials Network Monitor" and "DSM Essentials Task Manager" services just quits immediately when I try to start them.

The error persists even if I move the OMEssentials database back original (local) SQL server.

regards.

Jan Inge

Hi Jan,

Sorry to hear about the issue.

It is possible that Netmon and task manager will stop running during the retargeting.

If the retargeting cannot startup the services you may need to click the ‘restart services’ button.

When retargeting is complete it also removes the ODBC connection for Task Manager and Network Monitoring Service. This causes the services to rebuild their ODBC connection from the registry.

Can you try to restart the OME server and verify the both the services are running again?

Regards

Abhijit

One more thing you can try would be to delete ODBC manually which is used by the services. The services will re-create it when it runs the next time.

Run this application

C:\Windows\SysWOW64\odbcad32.exe

* This is not the same as the ODBC 64bit window.

  If you run the wrong one you will not see OMEssentials

Remove OMEssentials and ITAssist if it exists in the SystemDSN tab.

Additional diagnostics information is available at C:\Windows\Temp\OmeHostService.log

Thanks for the update Jan. Glad to hear it's working now. Indetically named ODBC does seem to cause an issue.

Regards

Abhijit

Thanks!

The problem was that I had a 64bit ODBC conntection called "OMEssentials", manually created for pushing Openmange status data to our in-house monitoring system.

When I retargeted the database, and restarted the services, they didn't manage to create the 32bit ODBC connection they needed, and just quit, I deleted the 64bit "OMEssentials" ODBC connection, restated the servies, and everything worked as intended. :-)

The reason it worked before retargeting the database, is that the identically created "in-house" 64bit ODBC connection was created manually after OM Essentials was installed.

The Dell code that re-creates the ODBC connection does not allow identical named 32 and 64 ODBC connections, but the 64bit ODBC GUI allows it.

Thanks for your help!

Regards

Jan Inge

I want to move my database away from SQL Express to a another server running SQL standard - following Peter's instructions. If for some reason you wanted to revert back to the local original SQL Express instance would you just type  "local" as the Server name, with user OMEservice, with password "DummyPassword" . Is that right ?

The password that "OMEservice" uses is generated on install.

To use the "OMEservice" SQL Login you would need to change the password for that SQL Login account in SQL Server.

The best way to do that is with SQL Server Management Studio (free with SQL Express)

After changing the password you can retarget OME to use Express with that login.

The server name would likely be .\SQLExpressOME

We install a named instance of SQL Express to avoid conflicts with other applications that may have installed SQL Server Express.

 Thx

Rob

Moved from Express SQL to a remote standard 2012 SQL Db using the notes. It worked perfectly. Thanks for you help.