+ Post New Thread
Results 1 to 10 of 10
Windows 7 Thread, Windows 7 Deployment in Technical; Has anyone got an Idiots guide for packaging and deploying Windows 7? I've got it sysprepped, but I dont know ...
  1. #1

    Join Date
    Jun 2007
    Location
    Rochdale
    Posts
    233
    Thank Post
    26
    Thanked 35 Times in 30 Posts
    Rep Power
    20

    Windows 7 Deployment

    Has anyone got an Idiots guide for packaging and deploying Windows 7? I've got it sysprepped, but I dont know what to do with regards an answer file to auto join the domain etc. I've tried the windows 7 AIK but the documentation with it is very confusing.

    Any help much appreciated

  2. #2

    Join Date
    Nov 2008
    Location
    Belfast
    Posts
    28
    Thank Post
    0
    Thanked 4 Times in 4 Posts
    Rep Power
    12
    its really the same process as vista so any any site with a guide to deploying vista will be 99% of the way to 7

  3. #3

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,205
    Thank Post
    876
    Thanked 2,729 Times in 2,308 Posts
    Blog Entries
    11
    Rep Power
    782
    This is probably the easiest free way:
    Deploying Windows 7 - Part 1: Windows AIK 2.0 Enhancements
    Using MDT 2010 Beta 2. It is still in beta but seems to work ok and you are probably still a little while away from a full scale deploy anyhow.

  4. #4

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,714
    Thank Post
    866
    Thanked 664 Times in 437 Posts
    Rep Power
    501
    I've found that Windows 7 Has stripped out the Graphics Drivers after sysprep even though they were the ones used during initial Installation!
    Real pain in the danglies as now we have to go to each Pc and ensure the driver downloads via WSUS and then run WSAT to get Aero back and the resolution back up to 1280x1024

  5. #5

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,205
    Thank Post
    876
    Thanked 2,729 Times in 2,308 Posts
    Blog Entries
    11
    Rep Power
    782
    Quote Originally Posted by Gatt View Post
    I've found that Windows 7 Has stripped out the Graphics Drivers after sysprep even though they were the ones used during initial Installation!
    Real pain in the danglies as now we have to go to each Pc and ensure the driver downloads via WSUS and then run WSAT to get Aero back and the resolution back up to 1280x1024
    I'm assuming that you generalized the image to make it span multiple types of pc, this behaviour is by design. If you are using MDT you just need to put the correct driver for the GPU in the driver store and it will insert it at install time. If not you will need to add it into a driver search path in your image and answer file manually or just have seporate images per PC type. Given the WIM image single instance storage this means you can have many no generalized images in the same file without increasing the size too much. Downside to that is that you have more than one image to remake each time you upgrade them.

  6. #6

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,714
    Thank Post
    866
    Thanked 664 Times in 437 Posts
    Rep Power
    501
    Yeah will be having a look at the new WDS when I get round to upgrading the Apps Server to R2!

  7. #7


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,720
    Thank Post
    229
    Thanked 872 Times in 749 Posts
    Rep Power
    299
    Quote Originally Posted by Gatt View Post
    I've found that Windows 7 Has stripped out the Graphics Drivers after sysprep even though they were the ones used during initial Installation!
    Real pain in the danglies as now we have to go to each Pc and ensure the driver downloads via WSUS and then run WSAT to get Aero back and the resolution back up to 1280x1024
    i assume like with vista you can prepare a sysprep file in such a way that it dosent strip drivers out

    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="generalize">
            <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>
            <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <RegisteredOrganization>a n other school</RegisteredOrganization>
                <RegisteredOwner>a n other school</RegisteredOwner>
                <StartPanelOff>true</StartPanelOff>
                <DoNotCleanTaskBar>true</DoNotCleanTaskBar>
            </component>
        </settings>
        <settings pass="specialize">
            <component name="Microsoft-Windows-IE-InternetExplorer" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <Home_Page>http://www.myhomepage.com</Home_Page>
                <IEWelcomeMsg>false</IEWelcomeMsg>
            </component>
            <component name="Microsoft-Windows-International-Core" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <InputLocale>en-gb</InputLocale>
                <SystemLocale>en-gb</SystemLocale>
                <UILanguage>en-gb</UILanguage>
                <UILanguageFallback>en-gb</UILanguageFallback>
                <UserLocale>en-gb</UserLocale>
            </component>
        </settings>
        <settings pass="oobeSystem">
            <component name="Microsoft-Windows-Sidebar" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <SidebarOnByDefault>false</SidebarOnByDefault>
                <SidebarVisible>false</SidebarVisible>
                <Gadget1 />
                <Gadget2 />
                <Gadget3 />
            </component>
        </settings>
        <cpi:offlineImage cpi:source="wim://server/windowscds$/vista%20x86%20sp1/sources/install.wim#Windows Vista BUSINESS" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    cant remember exactly which bit does it but i found every image i made with my old sysprep file killed the video driver (but none of the rest)

  8. #8

    Join Date
    Dec 2007
    Location
    Derbyshire. Ish.
    Posts
    266
    Thank Post
    29
    Thanked 23 Times in 16 Posts
    Rep Power
    24
    We've used exactly the same procedures to create our Windows 7 images as we did for our Vista ones with no problems.

    Except (and there's always a "but"!)

    We wanted to use our SCCM 2007 R2 infrastructure to deploy the images in a single hit - create the task sequence, advertise it to a collection (or collections!) and then watch the machines deploy 7 without having to visit them.

    I've found that although my WDS image works fine for WDS, joins the domain happily etc.. it won't play properly via SCCM.

    It's not a compatibility / Windows 7 support thing as SCCM will deploy a plain vanilla Windows 7 RTM image fine (as I discovered when I accidentally put it down to the entire network earlier this week...!) so it must be something I'm cocking up in the image creation process without realising it....

    We've nearly done the whole school via WDS now - so SCCM can wait for the moment, but if anyone has any thoughts on that it would be appreciated!

  9. #9

    Gatt's Avatar
    Join Date
    Jan 2006
    Posts
    6,714
    Thank Post
    866
    Thanked 664 Times in 437 Posts
    Rep Power
    501
    I've found a few probs with SCCM & windows 7 - cant connect to a Wiin7 PC with the remote tools..

  10. #10


    Join Date
    Jan 2006
    Posts
    8,202
    Thank Post
    442
    Thanked 1,032 Times in 812 Posts
    Rep Power
    339
    I noticed that FOG version 0.27 includes support for windows 7.

    The FOG Project Team is proud to announce the release of version 0.27. This release includes support for Windows 7 (RC) and task scheduling, as well as many other small improvements. Please try it out and let us know what you think!
    FOG :: A Computer Cloning Solution - Home

SHARE:
+ Post New Thread

Similar Threads

  1. Windows Deployment Service
    By neilmc in forum Windows
    Replies: 2
    Last Post: 14th August 2009, 12:20 PM
  2. Vanilla windows software deployment
    By djdohboy in forum Windows
    Replies: 4
    Last Post: 5th September 2008, 08:01 AM
  3. Windows Deployment Services
    By Burnsy2023 in forum Wireless Networks
    Replies: 1
    Last Post: 21st January 2008, 10:32 AM
  4. Windows Deployment Services Walkthrough
    By ctbjs in forum How do you do....it?
    Replies: 2
    Last Post: 1st June 2007, 09:58 AM
  5. Windows Deployment Services - the new RIS
    By steve in forum Windows
    Replies: 5
    Last Post: 14th October 2006, 05:09 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •