Posts made by agray

@Sebastian-Roth When we get our next batch of new PCs in, I’ll see if that fixes it and respond here. Thank you!

@Sebastian-Roth I was not! Not sure how it got that way but will fix that.
Is that was seem to be keeping it from getting to the needed size and spitting out that error?

@Sebastian-Roth
d1.fixed_size_partitions

:1:2

d1.minium.partitions

label: gpt
label-id: B300B49B-4800-44BC-BB1D-E29EB16E9E42
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134

/dev/sda1 : start=        2048, size=     1331200, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CE1A4E76-07A7-4004-A685-5589FD1A52CD, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=     1333248, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=A20895A8-3AF1-499D-95BB-F89DA7202209, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=     1595392, size=    68078446, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=15D7FC86-0674-4911-82C4-8122C656078F, name="Basic data partition"
/dev/sda4 : start=   939324416, size=      965312, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=34031986-6A02-42DB-8AFC-0B510AF755BA, name="attrs=\x22RequiredPartition GUID:63"
/dev/sda5 : start=   952557056, size=     1763454, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=8B928276-CF41-42FC-BFC9-9B5097DE653A, name="attrs=\x22RequiredPartition GUID:63"

d1.partitions

label: gpt
label-id: B300B49B-4800-44BC-BB1D-E29EB16E9E42
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 976773134

/dev/sda1 : start=        2048, size=     1331200, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=CE1A4E76-07A7-4004-A685-5589FD1A52CD, name="EFI system partition", attrs="GUID:63"
/dev/sda2 : start=     1333248, size=      262144, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=A20895A8-3AF1-499D-95BB-F89DA7202209, name="Microsoft reserved partition", attrs="GUID:63"
/dev/sda3 : start=     1595392, size=   937729024, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=15D7FC86-0674-4911-82C4-8122C656078F, name="Basic data partition"
/dev/sda4 : start=   939324416, size=    13232640, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=34031986-6A02-42DB-8AFC-0B510AF755BA, name="attrs=\x22RequiredPartition GUID:63"
/dev/sda5 : start=   952557056, size=    24201216, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=8B928276-CF41-42FC-BFC9-9B5097DE653A, name="attrs=\x22RequiredPartition GUID:63"

As well run ls -al /var/www/html/fog/services/ipxe/init* and post output here.

Says no such file or directory

@Sebastian-Roth said in Imaging an SSD:

What’s the size of the source disk and the destination disk?

The Image I’m pushing is set to “Single Disk - Realizable”
The original HDD I cloned was 500 GB, if that is what you mean, while the new SSD is 256 GB.

Well, new computer might need an updated version of FOG at some point as well.

If I need to update it, I can but not in time for this project. If that is my only option, no worries, I can take the long way to getting everything there.

@Tom-Elliott I already have an Image captured, just need to deploy it.
After what you gave me below, Fog was able to register it but, when I try deploying an image to it, it’s spitting out “Error trying to restore GPT partition tables (restorePartitionTablesAndBoodLoaders)”

@Tom-Elliott I can re-enable this after the image is deployed right?

My FOG version is 1.5.5
When I attempt to Quick Register/Full Register/ or deploy an Image to our new Dell Latitude 3500, it spits out the error “Cannot find disk on system (getHardDisk).”
It has a 256 GB SSD that functions properly as it boots to Win10 with no problem.
If you need any logs, pictures, or diagnostics run for more info, fill free to ask!
Thanks in advance!

@george1421

@george1421 said in Golden Image Deploy Problems:

I would recommend that you put the sysprep file in c:\windows\panther and not the legacy sysprep directory.

Thank you for the advice, I will start doing so. Didn’t know that was the legacy directory. I run my .bat file from the desk top if that’s an issue too.

@george1421 said in Golden Image Deploy Problems:

Are you injecting the model specific drivers into image as part of a post install script or are you front end loading

My system is set up to do it post install script if it works properly xD.

The Chipset of my VM is set to PIIX3. I’m pretty sure that was my original problem.

@george1421 said in Golden Image Deploy Problems:

FWIW: this sysprep setup file looks suspiciously close to the one I use.

I pulled this setup file from a post on here and just tweaked a few thing for my need. That could be why it looks close xD.

@Wayne-Workman
Thank you! I’ll test these out and read the page. I’ll come back and update this thread after, on if it worked or not.

@Wayne-Workman I apoligize for the delayed response, been a crazy week.
My FOG Version is 1.5.5.
I am captureing the Golden from a VW, the software is Oracle Virtualbox.
I did syprep the Image using a .bat file that looks like this:

@echo off
NET USER 1 /DELETE
powercfg -h off
rem C:\Support\Tools\Shutup\OOSU10.exe ooshutup10.cfg /quiet
del /F c:\windows\sssystem32\sysprep\panther\setupact.txt
del /F c:\windows\system32\sysprep\panther\setuperr.txt
del /F c:\windows\system32\sysprep\panther\ie\setupact.txt
del /F c:\windows\system32\sysprep\panther\ie\setuperr.txt
rem "C:\Program Files\Oracle\VirtualBox Guest Additions\uninst.exe"
copy unattend.xml C:\Windows\System32\Sysprep /Y
reg import C:\Support\Tools\ResetERAgentUUID.reg
cleanmgr /sagerun:1
defrag c:
c:\windows\system32\sysprep\sysprep.exe /oobe /generalize /shutdown /unattend:c:\windows\system32\sysprep\unattend.xml

The machine I’m deploying to is and Optiplex 3060. I don’t have drivers specific for the 3060, but I do have 3050 which are close. Could that be the problem?
I’m not sure where to check what mode my VM is in but from previous testing, I did put a note on my Image saying it was required to boot into Legacy.

I’ve scratched my head at this for weeks now and have no idea why it’s not working.
When I attempt to deploy my golden image to a physical machine, it fails. It come up with dell’s “Checking hardware for problems” and then shuts down.
BUT, when I deploy the same image to another vm, it succeeds.
I’ve set the physical machine to Legacy: Secure Boot off, and UEFI: Secure Boot off and deployed it, both have the same outcome.
Photo’s of my VM config can be found here.
Any ideas on what’s happening and how to fix it?

@george1421 said in Windows Not Booting:

best hypervisor

What do you feel is the best Hypervisor for Imaging?

@george1421 said in Windows Not Booting:

But if all you have is a hammer, everything looks like a nail.

Very true!

@george1421 Turns out I’m just really a noob when it comes to VMs. VirtualBox was set to Legacy in the setup. After changing my physical machine to Legacy, it works fine! Thank you George

If I’m undestadning correctly, when I go to capture and deploy the image, I boot into UEFI Secure off.

I’ve tested this several times and can’t seem to get my windows to boot up on my physical machine.
I captured the image in VirtualBox and syspreped. It will deploy to a VM with no problem but when I attempt to boot on my PM (OptiPlex 3020), it says “No bootable devices found.”

Ideas?

@Sebastian-Roth said in Connecting FOG to Virtual Machine:

What host OS do you have VirtualBox installed on?

Windows 10

@Quazz said in Connecting FOG to Virtual Machine:

the PIIX3 one works fine though.

I changed my chipset to PIIX3 and it works! Thank you guys for the long headache relief!

@george1421 I tested uninstalling VirtualBox and it didn’t do anything. I’m going to attempt using Hyper-V and will get back to you with results.

To cover all our bases, does my VM set up look correct?