@AlexPDX @Sebastian-Roth it was something simple in the end
BIOS > advanced > system options
i turned off/unticked - configure storage controller for VMD
basically its there version of RAID, untick it and its AHCI
@AlexPDX @Sebastian-Roth it was something simple in the end
BIOS > advanced > system options
i turned off/unticked - configure storage controller for VMD
basically its there version of RAID, untick it and its AHCI
Sorry taken ages to reply, just busy this week at work
It’s fog v1.5.10 and single disk resizable
As said I can deploy image fine on other machines, just not this dam hp z2 g9
Hi all,
So I’ve deployed a windows 10 image to a hp z2 g9 pc, it’s written the image to the disk, as I saw it doing the part clone process but when it succefully completed, it then rebooted and loaded up windows, once it rebooted to load windows, I have a blue screen of death with a stop code
inaccessible boot device
I have deployed the same image to a VM and a hp laptop with success, so maybe it’s something to do with this pc
Thanks,
Rob
case closed, all good in da hood
it took ages compiling the ipxe binarys but now its been succesfully updated
thanks @Tom-Elliott @Sebastian-Roth
@Sebastian-Roth @Tom-Elliott ok i re ran the installer multiple times and its got past that stage now, its getting stuck at this stage now
Compiling iPXE binaries trusting your SSL certificate…
@Sebastian-Roth @Tom-Elliott got a problem
Downloading kernel, init and fog-client binaries… * Could not download init_32.xz properly
[root@lon-c-fog10 bin]#
@robertkwild lovely i wget the new file and it found my fog install and its now upgrading it
@Tom-Elliott when i do the git method, do i need to first cd to my fog base installation dir
rather than the tar i just can install it and it will persume see ive already got a fog installation and just update it
hi all,
yes i know i want to update on centos 7, i know its dead but how do i update from 1.5.9 to the new one 1.5.10
is it just the case of installing it again and it will know its already installed and will just update it
thanks,
rob
@tom-elliott said in deploy image oobe issue:
mmcblk
lets say if one drive is partitioned into 2 partitions will it blow all partitions away and deploy image on whole disk?
@tom-elliott ahhhh yes, how stupid of me, should had thought of that LOL, thanks Tom
hi all,
got a weird one, on one laptop i deploy my image to, normally after partclone deploys the image to the disk, i get the oobe messages ie create new user, new password blah blah
but this laptop it looks like it hasnt blown away the hard drive and over written it with the deployed image one as instead of the oobe messages i get a message to enter in my capital one o365 username
ive never had problems before with this image on my fog server
and when i was looking at when fog deployed the image to the new laptop i saw no errors ie saying failed to deploy image etc
thanks,
rob
great thanks @george1421 i understand now, basically to do this right, you need to sysprep using an unattended xml file which i dont do, so best case scenario is i can just leave the drivers there and install once im on the desktop,
thanks again george
@george1421 ok i feel this won’t work for me as when I captured the image I ran a sysprep without an unattended answer file, so I fear I’m going to have to run the sysprep again this time specifying an answer file
As how do I get Windows or fog to run the script after my oobe generalise
i mean this script
SetupComplete.cmd
pnputil.exe /add-driver “C:\Drivers*.inf” /subdirs /install
@george1421 is there any way to auto call that batch file after the oobe generalise has finished
bear in mind im not using an unattended.xml answer file
Ok I save it here
%WINDIR%\Setup\Scripts\SetupComplete.cmd
In that setup complete CMD it’s
pnputil.exe /add-driver “C:\Drivers*.inf” /subdirs /install
But how do I get fog to dump the script in there in the first place
@george1421 So make a batch file when I’m in the windows desktop after the oobe generalise stage, call it
setupcomplete.cmd
And put
pnputil.exe /add-driver “C:\Drivers*.inf” /subdirs /install
Or I could just run that command instead
@george1421 This step may not be necessary now days since windows 10 does a good job of having the common hardware drivers on board.
That’s what I thought but obviously when deploying a syspreped windows image back on this hardware it doesn’t have the Intel NIC driver
That 7204\Win10\x64 directory will be copied in full to the target computer in c:\drivers directory
So if it finds the compatible NIC driver in c:\drivers, will it install the driver or will I have to manually install the driver
@george1421 so basically instead of syspreping a standard windows OS, you sysprep a winPE ?
heres the structure i got from extracting that CAB file
7204-WIN10-A05-CJ9XY\7204\Win10\x64
do i need to create a folder called
7204-WIN10-A05-CJ9XY or will 7204 do?
and you say i get the model info from the web GUI when it does an inventory of the system
@george1421 thanks you george, i will try this tomrrow as i have a pc that needs doing so this is a good test
so the windows driver packs are different from the winPE drivers?
@george1421
images
├─/drivers
├─z2
├─win10
└─x64
So under the x64 folder do I put the inf files straight in there
do I do this as well after I drop the inf files
pnputil.exe /add-driver “C:\Drivers*.inf” /subdirs /install