Installing a new clean fog server

[Predator]

Hey all,

I have a couple of questions regarding the installation of FOG from scratch.

What is the difference between the FOG 1.4.4 Officially Released and FOG 1.5.0 RC 3?

What is the best and simplest OS to use with FOG? I have read that some have problems with ubuntu… Furthermore i am a noob in Linux distro’s and it would help me a lot to have something that’s stable and simple with a GUI.

My goal is to implement a virtual fog server for the enterprise where i am currently working so i can deploy images over pxe boot.

[Quazz]

@predator On the web console, what does it say is the assigned image for that host?

[Predator]

Hi again,

I’m trying to capture an image on a fresh new installed physical machine…

1. I logged into the FOG Management and created an Image. Told the Image the OS was Windows 7 and set it for image type: single disk resizable and partition: everything

2. Boot the machine into the Fog Menu. Do a Full Host Reg and it shows up in the FOG Management as expected.

3. In task management when i click on capture image i get: invalid image assigned to host

[Wayne Workman]

@predator said in Installing a new clean fog server:

Now we don’t have VL keys but i do have found two Win 7 - MAK keys in our Microsoft License database. If i’m correct MAK is not the same as VL… Can i still use it though to create a master image and deploy it on OEM computers?

Legally, yes. You must use the MAC key though. deploying OEM violates Microsofts terms of service.

[THEMCV]

@predator Here you go, start here

https://forums.fogproject.org/topic/8878/fog-drivers-script-will-not-run-correctly-in-postdownloadscripts/52

All the devs and mods helped me get a working solution. That is a gold mine of information in there!

[Predator]

Hey all,

I have installed fog and it’s working great with pxe boot. I’m now looking for a procedure on how to create a master image aka golden image. My enterprise buys OEM pc’s with preinstalled windows 7. This means that they have an activation key delivered with the image.

Now we don’t have VL keys but i do have found two Win 7 - MAK keys in our Microsoft License database. If i’m correct MAK is not the same as VL… Can i still use it though to create a master image and deploy it on OEM computers?

[Predator]

@quazz

Thanks a lot.

[Quazz]

@predator The installer mentions this, but in case you missed it:

Username: fog
Password: password

[Predator]

OK i get it…

Now for the part of the management console web interface page…

How do i login? I tried several password and usernames but nothing seems to work…

I don’t even remember where i have configured a username and password for this page.

[Predator]

@quazz

Yep i did configure it as bridged adapter.

[Quazz]

@predator

Let’s keep things simple here.

A FOG Client is a different computer that connects to the FOG Server.

In other words, your 2 and 3 are one and the same (and thus not a FOG Client). A FOG Client would indeed need a different IP as George said, but this is not the case for you.

Your FOG server ip is the Centos IP, since they are the same. FOG is just software that runs on it, if that makes sense.

[Predator]

@tom-elliott

I think i am. The fog client is what i call the fog server because we have to install the fog console on the server.

Debriefing:

1 VMWare Workstation (VM Host)
2 CentOS (VM Guest)
3 FOG Management Console (FOG Client)

So the FOG management console needs the same IPV4 address as CentOS?

[Quazz]

@predator How did you configure the virtual NIC to act? (bridged?)

[Tom Elliott]

@predator Well, I think you’re confusing terminologies here.

FOG Client, in my eyes, is the machine you’re attempting to image. The FOG Client, you’re basing your layout on, is actually what I would term “FOG Server”?

VM Host needs an IP address.

VM Guest = FOG Server as I’m seeing it. (This is the vm guest that’s hosting the fog server)

[george1421]

@predator You are adding a little bit of complexity because you are using a type-2 hypervisor.

The requirements for FOG are the same.

1. FOG server must have a unique static address that is not changed after FOG is installed.

2. The target (client) computer must have its IP address assigned by dhcp, because that is the only way it can find out about the FOG server to boot from.

[george1421]

@predator You have this incorrect.

1.VM Host = leave network settings on dynamic
2.VM Guest = configure network settings on static
3.FOG Client = configure network settings on static

This should be,

1. VM Host = Must be unique, but don’t really care. Not used by/for fog
2. VM Guest = configure network settings on static
3. FOG Client = dhcp

[Predator]

@tom-elliott

Because George confirmed all three need different ip addresses…

@george1421
1.VM Host = leave network settings on dynamic
2.VM Guest = configure network settings on static
3.FOG Client = configure network settings on static

So if we set it up like this all 3 would have different ip addresses correct?

[Predator]

@george1421 said in Installing a new clean fog server:

And you are correct all three need different IP addresses.

[Tom Elliott]

@predator Why did you setup on 207, but then go to 208?

[Predator]

@george1421

I have setup centos on IPV4 10.2.3.207

When installing the fogclient i choose IPV4 10.2.3.208

I get a response in the terminal to open the management console on http://10.2.3.208/fog/management/index.php

Yet http://10.2.3.208/fog/management/index.php is not reachable…

But when i enter http://10.2.3.207/fog/management/index.php i do get the fog login page…