6 Replies Latest reply on May 7, 2014 3:33 AM by pierce

    Epo 4.6 data doesn't match client info

    cg-windstream

      My Epo server (4.6) is reporting information that is old/incorrect for at least 1 of our windows servers. 

       

      On the EPo Console the reported information is:

      • VSE Patch V 2
      • DAT 7249
      • Last Communication: 11/5/13 12:46:00 AM

      The About page on the Client Server reads:

      • VSE Patch V 4
      • DAT 7428
      • Obviously very recent comm. as the DAT is from yesterday

       

      Yes it's the same server Name, IP, and even MAC.

       

      We are using 1 main EPo 4.6 Server and client Agents 4.6

      The client is able to telent to the EPo Server via ports 443 & 80.  The Epo Server is able to telnet to the client via 8081.

       

      I've tried the ping and wakeup agents buttons on the console with no change.

       

       

      Any Ideas, Theories?

      CG

        • 1. Re: Epo 4.6 data doesn't match client info
          mbauman8

          hi,

          Have a lock at  Technical Articles ID:  KB66797

          At least Port 443 must be bidirektional! If you use agenthandler also Port 80 must be open ...

          good day

          • 2. Re: Epo 4.6 data doesn't match client info
            Laszlo G

            cg-windstream escribió:

             

            My Epo server (4.6) is reporting information that is old/incorrect for at least 1 of our windows servers. 

             

            On the EPo Console the reported information is:

            • VSE Patch V 2
            • DAT 7249
            • Last Communication: 11/5/13 12:46:00 AM

            The About page on the Client Server reads:

            • VSE Patch V 4
            • DAT 7428
            • Obviously very recent comm. as the DAT is from yesterday

             

            Yes it's the same server Name, IP, and even MAC.

             

            We are using 1 main EPo 4.6 Server and client Agents 4.6

            The client is able to telent to the EPo Server via ports 443 & 80.  The Epo Server is able to telnet to the client via 8081.

             

            I've tried the ping and wakeup agents buttons on the console with no change.

             

             

            Any Ideas, Theories?

            CG

             

            Maybe your McAfee Agent is corrupted, you have a duplicated GUID on your ePO's database or the server has been duplicated under the system tree, have you seen if it's name appears more than once at ePO's system tree?

             

            The first thing you should try is to remove McAfee Agent on one of these servers with the frminst.exe /forceuninstall option and then install it again. After this check if it can communicate with ePO and if it appears at lost&found

            1 of 1 people found this helpful
            • 3. Re: Epo 4.6 data doesn't match client info
              pierce

              Was about to say, just blacklist the GUID via the menu in ePO, system will remove itself until it checks back in with new GUID.

              1 of 1 people found this helpful
              • 4. Re: Epo 4.6 data doesn't match client info
                akill

                try to make a forceuninstall of the MA and then reinstall it

                • 5. Re: Epo 4.6 data doesn't match client info
                  cg-windstream

                  Laszlo & Pierce apparently were on the correct track.  The least dangerous (to the client server) was Pierce's suggestion.  So I went that route and voila!

                  • 6. Re: Epo 4.6 data doesn't match client info
                    pierce

                    There are some tasks you can set to run around duplicate GUID's, I have my tasks run everyday.

                     

                    The first one looks for high sequence errors, if so it blacklists that GUID. The second task resets all those sequence errors.

                     

                    Helps keep things running as expected, especially if you have clones of machines going on (my biggest issue with this)

                    1 of 1 people found this helpful