If there is a way to do it, I’m not aware of it.
Can anyone confirm this is possible? If so please leave instructions.
Best posts made by Adam Wright
Latest posts made by Adam Wright
RE: Unable to register host
[quote=“Amir, post: 785, member: 335”]There are several places that you can check in order to make sure that your new hosts are communicating with the right FOG server IP address specified on /tftpboot/pxelinux.cfg/default[/quote]
I forgot all about the ip addresses passed in the append lines of the default config file! That did it!
I’m going to add this to the wiki page for [URL=‘http://www.fogproject.org/wiki/index.php?title=Change_FOG_Server_IP_Address’]changing the IP address of a FOG server[/URL].
Unable to register host
I did an IP address change recently and most everything seems to be working smoothly. If I have a machine in my FOG hosts list, I can push an image out, and snapins too. However, when I attempt to register a new host, I get an error:
[QUOTE]Starting host registration…
Unable to register host for the following reasons:[/QUOTE]
But no reasons are given.
So now I’m in debug mode looking at client information and all I’ve noticed that’s out of whack is the DNS server debug mode is using is my old DNS server, .31 but my current/new DNS server is at .14. I changed the setting in the FOG webUI and its still saved as the new correct IP when I log into the webUI.
I’ve tried restarting the networking service as well as rebooting the server itself to no avail.
Any ideas why FOG might be using the old DNS server rather than the new one? And if that’s what’s causing my host registration process to fail?
Will update here when anything further develops.
Group deploy single snapin
As of version 0.32, you can only deploy all snapins to a group of PCs.
I’d like to be able to deploy one snapin to all PCs in a group.
Example: Systems are all working fine, professor says labs need new piece of software for a class, I create a snapin for the software and want to push it out to labs via FOG.
RE: Auto Populated Snap-Ins
We use MSE for anti-virus, and I’ve had nothing but problems when pre-installing it on the image I push out.
If I do pre-install it, when a user logs (student) in, they get a popup box for MSE, something about finishing the install process I believe.
Also, as for “…and will (should) not differ between your hosts”, if a piece of software shouldn’t differ between hosts, isn’t that more of a reason to allow a snap-in to be applied to all hosts like my idea?
Lastly, I like to have anti-virus and other software available via snapin rather than pre-installed for many reasons:
The process of having FOG push the image out to multiple PCs takes less time because the image is smaller than if the snapins were pre-installed. The snapins need to install afterwards, yes, but when imaging 60+ PCs with a 10 PC queue, the most important thing is getting the image deployed on each machine fast so that a spot in the queue opens up for the next machine.
It’s nice to have a piece of software deployable via snapin remotely for well, remote systems you don’t have access to or don’t want to physically go to, or for ease and scheduling. Example: a professor has a different anti-virus on a laptop he brings in, he decides he wants to switch to the anti-virus we use. He uninstalls old anti-virus, I add the snapin to his PC in FOG then deploy it, it installs in the background silently while he works, or his office is locked, or whatever.
[*]What if you decide to change anti-virus (or another piece of software, i.e. Office)? If its preinstalled, then you have to go back to an image backup, uninstall the anti-virus software, install the new software, sysprep it back up, re-upload it, change imageid for all the PCs that were using old software to newly uploaded imageid, re-deploy to all PCs. Whereas if its a snapin, you just create the new snapin, remove the old snapin from all PCs, add the new snapin to all PCs, redeploy.
For these reasons, and others, I support the idea of having hardly any applications pre-installed on my image. I’m open to hearing rebuttals and reasons for the contrary, however.
Auto Populated Snap-Ins
There are autopop settings for newly register machines such as ImageID association, OS association, whether or not AD should be enabled by default, etc.
It would be very helpful if I was able to choose default snapin(s) to associate with new machines.
You use SoftwareX for anti-virus, and you install that on machines via snapin. You want each new lab PC to have that snapin. Currently, once you’ve registered all the machines with FOG, you must either enable that snapin for each machine manually, or put all machines in a group and enable the snapin that way (which isn’t always an option because you don’t ALWAYS get a whole room of PCs at the same time).
It would be nice to just have to register the PC with FOG, and, by default, FOG enables the SoftwareX snapin with each new machine.