Posts made by imagingmaster21

@sebastian-roth
How do I get that information, you just want a screenshot of the disk management of a computer with the image deployed to showing this problem? Or you need something else?

I have made a Windows 10 image on a VM (VirtualBox). It was originally made by someone who did it in Legacy rather than UEFI so it needed converted, so that was done prior to it being captured.

The problem is that when you deploy the image to any machine it shows the Harddrive is only 50GB large, which was the Size of the VM. I am able to fix this after deploying the image but it kinda takes up to much time.

Example of how it shows on a machine after being deployed:

• Partition 50 GB Capacity

• Unallocated storage 400GB capacity

I can expand the 50GB with the unallocated 400GB capacity and fixes it , but takes an extra 5 minutes per machine which is a bit of a pain.

I am thinking converting from Legacy to UEFI screwed the image up, but I am wondering if anyone knows of any easy fixes for this issue?

Rather than having to fix it each time, which takes about five minutes or rebuilding the image. The image is set to a compression of 10, GZip, and Single Disk Resizable. Could changing any of the settings fix this?

@boyan-biandov I’ve laely bene building images off Virtual Machines and not running Sysprep Before capturing I just do a command of:

shutdown -s -t 0

I hae not had any issues with both Windows 7 and 10, with it being a VM it does just as good if not better at getting drivers after imaging on actual machines than with sysprep.

@boyan-biandov
On one of the machines affected can you launch Command Line elevated and run this:

sfc -scannow

Let me know the results, this will check for integrity issues with Windows. I haven’t seen this issue in particular but dealt with strange issues and running this scan sometimes fixes it. It is worth a shot. Along with @Joe-Schmitt suggestion of the app data folder.

@EJoc242
Connect one of those computers at a time to FOG server and run a TCP dump. Once you know the vendor id try modifying that in your DHCP settings.

@ddavis
If rebooting the server does not fix the problem it could be an apache problem, you could run a

tail -f /var/log/apache2/error.log``````

let this run and see what you get when you try modifying your changes.

@Malos Have you tried changing this in the BIOS? You should be able to do this in the BIOS easily, Windows does not really modify anything in the BIOS unless you make a script specific to your BIOS. I honestly would just remove the Windows Boot Manager. Making the hard-drive first boot priority in the end should resolve it, while having PXE as second boot option.

@zago123
Here is a link that explains how to format/create partitions. You will need a Windows boot media. So when you get this up, you will need to identify which partition you want to do which task to (format, create, etc.). Make sure you are careful with this and do the wrong partition by mistake.

Links:

• https://davidzych.com/install-windows-10-from-a-usb-flash-drive/

• https://davidzych.com/install-windows-10-from-a-usb-flash-drive/

@wayne-workman

Going from 1.5.0 to 1.5.2 resolved the issue.

@wayne-workman
Upgraded the version to 1.5.2 and capturing and pulling the image seems to be working correctly now. What would have cause this issue, just a bug in 1.5.0 that was fixed in 1.5.2?

@wayne-workman
I am running 1.5.0-RC-9, would upgrading 1.5.2 fix this potentially?

@Wayne-Workman @Sebastian-Roth
I was looking at this here:
https://forums.fogproject.org/topic/7256/no-dhcp-response-when-trying-to-inventory-a-host-fog-trunk

I seen about trying a standard switch to see if it worked. So I grabbed a 5 port switch and still did not work. Here are some more screenshots:

• https://dl2.pushbulletusercontent.com/TjpLuWB0KKYGzdG41NsrvEeg1JoKErgy/20180517_133337.jpg
  -https://dl2.pushbulletusercontent.com/t1T9aZUgVR6dnnp23c74YsfDMYaoH9zk/20180517_133341.jpg
  https://dl2.pushbulletusercontent.com/zmul5sOnbxVi1AsknychwMCzYWxezeuQ/20180517_133343.jpg

I did use trunk to do the upgrade fro 1.4.4 to 1.5.0.

@wayne-workman
I just tried this on a switch that another FOG Server running the same version worked on. The FOG Server that I am having issues on still does not work on the known good switch. So it is not the switch.

Any idea on what the culprit could be in DHCP?

@wayne-workman
The switch is… Pvst+ It’s basically a unique spanning-tree per vlan, but its running standard spanning-tree over them (not rapid)

@wayne-workman This worked before we upgraded from 1.4.4 to 1.5.0. We haven’t changed anything on the switch and all the settings are correct on the switch I verified those before.

@wayne-workman
https://dl2.pushbulletusercontent.com/J08p9FQbsYLXGwN5l8vqu3Z98q9LnLhP/image.png
Is the status.

@Wayne-Workman
Here is what my DHCP looks like.
https://dl2.pushbulletusercontent.com/sqF0fk0cF5pcqG4a0ZesbQK5ooEeBAet/20180517_120927.jpg

https://dl2.pushbulletusercontent.com/sqF0fk0cF5pcqG4a0ZesbQK5ooEeBAet/20180517_120927.jpg

https://dl2.pushbulletusercontent.com/z8gfNItC5aXxVxn92EgdjkEX1BqVVQHX/20180517_120911.jpg

@wayne-workman DHCP is dealt with on our FOG Server. I made sure DHCP settings were the same as form before we did an upgrade.

I recently updated FOG from 1.4.4 to 1.5.0. When I go to capture a image off a host it gives this error:
https://dl2.pushbulletusercontent.com/U0KLNaXqAMHQxsyMAsmlwyVtQpAzAglH/20180517_100332.jpg

It seems it is trying to start Eth0 network interface,

The FOG webui loads fine and DHCP is not giving any errors I just cannot capture any images.

Also as a side note we did add more storage and moved the images directory to another drive with a SIM link, not sure if that is realeted or not.

IF I got to deploy an image it does try to do Eth0 and fails and ask you to hit enter and it ends up deploying no problem. My issue is only with capturing.

Also if you trace DHCP when a machine connects via PXE boot it shows it by IP and says it does not accept TFTP options.

@sameer
Try going by this link to correct this problem on your DHCP server.
https://wiki.fogproject.org/wiki/index.php/Modifying_existing_DHCP_server_to_work_with_FOG