topic Re: EEPC 5.24 and Autodomain in Encryption EEM Managedhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268035#M12654
<HTML><HEAD></HEAD><BODY><P>If the machine already exists, and the users have been set up - there may be nothing more it needs to do?</P><P></P><P>Did you take a look at the logfile? That will show you all the decisions it's making.</P></BODY></HTML>Sun, 06 Jun 2010 16:55:18 GMTSafeBoot2010-06-06T16:55:18ZEEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268034#M12653
<HTML><HEAD></HEAD><BODY><P>We were using EEPC 5.17 and matching Autodomain with mixed success.&nbsp; Most of the issues were caused by latency on other sites and my failure to add a wait time.&nbsp; Well we have since moved to EEPC 5.24 because we were told that some of our sbfs issues were resolved one of the newer releases.&nbsp;&nbsp; I have been testing both 5.25 and 5.5 versions of autodomain but I can not seem to get it to do anything with machines that already exist.&nbsp; It will move the machine from one group to the templet group, but not delete, recycle or clearkey.&nbsp; I've pretty much copied many of the settings from the 5.17 autodomain.ini and that worked.&nbsp; If I remove the machine from the console, everything works fine.&nbsp;&nbsp; Anyone using autodomain with eepc 5.24?</P></BODY></HTML>Fri, 04 Jun 2010 17:50:51 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268034#M12653jvolltrauer2010-06-04T17:50:51ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268035#M12654
<HTML><HEAD></HEAD><BODY><P>If the machine already exists, and the users have been set up - there may be nothing more it needs to do?</P><P></P><P>Did you take a look at the logfile? That will show you all the decisions it's making.</P></BODY></HTML>Sun, 06 Jun 2010 16:55:18 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268035#M12654SafeBoot2010-06-06T16:55:18ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268036#M12655
<HTML><HEAD></HEAD><BODY><P>The log just says that the machine already exists and ends.&nbsp; The old machine never seems to make it in to recycling.&nbsp; If i delete the old machine manually, the initial sync happens as you would expect.</P></BODY></HTML>Mon, 07 Jun 2010 11:25:58 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268036#M12655jvolltrauer2010-06-07T11:25:58ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268037#M12656
<HTML><HEAD></HEAD><BODY><P>I'm confused as to what you are expecting to happen then? Can you post the log as an attachment and describe what behavior you are expecting? </P></BODY></HTML>Mon, 07 Jun 2010 13:07:48 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268037#M12656SafeBoot2010-06-07T13:07:48ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268038#M12657
<HTML><HEAD></HEAD><BODY><P><SPAN style="font-family: &amp;quot;Arial&amp;quot;, &amp;quot;sans-serif&amp;quot;; color: #333333; font-size: 10pt;">I'll throw in an example.&nbsp; Client brings his machine to site IT.&nbsp; It has EEPC installed on it.&nbsp; Drive has crashed or something else has happened that necessitates a reimage of the drive.</SPAN></P><P class="MsoNormal" style="margin: 0in 0in 10pt;"><SPAN style="font-family: Calibri; color: #000000; font-size: 12pt;"> </SPAN></P><P class="MsoNormal" style="margin: 0in 0in 10pt;"><SPAN style="color: #000000; font-size: 12pt; font-family: Calibri; ">The tech, throws an xp image on the machine and gives the machine the same name.<SPAN style="mso-spacerun: yes;">&nbsp; </SPAN>In the past, when autodomain.exe was executed, a detection was made that an older machine was in the DB.<SPAN style="mso-spacerun: yes;">&nbsp; </SPAN>The old machine was moved to the recycling bin and a new machine with new ID was created.<SPAN style="mso-spacerun: yes;">&nbsp;&nbsp; </SPAN></SPAN></P><P class="MsoNormal" style="margin: 0in 0in 10pt;"><SPAN style="color: #000000; font-size: 12pt; font-family: Calibri; ">Right now I either have to rename the&nbsp; existing machine or delete it manually.&nbsp; This log was created using autodomain 5.25 but the results seem to be the same with 5.5.&nbsp; I've included the 5.25 ini and the production 5.17 ini which works most of the time (latency issues with network).&nbsp; I've also noted in teh autodomainlog.txt file where I made a change in the console.</SPAN></P><P class="MsoNormal" style="margin: 0in 0in 10pt;"><SPAN style="font-family: Calibri; color: #000000; font-size: 12pt;">As always, thanks for the help.</SPAN></P></BODY></HTML>Mon, 07 Jun 2010 13:37:45 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268038#M12657jvolltrauer2010-06-07T13:37:45ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268039#M12658
<HTML><HEAD></HEAD><BODY><P>the log shows a number of activations, each time the machine name existed as a template - we need to see a log of the problem occuring <span class="lia-unicode-emoji" title=":winking_face:">😉</span></P><P></P><P>I can't see a run in that log where the script didnt do something? </P></BODY></HTML>Mon, 07 Jun 2010 13:45:00 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268039#M12658SafeBoot2010-06-07T13:45:00ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268040#M12659
<HTML><HEAD></HEAD><BODY><P>Ok.&nbsp; I'll rerun the test.&nbsp; Would you prefure I use 5.5 or 5.25?</P></BODY></HTML>Mon, 07 Jun 2010 13:46:55 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268040#M12659jvolltrauer2010-06-07T13:46:55ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268041#M12660
<HTML><HEAD></HEAD><BODY><P>not sure it matters - just need a log of a problem, and a description of what you think went wrong <span class="lia-unicode-emoji" title=":winking_face:">😉</span></P></BODY></HTML>Mon, 07 Jun 2010 14:03:18 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268041#M12660SafeBoot2010-06-07T14:03:18ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268042#M12661
<HTML><HEAD></HEAD><BODY><P>I think I figured it out.&nbsp; What I had been doing for testing is set the existing safeboot machine to Remove/Reboot and then I'd leave it in the console.&nbsp; This time, I exported the machine, set it to remove/reboot.&nbsp; I then deleted the machine from console and imported the machine before I removed eepc.&nbsp; I thought this would be a more realistic.</P><P></P><P>So the issue seemed to be that the machine could not be move to recycling if it was set to Remove/Reboot.&nbsp;&nbsp; The only problem I have to figure out now is that the $AUTOBOOT$ account was not removed.&nbsp; I think I can figure that out.&nbsp; Thanks for the help.</P></BODY></HTML>Mon, 07 Jun 2010 14:12:14 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268042#M12661jvolltrauer2010-06-07T14:12:14ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268043#M12662
<HTML><HEAD></HEAD><BODY><P>yes, if there's a machine in the db with a policy of remove, then whenever that machine tries to activate, it will get the policy and remove itself. It's doing what you told it to <span class="lia-unicode-emoji" title=":winking_face:">😉</span></P></BODY></HTML>Mon, 07 Jun 2010 14:13:43 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268043#M12662SafeBoot2010-06-07T14:13:43ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268044#M12663
<HTML><HEAD></HEAD><BODY><P>OP worked it out on their own - misconfiguration it seems. </P></BODY></HTML>Mon, 07 Jun 2010 14:14:07 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268044#M12663SafeBoot2010-06-07T14:14:07ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268045#M12664
<HTML><HEAD></HEAD><BODY><P>The odd thing is that it never removed or rebooted which is why it didn't dawn on me that that's where the issue lied.&nbsp; It just said the machine existed and did nothing until I deleted the old machine.</P></BODY></HTML>Mon, 07 Jun 2010 14:15:29 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268045#M12664jvolltrauer2010-06-07T14:15:29ZRe: EEPC 5.24 and Autodomainhttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268046#M12665
<HTML><HEAD></HEAD><BODY><P>It would have taken another reboot I expect - one boot to install everything, then the policy is applied on the 2nd. </P></BODY></HTML>Mon, 07 Jun 2010 19:12:04 GMThttps://community.mcafee.com/t5/Encryption-EEM-Managed/EEPC-5-24-and-Autodomain/m-p/268046#M12665SafeBoot2010-06-07T19:12:04Z