When I push autodomain script to client, it gives an error [e0130006] Error opening file. Can anybody please help? I can see in the status window, it's getting all the 5 files, then starting to do update "SbAdmcom.dll", then this error comes
7/7/2009 10:40:04 PM Transferring local audit information to database 7/7/2009 10:40:04 PM Checking for file updates 7/7/2009 10:40:05 PM Downloading update for file "SBAdmCom.dll" 7/7/2009 10:40:06 PM Downloading update for file "SBAdmDll.dll" 7/7/2009 10:40:06 PM Downloading update for file "AutoDomain.exe" 7/7/2009 10:40:07 PM Downloading update for file "AutoDomain.ini" 7/7/2009 10:40:07 PM Downloading update for file "Install_AutoDomain.srg" 7/7/2009 10:40:21 PM Updating file "SBAdmCom.dll" 7/7/2009 10:40:22 PM Error [e0130006]: Error opening file 7/7/2009 10:40:22 PM Applying configuration 7/7/2009 10:40:22 PM Synchronization complete
I assume that you are pushing out the AutoDomain script out after the initial client installation/ encryption and not during initial client installation. The file SBAdmCom.dll probably exists on your machine's MEE root installation folder and causing this error. You can either :
1. Remove the file SBAdmCom.dll from you machine MEE installation folder and synchronize. The AutoDomain File Group will download and install the file.
2. Leave the existing file there in the root installation folder, remove the file SBAdmCom.dll from your AutoDomain File Group, and synchronize.
Now the behavior I am seeing is that the AutoDomain executable will have to run manually after this syncronization. Depending on your AutoDomain.ini settings you can have the script run each time a user logs into Windows.
But only one thing I am not sure about is this "You need to supply an admin user and auth either in AutoDomain.ini, on the command line, or hard coded into this script ". This I am getting in the Autodomain log. I created a special a/c scriptadmin and that I created in both MEE user group and domain user group (gave admin privileges too). So why it's saying so? Any idea?
Also I can't see it's adding my cached local users in the machine to the MEE user list. Should I change something in the autodomain ini file to make it happen?
Yes, I just followed those instructions. When I tried configuring the ini file -> The first user name and pw it asked I supplied my MEE admin username/pw, second thing it asked me to create script user -> assigned a name/pw. Also created that scriptuser in my local system and assigned admin privileges....still I got the error
I checked the ini file. I can see my username for scriptuser and the passauth in the file. So what else it's asking for...?? Any idea
I configured AutoDomain before importing the files but I get the same results and error message that amiyabisoi did. After downloading the File Group from a synchronization it runs successfully if you manually run autodomain.exe from the EEPC root folder afterwards. I went another direction, I placed all five autodomain files in the EEPC root folder manually on the client and it was successful after clicking autodomain.exe. To eliminate the need to remove the SbAdmCom.dll file as suggested from my previous post I went to the AutoDomain File Group changed the SbAdmCom.dll File Type to Windows DLL . This seemed to work well without error when synchronizing the AutoDomain File Group on the existing MEE client.
Here is the synchronization log file: 7/13/2009 10:59:28 AM Starting synchronization 7/13/2009 10:59:28 AM SbFs total space = 33437696 bytes (31.89 MB) 7/13/2009 10:59:28 AM SbFs free space = 28581888 bytes (27.26 MB) 7/13/2009 10:59:28 AM Connecting to database: "MEEPS2" 7/13/2009 10:59:28 AM Address=192.168.88.148 7/13/2009 10:59:28 AM Port=5555 7/13/2009 10:59:28 AM Authenticate=Yes 7/13/2009 10:59:30 AM Checking for machine configuration updates 7/13/2009 10:59:30 AM Updating machine configuration 7/13/2009 10:59:30 AM Checking for user updates 7/13/2009 10:59:30 AM Checking for token data updates 7/13/2009 10:59:30 AM Checking for SSO updates 7/13/2009 10:59:30 AM Checking for Local Recovery updates 7/13/2009 10:59:30 AM Checking for hashes updates 7/13/2009 10:59:30 AM Transferring local audit information to database 7/13/2009 10:59:30 AM Checking for file updates 7/13/2009 10:59:31 AM Downloading update for file "SBAdmCom.dll" 7/13/2009 10:59:31 AM Downloading update for file "SBAdmDll.dll" 7/13/2009 10:59:32 AM Downloading update for file "AutoDomain.exe 7/13/2009 10:59:32 AM Downloading update for file "AutoDomain.ini" 7/13/2009 10:59:33 AM Downloading update for file "Install_AutoDomain.srg" 7/13/2009 11:00:12 AM Updating file "SBAdmCom.dll" 7/13/2009 11:00:13 AM Updating file "SBAdmDll.dll" 7/13/2009 11:00:13 AM Updating file "AutoDomain.exe"
Here is where autodomain.exe is started and it appears the two files below are not updated during the autodomain.exe process.
7/13/2009 11:00:39 AM Updating file "AutoDomain.ini" 7/13/2009 11:00:40 AM Updating file "Install_AutoDomain.srg" 7/13/2009 11:00:41 AM Synchronization complete 7/13/2009 11:00:42 AM Applying cryption changes
So…..AutoDomain.ini is not updated and the AutoDomain.exe cannot find the correct parameters for the script.
The solution I found is to delete the AutoDomain.ini file from the original AutoDomain File Group and create a separate File Group with the AutoDomain.ini file. I first assign the AutoDomain.ini File Group to the existing MEE client and synchronize. After the autodomain.ini file is in the EEPC root folder I now assign the original AutoDomain File Group to the existing MEE client and synchronize. Once the autodomain.exe is started automatically it will find the AutoDomain.ini file and successfully run the first time and without the Auth errors.
This method could be avoided if the API would let us choose the order that the files synchronize and update to the client. It would be great if AutoDomain.exe would update last on the client machine. If you wanted to avoid all this administrative overhead on the MEE Database I guess you could use SMS, Altiris, or something like that.
So, did it work for you? I mean importing of users etc. so it run without any admin auth errors, right? I know you have already given step by step process above, but do u mind just write it in few steps what you did again