@george1421 you are a wizard.

thats fixed!

now onto my next thing. heres to hoping that once i can grab a HDD big enough for my images that can support these ginormously underused HDD’s in these labs…that all is good 🙂

Yes you can.

Duplicate post: https://forums.fogproject.org/topic/13510/has-any-one-installed-fog-on-a-raspberry-pi

@Sebastian-Roth sorry it took so long, but I finally was able to create a separate thread in bug reports. https://forums.fogproject.org/topic/13486/fog-1-5-6-pushbullet-plugin-not-functioning

We are in the midst of reassembling classroom tech after the custodians did their cleaning so that is what caused the delay.

@Sebastian-Roth will do.
Thank you

@lucycle We’ll follow this one here for now: https://forums.fogproject.org/topic/13125/fog-postinit-not-executing-fog-reg-man-fix

@Quazz
You had the same. https://forums.fogproject.org/topic/7324/small-text-display-bug-image-capture
I should have seach before asking…

VirtualBox_vm1_28_06_2019_15_34_37.png

@george1421 Can confirm, had to switch to ProxyDHCP after the ISP upgraded the modem that has a buggy DHCP implementation (turning off DHCP makes it not give out IPs but the DHCP server is still running so it just NACKs all the IPs lol)

@mikmatcr OK since I still have the development system setup I just spun up a Gen2 vm client. MDT is currently building the golden image. I did see that they changed the disk controller to SCSI. It will take about 1hr for MDT to finish the build. I’ll get some bench mark numbers after that.

@geardog said in Resize failure?:

A cold boot with fast-start disabled allowed a good capture.

Just for another option:

Let sysprep power off the computer after its run Run the following command from a command prompt shutdown -s -t 0

Both of those commands will ensure that the system is properly powered off and ready for image capture.

@krejci You are going to have a difficult time finding a server that meets your requirements, especially with a 31cm depth. Maybe a 37cm depth, but 31 will be really difficult unless you have a custom system. One issue is that 31cm is close to the ATX style motherboard in size. Also to get >10TiB drives you need 3.5" drives since 2.5" drives are not at the 10TiB capacity yet.

I did find this chassis with a 40cm depth, but it is a build your own server. Its not an already complete server, just the chassis: https://www.newegg.com/p/N82E16811219052

In theory you should be able to get FOG running on a synology nas since the nas OS (DSM) is based on linux. I have not tried to do this, but DSM has most of the components needed. You may need to add additional RAM to the rackstation to support both DSM and FOG. Again, I can’t say for 100% sure it will work, only it should work with some hard work. I can say I have turned a synology nas into a FOG Storage Node (not the main server) before, and it works. I have a tutorial here: https://forums.fogproject.org/topic/9430/synology-nas-as-fog-storage-node

@Fernando-Gietz
Well, you may not intend to support such at the moment, but it does work in 1.5.6 provided the groups are specified in the web interface as a comma separated list, which may cause its own problems for some group names. It actually doesn’t look like much more needs to be done to flesh out that first enhancement beyond the UI elements and input validation. 🙂

I would suggest taking a look at the sequence of events for the bindings and searches, or at least making sure that the permissions contexts in which those searches occur are consistent. I think the quick and dirty fix I put in at line 547 won’t mess up anything, but I don’t have a lot of experience with either php and ldap.

And for posterity (read: when I forget what I did), diff against ldap.class.php released with 1.5.6 for the changes to address the issues for this thread:

547a548 > $bind = @$this->bind($bindDN, $bindPass); 616,617c617,618 < '(&(|(name=%s))(%s=%s))', < implode(')(name=', (array)$adminGroups), --- > '(&(|(cn=%s))(%s=%s))', > implode(')(cn=', (array)$adminGroups), 640,641c641,642 < '(&(|(name=%s))(%s=%s))', < implode(')(name=', (array)$userGroups), --- > '(&(|(cn=%s))(%s=%s))', > implode(')(cn=', (array)$userGroups),

Well this will get a little complicated to explain, but lets try.

Traditional pxe booting requires dhcp options 66 and 67 to be set with the proper information namely the next-server and boot-file settings. In a normal environment that is all that is needed to pxe boot a device.

Now enter a network function called ProxyDHCP. A proxy dhcp server can be configured to override what is set in dhcp options 66 and 67. FOG can use a ProxyDHCP server in cases where the main dhcp server can’t be modified such as in a managed service. For the FOG/linux world you would install DNSMASQ which can be configured as a proxy dhcp server. ProxyDHCP servers work over broadcast messages. So if you have a ProxyDHCP server on one subnet it will not hear or respond to pxe boot requests on a different subnet unless you have the ProxyDHCP server configured in the dhcp-helper/dhcp-relay service on your subnet router.

SCCM / WDS has a built in ProxyDHCP server. So that is why your dhcp options are being over written with the SCCM boot loader. If you want to block / stop this there is a netboot service on your SCCM server that you need to stop.

If you want proof this is happening you can use wireshark on a computer on the same subnet as the pxe booting computer that connects to sccm instead of fog. If you use the capture string of port 67 or port 68 or port 4011 then capture the pxe booting process.

When you look in wireshark you will see

Discover sent by the client. (2) Offers one from your dhcp server and one from sccm Request from the client ACK from the dhcp server You probably won’t see this unless you run wireshark on your sccm server, but he client will talk to the proxydhcp server over udp port 4011 to get the pxe boot information.

@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!

@Sebastian-Roth

It looks like these files fixed the issue. 🙂

@cmurray139 Just to add a bit more information. default.ipxe -> http://x.x.x.x/fog/service/ipxe/boot.php

But I guess you will run into another issue as the FOS Linux system is another environment that you’d need to use the fake MAC address…

Nevertheless it’s an interesting idea. Please give it a try and see how far you get. Let us know what you find out and if we can help you with anything.

@Quazz Thanks for the help. I really appreciate.

Thank you all for your responses. Thye have been very useful.
I’ve been able to do it using a real machine. It was indeed a Virtualbox problem.

The only time you will impact current systems in production is if your current environment relies on dhcp next-server (option 66) or boot-file (option 67) or uses ProxyDHCP (udp port 4011) to communicate configuration files to your booting devices (such as a voip phone needing to find the pbx system to get its configuration file). If a booting device never attempts to get booting information from dhcp then there is no impact.

Having FOG and either Microsoft’s WDS or SCCM on the same network will cause conflicts.

@george1421 I forgot to mention that in my notes. I will fix that. Changing fetch=tftp://${fog-ip}/gparted/filesystem.squashfs to fetch=tftp://<fog_server_ip>/gparted/filesystem.squashfs worked just fine and booted properly.

@LindsayS said in AD Join:

it would auto-encrypt the password

Have you used the old legacy client before? With the new fog-client we don’t do the password encryption anymore.