hai....

where can I see the new version status ? - The "about" says 1.2.0.3441 and it seems there is no essentialsversion.exe anymore...

Thanx & regards,

Stephan.

Ah....after a reboot it is ok....

(or would it be enough to restart the services...?)

I have the same issue that the version number is not changed after an upgrade. Seen in the documentation that you can have installation issues if you install with an domain admin account, so I have tested with local admin as well. Have also restarted the server but the version remains 1.2.0.3441.... I am out of suggestions and I hope someone can give me a hint on this issue. 

We have seen another even more serious issue: we installed the patch on another OME installation with the database running on a separate server.

The initial OME 1.2.0 installation used the local db, then it was moved to the remote db, following this guide:

http://en.community.dell.com/techcenter/systems-management/f/4494/t/19440364.aspx

Afterwards the local MS SQL Express server was disabled (but not uninstalled).

Now we installed the OME 1.2.1 patch - but now we have problems, it was not possible to run discoveries anymore and in the logs we found messages that no connection to the network monitoring service can be established (although running).

Thanks for the information Szychelm,

We will verify this in our lab and update the FAQ with this information as needed.

Regards

Abhijit

It seems that the patch installation changes the reg keys in 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Dell Computer Corporation\Dell OpenManage Essentials\Database\Master

and in 

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Dell Computer Corporation\Dell OpenManage Essentials\Database\UserDefined

back to a local SQL Instance with a trusted connection, no SQL authentication...

I stopped the services of OME and changed the Keys to reflect the situation before the patch installation.

When I restarted the services and tried to connect to the OME console I was asked to provide the database server, db name and access credentials. After I entered them the reg key were rewritten and now everything works as before...

Thanks for your replay Abhijit,

The version od the DLL file is 1.2.1.0 so I guess that file is updated. But when I click on the about link in the Essentials web page it still says 1.2.0.3441. Maybe it is only a bug in the About page?

Yes, it is version 1.2.1.

Hi TXE,

Assuming you have used default installation path, can you verify the version of the following DLL?

C:\Program Files (x86)\SysMgt\Essentials\bin\Dell.OpenManage.Essentials.OOBPatch.dll

 That will tell if the patch has been applied to the system.

Regards

Abhijit

Thanks TXE. The version of the DLL is updated which means the patch is installed and it might just be the about box related issue.

Regards

Abhijit

Thanks SZYCHELM for confirming this.

Regards

Abhijit

I can confirm that the patch installation is changing the reg-keys - I have tested it on a second OME installation with a remote DB.

This OME installation has not had a local SQL when it was installed the first time!

Changing the key HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Dell Computer Corporation\Dell OpenManage Essentials\Database\UserDefined\SQL_AUTHENTICATION from "1" to "0" and restarting the services led to the input dialog where the database connection needs to be defined in IE - after entering the remote DB server Name and the credentials needed to connect everything seems to work normal... 

I updated to the newest patch, and I am still having systems that are updated showing up as non compliant.  A lot of them are ESXi boxes running 5.1, but a few are physical windows boxes as well.  Is anyone else having this issue?

Hi,

The systems which are showing up as non-compliant, do they show the same version as installed and available updates or do those show different versions?

Regards

Abhijit

They show the same or they show 0, this issue really started happening when we went to 1.2, before this version OME was spectacular, now it is more of a headache sadly.