Skip Navigation LinksHome > SSW Standards > Rules > SSW Rules to Better Windows 7 Deployments

There was an error displaying the testimonials. Please report this error to SSW and include the following text:
- A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

 

Do you agree with them all? Are we missing some? Let us know what you think.

 

Still stuck on old Windows Vista?

Please see Rules to better Windows Vista Deployment

At SSW we buy new computers as we need them – developers choose what they like e.g. Dell, HP, IBM or even the MacBook Pro with the dual boot that makes the designers happy!

Choice is good, however it does have its drawbacks; particularly when it comes to operating system deployments. In the past, each developer has had to build their environment each time they get a new PC or format from scratch because most deployment systems (such as Norton Ghost) are hardware specific. Depending on how much software a developer need to install, the time would range from a few hours to a couple of days.
With the latest set of administration tools deployed with Microsoft Windows 7 we finally have a nice solution to deploying our operating environments.

We choose to implement Microsoft’s new Business Desktop Deployment (BDD) solution and boy it deploys Windows 7 images quickly. The images include not just the OS, but all our standard applications.

As a result, unattended deployment time takes on average 45 mins. This includes the format! We were impressed and this *one feature* has saved us significant time and money.
We’ve learnt a lot in the process, and I’m sure you’ll find the new Rules to Better Windows 7 Deployment valuable. These rules aim to help you prepare your deployment of Microsoft Windows 7 across your small to medium sized organization.

