[B]@ArchyFan [/B]I had 0.32 working fine before our network was VLAN’d so this is the first attempt at trying to get FOG working in a VLAN’d environment.

[B]@Mentaloid[/B] TFTP test fails from client location “Timeout occurred”

[B]@Tom[/B]
[QUOTE]Are your switches configured to point back at the dhcp server for each of the different subnets/vlans?[/QUOTE]
I [I]believe[/I] they are. How would I be sure? (Forgive me for my ignorance, I didn’t configure the switches; however, I can gain access to them).

[QUOTE]Many times, when one has multiple VLANs as you do, the DHCP is still handled centrally. However, in order for those subnets to communicate across one another, they need to know how to pass the data back and forth. This is where the DHCP server really shines.[/QUOTE]
I [I]believe[/I] this is how our’s is setup (handled centrally). The pic may be entirely irrelevant to the problem but extra info anyways:
[IMG]http://i.imgur.com/NjFXNTY.png[/IMG]

[QUOTE]One thing I notice, however, is that the separate VLANs all have their own DNS servers? Do each of the VLANs have their own Gateway address as well?[/QUOTE]
They all have the same physical DNS server (the Windows Server - also our DC, DHCP, and DNS server). The different DNS IP’s on each VLAN all point back to the same server. The gateway IP’s are also different relative to their respected VLAN; however, they all point to same router/firewall.

[IMG]http://i.imgur.com/sLJ7qZS.png[/IMG]

[QUOTE]We have 12 separate VLANs in our organization. All have their own Gateway’s that lead back to our routing switch. Our routing switch has an ip-helper setting back to our central DHCP server for their related Gateway. This way there’s still a gate to communicate across, and the routing switch has all the routes configured to allow pass of traffic from one subnet to another.[/QUOTE]
Would you know how I would setup an ip-helper setting like you’re talking about? I’ll research Fortinet’s website for it. Is that called a [I]DHCP relay[/I]?

Thanks fellas!

[B]Environment Details:[/B]
[LIST]
[]School District Network with each school on their own VLAN
[]Windows Server 2008 R2 w/ AD, DHCP, and DNS
[]FOG server installed on Ubuntu Server 12.04.5 LTS
[]FOG server (hardware server) hooked into trunked VLAN port in switch
[]DHCP 066 is set to “fogserver” and not a specific IP
[]Configured DNS Forward Lookup Zones to point “fogserver” to it’s relative VLAN IP
[LIST]
[*][IMG]http://i.imgur.com/t2GZ5SS.png[/IMG]
[/LIST]
[/LIST]
[B]FOG Installation Configuration:[/B]
[CODE] Here are the settings FOG will use:
Base Linux: Debian
Detected Linux Distribution: Ubuntu
Installation Type: Normal Server
Server IP Address: 10.52.4.23
DHCP router Address: 10.52.4.20
DHCP DNS Address: 10.52.4.20
Interface: eth2
Using FOG DHCP: 0
Internationalization: 0
Donate: 0

    DHCP will NOT be setup but you must setup your
    current DHCP server to use FOG for PXE services.

    On a Linux DHCP server you must set:
        next-server

    On a Windows DHCP server you must set:
        option 066 & 067

      Option 066 is the IP of the FOG Server: (e.g. 10.52.4.23)
      Option 067 is the undionly.kpxe file: (e.g. undionly.kpxe)

[/CODE]
[B]**NOTE: [/B]I figure maybe when FOG asks for IP’s like above, it may cause issues since 10.52.4.x is the High School VLAN. The only way a server/workstation can communicate with another server/workstation on another VLAN is to use the DNS name I configured in DNS Forward Lookup Zones (“fogserver” in my case) but the FOG Install Script only wants IP addresses.

[B]/etc/network/interfaces configuration:[/B]
[CODE]# The loopback network interface
auto lo
iface lo inet loopback

The primary network interface

auto eth2

iface eth2 inet dhcp

High School

