@tolaria said in Unable to display Fog Management Console - Newbie to Linux & Fog Project:

After that, tried to open Fog Console and still fails

What is the URL you’re trying to use for the web interface? None of this is making any sense at all. The fog installer is solid, and is especially solid on CentOS 7. Something about your setup is not standard, or fog would just work. What is not standard? Are you downloading the CentOS 7 ISO yourself? Are you installing FOG on it’s very own OS, on it’s very own hardware/vm ? What is not standard here?

Pinging the creator of the fog client @joe-schmitt to look at it.

@bc601 said in boot into windows failure after deployed image:

I did not sysprep the image correctly went back and syspreped the PC used for the image and tried it again. This time it worked after redeploying the image

Do you know what you did wrong? What did you do differently?

@lebowski said in using kerberos - Setting up fog password failed!:

I try to integrate it onto an existing server.

That’s a really bad idea and will only cause you problems. FOG wants it’s own OS, and doesn’t play nice with other software. You’ve likely broken things that were already on the box simply by trying to install FOG onto it.

@azuroth I’m giving you the fishing rod, not the fish:
find / -type f -name ltsp.conf
You should memorize that command.

@andreiv and is it fixed?

@lebowski What’s the actual error?

@andreiv said in Is fog changing something in Ubuntu:

a few seconds of delay in the first boot

If it’s only the first boot, that’s just the kernel realizing things have changed - it’s looking for all hardware and re-configuring itself possibly. The same thing happens when you install a linux OS and then boot it for the first time - the first boot takes a bit longer, and subsequent boots are much faster.

My problem however happens every time I boot.

@andreiv said in Is fog changing something in Ubuntu:

Is FOG doing something to the Ubuntu partition after deployment? Something like reinstalling GRUB or changing in any way the Linux config files?

FOG doesn’t touch any of the config files in the OS unless you’re using the FOG Client in the OS your deploying - in which case the FOG Client does it’s thing as intended.

As far as the slowness, I myself have had very slow boot times for Ubuntu machines I’ve deployed using FOG - but after the OS is loaded, things are very snappy as normal. I don’t think it’s grub related, I think it must be something else.

In my particular case, I took an image from a spinning SATA 3 disk, and deployed it to a solid-state SATA 3 disk in the same laptop. (the reason for the capture/deploy was to go from mechanical to solid-state).

I haven’t looked at your videos yet, as I’m at work. I just wanted to pop in with a quick reply.

@gwendallecoz said in Rename after deployment:

I’m looking for the way to rename my machine windows automatically via fog but how?
Can we create a file with a matching name / address mac that fog would consult to rename the machine?

As @Sebastian-Roth said, FOG already does this. You have to register your computers for this functionality to work. You can individually register machines as you image them, or you can upload a CSV file via the Import Hosts feature in Host Management. If you want to see the syntax of the CSV that is required, do a full registration of one of your hosts via the boot menu and then do a host export inside Host Management. Either way - a host must be registered with the FOG server in order for the FOG Server to use 95% of it’s functionality.

@scott-b Can you post a chunk of the c:\fog.log file showing where it adds the printer, and then where it removes it when a 2nd person logs in please?

@meki333 If you cannot connect via the computers FQDN, then you have a DNS problem (or are lacking a DNS implementation altogether).

@scott-b What version of Windows is this on? Also are you using any group policy to install printers?

@scott-b said in printer installs for only one user account:

a few PCs that only get the printer installed for one user then once user two logs in FOG removes the printers

Not sure how that’s possible since the FOG Client installs printers based on what computer it is, and not what user is logged in. Are you using any group policy at all for printers too?

@andrewg78 Probably, I’ll have to look into it. Multicast tasks are handled differently than unicast tasks - they are treated as an individual job. If you wanted to get the status of the entire job, you could probably just follow along with the examples in this link: https://forums.fogproject.org/topic/9779/can-i-use-some-kind-of-script-to-create-image-and-ghost-my-lab-machines Though you would need to use the multicast task type, or know the task ID already.

@george1421 said in Fog Storage Nodes on Metered Connections Are Killing Us:

Or write you own replicator function using rsync on both ends. IMO rsync is a bit more elegant solution than the fog replicator, but then by going with rsync you loose the tight integration with FOG. So there are drawbacks on both sides.

I’ve wanted to rewrite the replication stuff for a while. A brand-new daemon written in Python3 that strictly follows the existing behaviors of replication - but with extra features like operation times. I’d use all native Python3 calls, no subprocess calls, no shell commands.

@tolaria said in Unable to display Fog Management Console - Newbie to Linux & Fog Project:

cat /etc/systemconfig/selinux

That’s not where SELinux’s configuration is on CentOS 7. It’s here: /etc/selinux/config

@tolaria Just follow this guide, don’t skip any steps: https://wiki.fogproject.org/wiki/index.php?title=CentOS_7

@fernando-gietz Truncate it.

@jim-graczyk said in Fog Storage Nodes on Metered Connections Are Killing Us:

is there any way to manage the frequency of image and snapin replication tasks?

Yes, the service sleep times inside the fog configuration area.