After updating to EEC 184.108.40.206 from 5.1.9 and creating a new install set scriptrunner doesn't seem to be kicking off autodomain.vbs and more.
I did more than just update EEC to 220.127.116.11 I also created new filegroups.
I am using 3 file groups now instead of just 1
1 for scriptrunner with ini file and script runner - scriptrunner.exe is set to "Post-Installation Helper Executable"
1 for sbadmcl and related dll's
1 for the actual autodomain script and the ini file for it
I changed how it setup because management decided they wanted to have the sbadmcl command on the clients but didn't want the autodomain.vbs and autodomain.ini file to stay after client installation.
Everything seems to be present on the client but the autodomain script doesn't run automatically any more.
You might want to update to a more recent version of AutoDomain, we (I) gave up on scriptrunner when even McAfee started flagging it as a possible virus.
The most likely issue though is that scriptrunner is running prior to the script being written?
Does it work if you run it manually post install?
I found the http://sites.google.com/site/ctogonewild/Home/intersting-files collection of files and updated my autodomain.vbs files and switched to autodomain.exe from scriptrunner.exe and it seems to have resolved the issues i'm having.
Ironically, I might have to "reinvent" scriptrunner to get around the fact that Primalscript won't let me package a VBS to run in 32bit mode on 64bit systems. Annoying.. :-(