Deployment Artist


The site is finally put to rest...

You find new content on the Deployment Research site, a site filled with articles and video-tutorials on how to deploy operating systems. If you are missing something on the new site, please let me know. You can find me on twitter on my @jarwidmark alias.

You can also search the old article archive below.

Regards / Johan Arwidmark

 Blog_Archive Minimize

 A Pretty Good Frontend (IMHO) Minimize
Location: BlogsJohan Arwidmark    
Posted by: johan 8/25/2007

Summer 2007 in Sweden is one for the record books, for being the rainiest one in a long time... So if you can't hit the beach, what do you do?  Some serious coding of course! :)

So today I have released a Frontend for ZTI (BDD 2007) to the web...

Credits goes to Morgan Hjalmarsson, Sami Lehtonen, Martin Hultstrom and Kristoffer Lindblad for their efforts and continuous support...

Best Regards / Johan Arwidmark
Microsoft MVP - Setup & Deployment

The name: Pretty Good Frontend

Download link

- Only appears if computer is not in the BDD Database already
- Allows for entering a computer name
- Allows for Selecting target OU (Selection list is from live Actice Directory data)
- Allows for entering UDDIR folder (for replace scenarios)
- Allows for OSD/ZTI Image selection (Selection list is from live SMS data)
- Allows for role selection (Selection list is from live BDD database)
- Configured from rules in bootstrap.ini, no hardcoded values in the Frontend
- Started as a userexit (no scripts on the winpe image)

The screenshot

System Requirements
- A Windows PE 2005 image generated from the BDD 2007 Deployment Workbench
- Added support for ADSI (not terribly hard, just copy activeds.tlb and adsldp.dll from Windows Server 2003 SP1 to System32)

- From the download, copy the following files to ZTI$ Share: Z-Frontend.vbs and Z-Frontend.hta
- From the \distribution\scripts folder, copy the following files to ZTI$ Share: wizard.css and wizard.ico
- Using Deployment Workbench, update bootstrap.ini using info from the sample files and update the Deployment Point (Update files only)
- I'm assuming your are running the BDD database on the SMS SiteServer (SMS Database)

The following values need to be configured in bootstrap.ini (sample for single and multiple locations included)

SMSSiteDatabaseServer:  The Server name of the SMS SiteServer (database)
SMSSiteDatabaseName:  The SMS database name
DomainController1:  A domain controller to bind to
BDDDataBaseName:  The BDD dataabase name
StartingOU:   OU to list subOUs from (1 level only)
ListADUserName:  User to Bind with AD
ListADPassword:  Password for AD user

Note 1: Minimum Memory requirement is set to 256, you shouldn't deploy windows XP or higher versions with less, nor use WinPE 2005... :)

Note 2: If you have used Microsoft sample file (SERVERSP1-REMOVELIST.TXT) to reduce WinPE 2005 size, make sure you configure it to not delete the following



Note 3: As for usual I recommend configuring winbom.ini to always wipe the disk (otherwise leftover junk may prevent the setup)

Sample winbom.ini


Disk1 = Disk1.Config

WipeDisk = Yes
Size1 = *
PartitionType1 = Primary
FileSystem1 = NTFS
QuickFormat1 = Yes
SetActive1 = Yes


Permalink |  Trackback

Comments (3)  
Re: A Pretty Good Frontend (IMHO)    By kingskawn on 11/19/2008
Superb guide you made here. But what would you do when you receive a machine or several machines where the only thing you know about them are the MAC addresses?

How can you launch this? It's based on the computername and you can't put a mac address for deployment or am I missing something :-)

Re: A Pretty Good Frontend (IMHO)    By cortez00 on 4/16/2009
i think i asked this before.. will this work for MDT 2007 and SCCM. I thought you mentioned that you where working on it.

Re: A Pretty Good Frontend (IMHO)    By kingskawn on 4/22/2009
Is this compatible with SCCM? What do we have to change that is more for sms to a SCCM scenario?

 Search_Blog Minimize

Copyright 2006-2012 (c)   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2015 by DotNetNuke Corporation