AutoDomain 5.60…
NOTE – Production-ready version 5.63 (as far as I am aware) is now available on CTOGoneWild
This version is a real departure from the 5.2 and before series, as I got rid of the dependence on IE for the UI – it was becoming a real pain, with IE trying to display first run screens, telling me it was not installed etc. Generally the IE object was unreliable to say the least.
Instead, I used a whole bunch of HTAs – This is nicer architecturally as each stands alone and can be modified as you see fit, so you can change the UI without changing the logic of the script, plus they run independently so if they crash and burn, again, no problems for the script.
Other than that, there were some more changes to make the “Run On Logon” code asynchronous, so it does not stall the user experience when provisioning them. You can find a full list of changes at the top of the autodomain.vbs script.
Finally, if you enjoy this tool and it saves you a whole bunch of time and effort, you might want to send me something from my Amazon Gift List? Thanks!
You can read more about the current version on my previous blog on this topic.
Leave a Reply
Who?
 | EVP Cyber Product Innovation for Mastercard. Formally the Chief Technology Officer for Intel Secure Home Gateways, CTO for McAfee Enterprise Endpoint, CTO McAfee Innovation team, and Founder/CTO SafeBoot Corp. |
Comments
 | Christopher Burgess on How not to implement smarthome… |
 | Mike on Is Encryption enough? Why just… |
 | Simon Hunt on Is Encryption enough? Why just… |
| Mike on Is Encryption enough? Why just… |
 | Stéphane Pautrel on New S.M.A.R.T Monitor Tool for… |
Simon Says - Musings of a Technology CTO 
I would love to help with this project. Hit me up Anthony@amftech.net
We are currently using 5.50 in the Test Lab and are actively progressing to its use in production within the next 7 days. so far I’ve only found one issue with 5.50, however, have not yet isolated if it is an AutoDomain issue or a GPO issue.
Good luck Jason – there are a few companies using 5.50 in a major way, so you’re not alone – let us know how it works out!!!
Thanks Simon and we are one of the companies using version 5.506.
It is working great for machines with only EEPC installed.
We are also using Autodomain for our EEFF installation. When the EEFF installation is run on a machine with EEPC installed the EEPC version is called rather than the EEFF version. This also happens with ‘LogonBox.hta’.
Looking at the 5.53 code, a SkipDottedUserNames was added. what issue or feature does this address?
thanks
Bryan
the problem is because you are deploying as an exe, autodomain unpacks the script into the temp directory – the ini file is not there, so it goes looking for it – the code first looks in its directory, then the eepc directory etc (see the getparameters routine). You can fix it to a particular path by using the command line option /configfile:”filename” when you run the script.
So, either put the ini file in the same place you’re unpacking the script into, or the code will have to be changed to add the eeff path as an option for a place to go looking for the ini file.
re skipdottedusernames, one customer “liked” a bug in earler versions which meant user names with a dot in them were ignored – a user name of “simon.hunt” would be interpreted as a user “hunt” from the “simon” domain – I fixed this a while ago so it properly imported and created users with dotted names, but this customer was relying on this bug to ignore system accounts. This new option just means any user with a dot in their name won’t be processed.
Thanks
We will look into adding a parameter to the autodomain.exe used in the installation. Currently I do not see how to do this via the management console.
I am not sure if this will help regarding the wrong autodomainl.exe being called. We see the issue on Win7 x64. The EEFF autodomain.exe is called then the script exits and restarts in 32bit mode but from the EEPC folder rather than the EEFF folder.
re: skikpdottedusernames. Will need to test this latest version but we use UPN accounts which have ‘dots’.
Thanks Simon
Bryan
We are currently using Autodomain v5.25 in our EEPC v5.24 environment. I built a “new” EEPC 5.2.9 infrastructure (because it supports Win 7-64bit) and am trying to use the new Autodomain v5.60 with our current Autodomain.INI file and receive the following msg after an installation set is run on a device:
c:\Program Files\McAfee\Endpoint Encryption for PC\autodomain.vbs Line:9877 Char:22 Error:Type Mismatch:’cbool’ Code:800A000D Source: Microsoft VBScript runtime error.
Any idea why? Thanks.
most likely you have a configuration problem in your autodomain.ini file – you have something other than true or false for a boolean value. What do you have for your runonceonlogon value for example?
You were correct. There was a syntax error causing the problem. One last question about autodomain v 5.6. How do I prevent the LiveLog and autodomain progress window from appearing during the running of the install set? I need a totally silent installation and these windows never appeared in previous versions of autodoman (as far as I know). Thanks for your help. Mike
Mike, the best place for support is http://community.McAfee.com in the data encryption forum.
But the simple answer, is don’t deploy livelog or progressbox with the autodomain file set.