DHCP options for VMWARE appliance
-
@Paul-Storic VERY VERY VERY old.
Considering 0.32 was released in 2011, I imagine 0.27 was released in 2009-2010 era?
-
@Paul-Storic Yes, very old and not worth the effort if you want to deploy win7 or newer. Just get a copy of Centos 7 and install it. The only thing you need to do other than select the defaults is with hard drive partitioning. Centos will try to split the disk space evenly between /home and / (root). Just remove /home and give all disk space to / (root). There are better ways to set this up, but this is the easiest for new users.
-
Yea I can see the newest version is 1.20 so it’s way out of date already. Not really too familiar with Linx and I’m stuck with no GUI so I guess I would need to build a new Ubuntu VM and start fresh. May wind up using MDT and sccm instead lol.
-
@Paul-Storic You can use MDT if you want, I’ve done it that way too. FOG is much faster to get the image on disk.
You can use ubuntu or centos. Centos (my choice) will not have a gui if you pick minimum. But really once the OS is setup you run the installer and once FOG is running you don’t touch the OS again, everything is done via the web gui.
There is a current dev branch (a.k.a trunk build) that is current. Understand that it is a dev build so there is occasional bug, but it is nearing the release of 1.3.0. If you want to deploy Win10, to uefi firmware computers, gpt disks you will want to be on the trunk build. You can install the trunk build directly and not need to install 1.2.0 stable then upgrade.
-
Thanks George
-
@Paul-Storic said in DHCP options for VMWARE appliance:
it’s version .27
Holy cow. Stay away from that. Latest is 1.2.0, use that. Or better yet, FOG Trunk.
-
Well turns out we have no volume license so MDT is not a solution. Going to spin up and Ubuntu 16.06 VM and attempt to setup FOG from scratch.
-
@Paul-Storic Just a comment on volume licensing.
You only need one VLK key to allow you to deploy OEM licenses to workstations. That volume key version must match the OEM license you have. For example if you want to deploy a consistent version of Win7 pro and all of your workstations have Win7 pro you just need 1 Win7 Pro VLK. Now if you want to deploy Win8 pro and have the proper OEM license the you will need a second Win8 Pro VLK. What you can’t do here is a version upgrade. If the OEM license that came with the computer is Win7 Home, you can not use a Win7 Pro VLK to upgrade the version Same as Win7 Pro to Win8.1 Pro. No version upgrades are allowed with a single VLK. To buy into the VLSC program you need 5 points. Each product is a point. So you can purchase 1 VLK key and 4 windows server client access keys (can never have enough) and be in the VLSC program.
Now with that said, deploying with MDT and deploying FOG (ghost, acronis, etc) has the same licensing limitation as MDT. This is a windows licensing restriction not your deployment tool.
@Wayne-Workman The OP will need to fix instructions for Ubuntu 16.04, my forum searching capabilities are inadequate today. If you have that link handy, could you post it here.
Ref post in Spiceworks from Chris: https://community.spiceworks.com/how_to/69219-reimaging-rights-how-they-apply-to-your-licensing
-
@george1421 if you search for
Ubuntu 16it’s normally the first one after the ads.Here it is:
https://forums.fogproject.org/topic/7131/fog-on-ubuntu-16-04-php7/27 -
@Paul-Storic said in DHCP options for VMWARE appliance:
For 67, I simply put “undionly.kpexe”?
I just noticed there’s a typo on that. It should be
undionly.kpxeorundionly.kkpxeThese two are valid, what you typed isn’t. -
I copied and pasted it but thanks for the heads up
-
@Paul-Storic Any word on this? Also, current FOG version is 1.3.0 RC-6, and 7 is to be released soon (august 2016).
