MSME - Windows Error 2045

[IMPJamie]

Another Tip:  Make sure you are using the FQDN in the MSME URL, otherwise you will likely get:

"The McAfee Security for Microsoft Exchange is not currently available. Please try again later."

If you only use the hostname as below, you will likely get a Certificate error (address mismatch):

Wrong

hxxps://<hostname>/MSME

Right

hxxps://<hostname>.mydomain.com/MSME

[norbertg]

I updated MSME this morning with the latest rollup. I stopped MSME service and copied back a config file from 2 weeks ago (newest only one I had available on tape) and started MSME. IMO the xml file was corrupt due to me adding in 2 email addresses manually to MSME and EPO trying to push down it's own config. Not sure if default config or MSME config that has vanished.

I don't want to reset the config file to default as I am not sure what EPO will push down to the client.

[norbertg]

I have no windows error 2045 for the last 3:30 hours, though I did receive 2 emails this morning:

Subject: VSEXCH01: McAfee Tranport Routing Agent registration failed. 

McAfee Tranport Routing Agent registration failed on '05/23/2013 05:47:31'.

1. McAfee Tranport Routing Agent registration failed.
2. Register the McAfee Tranport Routing Agent manually.
3. Please contact McAfee Technical Support.

Subject: VSEXCH01: McAfee Tranport Agent registration failed. 

McAfee Tranport Agent registration failed on '05/23/2013 05:47:41'.

1. McAfee Tranport Agent registration failed.
2. Register the McAfee Tranport Agent manually.
3. Please contact McAfee Technical Support.

[norbertg]

Had another look at the xml config file and looks it's set back to default.

Message was edited by: norbertg on 23/05/13 9:06:29 AM

[norbertg]

I've started recreating the policy on EPO, I have 2 settings that are different. See https://community.mcafee.com/message/289992#289992

[Aidan]

If you have an extension installed in ePO and not configured (defaults) - it is assigned at My Org level - then unless you specify at that level or at the Group or node level not to enforce - then machines will get default policy. Also if you create or upgrade policies from previous versions they must be assigned again at org, group or  node level. 

So if you import or replace a config locally and it gets writen over by default - it suggests that default is coming from ePO.

If you want to leave local config alone you could set "Not Enforcing" at specific level  - and this should not write over config.

Can you do a quick check in registry at  :- HKLM\Software\WOW6432Node\McAfee\MSME\Configuration

Under this can you confirm existence of a key key called "ExtraConfig"??

[Aidan]

...... oh and if you have installed the MSME 7.6 P1 RU2 locally make sure you have added the correct Extension to ePO from that package .... e.g the MSME___7600_<lang code>   (MSME___7600_0409 for English)

[norbertg]

Under the reg setting  have the following:

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\McAfee\MSME\Configuration]

"directory"="C:\\Program Files (x86)\\McAfee\\MSME\\config\\"

"location"="C:\\Program Files (x86)\\McAfee\\MSME\\config\\McAfeeConfig.xml"

"PersistenceMethod"=dword:00000001

"Schema"="McAfeeConfig.xsd"

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\McAfee\MSME\Configuration\ExtraConfig]

"1"="CSRules,cs_rules_en.xml"

---

I've updated the extension a few minutes ago. Thanks for that, forgot to do that.

It list 7.6.7960.102 as the extension installed.