Is FOG for me?
-
Thanks for that confirmation and tips
How about licensing?
-
And i can deploy the image in multiple destination pc all at once right?
I have server2008r2 domain, pfsense router firewall, win7 and win8 on i3 and athlon, xp on pentium4 celeron
-
Hi
You already mentioned that you use VAMT for licensing, so depending on whether you use KMS or MAK keys for your install you will still use VAMT. Just supply either your KMS or MAK key in the unattend.xml file you’ll create while building your image and then once the machines are imaged you will licence them. KMS machines should in most cases check in with the KMS server that VAMT is running on and then license themselves, if your using MAK keys then you may need to use VAMT to perform an online validation en-masse. Depends on your setup, but due to the volume of PC’s we have here I use KMS. Simplifies everything a bit
Hope this helps
Cheers
-
[quote=“prince xyryl, post: 34283, member: 25316”]And i can deploy the image in multiple destination pc all at once right?
I have server2008r2 domain, pfsense router firewall, win7 and win8 on i3 and athlon, xp on pentium4 celeron[/quote]
Yes you can run multiple tasks and deploy different image types simultaneously. You will need to build a different image for each OS of course but you can set up your machine groups in FOG and then push each image out to each group. Make sure when you set FOG up that you don’t allow it to be used as a DHCP server and that your DCHP options 66 and 67 on your Windows DHCP server are set correctly or iPXE wont boot. This is all covered in the guide I linked earlier
-
Hi Liam
Thanks again…
I read your guide and i have a followup question …
I have WS2008r2 for DNS, but pfsense for DHCP and IPs on my main network PCs are static…
What will be the easy but effective solution ?
-
[quote=“prince xyryl, post: 34400, member: 25316”]Hi Liam
Thanks again…
I read your guide and i have a followup question …
I have WS2008r2 for DNS, but pfsense for DHCP and IPs on my main network PCs are static…
What will be the easy but effective solution ?[/quote]
I answered that Question for you here -> [quote=“Jaymes Driver, post: 34302, member: 3582”]
My suggestion is using DNSMasq[url]http://fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server#DNSMASQ_settings_for_iPXE[/url]It does not matter what ip address your machines have, when they enter TFTP they look for a dhcp server and DNSMasq will offer the correct information to the clients so they can boot.[/quote]
You will want to use DNSMaasq to proxy boot your clients looking to TFTP, DNSMasq will help them to resovle your boot server and file name.
DNSMasq works as a proxy DHCP server, it doles out ip addresses to machines looking to TFTP boot. Some environments that don’t have a DHCP server, or an option to enter a next server or boot file name will use this service to acquire the correct boot information and resolve to your FOG server.
-
hi! Thanks
I decided to install DHCP server on my WS2008R2…so its serving DNS and DHCP now…
here’s my details
pfsense router = DHCP disabled / IP is 192.168.1.1
WS2008R2 = DHCP + DNS / IP is 192.168.1.2 / gateway is 192.168.1.1
now in my UbuntuServer 12.04LTS
[FONT=Courier New]“”“”“1.#The loopback network interface[/FONT]
[FONT=Courier New]2.auto lo[/FONT]
[FONT=Courier New]3.iface lo inet loopback[/FONT]
[FONT=Courier New]4.[/FONT]
[FONT=Courier New]5.#The primary network interface[/FONT]
[FONT=Courier New]6.auto eth0[/FONT]
[FONT=Courier New]7.iface eth0 inet [B][I]static### Set to static IP[/I][/B][/FONT]
[B][I][FONT=Courier New]8.address 192.168.1.5[/FONT][/I][/B] [B][COLOR=#ff0000] 192.168.1.3[/COLOR][/B]
[B][I][FONT=Courier New]9.netmask[/FONT][/I][/B][B][COLOR=#ff0000][FONT=Courier New]255.255.255.0[/FONT][/COLOR][/B]
[B][I][FONT=Courier New]10.gateway [/FONT][/I][/B][B][COLOR=#ff0000][FONT=Courier New]192.168.1.1[/FONT][/COLOR][/B]
[B][I][FONT=Courier New]11.network 192.168.1.0[/FONT][/I][/B] [B][COLOR=#ff0000] What should I put here?[/COLOR][/B]
[B][I][FONT=Courier New]12.broadcast[/FONT][/I][FONT=Courier New][COLOR=#ff0000] 192.168.1.255[/COLOR][/FONT][/B]
[B][I][FONT=Courier New]13.dns-domain example.org ## Your internalDomain Name[/FONT][/I][/B] [B][COLOR=#ff0000]my FQDN is ccslynx.local[/COLOR][/B]
[B][I][FONT=Courier New]14.dns-search example.org[/FONT][/I][/B] [B][COLOR=#ff0000]ccslynx.local [/COLOR][/B]
[B][I][FONT=Courier New]15.dns-nameservers 192.168.5.3 192.168.5.4## enter your DNS server[/FONT][/I][/B]”“”" [COLOR=#ff0000]192.168.1.2 my WS2008r2 ip?)[/COLOR]I’m doing fine right?
-
Hostname Changer == I disable this… I want to join my clientsPC to domain manually.
is it ok?
- FOG Settings IMPORTANT
Active Directory Defaults
= I dont put anything here since I want to join my clients manually in my domain
and i just want to clarify? Once I already deploy the images on target PC… I can now TURNOFF/SHUTDOWN the FOG server?
or FOG server should be ON all the time?
Thanks
-
Hostname Changer isn’t just for joining domain, it can change the host name, though this also happens during the download task, if the host isn’t sysprepped after the task is completed with the download to the client.
You don’t need to specify the AD information to enable the renaming of the hosts. If you’re not using the FOG Server, you can shut it off, though in most environments they just have it running all the time so tftp and imaging can happen at the click of a button.
-
[B]iv. FOG Client Installation
[/B]On your build system open your web browser and navigate to the FOG interface
a.[B] Download the FOG Client Service [/B]b. Extract the file and run Setup.exe c. On the Configuration page
i. Enter the host name of the FOG Server. (you can use IP, but depending on firewalls and routing non-domain computers may have issues communicating which will disable the auto-domain join feature)
ii. You can leave all other options selected as once the client service connects to the server it will copy the configured FOG options.[B]
[COLOR=#ff0000]how? Where?[/COLOR]
[/B]I cant see this on my FOG management page[B]
[/B] -
[quote=“prince xyryl, post: 34589, member: 25316”][B]iv. FOG Client Installation[/B]
On your build system open your web browser and navigate to the FOG interface
a.[B] Download the FOG Client Service [/B]b. Extract the file and run Setup.exe c. On the Configuration page
i. Enter the host name of the FOG Server. (you can use IP, but depending on firewalls and routing non-domain computers may have issues communicating which will disable the auto-domain join feature)
ii. You can leave all other options selected as once the client service connects to the server it will copy the configured FOG options.
[B][COLOR=#ff0000]how? Where?[/COLOR] [/B]
I cant see this on my FOG management page
[/quote]up…
[B][COLOR=#ff0000]how? Where?[/COLOR][/B]
[B][COLOR=#ff0000][/COLOR][/B]
I cant see this on my FOG management page ([B] Download the FOG Client Service)[/B] -
[quote=“prince xyryl, post: 36350, member: 25316”]up…
[B][COLOR=#ff0000]how? Where?[/COLOR][/B]
I cant see this on my FOG management page ([B] Download the FOG Client Service)[/B][/quote]
[url]http://youripaddressofyourfogserverhere/fog/client[/url]
Alternatively you can use the links at the bottom of the management page to get to the client.