Join domain vb scripts fail
After an upgrade of our K2000 about 6 months ago we noticed that our customized "join domain and OU.vbs" post-deployment task didn't work anymore. Now I've finally got my head above water to troubleshoot this but it's seems to go much deeper than just our vbs-script failing. As I tried the kace-bundled example: join domain and so on, I couldn't get any of them to work properly. I'm using domain admin account and now the most simple of the scripts, the "join domain.vbs", and it keeps throwing me a "The system cannot find the file specified".
I use parameter "join_domain.vbs our.domain administrator password
The second thing I've noticed is that these pre-upgrade was defined as "windows script" tasks. Now all of a sudden, they are changed to "application" type. Can anyone help me getting these native vb-scripts to work again?
Community Chosen Answer
The join domain script should be an application task. 3.6 is the first version that introduced the task type "Windows Scripts" Windows scripts accept .vbs, .wsh and java script files. However, through version 3.7SP1 this type of task does not accept parameters (which is why the join domain script is not a windows script task.
Lead T3 Enterprise Solutions Consultant, K2000