Windows 7 Deployment FOG- SAD2 Driver tool
-
[quote=“raimon93, post: 24563, member: 22311”]Thanks! also what can be the problem of this? got an error, i tried the image in VMware checking if its correct but got this error:
[URL=‘https://www.dropbox.com/s/qelairrkreko9ts/2014-03-21 14.51.47.jpg’]https://www.dropbox.com/s/qelairrkreko9ts/2014-03-21 14.51.47.jpg[/URL][/quote]
It looks like windows hasn’t loaded properly yet, it’s still logging on. I think mine does that too but can you test a fresh install of win 7, then run the driver packs manually while logged on as admin?
-
oke, after another VM image it worked, meby the problem was that somthing wasend loaded. but after a while it worked flawless!
Thanks for support
-
I was able to use the SAD3-130627 tool to extract and install the drivers just like the SAD2 tool. I had to modify the DP-Install_Tool.cmd with code from the originally modified SAD2 .cmd. I will upload what I have done. There are switches in the beginning of the code that you can change to do reboot or shutdown, delete drivers, ect. It explains it in the notes in the code. Mine reboots and leaves the drivers as it only amounts to a gig of space. I also had to modify the command that is put in the sysprep script folder to use SAD3-130627 instead of SAD2-111118. Other then that it ran the same. Add the 7zip file just like in the tutorial.
Just open the attached txt file in notepad and save it as a .cmd.[url=“/_imported_xf_attachments/0/615_DP_Install_Tool.txt?:”]DP_Install_Tool.txt[/url]
-
Sooo… I have used the instructions from the initial post with great success many times though apparently I haven’t done so since November. My VMWare Workstation snapshots from November work fine but if I upload an image after taking a new snapshot and then deploy it to any machine I get a blue screen stop error and the computer boot loops at the “Starting Windows” screen.
Unfortunately I can’t recall exactly what changed around that time. I first noticed trouble when I started to experiment creating 64bit images last winter. I mistakenly thought it was an issue with my x64 imaging process which wasn’t critical so I didn’t think much of it. As I am trying to update my 32 bit image from last November I finally realized that the issue extends to all VMWare Workstation images EXCEPT those with snapshots that go back to November and before.
I did upgrade from VMWare Workstation 9 to VMWare workstation 10. I thought that was in September or October but it might have been around the time of the problem. My next plan is to roll back to VMWare Workstation 9.
Anyone experienced anything like this and found a solution?
-
Fog is a great tool. question: Any idea why SAD 2 is not running silently ? I am prompted every step of the way. Used the DP_Install_tool posted here and still no silent install. should c:\windows\setup\scripts\setupcomplete.cmd have “/s” added to the end of this line ? START C:\Drivers\SAD2-111118\DP_Install_Tool.cmd
-
This topic is still a bit hard to understand when i used SAD 2 for more than a year and now SAD 3 !
I added to SAD a FOG configuration generator based on network IP and DNS suffix and a Windows OEM Activator based on brands but it’s far from perfection so i don’t use them anymore.
But if some people are interested to improve my script, i can share them.To use SAD 2 or 3 in silent, you have to add the /S to the .cmd of SAD and run something like this in the “FirstLogonCommands” of the sysprep :
C:\SAD3-130627\DP_Install_Tool.cmd /SThere is no problem to keep this kind of image under VMware Workstation 10 even after making with an older version.
Mine was made in 2013 and i keep updating it since. -
[quote=“jmeyer, post: 32276, member: 6537”]
There is no problem to build this image under VMware Workstation 10.
Mine was made in 2013 and i keep updating it since.[/quote]Thanks for confirming this.
I’m thinking this could be a problem with my configuration of VMWare Workstation configuration or the hardware/OS it is running on. I would question the settings I’m using when creating the VM guest images but older snapshots work fine on VMs created in November 2013 or before. I tried starting from scratch with a fresh install of Workstation 9 and still end up with unbootable deployments. The file system transfers fine and partitioning looks good but still won’t boot.
Are there any recent Windows updates known to break VMWare V2P? My workstation 10 is Windows 8 x64(not 8.1) on an HP 6200 Pro while Workstation 9 is Windows 7 x64 on an HP 6000 Pro. P2V is well documented but the reverse not so much.
We are an HP shop with 6000/6200/6300 pro and will be adding 600 G1 shortly. Aside from the 6000 not wanting to step through the boot order when a PXE server is not found these machines have worked well for us until now.
I’m quickly running out of ideas so any thoughts are welcome. Reports of success with similar hardware will also help me feel more hopeful.
Thanks
Eli
-
There were something about disabling SCSI (scsi0.present = “FALSE”) and put drive as IDE but i haven’t edit vmx file under Workstation 10 for a new image version so i’m not sure it’s something to check.
I don’t understand what you try to do when you speak of P2V for HP home computers.
-
I do set the drives as IDE but I have not edited the VMX file to disable SCSI. It is a good thought that I will try to tomorrow and report results.
P2V is shorthand for the process of capturing a physical machine to a virtual machine. This is not what I’m trying to do but my point was there is plenty of documentation of that process. V2P is essentially what we are doing when we are preparing virtual machine images with VMWare Workstation for deployment to physical machine with FOG.
-
think there must be a fault with my machine as the vm now and again will bluescreen with reference pointer error. but I continued but when it came to the vm restarting after sysprep it gets to starting services and hangs and gets a error and keeps going round ina cycle same if I then deploy the uploaded image to a machine.
I tested the driver install tool on a baremetal fresh install of windows 7 x64 and it installed every driver fine, I then syspreped it with my unattend file and that goes through fine (doesn’t activate but think that’s a key issue).
am guessing if I need to this process can be done on a baremetal machine I just loose the ablity of snapshotting.
-
[quote=“Eli Kelly, post: 32305, member: 1152”]I do set the drives as IDE but I have not edited the VMX file to disable SCSI. It is a good thought that I will try to tomorrow and report results.
P2V is shorthand for the process of capturing a physical machine to a virtual machine. This is not what I’m trying to do but my point was there is plenty of documentation of that process. V2P is essentially what we are doing when we are preparing virtual machine images with VMWare Workstation for deployment to physical machine with FOG.[/quote]
Why you don’t build a clean Windows in a VM and use snapshot to revert modification if needed then use SAD in sysprep ? This way, if you have special soft to add to an image, just install them, run sysprep, upload image then revert modification to the VM.
We have HP, DELL, LENOVO, ACER and few other brand of computer and we use ONLY ONE image with sysprep…
Using an image from a computer means that you backup all the specification of the computer for nothing (driver and software).
Maybe you don’t even handle temp files… -
I have another query.
The company I work for manufactures pcs. All the machines were am trying to implement this are my work branded machines, they are licenced with a oem os which activates against the bios.
I have one of the oem 32 bit disks but not the 64 am getting hold of one. But what would I need to change in my sysprep file as I won’t need a key in there as the oem os activates against the bios.
I don’t know of any of that makes sense but if you understand please let me know.
-
Change the architecture from amd64 to x86
-
Oh yea I’ve done that. I mean do I just leave the section in the unattend file for the product key blank as this ets activated against the bios.
-
Remove the <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey> in it’s entirety.
I also believe you need to set the -SPP parts to -SLC
-
[quote=“jmeyer, post: 32396, member: 6537”]Why you don’t build a clean Windows in a VM and use snapshot to revert modification if needed then use SAD in sysprep ? This way, if you have special soft to add to an image, just install them, run sysprep, upload image then revert modification to the VM.
We have HP, DELL, LENOVO, ACER and few other brand of computer and we use ONLY ONE image with sysprep…
Using an image from a computer means that you backup all the specification of the computer for nothing (driver and software).
Maybe you don’t even handle temp files…[/quote]That is exactly what I am doing and it has been working beautifully until recently. I have a full set of snapshots from every stage of preparing my clean image. From time to time I like to patch the OS, take a new snapshot and then update the stock image on the FOG server. For some reason any new snapshots break this process.
I did try your thought about setting scsi0.present = “FALSE” in the VXD (edited:meant VMX) file. Unfortunately that doesn’t seem to make a difference.
-
[quote=“Eli Kelly, post: 32474, member: 1152”]That is exactly what I am doing and it has been working beautifully until recently. I have a full set of snapshots from every stage of preparing my clean image. From time to time I like to patch the OS, take a new snapshot and then update the stock image on the FOG server. For some reason any new snapshots break this process.
I did try your thought about setting scsi0.present = “FALSE” in the VXD (edited:meant VMX) file. Unfortunately that doesn’t seem to make a difference.[/quote]
Maybe make a new Windows installation will solve the problem…
I join my .vmx content to compare with yours in case something in it bring the problem.[CODE].encoding = “windows-1252”
config.version = “8”
virtualHW.version = “9”
scsi0.present = “TRUE”
scsi0.virtualDev = “lsisas1068”
memsize = “1024”
mem.hotadd = “TRUE”
ide0:0.present = “TRUE”
ide0:0.fileName = “Windows 7 x64 2-000001.vmdk”
ide1:0.present = “TRUE”
ide1:0.autodetect = “TRUE”
ide1:0.deviceType = “cdrom-raw”
ethernet0.present = “TRUE”
ethernet0.virtualDev = “e1000”
ethernet0.wakeOnPcktRcv = “FALSE”
ethernet0.addressType = “generated”
usb.present = “TRUE”
ehci.present = “TRUE”
ehci.pciSlotNumber = “35”
sound.present = “TRUE”
sound.virtualDev = “hdaudio”
sound.fileName = “-1”
sound.autodetect = “TRUE”
mks.enable3d = “TRUE”
pciBridge0.present = “TRUE”
pciBridge4.present = “TRUE”
pciBridge4.virtualDev = “pcieRootPort”
pciBridge4.functions = “8”
pciBridge5.present = “TRUE”
pciBridge5.virtualDev = “pcieRootPort”
pciBridge5.functions = “8”
pciBridge6.present = “TRUE”
pciBridge6.virtualDev = “pcieRootPort”
pciBridge6.functions = “8”
pciBridge7.present = “TRUE”
pciBridge7.virtualDev = “pcieRootPort”
pciBridge7.functions = “8”
vmci0.present = “TRUE”
hpet0.present = “TRUE”
usb.vbluetooth.startConnected = “TRUE”
displayName = “Windows 7 x64 2”
guestOS = “windows7-64”
nvram = “Windows 7 x64 2.nvram”
virtualHW.productCompatibility = “hosted”
powerType.powerOff = “hard”
powerType.powerOn = “hard”
powerType.suspend = “hard”
powerType.reset = “hard”
extendedConfigFile = “Windows 7 x64 2.vmxf”
scsi0.pciSlotNumber = “160”
ethernet0.generatedAddress = “00:0c:29:ef:45:1b”
ethernet0.pciSlotNumber = “33”
usb.pciSlotNumber = “32”
sound.pciSlotNumber = “34”
vmci0.id = “1492075803”
vmci0.pciSlotNumber = “36”
uuid.location = “56 4d 18 a6 8c f9 61 ab-c7 34 18 d6 58 ef 45 1b”
uuid.bios = “56 4d 18 a6 8c f9 61 ab-c7 34 18 d6 58 ef 45 1b”
cleanShutdown = “TRUE”
replay.supported = “FALSE”
replay.filename = “”
ide0:0.redo = “”
pciBridge0.pciSlotNumber = “17”
pciBridge4.pciSlotNumber = “21”
pciBridge5.pciSlotNumber = “22”
pciBridge6.pciSlotNumber = “23”
pciBridge7.pciSlotNumber = “24”
scsi0.sasWWID = “50 05 05 66 8c f9 61 a0”
usb:1.present = “TRUE”
ethernet0.generatedAddressOffset = “0”
vmotion.checkpointFBSize = “134217728”
softPowerOff = “FALSE”
usb:1.speed = “2”
usb:1.deviceType = “hub”
usb:1.port = “1”
usb:1.parent = “-1”
checkpoint.vmState.readOnly = “FALSE”
checkpoint.vmState = “”
tools.remindInstall = “TRUE”
numvcpus = “2”
cpuid.coresPerSocket = “2”
floppy0.present = “FALSE”
usb:0.present = “TRUE”
usb:0.deviceType = “hid”
usb:0.port = “0”
usb:0.parent = “-1”
[/CODE] -
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.
