| One of the best ways to deploy Microsoft Windows | | | | So if your still happy with that then here we go |
| operating systems automatically is via Remote | | | | First of all you will need: |
| Installation Services (RIS) / Windows Deployment | | | | - A licensed copy of Server 2003 (Standard or |
| Services (WDS) server over a LAN. We won't go | | | | Enterprise, Web Edition won't work) |
| into depth regarding of the setup of these services | | | | - A copy of XP Home or Pro |
| but will explain briefly what they do. If you need help | | | | - Virtual PC downloaded and installed |
| with a RIS /WDS server setup then please Contact | | | | - A decent amount of RAM on the laptop (2 GB+) |
| Us | | | | - Free HDD space on the laptop |
| With these methods the target machines boot from | | | | - A small 4 / 8 port switch or a crossover cable |
| a PXE network interface card (NIC), they are then | | | | Got all that? OK let's begin |
| offered a choice of operating system images to | | | | - Download and install Virtual PC |
| install from a RIS / WDS server. An authorised user | | | | - Create a virtual machine (VM) for Server 2003 with |
| choose the correct image, supplies the appropriate | | | | atleast 512 MB RAM. For VM creation / setup here |
| domain credentials and away you go. | | | | - Configure the machine with ATLEAST 2 virtual hard |
| Now traditionally these types of deployment setups | | | | disks |
| required dedicated equipment such as a server, | | | | - Install Server 2003 on the virtual machine |
| switches, cables etc etc. | | | | - Once installed configure the server as a Domain |
| We are going to show you how to do this with | | | | Controller (a .local domain is fine) (DC) via the Add |
| nothing more than a laptop, virtual machine software, | | | | Server Roles wizard or dcpromo from the command |
| a simple switch and network cables | | | | prompt |
| But first of all let us clarify what this setup will and | | | | - Make sure you have Active Directory (AD), DHCP |
| won't do. | | | | and DNS services setup |
| It Will: | | | | - From Add / Remove Windows components install |
| - Give you a portable deployment server | | | | Remote Install Services |
| - Save you the expense of a dedicated server | | | | - Run risetup and configure your image |
| - Allow you to turn up a clients premises and deploy | | | | - Once done, create an XP VM and configure the |
| operating systems with nothing more than a laptop, | | | | BIOS to boot from the PXE NIC - This will allow you |
| switch or cross over cable | | | | to test your setup for errors |
| - Allow you to install RIS or RIPREP images to target | | | | Tips for better performance: |
| machines | | | | - If you have router at home / office disable DHCP |
| - Be more than capable for small workgroups / | | | | on the router (atleast while the VM server is running) |
| domains | | | | - Set the VM server NIC with a static IP |
| - Customise deployments for each clients | | | | - Use your computers NIC for the VM and NOT local |
| It Won't: | | | | only |
| - Replace a full, dedicated server with server | | | | - For clients that do not have a PXE NIC, create |
| hardware | | | | Remote boot floppy disk |
| - Be as fault tolerant as a dedicated server however | | | | - Once you have successfully created a RIS /WDS |
| you can backup / duplicate your server to a USB / | | | | client. Install the intended applications then create a |
| external drive | | | | RIPREP image back to the server - This way you |
| - A PC or laptop NIC will not be as good as a server | | | | can then deploy full images to clients |
| NIC so you probably cannot deploy to hundreds of | | | | - Create different folders for different images |
| target machines in one go | | | | - By default RIS / WDS creates a ristndrd. |