auto eth2.4
iface eth2.4 inet static
address 10.52.4.23
netmask 255.255.252.0
gateway 10.52.4.1
dns-nameservers 10.52.4.20 8.8.8.8
vlan-raw-device eth2

Junior High

auto eth2.8
iface eth2.8 inet static
address 10.52.8.23
netmask 255.255.252.0
dns-nameservers 10.52.8.20 8.8.8.8
vlan-raw-device eth2

Central Office

auto eth2.10
iface eth2.10 inet static
address 10.52.1.23
netmask 255.255.255.0
dns-nameservers 10.52.1.20 8.8.8.8
vlan-raw-device eth2

Primary School

auto eth2.12
iface eth2.12 inet static
address 10.52.12.23
netmask 255.255.252.0
dns-nameservers 10.52.12.20 8.8.8.8
vlan-raw-device eth2

Elementary School

auto eth2.16
iface eth2.16 inet static
address 10.52.16.23
netmask 255.255.252.0
dns-nameservers 10.52.16.20 8.8.8.8
vlan-raw-device eth2
[/CODE]

[B]RESULTING PROBLEM:[/B]
[B][IMG]http://i.imgur.com/34wfJco.png[/IMG][/B]

Any suggestions?

Excellent job on documenting all of this - I know it took time. Much appreciated!

bump

I have FOG running in a virtualbox on my workstation and has been working great for the last 7 months until we received a new batch of Optiplex 960’s we are putting in a few labs. The issue is when booting to network PXE-E51 No DHCP or proxyDHCP offers were received. This is an intermittent problem… sometimes works… sometimes don’t… some not at all. These computers were refurbished and have different versions of the Intel Boot Agent but its still intermittent (even if they have the same version).

Our setup:
[LIST]
[]FOG is running on Ubuntu 10.04 LTS
[]Windows 2008 r2 as our DNS/DHCP/Domain server.
[]I’ve set options 066 and 067 correctly.
[]Went into DHCP Scope properties > Advanced and checked “Both” under Assign IP addresses dynamically to client of.
[*]Switches connect the buildings together. I haven’t messed with the switches (we probably have close to 2 dozen switches total on our network).
[/LIST]
AFAIK, this is only affecting the Optiplex 960’s.
Has anyone else had issues with this Dell model? Any tips or advice?

[B]NOTE:[/B] Plugged an Optiplex 960 directly into the wall ethernet port and got the No DHCP offers received. Then restart it but this time plugged the ethernet into our KVM/Ethernet Switch combo that is connected to the SAME wall port and it worked perfectly.
This is a weird issue. Advise please.

I use fog daily and I love it.

However, I’ve noticed it’s been over a year since the last release.

Has development stopped?

I have my golden image setup and joining our Active Directory domain with no issues.

My question now is:
Is there a way I can display a default domain username to login with instead of the computer defaulting to trying to login to the local account.

This is a sysprep’d image if that makes a difference.

I’ve previously read an article about using a SetupComplete.cmd script to auto-delete a local account once sysprep is done setting up everything - so this isn’t as important as figuring out how to give it a default domain username.

Thanks in advance!

It worked! What the crap?

[url]http://i.imgur.com/6kJMP.png[/url]

I guess I was over-complicating the process afterall - as usual.

Thanks for bearing with me man. I swear I thought I tried it like that (maybe it was with the non-sysprep’d image tho). I appreciate all your help!

Maybe I’m not entering the correct info in the Organization Unit field in FOG management WebUI

It should go under HighSchool>Students - bah, I need to learn AD. period.

Check it: [url]http://i.imgur.com/44d8o.png[/url]

Thanks!

Still a no-go.
I created another account and delegated rights to let it join computers to the domain.

No messages in fog.log this time shrugs

I’ve only been learning AD for a month now, so my problem could very well be my AD management and how it’s setup.
See: [url]http://i.imgur.com/9TBCB.png[/url]

