@FlowLive I guess the only question I am seeing is that you are asking how to determine if the machine is a laptop or desktop. The easiest way to accomplish this is to use a script as the snap in that will check if it is a laptop and if so run the installer from a share some where. If it is a desktop then no installer is run.

Natively there is no way to have FOG determine if the machine is a laptop. But if you know what machines are laptops as you add them, you can have machines belong to multiple groups, add all laptops to a Laptop group and apply only those 3 snapins with no other setting in that particular group. Not automatic, but does work.

I quite often use scripts instead of actual files for snap ins, mostly due to old limitations of snapins back in the .32 days, so I guess it is just an old habit.

@wdmartin said:

It may not like having been put on a VirtualBox when it was originally built against an Optiplex 990.

For sure! Windows is very picky when it comes to IDE controller drivers… Not easy to get a system from bare metal to VM if you don’t adjust the drivers before capturing the image!

I got the 58 GB figure from the FOG imaging screen while it was building the second partition.

Ok, this meants the data within your second partition is 58 GB (28 GB compressed!) but does not tell you anything about the source partition/disk. It’s not an issue to put 58 GB to a 200 GB disk but a problem if the original file system used to reside on a larger disk - no matter how much free space there is!

@Ignacio Sí, trato de traducir. Explicar su problema, por favor.

@FlowLive So far the persistent groups as I laid out in the kb and link previously is working in my environment. A formal solution (authored by the devs) would be better. But if there is no plan to support persistent groups in fog 1.3 (as of today) then this solution should work for you too. You will just need to create your host consistent templates and then setup your host groups as outlined in the KB.

The issue, for others who may stumble across.

If you’re getting Private key not found but all the data seems to point that you do have a Private key file. Make sure the node (ip address or whatever) is actually a node within the system.

In @raumin’s case fog-server was not the node he was working with. The node he had defined was a NAS. NAS’s suck (plain and short) but have their own uses. (No offense to anybody using one, just they’re a bit of a pain to play with to get working with fog).

So the clients were looking at the thing @raumin is using as the GUI access point for private key. This was not a defined node (and I will try to come up with a better approach).

The fix, for now, is to always have a node for the GUI as well. You do not need to have the node enabled for things to work, and I would highly recommend against using in such a setup (NAS->Central GUI) trying to make the GUI node a “master” of the group it’s working with, unless you want it setup in such a way.

For our fix. We created a definition for the node and gave it the proper ip address. All started working immediately.

Hi Gents,

I am no expert, but hopefully my input can help a little.

First, quick MACLookUp on the MAC in the screenshot 080027 cadmus computer systems, looking for cadmus computer systems, VirtualBox came up. so that’s that. https://www.virtualbox.org/pipermail/vbox-dev/2011-August/010036.html

Just this past week i had an issue with our POS system that runs over PXE (Nothing to do with FOG).

Scenario

EXSi 5.5 Upt 2 host running Windows 7 guest and inside the guest VirtualBox. Inside VirtualBox a Virtual machine running our POS system (Point of Sale jst fyi 🙂 ) that is called via PXE.

The PXE call would time out, which i think is the problem you are having.

The way i was able to make it work was by ENABLING – PROMISCUOUS MODE – in the EXSi Host.

In Virtual box not sure how to enable, but a quick search tells me that all you have to do is change the NIC you are using the FOG with to Bridged Adapter instead of Internal Network which is most likely what you are using.
https://www.virtualbox.org/manual/ch06.html

Just to try change your FOG server network adapter to Bridged Adapter (Literally will simulate you physical NIC ) to see what happens, it wont hurt !!!

Again way far from expert, but in my case using fog, since this beautiful software uses PXE and DHCP among a lot more things. I though to myself, just to be on the safe side i will keep my FOG server completely isolated from my actual network, because in my case i just use it to clone computers and more important i already have a DHCP and PXE service already running … that would be a call for problems to put my fog server on the same network !!!

Hope this helps a little, if not well i shared something !!!

Cheers mate !!!

@andyroo54 You can edit it from the GUI on the “User Management” tab. There is no link between fog user on GUI and fog unix user.

@Wayne-Workman Yeah it’s not a big deal. It was just a nice feature of .32

Like I said it’s a small price to pay to upgrade.

It only shows we need a lot more testing. I plan on hopping onto the Ubuntu/Debian wagon soon to bang out some tutorials and videos, but I’m busy getting a fog-dhcp plugin / service / interface put together.

@Sebastian-Roth Yes Sebastian, I meant to write yesterday, fog is booting no probs now with the new trunk version. I am getting corruption of the image but that might be the OEM image I’m trying to upload. I’m going to try a win 10 soe today.

@jfath Have you tried updating to the latest version and tested again? Please let us know!

@Raymond-Bell Is this still an issue in latest trunk?

I ended up just adding them to groups and changing them using the group active directory section. Thanks again for all you guy’s help!

truncating the history table fixed it.

truncate table history;

@george1421 Yes.

@falko

SOLVED!!

After trying to download the client I now have the FOG Server set up after getting https://github-cloud.s3.amazonaws.com unblocked by our provider LGFL (along with the below four links from yesterday)

http://downloads.sourceforge.net/project/freeghost/InitList/init.xz
http://downloads.sourceforge.net/project/freeghost/InitList/init_32.xz
http://downloads.sourceforge.net/project/freeghost/KernelList/bzImage
http://downloads.sourceforge.net/project/freeghost/KernelList/bzImage32

Thanks all

EDIT: 2017-05-29

For Client: https://github-production-release-asset-2e65be.s3.amazonaws.com

For Dev/working branches
https://fogproject.org/inits/init.xz
https://fogproject.org/inits/init_32.xz
https://fogproject.org/kernels/bzImage
https://fogproject.org/kernels/bzImage32

Hi Guys,

Didn’t wanted to bother anyone again since we solved the problem. But indeed as @MagicLink said when entering a password during fog installation gave me the issue again (I had to prepared a backed server in case this one goes bad), however all i had to do was make sure MYSQL was running correctly (ran into the same problem, but i had a fixed !!!) 0_1459315888568_ERROR 2002 (HY000)-FOG SERVER MYSQL FIX.txt

Then make sure that the both configuration files match the inf you entered during the installation
/var/www/html/fog/lib/fog/config.class.php
/opt/fog/.fogsettings
and DONE.

ps,

Not sure what i did wrong but when i re-ran the install the LOCALHOST in the config file /var/www/html/fog/lib/fog/config.class.php was changed to the IP i gave my server instead of the “localhost”

Just change changed it to “localhost” and DONE !!!

Lesson !!!

Always make sure your config file is setup correctly !!!

Regards Gents !!!

@Wayne-Workman : It worked. I just updated the Unix Fog password. Thanks 🙂

@Wayne-Workman THey base on the time. If all of them have the exact same checkin time, they will ALL say 0 before me, because it doesn’t know which is which, (of which I’ll likely fall back to the ID of the tasking).

For now it’s working but a bit odd.