Auto-assign computername in OSD Deployment with VB Script

[Bever87]

Hi everyone,

 

I am trying to deploy windows 7 computers in our company environment and they should get dynamic names.

This is how it should work:

 

- We have an Active Directory OU assigned to deployed workstations. I have 2 dummy computers in here just to test the setup, it looks like this atm.

 

 

- Next I have a script which reads the ou and generates the new computername

 

 

- I created a package with the script and distributed it to the DP

 

- Then i created a new task in the task sequence who performed a command line:

 

 

- when i am deploying I get the following error message:

 

 

 

Is there anyone that knows if this is possible to do, to start with. If my script is having errors in it, or what I am doing wrong?

 

Kind regards,

 

Thomas

 

[Bever87]

I made it work, he is loading in my script in the task sequence, but i'm getting the next error:

 

[Bever87]

*Bump*

[anyweb]

ActiveX component can't create object: ADODB.Connection

 

 

have you added any connection capability in your boot wim ? you need to add the optional component (Winpe-mdac) ?

[Ocelaris]

Why go through the custom VBScript route? There is a good method built into MDT for naming machines and adding it to an OU structure. Create a customsettings.ini package from MDT, and use this naming convention. I imagine there is a walk through, we have had this in our environment for a long time and it works quite well.

 

 

[Iroqouiz]

I would go with the MDT route as well. Mikael Nyström has made several blog posts/videos about this. Seems easy enough. Using MDT also enables you to test deployments without actually imaging computers.

 

http://deploymentbunny.com/2011/04/27/quick-and-dirty-testing-customsettings-ini-variables-in-mdt/