![]() ![]() The next few articles of the “Deploying Windows XP” series will explore some of the more common ways of dealing with both of these stages, starting with the initial one. ![]() On the other hand, implementing two remaining stages in this process, one immediately preceding the operating system installation and one that follows it, require extra creativity and can vary greatly from one environment to another. Fortunately, a significant part of the installation - dealing with core operating system and its main components - is well documented (DEPLOY.CAB file, included with the installation CD of every Windows version located in the SUPPORTTOOLS folder provides detailed information on deployment tools as well as “Guide to Unattended Setup” detailing Answer File parameters) and augmented by Microsoft (the same file contains the utilities Setup Manager and SYSPREP.EXE, which assist with the creation of answer files, creation of distribution share points, and cloning), which greatly simplifies its automation. ![]() The benefits gained from an install make the effort worthwhile and allow the admin to considerably limit time spent setting up new computers and ensuring each of them is configured to the same set of standards. While an upgrade is typically an easier option to implement, it does not provide the same flexibility as a new installation and typically leaves systems vulnerable to issues inherited from legacy software and configuration options. At some point, nearly every system administrator in a large computing environment will be faced with the challenge of automating the setup of a new operating system. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |