@Joseph-Hales Thank you sir, yes, it would appear that may be a best practice that has to be instated. Even though I regularly update images, at no more than 2 month cycle, it shouldn’t add much extra work to the process in total.

@alh said in Group Management: Handling Conflicts:

So if I change the settings of a group, this change is applied to all members of the group overwriting the settings received through “earlier” group memberships?

Yes.

@tri_94 said in Active Directory Joining:

I can get it to join if I wait till the machines are imaged and then un-tick and re-tick the box to send the command again.

This doesn’t send the command again. The FOG Client gets it’s information via polling the server every x amount of seconds, default is five minutes. The server doesn’t initiate a send, the client does. On every single pole, the FOG Client is given all configuration the host should have from the server - similar to how Puppet works in a way. It sounds to me like you’re probably experiencing a server bug in what is probably an older version of FOG - The latest is 1.4, I strongly suggest you upgrade to it.

The only things the FOG Server initiates a send of are WOL and Multicast and pings, replication, maybe a couple other minor things. Most client side activities is completely controlled either by the FOG Client or network booting via some method at the client.

@Wayne-Workman @george1421 thank you both so much. you’ve been incredibly helpful!

I just wanted to post to close this out.

I got a test environment working with better switches and FOG was able to pass 64-bit UEFI traffic correctly the first time, every time. Thanks all for the big help! I really appreciate it!

#wiki worthy

@RobertFontaine If will be interesting to see if you can make it work.

Wow … that one almost got lost to the mists of time.

Yes. An update.

I don’t remember precisely when, but I think it was soon after I made this initial post that it started working again.

Regardless, I’m currently running 1.4.0-RC-4 and I just tested on both types of VMs for this reply and they work.

Gen1 (Legacy) picks up undionly.kpxe and Gen2 (UEFI) pulls down ipxe.efi on Hyper-V 2016 VMs .

@watson you just need to elevate your privileges to edit the file. what do you mean you lost the images?

Thanks for your reply, I have installed the IGMP protocol on my routing server under windows server 2008 but I do not know how to configure it and I do not find much about this on the internet, could you explain to me How to setup this?

@fmslick said in Booting ISO issue / Mount /dev/cdrom:

I am working on moving the files off my fog server and on to a file server

There was also guidance for using both nfs as well as CIFS (windows) share depending on the file server you intend to use. The use of the fog server is not a requirement of this setup.

But great!! Case solved!!

@wanderbread Ah yes ISA cards. Glad I left them behind back in the 1990’s…

Watch the IRQ number, make sure its not shared with another device in the computer. The ISA cards had a jumper to select the irq port. irq 3 and 4 were for the serial ports. irq 2 was for the printer (I think). That left irq 5 and 7 open for add in cards (confirm with ancient text documents to be sure). Could the on board nic be interfering with the add in one?

I fail to see how this is a bug. This has been the case since 1.3.0 was released and discussed on numerous occasions.

@jamcdonald120 Well what I wanted a bit of clarity on is this. Tom saw as well as I saw in your files that you were / are sending the wrong boot file to this computer.

There are two types of boot files and its important to configure the right one to be sent to the right type of hardware.

There is the undionly.kpxe boot file, that is for bios (legacy) computers. And there is ipxe.efi that is for uefi based computers (as in the one from the pictures). If you have a mix of computers (bios and uefi) in your environment you will have some difficultly with imaging. There are ways to work around this but knowing what you are deploying to is the first step.

@daUK2010 Yes, you can restart the process, but if you’re low on space, you’ll want to clear out the folder with the mac address as name of your current capture computer in /images/dev

@Hanz Login history has not been removed at all.

Is there an ALLUSERS switch you can add on? It’s likely as Tom mentioned, it’s only adding shortcuts under the account used to install it.

If there isn’t switch to install for all users you could write in your batch the commands to copy to the public desktop and start menu.

Assuming that messenger-setup.exe and the shortcut file are in the same root location as the installation script, something like this should work:

CLS ECHO Installing School Messenger... Do not close. ECHO. CD %~dp0 START "School Messenger" /wait "messenger-setup.exe" /verysilent SLEEP.exe 10 COPY "School Messenger.lnk" "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\School Messenger.lnk" COPY "School Messenger.lnk" "C:\Users\Public\Desktop\School Messenger.lnk" CLS ECHO Installed School Messenger ECHO. SLEEP.exe 5 EXIT

If that doesn’t work, maybe provide the application so others can test it.

@Wayne-Workman said

@Joe-Schmitt Yes I can, #wiki worthy.

