This content has been marked as final. Show 9 replies
you have to run it silently as the EPO installer does not have desktop access.
aD will simply run on the next boot instead. Make sure you have the latest version of AD.exe, check the autodomain log file for the reason it didnt do anything.
I am using version 3.2 which I assume that this is the latest version?
Here is the autodomain log. Like I said the process of adding cached users are skipped. There are no errors noted on the log. I have two domain users and a local account that have a cached profile on the machine.
5:22:52 PM: Set my options from autodomain.ini
START! Version 3.2
5:22:57 PM: Please wait while I add everyone who has used your machine to the list of users who can login to SafeBoot.
I'm going to add them if they seem to be members of the following domain(s) NEODEV
This might take several minutes to complete so please be patient and please don't shut your machine down until I am finished. Once all the users are added, they will be able to login to SafeBoot with their normal SafeBoot userID and password.
5:22:57 PM: RandomAdminUser picked user name "admin" from 1 possible accounts for this script command
5:22:57 PM: Waiting 1 seconds before I start...
5:22:58 PM: I tested the SafeBoot API, it's working and the version is good (220.127.116.11)
5:22:58 PM: I'm going to use the group "Eng_Machines" if I have to create any machines.
5:22:58 PM: Found a good connection in the DB list for database "MEEDEV"
5:22:59 PM: SafeBoot Device Encryption is not installed
5:23:00 PM: Created a new machine entry in the database for "XPDEV3" in group "Eng_Machines"
5:23:00 PM: Using Machine Name:"XPDEV3" for future activity.
5:23:00 PM: Getting the current list of users for machine "XPDEV3"
5:23:01 PM: I will skip adding the following users for you because they are either already allocated, or on a blacklist your administrator
has set:|Administrator|,|LocalService|,|All Users|,|Default User|,|NetworkService|,|Guest|,|systemprofile|,|emanager|,|$autoboot$|,|Admin|
5:23:01 PM: Searching for AutoBoot users to remove..
5:23:01 PM: As you don't have SafeBoot installed, I'm not going to bother forcing a sync of your machine.
5:23:01 PM: Removing Registry entries so I never run again...
5:23:01 PM: Removing ScriptRunner entries so I never run again...
5:23:01 PM: You can close this window, or I'll close it for you in 10 seconds...
5:23:01 PM: DONE!
For some reason the section to query the registry and add the cached users are ignored in the script. I am guessing that this part has to be run interactively on the machine instead of silent like ePO demands?
I ran a silent install set separately without the ePO package and the cached users were processed successfully. This problem only occurs while it is packaged and ran under a client task by ePO.
I have never seen the autodomain script run again after first reboot automatically. Is there a setting in the script to make this happen? I thought that this could only be done manually and this will be unwanted administrative overhead to some organizations. I can see in some situations that after the initial install the user will be given back control to the machine after first reboot and work during encryption. The user may not have local administrative rights on the machine and will be not be able to execute the script. I guess it depends on the sys admin's mood to push this script through group policy.
Autodomain is awesome to use and so is ePO. I just wish both of them could play nice. Maybe they do and I am just missing something. sad
current version is 5.10 ;-)
I think you need to set the "processusers" var to current,cached but this version is soooo old I'm not sure if it even works ;-)
Current version 5.10? Ouch. Time for an upgrade. Where I can get my hands on this version?
I hate to say it, but the same place you got the 3.2 version wink
I am reporting good news! I have obtained AutoDomain 5.10 and it runs exactly as it should on the client devices with the ePO EEPC install package. I also am fond of the UseUPNIfPossible, SecurityGroup, and ConnectorName options. I suggest that this script be an option in the database as a standard File Group in the furture.
now you should get 5.14 and try the runonlogon option - it uses the Windows Active Installer technology to make the script run once per user when they logon, so, as new people use the machine (or existing old users), it will one-time capture their credentials and ensure they are correctly set up.
I had heard from someone that this script would be built into future builds? As in, it will be a default option available for use with future builds of MEE? Is this true?
I have used the older versions and newer versions and they are all very easy to use just wondering if this actually ever will be built into MEE.
some of the functionality is planned for future versions, but until that time we're using the API to do this. Though it may seem strange to use scripting to provide such essential functionality, that's what the API was designed for - whether we use the API internally to provide it, or provide a script which uses the API makes very little difference - the advantage of the script of course is that it can be easily customised to your own requirements.