2003 server
2003 server - Thursday, February 28, 2008 3:01 - 0 Comments
Sysprep and networking components
How to properly deploy servers with pre-configured networking components
Sysprep can be used to prepare Windows servers for image-based deployment, and IT shops who are planning on deploying servers to branch offices often use Sysprep and disk imaging tools for this purpose. Someone asked me once whether they could also pre-configure a server with networking components like DNS and DHCP services and then sysprep the server for deploying to multiple locations.
The answer is no, you can’t do it that way. Why? Because Sysprep resets your network settings, so you’ll lose any customizations you’ve configured.
What’s the alternative? Script the following post-deployment tasks for the branch office servers you plan to deploy:
Use Sysocmgr.exe to automatically install networking components like DHCP and DNS (see http://support.microsoft.com/kb/222444).
Then use netsh.exe to configure networking settings for these services (see http://support.microsoft.com/kb/242468)
Article written by MyComputerAid.com
- Maximum number of services
- Maximum size for Event logs
- Increasing Free Disk Space on the System Partition
- Simplifying Quota Management with Quota Templates
- Missing Computers in the WSUS Console
- Uninstalling WSUS
- Technical Overview of Windows Server 2003 Active Directory
- Introduction to Windows Server 2003 Active Directory in Application Mode
- Enabling Caching of Universal Groups