Do you agree with them all? Are we missing some? Email me your tips, thoughts or arguments.  Let me know what you think.

  1. Do you ensure you have a computer with the recommended specifications before upgrading to Windows 7?

     Windows 7 is about 27% faster than Windows Vista. It is essential for PCs, which are being upgraded to Windows 7, to meet the minimum recommended specifications. You can install Windows 7 Upgrade Advisor Beta to check if your system is ready to install Windows 7.
    Windows 7 image developer
    Figure: Results from Windows 7 Upgrade Advisor Beta
  2. Do you know whether to upgrade or reformat?

    When you're installing a new OS on your PC it's always a dilemma as to whether to go the whole hog and reformat your hard drive or take the upgrade path into the new system. Upgrading is nice because there is no need to install all your programs again. The problem is all the old junk stays around.

    At SSW always go for a fresh start. We've already found a number of programs will not work in Windows 7. Besides, a nice, clean C: drive to go with your new, nice, clean operating system is always a big plus. Just be sure to follow your organization's backup standards carefully!

    Note: For individuals looking to upgrade to Windows Windows 7, the upgrade process is exactly the same as that for Windows Vista.

    Note: If you intend to follow an automated deployment then you will be forced to reformat.

  3. Do you know the best way to deploy Windows 7 across your organization?

    With Windows XP we commonly see situations where a system rebuild takes a day or more. With Windows 7 we have got that down to 45 minutes.

    Windows 7 has deployment tools which you can download, which make it significantly easier for organizations ranging from small to large sizes to migrate to Windows 7.

    Here are you deployment choices:

    1. Individuals - Standard Installation using Windows 7 CD (not recommended as you then need to install all your programs)
    2. Small Organizations (less than 100 computers) - Business Desktop Deployment 2007 (not recommended)
    3. Small Organizations (less than 100 computers) - Windows Automated Installation Kit (recommended) Recommended
    4. Large Organizations (100 computers or more) - Windows Deployment Services (WDS)

    At SSW, we use option 3, which means that you need the new deployment tool which utilizes Image Based Setups (IBS). When you use IBS you install all the programs you you create a large .WIM file. Once the custom image is created you deployed individually to each PC as detailed below:

    Note, for option 4, you use the same IBS method described for creation of your image. Windows Deployment Services is the equivalent of Remote Installation Services on Windows Server 2003. For this deployment process, a dedicated server is required.

    In order to use IBS you will need to:

    • Step 1: Create a CD with the tools needed to deploy the Image
    • Step 2: Creating a custom image of a Windows 7 Installation
    • Step 3: Get your new PC and Deploy this custom image

     

    Step 1: Create a CD with the tools needed to deploy the Image

    Windows 7 image developer
    Figure: This is for Windows 7 image developer to follow
            every time he creates a new version of Windows 7 image.

    PS: You may skip Step 1 because the CD labeled WIN PE and Image X is kept in n the SSW Sydney boardroom.

    Note: Use the CD labelled WIN PE and Image X x64 bit for building Windows 7 x64-bit image.

    1. Install Windows Automated Installation Kit
    2. Open Command Prompt and change from the current location to the PETools directory.
      Type CD C:\Program Files\Windows AIK\Tools\PETools
    3. Copy the PE Tools into a directory on your C: drive.
      Type Copype.cmd [arch] [destination]
      Where arch is the arhitecture of the computer on which Windows 7 is being deployed, either x86, amd64 or ia64 and destination is the path to the local directory, for example, type:
      Copype.cmd x86 C:\WinPE_x86
    4. Copy ImageX into the same folder.
      Type copy "C:\Program Files\Windows AIK\Tools\x86\imagex.exe" C:\WinPE_x86\iso
    5. Using Notepad, create a configuration file with the following text and save it as wimscript.ini.
      [Exclusion List]
      ntfs.log
      hiberfil.sys
      pagefile.sys
      "System Volume Information"
      RECYCLER
      Windows\CSC
      [CompressionExclusionList]
      *.mp3
      *.zip
      *.cab
      \WINDOWS\inf\*.pnf

      Save the configuration file to the same location as the ImageX:
      C:\WinPE_x86\iso

    6. Create an image file (.iso) of the folder you just created.
      Type cd C:\Program Files\Windows AIK\Tools\PETools
      Oscdimg -n -bc:\winpe_x86\etfsboot.com c:\winpe_x86\iso c:\winpe_x86\winpe_x86.iso
    7. Burn tthe image onto a blank CD ROM.

     

    Step 2: Creating a custom image of a Windows 7 Installation

    Warning: If you're using a VPC or VMWare then it is best to create a "Clone" before you generialize so that you can revert back to it after the image has been created. 

    Now that we have all the tools on a CD, we now need Windows 7 and all the programs.

      Attention: SSW Developers

      Please refer SSW's change log of Windows 7 Image for installed applications on Windows 7 image.

    1. Using a master computer, install Windows 7.
    2. Install all your applications.
    3.            Installed applications document on desktop
      Figure: Inside your image, make sure you keep track of all the installed applications (along with whom added them, and when). We keep a word document on the desktop.

    4. It will be much easier for user to know the version of the Windows 7 Image installed in their machines if you put the versioning information in a text file, for example: C:\_Windows7ImageVersion.txt.
    5. NOTE: When you build the image you need to update C:\_Windows7ImageVersion.txt.

                 Image Versioning
      Figure: Windows 7 Image Versioning File Image Versioning File
    6. Prepare the computer for imaging by running the Sysprep tools and cleaning up User settings.
      In Command Prompt, type C:\Windows\System32\Sysprep\Sysprep.exe /oobe /generalize /shutdown
    7.  
      • Caution: Do not forget to execute the above command before capturing the image. Not performing the above step may cause Boot Failure error message when you try to boot the installed image on your PC.
      • Note: You can only generalize your installation 3 times. After that you'll received an error when trying to generalize the installation.
    8. Boot up from the Windows PE CD that you created previously.
      Figure: This is what it looks like the first time you boot off the CD C it is the Windows Pre-Installation Environment 2.0 - now you capture the image
    9. In the command prompt, capture the image.
      Type D:\ImageX.exe /capture C: C:\MyImage.wim "My Windows 7 Install" /verify

      (Where MyImage.wim is the image name, you can give any name you wish).

    10. Option A (Not Recommended): Copy the image to a network location. (Note: This will not work in VMWare as the network drivers aren't supported without VMWare Tools, instead boot up the Windows 7 install and copy the image to the network drive from within Windows 7)
      Type: net use \\[network share]
      Where network_share is the location to which the Image will be saved on the network.
      Type your username and password
      Type copy C:\MyImage.wim \\[network_share]
    11. Now the image is on the network and all the guys can get their Windows 7 image from here

      Warning: It may take 8 to 10 hours to copy the file to network location. Instead try copying the file to any external drive.

    12. Option B (Recommended): Note: If you are building the image on a virtual machine, then

      • Once the .wim file is created successfully, shutdown the virtual machine > Take a snapshot > Restart the virtual machine.
      • Browse to C:\ and copy C:\MyImage.wim
      • If you experience any problem copying file to an external drive then copy the .wim file to \\<local computer>\Public\
      • If you are unable to connect to your local computer then, perform the following steps:
        • On your local computer and virtual machine Enable Public folder sharing option in Network Sharing Center.
        • Disable Windows Firewall.
      • Then try copying the .wim file to local computer.
      • Once the file is copied to local computer, copy the file to any external drive.
      • Now your image is ready to be applied from the external drive.

         

    Step 3: Get your new PC and deploy this custom image

    Windows 7 image User
    Figure: This is for Windows 7 image user to follow.
    1. On the PC, to which the Image is to be deployed, back up all your data.
    2. Boot up using the Windows PE CD you created previously.
    3. Format the hard drive and create partitions by typing these commands in order:
      diskpart
      select disk 0
      clean
      create partition primary size=<size of hard disk> (For example 'create partition primary size=20000' where 20000 equals 20 GB.
      select partition 1
      active
      format (format quick)
      exit
    4. Option A (Not Recommended): Copy the image from the network share onto the local hard drive.
      Type net use \\<network share>
      Type your username and password
      Type copy \\<network share> C:
      Warning: It may take 8 to 10 hours to copy the file to network location. Instead try copying the file to any external drive.

      Option B (Recommended): If you have followed the recommended steps to copy the .wim file to external hard drive, then type the following command to apply the image to your local hard drive:
      Apply the image to the C: drive.
      Type D:\ImageX.exe /apply X:\Myimage.wim 1 C:
      (Where X = External hard drive).

    5. Reboot once the above process is complete.
    6. Follow the on-screen instructions to complete the installation.
    7. Run Windows Update to get all necessary drivers and software updates.

    You are now ready to work ( it has taken about 45 mins)

  4. Do you run all your incompatible applications in a Virtual PC?

    When upgrading to Windows 7, you will find that many of your important applications may not install or give errors.
    To ensure a smooth migration process, your image will include a shortcut on the desktop to a Virtual PC so you can continue with all of these incompatible applications.

    Running incompatible applications in Virtual PC
    Figure: Run incompatible applications in Virtual PC

    Tip: VPCs are a bit slow, so you will want your VPC to be as fast as possible so please see Rules to Better Virtual PC's for an extensive guide to creating an efficient development environment.

  5. Do you use default gateway on remote network?

    VPN is a wonderful tool for users to remotely control the other PCs via network. If we control the PC located in Sydney and use default gateway on remote network, some of the bandwidth in Sydney will be occupied by us. In order to avoid that, we need to configure the VPN as following:

    Gateway
    Figure: Uncheck "Use default gateway on remote network".

    Furthermore, the Microsoft Firewall Client for ISA Server, which connects with the remote server, will be disabled as well.

    After that we can detect our settings by accessing http://www.dnsstuff.com/tools/aboutyou.ch. The result will show Your IP, Your country and Proxy Server etc.

  6. Do you make sure all non essential services are set to manual

    The windows 7 image will work fast, even on slow PCs. So only have a service running if people use it the majority of the time

    Service Set To Manual
    Figure: See the ‘Start Mode’ are all set to Manual.
  7. Do you use custom images for your Windows 7 background rotator?

    Having the same background is boring. Enliven your PC by having a rotating series of background images (using the Windows 7 background rotator). For example at SSW we include images of the guys having fun, SSW products and past SSW projects.

    Attention: SSW Developers

    SSW background images are stored at: SSW's background images

    Follow the instructions mentioned below to change your desktop background:
    1. Select the images for your background rotator
    2. Save them at %userprofile%\Pictures
    3. Click Control Panel | “Appearance and Personalization” | Under ‘personalization’ option | Click “Change Background Image”
    4. Browse to %userprofile%\Pictures (For e.g., C:\syeddilawer\pictures\SSWBackgroundImages) | click Ok.
    5. If all images are not selected, then click ‘Select All’ option to select the images.
    6. Under ‘Picture position’ option, select ‘Fill’ | Under ‘Change picture entry’ option, select any time limit you like.
    7. Click 'Save changes'

    Using images for Windows 7 background rotator
    Figure: See the ‘SSW background images’ are used for Windows 7 background rotator.

  8. Do you check out built-in samples for Reporting Services?

    Microsoft SQL Server 2005 and 2008 comes with great sample reports. However they are not installed by default, for more information please see Rules to SQL Reporting Services.

    Also see our knowledge base article: How do I install SQL Server 2005 with the Adventure Works Samples?

  9. Do you have a recommended file structure for storing data?

    Using a standard file a structure for storing user data on laptops makes locating important information fast and performing automated backup operations easy.
    Our developers always have:

                    D:\DataExchange  - For storing the MS Outlook .OST file. This folder is deliberately separate so it is not backed up. (the Exchange server itself is backed up regularly)

    D:\DataFirstnameLastname - For storing all user data. This folder is automatically backed up.

                \ProjectsTemp

                \ProjectsVSS

                \ProjectsTFS

                \Personal

    D:\temp
  10. Do you use the "Boot to VHD" feature of Windows 7?

    Windows 7 introduced a nice feature called "Boot to VHD". This feature allows you to natively boot into a VPC image. This has a couple of advantages:

    • Usage of Aero styles
    • Bare metal performance
    • 64 bit support
  11. Do you start from scratch when creating a "boot to VHD" image?

    When you consider to use the boot to VHD feature, try to install a new VPC image from scratch. All your hardware is direct accessed and not anymore virtualized when you boot into the VHD image, only the HD is virtualized.
    So it is better to start installing a new VPC image from scratch so that all your drivers are up to date and use the full power of your machine.
    See our rules Do you use an operational base when creating VPC images?

Acknowledgements

Syed Mehdi
Adam Cogan
Andy Taslim


Benefit from our knowledge and experience!

SSW is the industry leader in Custom Software Development, Software Auditing & Developer Training.

Call us on +61 2 9953 3000 or email us for a free consultation

What does it cost? I’m not in Australia. Can you still help?