Best Practices For Creating a VDI Windows XP Template in a VMware Virtual Center environment

Creating a well thought out and well tuned Windows XP Template is important for a successful VDI implementation.  My intent for this whitepaper is that it will guide you in developing a solid VDI Desktop standard for your organization.  Included in this whitepaper is information to assist in reducing your Windows XP footprint and to apply best practices to the Windows XP configuration for improved performance, manageability, and reliability of your VDI environment.  Since computer environments can vary from one organization to another, it is recommended that all best practices listed in this document be tested in your test VDI environment to ensure that it is helps and not hinder your VDI solution.

Download the whitepaper here: Creating a VDI Windows XP Template.

You can leave a response, or trackback from your own site.

Bookmark and Share

3 Responses to “Best Practices For Creating a VDI Windows XP Template in a VMware Virtual Center environment”

  1. Jordan Whitmarsh

    Hi,

    Some really great details on best practices for creating an XP VDI instance. I have a couple of questions however:

    Is the creation of a build use of nLite in an enterprise situation supported by Microsoft?
    Will we be seeing a similar guide for the creation of a Vista instance any time soon?

    Many thanks,

    Jordan

  2. Bill Gleeson

    thanks, really thoughtful stuff - you can see that it’s been based on practical experience. I am planning to redo my demo VDI environment and will as many of these tips as I can.

  3. Andrew Cooke

    In reply to this article.

    nLite cannot be used for commercial purposes! This rules it out for VDI deployments. In addition Microsoft themselves have tight guidelines on what they will support if you use an unsupported method other than sysprep.

    nLite is simply a tool for techies and should not really form part of anyone live running production setup for VDI or any other purpose.

    The best approach is to use the inbuilt SAN software to reduce the space requirements, or wait until VDM or Provision’s broker have the linked clone feature which is due out for both products next year we hope.

    —————————————————————————-

    LICENSE AGREEMENT:

    Your use of nLite is governed by the following conditions. Please read this information carefully before using nLite. By using it you are agreeing to the following conditions:

    1. nLite is freeware and can be freely used for any personal non-commercial purposes, subject to the following restrictions.

    2. nLite can only be distributed electronically through the official host http://www.nliteos.com.

    3. nLite is supplied “as-is”. The author assumes no liability for damages, direct or consequential, which may result from the use of nLite.

    4. Import Restrictions. International users also check any import restrictions that your government may impose. Reread eula.txt in your Windows\System32 folder.

    5. nLite is free for personal use only, you cannot use it for any company or business purposes at this time.

    6. MCDBNET2.dll is registered on me (the nLite author) with the royalty-free license and can be distributed only bundled with nLite.

    7. nLite is a copyrighted material of Dino Nuhagic aka nuhi. You may not decompile, disassemble or otherwise reverse engineer this product. You may not include the parts of nLite in your software without the author’s permission. You may not alter or modify nLite in any way or create a new installer for it.

    Copyright (C) 2004-2008, Dino Nuhagic (nuhi)

Post a comment: