Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We are currently using PXE boots to automate the installations and reinstallations of our dedicated servers. This is working great for all Linux based systems like Debian, CentOS, VMware and Ubuntu in combination with kickstart/preseed.

However, for Windows, this seems to be impossible. You need to use WDS/MDT with Active Directory and I'm simply not looking forward to changing the entire deployment system for this.

So we're looking for alternatives to WDS/MDT which allows us to deploy customized Windows Server 2003/2008 servers in an automated fashion with settings like IP address/password/license key in a separate file so we don't have to create an image per server.

We have a Linux based deployment system which is completely incorporated into our backend/control panels etc. Hence I'm looking for a deployment solution that can run on Linux.

The guides I did find suggest booting WinPE using PXE and then using the EXE installers of Windows Server. Is this the suggested way to go or are there better ways to accomplish it?

share|improve this question
    
You're a little unclear about what you do/don't want to implement. D you have a problem with using MDT, or with AD? Or do you not want to use WDS to deploy the boot image? You should go back and make it very clear what technologies you do or do not want to use and why. –  MDMarra Feb 25 '12 at 17:19
    
We have a Linux based deployment system which is completely incorporated into our backend/control panels etc. Hence I'm looking for a deployment solution that can run on Linux. –  Wouter van Eekelen Feb 25 '12 at 18:14
add comment

2 Answers

up vote 8 down vote accepted

Overview

You can distribute a WinPE image using pxelinux or any other PXE boot technology. That will get you a scriptable command prompt able to launch an unattended install.

You can use WAIK to create an unattend.xml file that's called during setup where you can create your own build scripts that meet whatever it is that your needs are. The unattend file can call batch or powershell scripts as well as any other application during the post-install phase for customization.

I strongly doubt that there is any commercial product that will do this. If you want to have a Windows imaging environment integrated with a Linux one, you're going to have to hand-roll a lot of it yourself. The good thing is that the tools to do it (WAIK,DISM, WinPE, etc) are all freely available.


Design Basics

You'll want to create an SMB share with a copy of the Windows OS installation files that you want to deploy. You can modify these files (incorporate patches, Windows modules, etc,) with DISM.

Once you have that, you'll want to deploy WinPE through whatever PXE solution you use. You can edit startnet.cmd in WinPE to contain whatever custom commands that you want. This cmd file is executed when WinPE loads. This will allow you to automate the install. At a minimum, you will map the SMB share with the source files

net use \\server\share

and call

\\server\share\setup /unattend:\\server\share\unattend.xml

This will run setup in unattended mode, assuming you've configured your unattend file correctly. There are many examples of how to do this on technet.

In the OOBE phase of the unattend file, you can configure autologin and call whatever build scripts you need. Slmgr.vbs can change product keys and activate, you can call netsh to set IP info, and directly in the unattend.xml, you can specify the creation of local users and groups.

This gives you a completely customizable install environment that can PXE boot from any TFTP server. It's a lot of trial and error if you've never done it before, but it can absolutely be done.

share|improve this answer
    
Our current environment is hand made too, commercial products are absolutely not a requirement :) I'll look into your suggestions and will let you know if I run into any issues. –  Wouter van Eekelen Feb 25 '12 at 19:18
add comment

What I've done in this situation is build a master image that has a script set to run when the newly imaged machine boots first. The script is smart enough to grab a temporary IP via DHCP, then contact a provisioning server where it grabs another script to run. This second script does things like activating windows, configuring the network, etc.

The advantage here is there's no need to screw around trying to get automatic installations to work. We roll out the image via Clonezilla, and the image already has all our application software installed (which is pretty much impossible to do automatically).

share|improve this answer
    
I disagree that it's "pretty much impossible to to automatically". Software vendors provide unattended install switches for a reason and Microsoft itself recommends thin images vs what you're describing. When yo do it this way, you need to capture a whole new image every time a new piece of software comes out that you want to use. You should only do this if there is really no other way. That said, I use thin images to deploy every piece of software to 20+ labs, so that situation is a rare one indeed. –  MDMarra Feb 26 '12 at 11:30
    
Try installing Cygwin automatically ;) The installer makes it impossible. There are switches that are supposed to allow it to install automatically, but they just result in the install failing. –  devicenull Feb 26 '12 at 15:35
    
I would consider having Cygwin as part of your standard server builds as falling into the "rare" category :) –  MDMarra Feb 26 '12 at 16:00
    
Well, that's true. Though it is handy having one uniform way to get into any server (windows or linux). Also handy for automation (no domain here, can't use powershell remotely!) –  devicenull Feb 26 '12 at 23:43
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.