4 Replies Latest reply on May 27, 2011 7:05 AM by TechSecurityNate

    EEM Migration - Broken AutoDomain

      Hi,

       

      We've recently migrated our EEM database between servers and have noticed that while EEM appears to be working fine as it connects to current clients, it seems to have caused problems with the custom AutoDomain script that we are running when deploying to new machines. Our AutoDomain script is configured to add the machine name and local users to the EEM database as it installs, however at the moment this part of the process is failing, generating this error message:

       

      25/05/2011 11:42:27 AM: New connection

      25/05/2011 11:42:27 AM: 0x5c020004 | Authentication signature is not valid

      25/05/2011 11:42:27 AM: Connection issue (0x5c020004/Authentication signature is not valid) on attempt 1, waiting 3388ms and retrying...

      25/05/2011 11:42:31 AM: New connection

      25/05/2011 11:42:31 AM: 0x5c020004 | Authentication signature is not valid

      25/05/2011 11:42:31 AM: Connection issue (0x5c020004/Authentication signature is not valid) on attempt 2, waiting 2690ms and retrying...

      25/05/2011 11:42:34 AM: New connection

      25/05/2011 11:42:34 AM: 0x5c020004 | Authentication signature is not valid

      25/05/2011 11:42:34 AM: Connection issue (0x5c020004/Authentication signature is not valid) on attempt 3, waiting 2636ms and retrying...

      25/05/2011 11:42:36 AM: New connection

      25/05/2011 11:42:36 AM: 0x5c020004 | Authentication signature is not valid

      25/05/2011 11:42:36 AM: Connection issue (0x5c020004/Authentication signature is not valid) on attempt 4, waiting 3997ms and retrying...

      25/05/2011 11:42:40 AM: New connection

      25/05/2011 11:42:40 AM: 0x5c020004 | Authentication signature is not valid

      25/05/2011 11:42:40 AM: Connection issue (0x5c020004/Authentication signature is not valid) on attempt 5, waiting 4067ms and retrying...

      25/05/2011 11:42:44 AM: New connection

      25/05/2011 11:42:44 AM: 0x5c020004 | Authentication signature is not valid

      25/05/2011 11:42:44 AM: Stopping as I can't login to the admin system!

      25/05/2011 11:42:44 AM: 0x5c020004 | Authentication signature is not valid

      25/05/2011 11:42:44 AM: Running Cleanup...

      25/05/2011 11:42:44 AM: No Connection to close

       

      We've checked the SDMCFG.ini file on both the server and client and have confirmed that the database entry for the new server is correct (correct name and serverkey for both). Also the autodomain.ini file contains a valid defaultadminuser and a one-way hash of the password associated with it (created with the sbadmcl utility). It is interesting that the SbClientlog does not contain any error messages about invalid authentication signatures which leads me to believe that it's not the EEPC client having problems but rather the autodomain tool. Unfortunately I haven't been able to fund out what the setting is that may be causing the problem. Also we tried turning off the new server and then turning the old one back on, which resulted in AutoDomain working again.

       

      Is anyone able to shed light on what we may be doing wrong?

      Thanks

        • 1. Re: EEM Migration - Broken AutoDomain

          Maybe you have two copies of the client installed on your machines, one running autodomain, and one running the client? Autodomain is using the sdmcfg.ini in the dir that the API is regustered to, usually the same as EEPC, but if EEPC is working and autodomain is not, then you must have two copies of sdmcfg.ini at least, or have more than one server in it, of which the first one is bad.

           

          Autodomain does not rotate through servers like EEPC does, it just uses the first one in the list, or the one indicated as last used by the client if that feature is supported by the client - you can see higher up in the log the details of the connection it picked to use.

          • 2. Re: EEM Migration - Broken AutoDomain

            Hi Safeboot,

             

            I've checked and we definitely do not have a second copy of the client installed anywhere. We are trying to deploy a brand new EEPC install set with AutoDomain on a freshly imaged machine just to confirm that there are no file remenants anywhere.

             

            Also I took your advice and removed all other database entries from the SDMCFG.ini file. The machine is connecting to the correct server and is synchronising correctly, but again the AutoDomain tool fails with the same error message. Do you know of any other reasons why the client cannot authenticate to the server?

             

            Thanks

            • 3. Re: EEM Migration - Broken AutoDomain

              No other ideas unfortunately. It uses the same files as the client, so you either hav a bad server entry in sdmcfg.ini, or more than one sdmcfg.ini

              • 4. Re: EEM Migration - Broken AutoDomain
                TechSecurityNate

                https://community.mcafee.com/message/5735

                 

                Similar issue, same error message, maybe helpful.