@Wayne-Workman Here is some info I’ve gathered for consideration as a potential starting point for a Wiki article on FOG Rebranding.

Rebranding was introduced to the FOG client in version 0.11.6 of the client. It has since been improved with additional features. So to clarify, the information in this posting refers to FOG client version 0.11.12, and FOG version 1.4.0-RC-5 (dev-branch).

The following was pulled from fogproject/packages/web/commons/schema.php found at
https://github.com/FOGProject/fogproject/blob/33586365cea09444b5f35c071e72d3357462b220/packages/web/commons/schema.php
sections 240 through 243 (currently lines 3499 through 3574).
The first quote for each setting is the popup text currently displayed in the web GUI, except for
the two settingDesc quotes which are used as the GUI popup text for their respective settings.

FOG_CLIENT_BANNER_IMAGE ‘This setting defines an image for the banner on the fog client.’
settingDesc=‘This setting defines an image for the banner on the fog client. The width must be 650 pixels, and the height must be 120 pixels.’

FOG_CLIENT_BANNER_SHA ‘This setting stores the sha value of the banner to be applied.’

FOG_COMPANY_NAME ‘This setting defines the name you would like presented on the client.’

FOG_COMPANY_COLOR ‘This setting is the hex color code you want progress bar colors to display as.’

FOG_COMPANY_TOS ‘This allows setting the company terms of service.’

FOG_COMPANY_SUBNAME ‘This allows setting the company sub unit.’
settingDesc=‘This allows setting the sub unit, and is only used on the Equipment loan report for tracking.’

The following was pulled from the original announcement at https://news.fogproject.org/fog-client-v0-11-6-released/

Rebranding
This release includes the ability to rebrand the shutdown prompt. This means you can change the colors, text, and images of the prompt to match your company’s. While this feature is free, we ask that if plan on using the rebranding option please consider providing a donation https://sourceforge.net/donate/index.php?group_id=201099 .
To set these options, go to FOG Configuration -> FOG Settings -> Rebranding.
Notes:
FOG_COMPANY_COLOR: This option is a hex value of your company’s color
FOG_CLIENT_BANNER_IMAGE: This should be a PNG image with 650x120 dimensions, note that the background can be transparent. See the default banner for an example. https://github.com/FOGProject/fog-client/blob/master/resources/banner.png (fog-client/resources/banner.png).

Additional notes and info.

FOG_CLIENT_BANNER_IMAGE
This setting is used for more that just the FOG client shutdown/reboot prompt. For example, it is also used as a heading within the PDF exports of certain reports. It is NOT used to rebrand the background image during network/PXE booting (that screen continues to use the default FOG branding). As noted above, the background for the banner image can be transparent. This is an option, not a requirement. The PNG file can have any arbitrary name when uploaded into the web GUI. However, when automatically copied to the clients, the image gets renamed to “banner.png” and is saved to the clients’ program installation folder (depending upon a check-box selection during the initial client installation). On the server, uploaded files are saved in the directory /var/www/fog/management/other. One can disable the custom banner image (which returns to using the default FOG banner image) from within the web GUI via the browse button (up arrow). To do so, simply submit a blank path. The banner.png file remains on the clients even if the FOG_CLIENT_BANNER_IMAGE setting is cleared. But the remaining banner.png file will not be used by the clients unless it is enabled/resubmitted via the web GUI.

FOG_CLIENT_BANNER_SHA
This field uses the SHA512 algorithm to automatically generate and display a hash value when a banner image is uploaded via the web GUI. This field is used to detect differences between the source banner image file on the server and the copies on the clients. Upon each and every client check-in event with the server, the client recalculates the SHA512 value of its current banner.png file and compares it against the SHA512 value calculated on the server. If the hash values do not match (or if there is no banner.png file on the client), the client will download the banner image file from the server, rename it and overwrite any existing banner.png file on the client. This effectively identifies and self-corrects for cases of tampering with the banner.png file on the client, and it automatically keeps the banner image file on the clients up-to-date whenever the file gets changed on the server.

I don’t have immediate plans to use the remaining four rebranding settings. So I have not tested them, and therefore don’t have anything additional to add for them.
FOG_COMPANY_NAME
FOG_COMPANY_COLOR
FOG_COMPANY_TOS
FOG_COMPANY_SUBNAME

I hope this is useful as a potential starting point for a Wiki article on FOG Rebranding.

Will do. I agree, not an issue for me. Thanks for letting me know.

@Tom-Elliott I vote to just remove the donate feature.