+ Post New Thread
Results 1 to 12 of 12
O/S Deployment Thread, Sysprep - hard drive drivers in Technical; Strange one here. I've built a Sysprep image in a virtual machine, and most of the drivers install and the ...
  1. #1
    this_is_gav's Avatar
    Join Date
    May 2009
    Location
    Shilbottle, Northumberland
    Posts
    43
    Thank Post
    19
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Sysprep - hard drive drivers

    Strange one here. I've built a Sysprep image in a virtual machine, and most of the drivers install and the HALs seem to work and everything. Fine. Except for, strangely, the hard drive. Sysprep goes through Mini-setup, does everything it's meant to do, installs all the drivers I've added (such as mass storage devices and chipset drivers)... but the hard drive has a yellow exclamation mark next to it in Device Manager.

    Obviously the hard drive is working fine, as I'm in Windows.

    I've used a Sysprep image previously, but haven't installed drivers as a part of it - they've been done through Acronis True Image's Universal Restore, and I've not seen this issue before. Now I'm using FOG instead, and wanted to automate deployment as much as possible.

    Any ideas?

  2. #2

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241
    Did you run a sysprep -bmsd before sysprepping to build the mass storage devices?

  3. Thanks to Hightower from:

    this_is_gav (12th April 2011)

  4. #3
    this_is_gav's Avatar
    Join Date
    May 2009
    Location
    Shilbottle, Northumberland
    Posts
    43
    Thank Post
    19
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by Hightower View Post
    Did you run a sysprep -bmsd before sysprepping to build the mass storage devices?
    I did.

  5. #4

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241
    Quote Originally Posted by this_is_gav View Post
    I did.
    Silly question again, but at the bottom of your sysprep.inf file do you have a load of MSD listings?

  6. Thanks to Hightower from:

    this_is_gav (12th April 2011)

  7. #5
    this_is_gav's Avatar
    Join Date
    May 2009
    Location
    Shilbottle, Northumberland
    Posts
    43
    Thank Post
    19
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Thanks for replying again,

    Yup, there are, and on the finished sysprep.inf they're all still there, following only by the [sysprepcleanup] section (for whatever reason, the sysprep folder isn't deleted after mini-setup runs).

  8. #6

    Hightower's Avatar
    Join Date
    Jun 2008
    Location
    Cloud 9
    Posts
    4,920
    Thank Post
    494
    Thanked 690 Times in 444 Posts
    Rep Power
    241
    Mind PMing me a copy of your sysprep.inf (not sure if the problem is in there, but worth a look) - if so obviously take out any personal data such as your product key.

  9. #7
    this_is_gav's Avatar
    Join Date
    May 2009
    Location
    Shilbottle, Northumberland
    Posts
    43
    Thank Post
    19
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Not a problem. Attached it to the post should anyone else want to see it.

    I know the line in the file says no to building the mass storage devices, but that's done separately as part of a batch file (obviously before the main sysprep process starts).
    Attached Files Attached Files

  10. #8
    morganw's Avatar
    Join Date
    Apr 2009
    Location
    Cambridge
    Posts
    816
    Thank Post
    46
    Thanked 132 Times in 126 Posts
    Rep Power
    39
    There aren't any mass storage device drivers in there, it looks like mouse and keyboard drivers. It's been a while since I set up mine but I think I manually entered what I needed, I think I just added entries for various Intel ICH controllers on the end of what it generated from -bmsd.

    -bmsd should create a lot of entries (five or six hundred lines), then if you want to add your own you can just add them at the end like this:

    Code:
        PCI\VEN_8086&DEV_2681&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_27C1&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_27C5&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_2821&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_2829&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_2922&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_2929&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_3A02&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_3A22&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_3B29&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_3B2F&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_3B22&CC_0106=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaAHCI.inf
    
        PCI\VEN_8086&DEV_2682&CC_0104=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaStor.inf
    
        PCI\VEN_8086&DEV_27C3&CC_0104=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaStor.inf
    
        PCI\VEN_8086&DEV_27C6&CC_0104=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaStor.inf
    
        PCI\VEN_8086&DEV_2822&CC_0104=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaStor.inf
    
        PCI\VEN_8086&DEV_282A&CC_0104=%systemdrive%\SysPrep\Drivers\MSD\Intel\iaStor.inf
    
        PCI\VEN_8086&DEV_2820=%systemdrive%\SysPrep\Drivers\MSD\Intel\ich8ide.inf
    
        PCI\VEN_8086&DEV_2825=%systemdrive%\SysPrep\Drivers\MSD\Intel\ich8ide.inf
    
        PCI\VEN_8086&DEV_2828=%systemdrive%\SysPrep\Drivers\MSD\Intel\ich8ide.inf
    
        PCI\VEN_8086&DEV_2850=%systemdrive%\SysPrep\Drivers\MSD\Intel\ich8ide.inf

  11. #9
    morganw's Avatar
    Join Date
    Apr 2009
    Location
    Cambridge
    Posts
    816
    Thank Post
    46
    Thanked 132 Times in 126 Posts
    Rep Power
    39
    Thinking about it further I don't think the you actually need the driver in the mass storage section unless your deployed images fails to boot, if you get past that stage it would install along with any other pnp drivers during the mini-setup.

    You'll have to setup sysprep to install all required drivers from within the image, I normally put them in C:\sysprep\drivers so they get deleted at the end of the deployment and then use the sysprep driver scanner from here before running sysprep.

  12. Thanks to morganw from:

    this_is_gav (12th April 2011)

  13. #10
    this_is_gav's Avatar
    Join Date
    May 2009
    Location
    Shilbottle, Northumberland
    Posts
    43
    Thank Post
    19
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by morganw View Post
    There aren't any mass storage device drivers in there[...]
    I mentioned that the bmsd section was added later (as part of the batch file I fire sysprep off from), and it too seems to work. The mass storage drivers don't appear to be the issue - they're installing fine - it's the hard drive itself which is giving a driver error!

    Quote Originally Posted by morganw View Post
    Thinking about it further I don't think the you actually need the driver in the mass storage section unless your deployed images fails to boot, if you get past that stage it would install along with any other pnp drivers during the mini-setup.

    You'll have to setup sysprep to install all required drivers from within the image, I normally put them in C:\sysprep\drivers so they get deleted at the end of the deployment and then use the sysprep driver scanner from here before running sysprep.
    Yup, that was all done anyway and it seems to work fine. It installs graphics drivers, mass storage drivers, everything.

    I thought it might have been a conflict with the custom XP CD which I used to make the image file originally, which included a few basic drivers, but I've tried it with a stock XP CD, so the only drivers are those offered on the XP CD and those I inject in the sysprep process, but that gives the hard drive driver issue too.

  14. #11
    morganw's Avatar
    Join Date
    Apr 2009
    Location
    Cambridge
    Posts
    816
    Thank Post
    46
    Thanked 132 Times in 126 Posts
    Rep Power
    39
    Sorry I mis-read it a bit and thought it was the drive controller not showing up, i've never seen a drive even require drivers, I think it's more likely to be something left over from building the image in a virtual machine. You might have to remove any drive controllers from device manager before running sysprep, easiest way to check this though would be to try making a sysprep image on a physical PC. Older ACPI uniprocessor ones seem to put you in a better position (supports HAL switching to ACPI mutliprocessor and they normally don't normally require additional drivers for network cards or drive controllers).

  15. Thanks to morganw from:

    this_is_gav (12th April 2011)

  16. #12
    this_is_gav's Avatar
    Join Date
    May 2009
    Location
    Shilbottle, Northumberland
    Posts
    43
    Thank Post
    19
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    OK, I tried a new approach this morning. I had been following the Sysprep guide on the FOG wiki, which combines various scripts with Sysprep. This morning I sort of merged part of that guide with the examples at Vernalex and that issue has disappeared!

    Many thanks to both of you for your help.

    As I always like examples when I'm searching for help, for reference's sake, I've attached the three files I used (sysprep.inf, hwid.cmd and sysprep.bat) to script my sysprep process. Obviously I've not included sysprep itself or the driver folder I used.
    Attached Files Attached Files

SHARE:
+ Post New Thread

Similar Threads

  1. Sysprep nearly working but drivers going?
    By reggiep in forum Windows 7
    Replies: 8
    Last Post: 26th October 2010, 04:05 PM
  2. Sysprep not adding drivers when WDS is used
    By eean in forum Windows Server 2008
    Replies: 2
    Last Post: 26th March 2010, 03:55 AM
  3. Drivers, sysprep and Mini Setup
    By sparkeh in forum O/S Deployment
    Replies: 1
    Last Post: 13th October 2009, 11:44 AM
  4. Hard drive image of a netbook without CD/DVD drive
    By zx2012 in forum Netbooks, PDA and Phones
    Replies: 2
    Last Post: 30th August 2009, 02:27 PM
  5. Sysprep & Drive Letters
    By jack0w in forum Windows
    Replies: 26
    Last Post: 16th September 2008, 07:24 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
  •