6 Replies Latest reply on Aug 8, 2010 11:28 PM by obelicks

    Duplicate Machine Entry

    rbdudani

      We have EEM 5.2.2

       

      I want to know if we can disable the duplicate entry creation on console.

       

      If there is an entry of a any machine in EEM console, the system should give an error while installation.

       

      Current is when we install EEPC on machine with same hostname (two diffrent host with same hostname) which is alreay exist on server it creates MACHINAME0001 entry. instead of creating duplicate entry it should not allow.

       

      is it possible ?

        • 1. Re: Duplicate Machine Entry

          No. Rename/delete original machine object prior to client reinstallation.

          Or, rename afterwards.

          1 of 1 people found this helpful
          • 2. Re: Duplicate Machine Entry
            rbdudani

            Hi,

             

            Can McAfee Help in this if a big client want this feature ?

            • 3. Re: Duplicate Machine Entry

              And how do you propose this to work? A lot of EEM functions is based on machine name, so it must be unique.

              Ask Microsoft to allow duplicate netbios names in domain, or machines with duplicate IP's to work properly.

              • 4. Re: Duplicate Machine Entry
                rbdudani

                not in that manner, (EEM functions work on machine ID)

                 

                If one machine ID is already there in EEM than EEPC client should now be allowed on the same machine name.

                 

                Eg: it may give message at client side like machine ID already exist

                 

                 

                Message was edited by: Ram Dudani on 7/20/10 7:13:26 AM CDT
                • 5. Re: Duplicate Machine Entry

                  rbdudani wrote:

                   

                  not in that manner, (EEM functions work on machine ID)

                   

                  If one machine ID is already there in EEM than EEPC client should now be allowed on the same machine name.

                   

                  Eg: it may give message at client side like machine ID already exist

                   

                   

                  Message was edited by: Ram Dudani on 7/20/10 7:13:26 AM CDT


                  I'm afraid you are wrong. While object ID is used in some operations, most of functionality is based on object names.

                  The same as in MS. You have names and GUIDs. Both needs to be unique.

                  • 6. Re: Duplicate Machine Entry

                    I understand the issue.. since we having same isue like this..

                     

                    We still looking a way to clean and maintain our database efectively..

                    It's troublesome for us to keep and maintain our database, we having sites all over the world and when Site IT installed MEE, we're not notified the deletion and creation of this..so existing machine will keep duplicated.. old and new one. Is there a way we can set in Mee manager to notify us the new installation? or new entry database created in MEE manager?

                     

                    basically, when MEE installed on machine which having same hostname it will create new unique ID in database and name profile same as it's hostname prio installation.. However if it's already exist it's then will create another and append 000N at the end of profile name.. N - 1 until 9999 is number append at the end of name profile.

                     

                    This is what we foundfrom MEE manager & reporting tools on the database.. prio to version 5.2.4

                     

                    We also having issue when user renamed the hostname the profile is not changed based on hostname, - i think this because maybe a machines can have more than 1 hostnames.. like alias..to check this we need to look on "network name" Instead of "machine name" Worse the GUI from manager can't show "network name'" but only "Machine Name" => profile name this only be view from properties just imagined if we have 1000 recored we manually view this one by one   so we're depends on search tools and reporting tools right now.

                     

                    We try to look on dissable/enable status.. but there 2 place that we found on the report..1)Boot protection = enable/dissable 2) Current Status = enable/dissable

                     

                    We think to clean out data base on last syn date.. but  other buggy that we found from report of our database.. "last sync" somehow is not accurate because some machine sucessfully syn with MEE Manager but no last sync date is recorded...

                     

                    There still more issue that we're not clear enough on this actualy.. beside working closely with Site It.. there is no way we can 100% identify unused profile from MEE manager/database.

                     

                     

                    Message was edited by: obelicks on 8/9/10 12:28:54 PM MYT