New Fog Server
-
Hi
Currently were i work we have a fog server setup (setup by ex employee) believe its using Ubuntu desktop 10.xx and fog 0.32 since this was set up the network has had several ip range changes and other work and i have managed to keep this fog server working.
am in a position i can set up another spare server as a new fog server my question is which os should i use Ubuntu14.04 or 12.04.4, and which fog version is 1.1.2 stable enough or should i use 0.32 etc.
my linux knowledge is basic only ever used openmediavault on my home nas which is Debian based and i do very little with cli.
any recommendations would be greatly appreciated, the other main reason am thinking about this is as currently the client machines are all running XP which all the images on the old server are and i want to make a windows 7 image (golden image i think its called) fingers crossed as ive never done deployment with windows 7 before on a vanilla Microsoft network.
-
I would use Ubuntu 12.04 and FOG version 1.1.2. Version 1.1.2 is stable. It includes all the updates and changes we have made up to this point.
Using a second fog server should not cause many problems, please pay attention to the installer script and follow the instructions carefully. The newer version uses a different boot file than the previous 0.32 version.
And of course if you run into problems feel free to come back and lets us know you need assistance.
-
well once the new server is up and running the old one will be powered down.
all I need it to do is image machines and auto rename and join domain, and move to correct location in ad, I think the difficult part for me is making a golden image as seams to be so many different ways mentioned on here none the same lol.
-
[quote=“chclark, post: 32043, member: 6419”]well once the new server is up and running the old one will be powered down.
all I need it to do is image machines and auto rename and join domain, and move to correct location in ad, I think the difficult part for me is making a golden image as seams to be so many different ways mentioned on here none the same lol.[/quote]
My recommendation is Virtualbox. Build your image Virtually and include all drivers and driver installation packs. If you set up a variable path that houses these installer files, then most of the drivers will be automatically assigned.
There are a number of golden image set ups, you are correct, but all of them should use a Virtual image as a base. I recommend Virtual box because it allows for easy snapshots and quick converting back to those snapshots. I don’t want to delve too deep, good luck.
I personally, wouldn’t decommission a working server, but I wouldn’t use it as the main environment either. I disconnected the network cable to my 0.32 server, but she’s still running today. I still use it from time to time as well.
-
oh yea when I say decommission it will still be there incase the new one goes belly up.
I had planed to use virtualbox for that very reason. I know theres a thread here about golden image but am abit confussed byt the sad2 tool.[url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]
another guide I found says to just install all the drivers on the virtual machine for every machine type we have and when it comes to been deployed windows would then just use the ones it need but am unsure on this. -
[quote=“chclark, post: 32046, member: 6419”]oh yea when I say decommission it will still be there incase the new one goes belly up.
I had planed to use virtualbox for that very reason. I know theres a thread here about golden image but am abit confussed byt the sad2 tool.[url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]
another guide I found says to just install all the drivers on the virtual machine for every machine type we have and when it comes to been deployed windows would then just use the ones it need but am unsure on this.[/quote]What I do, I do not know that this is correct but I do know it works in my environment. I use a tool to grab the drivers, such as DriverGrabber or DoubleDriver, and I will pull the drivers from an OEM install before I image.
Now when I begin audit mode in my Virtualbox Machine, I make a folder in the C drive called Drivers. I add this path to the variables section of the My Computer Properties, Advanced, and Finally under Environment Variables.
If I can not use my driver grabber, I just pull the installers off the driver disk and include them here. Most of the drivers will install when Windows is looking for INF files because they are included as a path variable. If the drivers aren’t installed after imaging, then I just manually run the installer from the Drivers folder. I touch each machine to make sure activation went through okay and that my scripts completed as expected.
I haven’t worked with that SAD2 tool, but I know there are some that do. Either way the direction is up to you. IMHO the Drivers is probably the one of the hardest parts about a golden image. After you decide how to handle them, then the other hard part is the unattend.xml file.
-
only way I thought to do it was from this guide [url]http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/[/url]
but it basically says install all the drivers to the VM to cover all the machines. -
ok so set the new server up today with Ubuntu 12.04.4 and fog 1.1.2, bit confused when running the fog installer were it asks if you want to add a ip for the router for the dhcp server and the dns part I think ive done it right though by adding my windows dhcp server in and the windows server dns ip.
I can access the web interface and all seams ok I did a quick test and changed option 66+67 from the old server tot he new on and pxe booted a client and it came up with the new servers pxe screen.
on the old server currently it auto joins the domain and renames clients. if I copy the encrypted password used for the network account will that encrypted password work for the new server or will I need to run fogcrypt again using the new servers fogcrypt client.
-
the client software has not changed. the encryption is the same
-
I would recommend 1.1.2 on Debian 7
-
Thanks junk that saves one job and I can just copy and paste the encrypted password from the old fog server.
Does it look like I installed fog correctly to add into a windows network from what I said in my previous post.
-
just from what you’ve described, it sounds right to me. remember that on 1.0+ Active Directory credentials have changed. you no longer need to put the domain in the username field.
previously it was “domain\user” now it is just “user” -
Great. Yea I read in another thread that domain\ isn’t needed now so I only out user in.
Just debating now how best to make a image wether I should make a golden image and if so how. Or do I make a seprate image per machine type I think there’s ruffly 4-6 different machine types.
-
Hi Ive attached my install log file could someone have a check through and see if it looks right for been installed into a windows network were we have a DHCP server already etc.
its these two settings which worry me as am not sure if I have done right by putting the details for my windows dhcp and dns server in these sections.
Would you like to setup a router address for the DHCP server? [Y/n]
What is the IP address to be used for the router on the DHCP server? [10.160.112.1]10.160.112.10Would you like to setup a DNS address for the DHCP server and client boot image? [Y/n]
What is the IP address to be used for DNS on the DHCP server and client boot image? [127.0.0.1] 10.160.112.10[url=“/_imported_xf_attachments/1/1101_foginstall.txt?:”]foginstall.txt[/url]
-
[quote=“chclark, post: 32212, member: 6419”]
Would you like to setup a router address for the DHCP server? [Y/n]
What is the IP address to be used for the router on the DHCP server? [10.160.112.1]10.160.112.10Would you like to setup a DNS address for the DHCP server and client boot image? [Y/n]
What is the IP address to be used for DNS on the DHCP server and client boot image? [127.0.0.1] 10.160.112.10[/quote]is 10.160.112.1 your DHCP server in your current network? or is 10.160.112.10 your dhcp server?
My recommendation is to use DNSMASQ to help to alleviate the issues of working with a DHCP server. It is a proxy boot service that helps to issue ip addresses to machines during the pxe boot process, this also helps to find the boot file.
Your log file looks okay, I would start by verifying that the DNS server and the DHCP server are in fact one in the same and that the address you are using is correct. IF that is the case, try using DNSMASQ to help to resolve to your FOG server.
-
Yes 10.160.112.10 is my DHCP and one of the dns servers there are two here 10.160.112.10 and 10.160.112.13
-
[quote=“chclark, post: 32289, member: 6419”]Yes 10.160.112.10 is my DHCP and one of the dns servers there are two here 10.160.112.10 and 10.160.112.13[/quote]
Then your settings, as far as I can tell, are correct.
If you have difficulties when resolving your tftp server or bootfile name please look into the DNSMASQ solution I have provided.
-
Fingers crossed it should be fine. like i say it pxe boots to the new server when i change option 66+67 and ive started to make a image and the vm registered in fog correctly as far as i can tell, just need to download the driver packs from home now as torrents are blocked on the work isp.
thanks for all the help ill be back if i get stuck
