fog client, do i need it?

[robertkwild]

hi all,

before i capture my sysprep windows 10 image, shall i install the fog client, are there any benefits of installing it?

the machines im going to be deploying the image to are going to be domain machines if that helps

many thanks,

rob

[Wayne Workman]

You absolutely do not “Need” the fog client.

However - you probably want it.

It will rename computers for you and join them to the domain for you, saving several hours of post-deployment manual labor. With many, many other added features.

If you are going to include the FOG Client on your sys-prepped image, there is one extra step that you must complete, it’s pretty basic. You can find steps here, in the “Sys-Prep” area towards the bottom:
https://wiki.fogproject.org/wiki/index.php?title=FOG_Client

[robertkwild]

nice adding it to the domain would be nice, i have seen that setting on the fog server for the host

[Wayne Workman]

@robertkwild There’s also a global default you can fill in inisde FOG Configuration -> FOG Settings -> Active Directory. With that filled in, whenever you click the checkbox for joining a domain via an individual host or group, it’ll auto-populate with the defaults you have set. The global default is also what’s used when you do a full host registration via network booting with FOG and saying “Y” to joining the domain.

[robertkwild]

so do i need to install the fog client on the computer or can i just select the host from the fog server and tick connect to domain?

[Tom Elliott]

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

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. Hostname Changer – Changes the hostname and joins the domain automatically.
8. 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.
9. Snapins – Allows you to install programs or run scripts on the host similar to GPO or PDQDeploy.
10. 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.
11. 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.
12. User Tracker – Just tracks who logs in/out of a client.

[Wayne Workman]

@Tom-Elliott wiki worthy

[Junkhacker]

@Tom-Elliott for good reasons to install the client, Hostname Changer, Snapins, and Task Reboot are the big ones, in my opinion.
it’s worth noting that when you do a standard deployment task for a host, any snapins assigned to it will also have their snapin tasks assigned to be done once imaging is complete.
that means that having a computer:

1. reboot itself
2. reimage
3. join the domain (and put itself in the OU you’ve assigned it to)
4. install any software you have assigned to it / run any scripts you need run

only requires scheduling a single task in fog. and you can even do it to whole groups of computers at a time.
you miss out on a lot of what fog can do if you don’t have the client installed.

[Wayne Workman]

@Junkhacker I did not know that associated snapins run on image deployment… that explains a LOT…

[Junkhacker]

@Wayne-Workman lol, that’s why there’s a “Deploy - No Snapins” task in “advanced tasks”

[Wayne Workman]

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

1. 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.
2. 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.
3. 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.
4. 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.
5. 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.
6. 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.
7. Hostname Changer – Changes the hostname and joins the domain automatically.
8. 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.
9. Snapins – Allows you to install programs or run scripts on the host similar to GPO or PDQDeploy.
10. 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.
11. 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.
12. 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