Posts made by Grizzly

@Wayne-Workman I updated to RC12 yesterday. Captured using multi partition and single disk, re-deployed to test both and everything is now working! Thanks for all your hard work on this @Tom-Elliott!

@george1421 Correct! I am capturing another image using Single Disk - Resizable and hoping it works!

I updated to RC12 and ran a capture then deploy using Multiple Partition Single Disk (Non Resizeable) and although I got the same error in the previous screenshot it seems to have taken the image. I am going to test on one more machine then try the single disk - resizeable option.

@Wayne-Workman I was able to catch a quick shot before the machine restarted, picture below.

@Wayne-Workman Just finished. It captured but when I deployed the image it threw an error but vanished before I could get a SS of it. Some failure type prompt.

@Wayne-Workman The capture works with Mutliple Partition Single Disk, just not single disk resizeable. I’m currently capturing a image right now and will test it on one of my non working machines after it’s done.

@Grizzly Also tested this on an Lenovo X230 image I created in 1.2 that works as well. Thanks for the fixes!

Also attached is the partition layout for this machine if that helps.

@Wayne-Workman I don’t plan on using the RAW file forever, but it would be nice to have the image just in case. At this point I have no working images other than the last 2 laptops I have. Lol.

Once I get the image working I can re-capture. It’s not an inconvenience.

@Wayne-Workman Secure Boot is off on the machine. I’ll see about doing a RAW capture file for this image.

Thanks.

Server

• FOG Version: 1.3.5-RC11
• OS: Ubuntu 14.04

Client

• OS: Windows 10

Description

I’m working on capturing a factory image for a Windows 10 machine using UEFI. I can boot and attempt to start the capture but I am receiving an error at the capture point which is in the attached screen shot. After this fails the computer then fails to start going to the error recovery screen for Windows. I’ve tried running chkdsk first then capturing and no go. There is plenty of space for images on the NAS and it looks like the Owner permissions are set as root.

I’m running out of machines to try this with and seeing as it’s breaking their base image I only have a couple more shots at this. Any help would be appreciated.

Model of the computer is a HP ProBook 450 G4 using UEFI. Factory image hasn’t been touched. FOG is on a VM and I’m using a NAS for storage of the images.

Thanks.

@Tom-Elliott Looks like the RC11 update has fixed this at least with my legacy 4530s image. I’ll be doing a couple more tests with our other models as I can get my hands on them to make sure.

Is there another section where you would like me to report this?

@george1421 That was my worry. I went ahead and got approval to upgrade our DHCP to 2012 R2 fearing that 2008 just wouldn’t work. Thanks for the reply!

Server

• FOG Version: 1.3.5-RC-10
• OS: Ubuntu 14.04

Description

Has anyone had any luck yet getting UEFI to work with Windows Server 2008 DHCP? I’ve been following this link: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence which states that no one has gotten it to work with 2008 yet. I’ve tried all the available PXE options listed and no go, but it also just reboots to startup menu instead of displaying what the issue is after it tries to network boot so I can’t get much more information. Wireshark reports it as Arch:00007:UNDI:003016.

I’m working on getting some images captured for our new Windows 10 HP Probook 450 G4 machines that are coming in and I would prefer to keep them UEFI rather than switch back to Legacy. Anyone have any other tips on possibly getting this to work?

@Tom-Elliott I can upload a new capture. I did this a couple weeks ago and it seemed to work out fine. If this is the solution I can just image with 1.2 then capture again with 1.3. We’re moving to Windows 10 machines with UEFI soon so I need to get things switched over and that working as well.

I’m not changing any of the SATA modes. The machines are all setup in the same manner using legacy.

@Tom-Elliott Can I provide anymore information in order to help out with this?

@Grizzly I just tried on another machine with a different image. I got the same message as before saying the clone was successful but on reboot it’s saying no boot device found, please install an operating system.

I’m at a loss of what might have happened. I just compared file sizes of the images and they look to be fine.

@x23piracy Well I’m not sure what is different but now it just worked. The partitions are a single partition. I just imaged one with the 1.2 server then the 1.3 and the imaging went through correctly. I’m wondering if it was because the other computer we tested with was previously encrypted or maybe the SSD was bad? I’ll have to wait till we get another machine in for re-imaging that is encrypted although this wasn’t a problem in 1.2.

I’m doing one more machine now and hopefully that works. I apologize for wasting time on this.

Thanks.

@x23piracy I have two machines that I’ll image here in a bit with 1.2 and then get back to you with the partition layout in Windows. One is the same model in the picture from before and one is a different model.

@Tom-Elliott None of the images are working from the copy over from 1.2 to 1.3 but I’ll test on a couple machines here in a bit. I have that same model from earlier as well as another I can test with again. If I do a capture and deploy from 1.3 it works fine though, but I’d rather not go back through our images and recapture if I can help it.