About to have to drop playing with FOG for a while before I go insane and since it’s taking up so much time with me trying to figure out how to auto-join our domain.

Maybe I’ll get a working unattend.xml file to auto-join by next week and just do things like that. Sorry for ranting…

I just several more times even with the non-sysprep’d image.

In the non-sysprep’d one I get an error in the c:\fog.log
[CODE]Hostnamechanger Domain Error! (‘Unknown Error’ Code: 2202)[/CODE]

I’ve tried googling the error code but found nothing. Any idea?

[QUOTE]Try joining it to the domain leaving the container empty. Just as a test. That will tell you if the join operation is working and you’re just having a problem with the container syntax.[/QUOTE]

Just to clarify, I should join like I was but leave the Organizational Unit container empty?

Using Windows Server 2008 R2 if that makes a difference.

extra information:

for the Domain Username I’ve also tried: school/administrator & school.local/administrator

Using FOG 0.32 with latest kernel.

I got my golden windows 7 machine just like I want it - I didn’t change anything special, just added the software I wanted and I’m trying to get it to join our AD domain.

I used:
[CODE]sysprep /quiet /generalize /oobe /shutdown /unattend:c:\unattend.xml[/CODE]

to sysprep it before I imaged it. The current unattend.xml doesn’t have anything in it that would affect the domain join; however, I’m considering just starting up Windows AIK and creating my own unattend.xml to auto-join the domain.

Does anyone else have these issues?

I checked the ‘Join Domain after Imaging’ and filled out the info:
[CODE]Domain name: school.local
Organizational Unit: OU=HighSchool,DC=school,DC=local
Domain Username: administrator
Domain Password: encrypted with FOGCrypt[/CODE]

Then started the task to deploy. After imaging and windows configuring itself it works fine - it’s just not joined to the domain.

Question: Can I join the domain before sysprep’ing and imaging the computer?

FOG is working so great except for this.

Point me in the right direction if you have an idea what I’m doing wrong. Yes, I’ve even tried just leaving the OU field blank. Thanks!

djm79, I will try that and it IS using the internet for some reason (the client machine). I have a real-time bandwidth monitor and as soon as the deployment begins the graph spikes (pretty much triples) and begins using 21Mb/s with the client’s IP being the culprit. [B]I’ve only tried imaging from the same location (my office)[/B]. [B]Network misconfiguration? [/B]I’ll try at another location and/or hook the client & server directly to a switch and go from there.

We’re calling the company we outsourced running the wires and installed the switches in the buildings to see if they would know of any reason before I get my hands dirty into uncharted territory.

chad, I know! It’s killing me not knowing why this is happening pulls and handful of hair out.

Thanks for all the help - I’ll report back with my solution as soon as I find out the problem. Thanks again guys.

Just more info:

We’re unicasting.
It happens with every model of computer we’ve tried (we’ve tried 4 different ones, 3 dells & an HP)

I ran the command and it seems that the machine that we’re deploying to was getting traffic to it at 8mb/s from the FOG Server. I was monitoring our network filter and it showed 100% bandwidth INTERNET traffic being used by the CLIENT computer (the computer we’re trying to image)… makes no sense. I’m stumped.

We have a dedicated server and when we set up a deployment onto a machine, it’s EXTREMELY slow (80MB/min) AND it maxes out our network.

Installed it on a Linux Mint 13 standalone server:
Here are the settings FOG will use:
Distro: Ubuntu
Installation Type: Normal Server
Server IP Address: 10.52.1.69
DHCP router Address:
DHCP DNS Address:
Interface: eth2
Using FOG DHCP: 0
Internationalization: 0

We have a Windows 2008 R2 server running AD and DHCP. Please tell me I just missed an obvious setting. I’d really like to get this going. The FOG Logs aren’t showing any errors in the WebUI. I know it’s FOG that is causing the bandwidth spike… I just don’t understand why it’s trying to communicate with something outside our network.

Any help would be appreciated! Thanks