@ch3i thank you.

There is nothing in the log pertaining to the situation. Only a favixon not existing

@Tom-Elliott, trying with 127.0.0.1/fog/client gives the same error (from clients Iceweasel). I can the server but that is all. Where are the logs stored?

Server

• FOG Version: 1.2.0
• OS: Debian 7.5

Client

• Service Version: N/A
• OS: Debian 7.5

Description

I have just installed a fresh Debian 7.5 OS (client) within a VM alongside my Debian 7.5 with FOG server (host). The client can ping the host but cannot access the page to download the client installer (<FOGSERVER>/fog/client) via Iceweasel. I receive the error that Iceweasel cannot establish a connection to the server. Do you know why this might be?

@george1421, thanks for your response. Would doing this not require the update of the configuration file every time a computer (i.e. MAC address) needs to be added or removed from the server? Would this require any restarting of the PXE boot service? I am not too familiar with networking as I studied OOP at university and just got plonked in to do this as an intern. It does look promising although getting my hands on the 150 computers separate MAC addresses doesn’t sound like a fun day.

-Anthony

Hi all,

We are currently assessing the feasibility of running a FOG server to meet our imaging needs. I’ll briefly explain the situation and our needs as well as the stumbling block we have run into.

1. We want to run a FOG server that will allow a subset of the computers on our network to be registered with it
2. These computers need to be controlled remotely (via the web browser)
3. They require a “zero touch” installation from imaging, deployment, and client setup via snapins

The issue we have is that the company also utilises 2 other PXE boot options which are tied together in a company PXE boot menu. This means that on boot we would first access the companies PXE boot menu, manually select the FOG server, and then let it carry on as normal. As I said before, we want this to be zero touch, so is there a method of getting around this that you know of? Perhaps there is an alternative booting environment?

Thanks,
Anthony

@Joe-Schmitt, that was what I imagined the case to be, thank you for the clarification.

-Anthony

Thanks for the response @Tom-Elliott. I am curious about not being able to specify user accounts in conjunction with a Zero Touch mentality. When installing an iso of, for instance, Debian, specifying the admin name and password is part of the installation process. How does FOG get around this?

Hi all,

I’m looking around at various imaging solutions and I was wondering if anyone could answer some questions I have. I’ve tried contacting the team directly via their web form but it’s been about a week without a response so I thought I’d ask here.

1. I know that FOG supports imaging to Win 7-10, mac OS, and Linux, but can FOG also image Android and Chrome? I did some digging when I had a moment and noticed people were able to image Chromium through some convoluted mechanisms but was unsure if there been any development since those forum posts (2014 - 2015)
2. Upon imaging, can FOG input OS activation keys and create user accounts (including admin/root)?
3. Can this all be completed in a Zero Touch way? I.e. specifying the image, applications to install, OS keys, accounts etc prior to imaging and then leaving it to complete

Thanks in advance for your help.

Excellent. Thanks for the replies @george1421 and @x23piracy. You are correct in that I am wanting the system to run the updates after the image is loaded to make sure that it is up to date rather than relying on my images being up to date.

I’m new to FOG and imaging in general so be easy on this newb. Is there a way to specify that certain scripts should run post-image? I.e. Windows Update, installation .exe’s, packages etc.

On a side note, can we specify user account information (name/password) and complete the entire process in a zero-touch way?