@datastream said in Active task still showing even when complete:

@george1421 At the end a window does pop up that says installation successful and it has an ok button that I have to click.

Well that is / was it. If the application never quits then FOG (as well as other deployment tools like PDQ Deploy) rely on the installer exiting with a success code to consider the application installed. The -silent or -quiet (or any other number of switches which means a silent install) are typically required for this to be a success.

Glad to help 🙂

@wayne-workman said in Changing image to a group, I get " There is a host in a tasking ":

Commands

I ran your command, it works, thanks

Next time, I will try after each command line

@jhalbert said in Snapins does not deploy:

an I reset encryption on 600 pcs? Can I use a script or is their a place where I can reset them all?

Use the web interface - put all of them into a group called “all” and use the group to reset the encryption on them all.

@wild1 said in Snapin Error:

without specifying the ip address of the Fog server the client install had a certificate error.

What exactly do you mean by that? Do you know about the installer options? See here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_0.10.0.2B_Installation_Options

@clickwir said in Don't want host registration.:

We aren’t looking for a way to manage multiple images of each OS on each server. All we want is to PXE boot a server, get a list of OS’s and start the install. The changes to a server between each OS install are significant enough that an image won’t work, most of the time.

Why would you use FOG for that? Just setup a DHCP and TFTP service on a server and you’re done… Maybe add apache/nginx and NFS to also server files through HTTP and NFS. All fairly easy to setup by hand and no need to have all the PHP/MySQL/FTP foo that would come with a full FOG install.

Just adding here that the updateIP tool does all of this stuff for you automatically… 🙂

All you gotta do is update your OS’s IP address according to the distribution documentation you’re using - then run the tool. The rest is magic.

@julienl yes, sorry found their existense, didn’t knew about that versions. Sorry for that confusing stuff.

Regards X23

@psycholiquid his issue: https://forums.fogproject.org/topic/10828/deploying-an-image-to-a-target-machine

Bild Text

This thread can be ignored 😉

Hey,

i was remote on the system and we installed the current RC (switched to dev branch).
Helped him out with some sysprep lines, added to stop fog service, set it to disabled and so on.

Seemed to work well but he still has a problem with the dell’s 7050’s but i have the feeling we have that spanning tree problem like here:
https://forums.fogproject.org/topic/10512/dell-optiplex-7050-fails-to-pxe-boot

This is what he gets when trying an 7050:

Bild Text

The op will ask his network admin for a check, i suggested to connect fog and the client with a dump switch and then to the environment. This is not done yet.

The initial problem with the dell 7050’s isn’t solved yet!
@msaglioc99 any chance to give the thread subject a better name (subject) about the problem?

Regards X23

@jodantiger Well you better tell me how this partition layout was created. How would I know…

Maybe try mounting it while you are in debug mode

mkdir /mnt/sda1 mount -t vfat /dev/sda1 /mnt/sda1 ls -al /mnt/sda1 umount /mnt/sda1

If vfat does not work then try ntfs instead. Take a picture and post here.

I was looking for this solution. I just wanted to create a simple standard user with no password for students to log into. I created a powershell script and just used this line personalized for me:

NET USER username “password” /ADD

I took out the password and set Student as the username. It created a standard user named Student. Worked slick.

These errors are not related to any updates that happened to FOG, ubuntu. These are hardware errors with the target computer. The ACPI errors are a bit of a warning and can be ignored, if they bug you too much you can disable acpi on this target computer by placing acpi=off in the host’s kernel parameters.

The USB ones are a bit more confusing. It appears you have a malfunctioning USB device connected to this target system? Is the firmware up to date on this target computer?

YES! It works!

Very good ducumentation, best Support!

Thank you very much!

@brian-hoehn Check the time on the imaged laptop and the fog server and make sure they match. I’ve had this problem before and it was very confusing until I changed the time or time zone inside the fog configuration web page.

@x23piracy Because there is a difference.

Typically for bios (legacy) mode the exit mode is SANBOOT (that is the way iPXE attempts to location the hard drive). For uefi system the best exit mode is rEFInd, which is an external program that is used to find the boot drives. You may be able to tweak the refind.conf file to look for legacy stuff but I haven’t tried it.

There is something I just discovered the other day while I was hacking FOG’s boot menus. That is the platform variable. ref: http://ipxe.org/cfg/platform you can use that in your boot local section to test to see if the platform is efi or pc-bios and then select the best exit mode there.

such as in: (warning I just glued this code together there is no testing done)

:bootlocal iseq ${platform} efi && goto boot-efi || goto boot-bios goto MENU :boot-efi <don't know the syntax for refind> || goto MENU :boot-bios sanboot --no-describe --drive 0x80 || goto MENU

@Wayne-Workman There were other issues like missing kernel command and incorrect variable name as well. Though in current FOG versions you cannot put stuff in /var/www anywhere you like because of our redirect configuration. When you turn on redirect engine debug logging you can see why. I remember having had a first unsuccessful go with trying to come up with a different redirect/rewrite config that works for the API but still allows you to have files pretty much anywhere in /var/www…

To me this sounds as if the OP never had IT in UEFI mode. I am pretty sure of that because when you try to PXE boot a legacy binary in UEFI it should not even get as far as “initializing devices” …

It worked with the following versions : mono 3.10 and fog client 0.11.12 on a debian 7 system.
Thanks !

@jgallo I’d put everything on the same particularly as it addresses replication directly. The ftp error however is not because of the password you add when installing a new node. That password is what’s created for the node automatically. Sometimes, however, it’s possible it creates unusable characters.