Windows 7 Deployment FOG- SAD2 Driver tool
-
Thanks!
Your vmx file is substantially similar to my working ones with the exception that mine have:
[CODE]virtualHW.version = “8”[/CODE]
An interesting observation is that all of my newer snapshots that are not working have an added line at the bottom of the vmx file
[CODE]monitor.phys_bits_used = “40”[/CODE] I’m not sure if that is significant at all but it is my best lead right now.
-
If i remember well, you have an endless loading problem after reboot, right ?
Is it reboot on the VM or on an other computer ? -
That’s right. It happens on deployment to a physical machine.
-
At first boot and before Windows make it self optimization ?
-
Yes at first boot and before self optimization. Just after “Starting Windows” is displayed just as the logo is starting to show up the computer reboots.
If I try to boot to safe mode it restarts right after Loading CLASSPNP.SYS
-
Have you reboot your VM before and after sysprep to see if this happen ?
-
Hi wondering if anyone can offer any advice, so all the machines at work we plan to use are all RM branded and have oem licences, i have now got hold of the RM windows 7 64bit oem recovery disk (activates against bios), do i have to do anything special to make a golden image with this or would i be best making a single image for each RM Machine type, in total about 5 different models.
ive tested the sad2 tool on them and it works fine gets every driver no problem apart from the RM laptops which is a issue we have seen before with a faulty intel onboard graphic driver which basically kills the display and you have to RDP to the machine and update the driver for the graphic manually in device manager by searching automatically for the driver and it will grab the correct one from the internet, am not sure how i would update this manually in the driver packs either.
any advice would be great.
-
[quote=“jmeyer, post: 32641, member: 6537”]Have you reboot your VM before and after sysprep to see if this happen ?[/quote]
VM reboot after sysprep completes normally.
Update: Gave up on VMWare for this. I switched to VirtualBox and the process is working perfectly except that I get prompts for a hostname when windows starts up after deploying to a physical machine. Actually it initially prompted for the hostname and timezone. My unattend (which works correctly with my old VMWare snapshots as well as with MDT deployments) originally declared the Timezone and ComputerName in the specialize pass. Adding a Timezone value in the OOBE pass fixed the prompt for time zone but adding the ComputerName tag there doesn’t make a difference. I have tried leaving the ComputerName tag out of both sections and not surprisingly the hostname prompt still appears when the physical machine boots after deployment.
Admittedly my unattend file is somewhat complex as it does a few things such as configure RDP, enable Administrator, disable WER. Tomorrow I will try a very basic unattend file but thought I would see if any ideas came up that would save me the troubleshooting time.
Thanks
Eli
-
[quote=“chclark, post: 33624, member: 6419”]Hi wondering if anyone can offer any advice, so all the machines at work we plan to use are all RM branded and have oem licences, i have now got hold of the RM windows 7 64bit oem recovery disk (activates against bios), do i have to do anything special to make a golden image with this or would i be best making a single image for each RM Machine type, in total about 5 different models.
ive tested the sad2 tool on them and it works fine gets every driver no problem apart from the RM laptops which is a issue we have seen before with a faulty intel onboard graphic driver which basically kills the display and you have to RDP to the machine and update the driver for the graphic manually in device manager by searching automatically for the driver and it will grab the correct one from the internet, am not sure how i would update this manually in the driver packs either.
any advice would be great.[/quote]
Hi Might be best making a new thread in the Windows section of the forum for this question.
HERE: [url]http://fogproject.org/forum/forums/windows-problems.6/[/url]
-
Andyroo is correct, another forum would be best to discuss your unattend file.
however, have some information in the mean time, this is how I handle my computer naming convention, I ofcourse have the fog Client installed, and I have elected to use the Host Name Change service. When I register the machine I register it as the name I want it to have when the process is complete.
[code]
<component name=“Microsoft-Windows-Shell-Setup” processorArchitecture=“x86” publicKeyToken=“31bf3856ad364e35” language=“neutral” versionScope=“nonSxS” xmlns:wcm=“[URL]http://schemas.microsoft.com/WMIConfig/2002/State[/URL]” xmlns:xsi=“[URL]http://www.w3.org/2001/XMLSchema-instance[/URL]”>
<ShowWindowsLive>false</ShowWindowsLive>
<ComputerName>*</ComputerName>
<RegisteredOrganization>Microsoft</RegisteredOrganization>
<RegisteredOwner>AutoBVT</RegisteredOwner>
<ProductKey>Use a generic key here if you activate via KMS, if nor provide you kms key here.</ProductKey>
<CopyProfile>true</CopyProfile>
<TimeZone>Eastern Standard Time</TimeZone>
</component>
[/code] -
VMWare is working again for me. There was one important step that I was missing. It was expressed clearly by the OP. There was even a screenshot. I have even done it hundreds of times correctly in the past.
It simply turned out that I have been forgetting to tick the “Generalize” box! Sysprep wasn’t processing anything from the Specialize phase of my unattend.
-
Hi all, I have one question regarding audit mode. As far as I understood, it’s equivalent mode to OOBE (or Windows Welcome) but it’s meant more for technically skilled and for corporations than for end users. But in the end, it has the same use: to prepare freshly installed win.
Now, is it problem to not do (2nd and n-th) image preparation in audit mode (of course, the 1st we did this way)? Is it ok to update windows, update/upgrade/install/remove software, change profile, etc. via logged in administrator and then start sysprep oobe with generalize from here (before capturing image)? Had anybody problems doing it this way or do you see any potential problems?
I read, that audit mode is needed for auditSystem and auditUser passes to happen (if I got it right). But since we based our unattend.xml on this tutorial, we don’t use auditSystem or auditUser.
Does anybody know some (perhaps official) text, which explains if there is any difference between doing sysprep in audit mode and normally from logged in administrator account?
Thanks.
-
No, OOBE is for making the machine into a Like new Out Of Box Experience. Audit Mode is a tool to use during an Image setup process, that requires the finalization of the OS so it can (if you supply an unattend.xml) make your Installation autonomous.
The Audit mode is where you get to windows BEFORE the OOBE process happens. You are suppose to install all your software at this point then sysprep and upload, On first deploy the installation will answer the installation questions with your provided unattend.xml and complete the OOBE process (generalizing the installation so that new drivers can be applied to the system, cleaning some registry values and other secretive windows type things).
Really, there isn’t much difference in if you just install the software as a user and push your image, except the generalization processes which allows the machine that you are imaging to have their own hardware identifiers and unique strings which will be required for activation. This is only really important if you activate to a KMS server or if you join to an active directory environment (speculation have not tested I am not AD).
Try it, tell us what does and does not work if you don’t sysprep, that’s really the only thing I can recommend.
Personally, I read many tutorials before I began pushing windows 7. each one mentioned using Audit Mode to install my software and drivers before completing the generalization process, and I have had marginal success in doing so.
Hope this helps!
-
I have done the “Build an OOBE” image without an unattend.xml.
The system boots, asks for the product key and then just needs drivers installed.
What I am considering doing is just rebuilding my sysprep-generalize image with a folder that contains these drivers as my hardware doesn’t vary greatly(Lenovo brand products mostly). So if c:\drivers has all of the necessities then so be it, even if I have to install my drivers manually. I might just make a batch file that searches for drivers within that folder and installs them upon login and be done with it.
I’ve also do hardware specific images, and they work just as well.
-
That’s the way I do my drivers right at C:\Drivers. I even add it to the path variable in the registry so that when windows parses for a driver it looks in that folder too by default.
-
That Jaymes is a wonderful idea.
Thank you for that
-
Ok, sorry for the delay, thanks for reply.
In the end we used our previous image - for which, afaik, there was never used audit mode and everything was installed via (normal) administrator account - and it seems there are no issues.
[quote=“Jaymes Driver, post: 35201, member: 3582”]No, OOBE is for making the machine into a Like new Out Of Box Experience. Audit Mode is a tool to use during an Image setup process, that requires the finalization of the OS so it can (if you supply an unattend.xml) make your Installation autonomous.
The Audit mode is where you get to windows BEFORE the OOBE process happens. You are suppose to install all your software at this point then sysprep and upload, On first deploy the installation will answer the installation questions with your provided unattend.xml and complete the OOBE process (generalizing the installation so that new drivers can be applied to the system, cleaning some registry values and other secretive windows type things).
Really, there isn’t much difference in if you just install the software as a user and push your image, except the generalization processes which allows the machine that you are imaging to have their own hardware identifiers and unique strings which will be required for activation. This is only really important if you activate to a KMS server or if you join to an active directory environment (speculation have not tested I am not AD).
Try it, tell us what does and does not work if you don’t sysprep, that’s really the only thing I can recommend.
[/quote]
And just for clarification - we do use sysprep, we just don’t install stuff via audit mode admin account.[quote=“Jaymes Driver, post: 35201, member: 3582”]
Personally, I read many tutorials before I began pushing windows 7. each one mentioned using Audit Mode to install my software and drivers before completing the generalization process, and I have had marginal success in doing so.Hope this helps![/quote]
-
[COLOR=#141414][quote=“Jaymes Driver, post: 35282, member: 3582”]That’s the way I do my drivers right at C:\Drivers. I even add it to the path variable in the registry so that when windows parses for a driver it looks in that folder too by default.[/quote][/COLOR]
[COLOR=#141414] [/COLOR]Hi, is it possible to expand on this. It sounds like a really simple way to have a master image setup by just having a single folder @ C:\Drivers
thanks
-
Sure you got it.
The way I handle my drivers is, When I get a machine in that already has windows installed, I run a program called DriverGrabber
[url]http://integrator.professorcpu.net/index.php?addons&id=242[/url]I usually create a folder on my virtual machine under the C drive called “drivers”.
I then set up a folder for each model and put the driver grabber folders in there. This way there is a nice neat structure so if you need to manually apply the driver for the nic card, you may do so by looking in the corresponding folder.
Then I use a registry key to associate the folder with the windows installation:
In HKEY_LOCAL_MACHINE/Software/Microsoft/Windows/Current Version click on “DevicePath” and enter “C:\Drivers” (remember the entries must be separated by a semicolon).
Alternatively you can add the path (C:/Drivers) to the environment variable path under My computer, Properties, Advanced Settings then at the bottom environment variables.
I do not know that this is the correct way to install drivers, but I have had a lot of success in doing this with Tangent machines which use MSI mainboard, Intel graphics and Processor, and Realtek Audio and Network cards.
Good luck!
-
I have been using Microsoft’s dpinst program, and it seems to work (at least 90% of the time), but I have had one severe program with it: it seems to go through and install every single version of drivers.
We are mostly a Dell shop, but we have many models of Dell, and even within the models, we have some with differing hardware. I get my drivers from Dell’s Web site in EXE format. I then change the extension to ZIP and extract everything from the file.
The problem is that the drivers often contain multiple versions of a driver. For example, let’s say for a video driver, it contains Version 1.0, Version 2.0, Version 3.0, and Version 4.0. Well, apparently dpinst does not check only for the latest version. It goes through and first installs Version 1.0. Then, it checks and finds Version 2.0, so it then installs that because it’s newer. Of course, it then finds Version 3.0 and installs that. The process continues until it installs the last version.
This is a problem for two main reasons: (1) because some drivers (especially from Intel, AMD, and nVidia) contain a [B]lot[/B] of versions it can take a while to get drivers installed and (2) it fills up the “Programs and Features” list with a [B]ton[/B] of entries, one for each driver version installed.
Is there any way around this?
