To clarify, all I’m doing is modifying the MAC address on a host in FOG and clicking the update button. After that, when refreshing the page, I noticed it added the old address as an additional MAC. You might not see it until you refresh. I’m not clicking any other buttons related to adding an additional MAC. FOG just adds one itself.

@brakcounty Having two network interfaces configured for the same subnet (found by performing an AND with the interface’s IP address and subnet mask) but not having those interfaces actually connected to a common network is going to cause problems. When sending traffic to an IP address, a routing table is consulted to direct the traffic to the appropriate interface. If there is no differentiation between the interfaces, then you are depending on the order in which the routing table was built to determine to which interface outbound traffic is sent. As there are a number of things that could trigger a change to that table, such as media disconnects, reboots, and dhcp lease expirations (if your fog server is not configured to use static addresses), access to the machine through both interfaces will be unpredictable. You should change your network configuration so that the interfaces are in different networks.

Some options. 1º Use a snapin pack including the executable. 2º Put it in a ftp server and use a cmd ftp client to download it. (You can use the fog server/node as ftp and the built-in ftp client) This two solutions works!!!

@f-an what does your storage subsystem look like?

@Deimos Isn’t that what command and configure is for (if you’re a dell shop at least)?

@Brad-Schumann said in Blank Screen with Blinking cursor in top left corner: Would a Windows, bios or driver update have this affect The short answer is no. Older firmware on the target system might. So just for additional clarity the 5570 is in uefi mode? If so then we have an issue with rEFInd executable not finding the disk controller. When the FOG iPXE menu exists it calls refind to locate the hard drive boot device to boot the target computer.

@Sebastian-Roth Sorry about that. I was just showing an example of what modifiers I used. (-S, -y, -K, -C) And the combinations I tried with them. I do install fog as a root user, but I have a habit of using sudo anyway.

@Lee-Rowlett said in Access Control Plugin: removehosteditgen.hook.php Lee, I searched everywhere for that file and cannot find it.

@Testers Anyone able to replicate this?

@Fernando-Gietz it worked before, not sure what version it changed in.

@darkxeno In the dell firmware switch the disk controller from Raid-on to AHCI mode. Unless you have more than one disk connected in a raid configuration raid-on mode doesn’t help you. There is a document issues between linux and intel controllers in raid-on mode. Once you have imaged with fog you can switch back to raid-on mode or leave it in ahci mode. It doesn’t matter to windows.

What device is your dhcp server. I’m going to guess it is a soho (home) router? The reason I think this is your gateway is 192.168.0.1 and your next server (from the picture) is also 192.168.0.1. Home (soho) routers will often say they are the pxe boot server and not the fog server.

@Sebastian-Roth if I had to guess it’s lvm setup.

@george1421 said in Capture problem: I have noticed an uptick in people reporting this invalid storage group. Aß mentioned in my last post it’s not the same error message everytime. A couple of times we hat the “Invalid Storage Node” but this one is not.

George, I have another question, this time about sysprep. Why do we need to go through OOBE for an installation that is all in the same locale? Wouldn’t it be easier to just generalize and be done? And if doing that, do I still need to disable the Fog Client Service before doing it? Thank you, Dave

@andrewhancock91 I am on the road right now und will be for the next two weeks. Not easy to give you all the details not having my laptop with me. First you should start by searching the forums for “https fog-client” and see if you can find my older posts about why this part is tricky. It’s not a no-go but it will need good planing and manual adjustment - could even compile your own custom fog-client package… For switching back to HTTP for now you’d edit /opt/fog/.fogsettings file, find the line httpproto=https and remove the “s” at the end of “https”. Save and re-run the installer. That should be it. Make you read all you can find on this topic before diving into this again. If you have many hosts with fog-client installed and communicating to your current FOG server already you break this switching your apache config to a different certificate! Feel free to ask here if you can’t find those forum topics.

ill take a look next time i capture. i make sure the actual image size is the compressed, used data from the drives i capture, in the terminal using dh -u. we use a custom sccm image that is based on the stock windows install, which has bitlocker disabled.

@dario-vettore Try testing aß suggested in the wiki: https://wiki.fogproject.org/wiki/index.php?title=Troubleshooting_a_multicast Are you sure there is no firewall between FOG server and the clients??