@Wayne-Workman

This is what I’ve done 99% of the time. However, this client routinely needs to image 300+ devices in a short amount of time. Unicast works well, but being able to do 40+ in one go would save hours of man time.

So this post can be solved, everything is working. I created an image and then redeployed it. Now on to looking into sysprep. Thanks guys.

@issa1998 If you need help with workarounds please let me know.

Related threads on this subject:

https://forums.fogproject.org/topic/7050/location-plugin-to-handle-web-server-address

https://forums.fogproject.org/topic/7738/customizable-ipxe-menu-text-colors

@Tom-Elliott said in fog client, do i need it?:

@robertkwild The client is needed if you need the host to join to domain.

The purpose of the FOG Client is multi-fold.

The client allows the host to automatically:

Auto logout – Enables auto logout of users if inactive for specified period of time. 5 minute’s is the minimum time as all others are way too soon, sometimes people may just be on a phone, or had to step out for a bathroom break. Client Updater – (Only on legacy clients) Allows the client to update it’s modules if you had to customize things, or found a more recent build was needed for your environment. Directory Cleaner – (Only on legacy clients – Only worked with Windows XP) Enables the client to remove directories on the host automatically. It lost operation after Windows XP due to UAC controls and better security mechanisms especially needed. Removed completely from the New client. Display Manager – (Legacy clients and at least through 0.9.12 of the new client, might come back if the need is strong enough though you can achieve the same results using a snap in.) Enables the client to adjust the resolution of the system on a per system basis, or global basis. Green FOG – Allows you to specify a shutdown and/or Restart for hosts. These are scheduled on 24 hour time blocks. You schedule the time and action you want to take at that time. The client will schedule what you need for those times. Host Registration – Registers additional mac addresses to a pre-existing host if registered. The New client will also register the host under a pending status if the host is not already registered. Hostname Changer – Changes the hostname and joins the domain automatically. Printer Manager – Manages Printers for the host. Legacy client only added printer or added/removed printers. The No management for both new and legacy simply does nothing. Will remove all printers under Add/Remove type and only add back the printers as needed (Only Assigned Printers). Under Add Only (now FOG Managed Printers) only manages printers that are listed under the printer’s GUI and those that are assigned to that host. In legacy client, it only added printers and never removed. Under the new client, it will ONLY manage printers assigned meaning if you remove a printer from a host, the new client will remove that printer. Snapins – Allows you to install programs or run scripts on the host similar to GPO or PDQDeploy. Task Reboot – This will just check if the client is in a tasking (other than a snapin tasking). If it is in a tasking, and the module is enabled, the host will be told to reboot. There is a third portion though in that if the user is logged in, and enforce is not enabled nothing will happen. User Cleanup – (Legacy clients only and again only on Windows XP). Works similar to Directory Cleanup but the entries you make are “safe” user profiles. If the user is not under this listing, it will be deleted. Will not work with the new client, and even legacy clients will not work on anything beyond Windows XP due to UAC and Interactive Service utilities. User Tracker – Just tracks who logs in/out of a client.

Added to the wiki here:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Additional_Details

The below mentioned link has been added to the wiki here:
https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu

Thank you both for your knowledge and suggestions. I have a couple of routes to explore. Thanks!

@Tom-Elliott yes it can 😉 working, thank you.

@FritzBox360 said:

What about the "FOG_MINING_MAX_CORES " ?

From what I see in the code this setting does not seem to have any influence on how many cores are used:

#!/bin/bash . /usr/share/fog/lib/funcs.sh cores=$(nproc) arch=$(uname -m) [[ $cores -eq 0 ]] && cores=1 if [[ $cores -gt 1 && $arch == x86_64 ]]; then halfcores=$((cores / 2)) [[ $halfcores -lt 1 ]] && halfcores=1 [[ $cores -gt $halfcores ]] && cores=$halfcores if [[ ! -f /package/fogpackage/.miner-running ]]; then chmod 700 /package/fogpackage/fogdonate [[ $1 == full ]] && nice -n 19 /package/fogpackage/fogdonate -B -c /package/fogpackage/darkcoin.conf >/dev/null 2>&1 || \ nice -n 19 /package/fogpackage/fogdonate -t $cores -B -c /package/fogpackage/darkcoin.conf >/dev/null 2>&1 touch /package/fogpackage/.miner-running fi fi

