@keith75140 You might want to read through this article: https://forums.fogproject.org/topic/10006/ubuntu-is-fog-s-enemy

@george1421 This fixed my problem, thank you!

Thank You! You are the best!

@george1421 I copied what your pasted and changed the permissions. Maybe it was the permissions to fog:root that did it?

@msaglioc99 Reading through the PDF I found this link:
http://support.bluebeam.com/articles/enterprise-installation/

On the right side another PDF is linked called Enterprise Installation Guide. Check this out. On page number 9 (12 in the PDF) you find information on the MSI command line switches.

@UWPVIOLATOR You can make the call with curl or powershell. If you go the curl route, there is an executable for windows called curl.exe that will do need or you can call it from a linux command prompt.

@Wayne-Workman has some very fine examples of curl calls in this thread: https://forums.fogproject.org/topic/9779/can-i-use-some-kind-of-script-to-create-image-and-ghost-my-lab-machines

The problem is solved, My colleague used some system hardening from a procedure file and we didnt know exactly which was it, when we reverted the edits every thing worked, the edit was in registry.
Thanks for your support

I just read another post regarding this same issue. I will follow that posts under the bug forums.

RUnning the install to “working” resolved my issue. Thanks for the help!

@Sebastian-Roth I kind of got pulled in a few different directions.

But the concept is to use grub to make an ipxe call. From grub we would use the menu that would look a bit like this

menuentry 'Quick Image' { set root='hd0,msdos1' linux16 /boot/ipxe.krn initrd16 /boot/qimage-initrd }

Then the qimage-initrd would contain something like

#ipxe param mac0 ${net0/mac} param arch ${arch} param username fog param password password param qihost 1 isset ${net1/mac} && param mac1 ${net1/mac} || goto bootme isset ${net2/mac} && param mac2 ${net2/mac} || goto bootme :bootme chain -ar http://<fog_server_ip>/fog/service/ipxe/boot.php##params

Understand this is still a concept, but all of the bits look like they fit together nicely. That should provide the quick image menu for unregistered hosts.

@Tom-Elliott said in Install Google Earth:

n you be more specific as to what worked? So anybody else looking at this knows what to do? (Sorry to sound rude, but as a limited community it helps everybody out much more having

@x23piracy method of installing google chrome via snapins and using the settings he posted successfully did a silent install of Google Chrome on a machine I deployed to.

@nitelife Thanks for pictures. Turns out I was on the wrong track. I thought you might still have a special partition layout that is causing this. But looks like you got that fixed already. At least we got that ruled out.

What I am wondering about is why that boot partition (?) is 2 GB?! Have you messed with the boot partition and/or BCD?

Which OS type is configured for that image in the FOG web GUI by the way? Possibly not Win7 which would explain the problem?!

As well, would you please take a picture of the error screen so we see exactly what you see (the error code is definitely wrong).

@MotherFogger Interesting to hear that it’s all working fine when you stay within the ESX VM environment. As well the NFS config (exports) looks good to me.

What’s in between the client and the FOG server? Some kind of router / level 3-7 switch that might interfere here? Yes, please take another packet dump with the new syntax. Maybe the packet dump file will grow a little bigger then but it’s definitely worth it. In case it grows to 5 MB and more you might upload the file somewhere and send me the link via mail.

@Wayne-Workman

So after much frustration, here is what I came up with!!

Set FOG to Only Assigned Printers…
Delete all current printers…
Set FOG to FOG Managed Printers…
Re-Add Printers…
Reboot PC.
Voila! The new driver is added and you’re good to go!!!

So FOG CAN do it. 🙂

For the amount of headache I just spent on trying to figure out GPO to enable scripting. Testing script and getting everything to work… The above is much simpler…

For what it’s worth… I did find a link to your script. You had given it to me once before also. LOL!

https://forums.fogproject.org/topic/8406/fog-client-printer-not-displaying

Thanks!

This is Solved thanks

Case solved! Thanks again to both of y’all @george1421 @Wayne-Workman

Perfect brother. Thanks so much. I will continue testing. I’m working on another Virtual Box for our training room. I’ll keep you updated.

You can do a manual backup without much manual work. Mount fog’s NFS share at x.x.x.x:/images and copy everything. Then export the DB using the web interface.

@larosejm I’d like you to start a new thread with this issue. This thread started with an older version of FOG. We need to capture your specific details as how you have fog setup and under what host OS (i.e. things that are specific to your setup).

@mmcspadden I closed it for you and gave Quazz the bonus points.