Posts made by nitelife

@Sebastian-Roth
Here is Master
https://ibb.co/c4Mc5Q
Here is Clone that wont boot
https://ibb.co/jP5tek

Thinking its something to do with BCD, MBR or partitions since a repair boot from a Windows 7 disk fixes it.

I checked my main image. For some reason there was a 100mb boot partition, then a 1gig Unallocated Partition and then a 280gb Windows Partition.

After the system was cloned the Partitions were different on the machines that wouldnt boot. The 1gig unallocated partition was at the end of the drive.

I fixed the partitions by removing the 1gig partition on my master image and moving the windows partition to the proper spot and expanding it another gig so there was no unallocated space.

Sent the image back up to the fog server and still get the same error.

@Tom-Elliott Just noticed that the partition size on my source was not expanded to the full disk. Fixing that and sending new image up. Hoping that was issue.

@Tom-Elliott They are the same model and same hardware and same os. The 4 working carts have alot more software on them like Adobe CS6 where the 3 that don’t work just have Windows and Office 2013

@Tom-Elliott
Running Version 12
SVN Revision: 6079
Jul 19, 2017 13:55 pm
Was running 1.4.4 but thought upgrade might fix

No its a complete image. We don’t use sysprep as we arent that advanced yet. We use deepfreeze so all images are the same base with different software for different classrooms.

Server

• FOG Version: 1.50
• OS: Ubuntu 14.04

Client

• Service Version:
• OS: Windows 7 x64

Description

Hi,

We have been imaging carts of laptops all HP 6475. 4 of the carts imaged fine but 3 carts are giving a 00000000f error (Failed to load Registry) on boot. These 3 carts have a different image then the other 4. I can restore an image from the working carts to it and if I take my master image from the original computer it will boot in a computer that would not boot after being imaged.
I ran chkdsk on original image. All Bios are set the same and using AHCI not IDE. Sent the image up a couple times to the server thinking it may have become corrupt or something.
Can boot off a windows usb and repair the bcd and the system will boot fine but its a pain to do this on 45 computers.
Suggestions?

@george1421 Our DHCP Server is housed on the other side of town. It hands out 10.95.7.* ips. We have our fog server set as 10.95.51.2 and its set in the DHCP Server for PXE requests to go there. 390 computers work flawlessly. ITs just these 10 that right after host registration or imaging looses the ability to ever get an IP again.

Tried different ports in switches. Plugging into our managed Cisco Switches. Deleting the old host IP out of the DHCP Server.

Just seems weird the computers worked fine before host registration or imaging it can no longer get an IP. Just making sure Fog cannot cause it somehow.

Possibly its blacklisted now on the DHCP Server somehow? Any other thoughts that may help?

Thank you

Are you thinking it is somehow and that is the issue?

using the kde.proxyonly or whatever that setting is on our dhcp server so no.

Server

• FOG Version: 1.44
• OS: Windows 7

Client

• Service Version:
• OS:

Description

Hi All,

Having a weird issue here at a school I manage.

I have 400 computers in a school I manage. On about 10 of my machines I had PXE Boot and did a full host registration. On these 10 machines from that point forward they are no longer able to get an IP from PXE boot or an IP in Windows.

Just curious if there is something in the Fog Server causing these to never get an IP again before I go and yell at our DHCP admin to fix it since they say there is no issue on their end.

Thank you