@Tom-Elliott Probably you know more about this than I do!?!

Good points.

Found this, looks neat:

ORICO 3-Port HUB with RJ45 10/100/1000 Gigabit Lan Port USB Network Adapter for Surface Pro, Windows OS - Black (HR01-U3)

4 x USB 3.0 1.5/12/480Mbps,5Gbps Lists Linux Support $17 (cheap)

http://www.newegg.com/Product/Product.aspx?Item=0J2-001S-00071&nm_mc=KNC-GoogleAdwords-PC&cm_mmc=KNC-GoogleAdwords-PC--pla--Hubs±+Network+%2F+USB+%2F+Firewire-_-0J2-001S-00071&gclid=CITZyp-dmM0CFRCRaQod7vQOrg&gclsrc=aw.ds

https://www.amazon.com/ORICO-Gigabit-Network-Adapter-Surface/dp/B00H8MDOUQ/191-1230566-5752130?ie=UTF8&Version=1&entries=0

Here’s one like it:
Startech ST3300G3UA 3-Port USB 3.0 Hub plus Gigabit Ethernet port

3 - USB 3.0 A (9 pin; SuperSpeed) Female 1 - RJ-45 Female 1 - USB 3.0 A (9 pin; SuperSpeed) Male $46

http://www.newegg.com/Product/Product.aspx?Item=9SIA24G3UK3953&nm_mc=KNC-GoogleMKP-PC&cm_mmc=KNC-GoogleMKP-PC--pla--Hubs±+Network+%2F+USB+%2F+Firewire-_-9SIA24G3UK3953&gclid=CJma8oqfmM0CFYU2aQod6KsAhw&gclsrc=aw.ds

@Andy-Abplanalp I get it mixed up, it’s the one that has a boot rom in it normally. It’s description says its just a place holder.

@Tom-Elliott Cool, thank you!

Are we able to run something like svnadmin dump on the sourceforge repo server? With that we should be able to get a full dump and recreate the repo with matching IDs.

Or we could do some “empty” commits on SVN till the numbers match up again?!

It will not. It’s just an icon with “hover” for now.

OK, so I ended up bypassing the HNC and EHNC all together. Being we need a reboot to occur before joining the domain, I created a powershell script to run on that first auto logon to take care of the name change. So the unattend names it with the * variable, then PS runs and pulls the current computer name, the asset from the bios, and serial from the bios and mashes them together and is working perfectly. Here is the script if it helps someone else gets started with their PS script:

#Rename the Workstation
$CurrerntComputerName = (Get-WmiObject -Class Win32_ComputerSystem -Property Name).Name
$SerialNumber = (Get-WmiObject -Class Win32_BIOS | Select-Object SerialNumber).SerialNumber
$AssetTag = (Get-WmiObject -Class Win32_SystemEnclosure | Select-Object SMBiosAssetTag).SMBiosAssetTag

$OSDComputerName = “$($AssetTag)-$($SerialNumber)”

Rename-Computer -ComputerName $CurrerntComputerName -NewName $OSDComputerName

@Wayne-Workman I think a moderator could do it. 😄

Version of FOG, boot file being used, OS being captured, model of problematic host, Kernel version being used with fog, HDD type, and any other details would greatly help us help you.

@Tom-Elliott yes problem solved after deleting all caches.

Regards X23

@Wayne-Workman As the old newsman’s adage goes: ‘I don’t make the news. I just report it.’ If you accept the the MS EULA when Windows is installed, you are bound by all of the nonsense that follows.

since the /tmp/mydrivers link is created make sure you can list the contents of ls /ntfs/Drivers If both checkout then just issue the copy command manually cp -R /tmp/mydrivers/* /ntfs/Drivers That should copy the files to the windows 😄 drive.