How to Setup Ubuntu Server/FOG 1.2.0/Create Univeral Windows 7 Image using Sysprep - Step-by-Step
-
Or, if you need a direct link, it would be:
[url]Http://<your[/url] fog server hostname or ip>/fog/management/index.php?node=client -
[quote=“Tom Elliott, post: 34308, member: 7271”]I don’t think it was meant as an “unprofessional” point of retention. It was more meant to inform. He still answered the question, and gave the “warning” in a descriptive way. Sometimes people’s phrasing may come off as “harsh”. We must all remember we’re reading text on a forum. There is no conceptual method of portraying the true intentions. Maybe it was meant to be degrading, maybe it was not intended in such a form at all.
Please understand that it’s just meant to suggest to a person that the tutorials, and especially those that are not requesting tutorials but actually giving tutorial descriptions, to use the appropriate forum areas to ask questions. If you need to link back to the relevant thread, simply copy the link in your post.
Hopefully this helps clarify the intentions of what we’re trying so hard to maintain and accomplish.[/quote]
oh? ok sir. Thanks
-
Hey all,
I am a District IT for a School District and we are mass deploying new teacher/lab computersI have everything set up and ready to pull a master image to send out to other PC and I am running into a problem. I have my FOG management up and running and I have a image created in Image Management. I have my FOG management on one laptop connected to a Linksys 8 port switch and the master laptop that I want the image from connected also. I have Sysprep the Master Image and booted it to Onboard NIC. It finds the Client IP that I have set up but can not find the PXE and the TFTP times out.
Anyone got a answer for this problem?
Thanks
-
[quote=“TCUAdmin, post: 34426, member: 25341”]Hey all,
I am a District IT for a School District and we are mass deploying new teacher/lab computersI have everything set up and ready to pull a master image to send out to other PC and I am running into a problem. I have my FOG management up and running and I have a image created in Image Management. I have my FOG management on one laptop connected to a Linksys 8 port switch and the master laptop that I want the image from connected also. I have Sysprep the Master Image and booted it to Onboard NIC. It finds the Client IP that I have set up but can not find the PXE and the TFTP times out.
Anyone got a answer for this problem?
Thanks[/quote]
TCUAdmin’s question is addressed here [url]http://fogproject.org/forum/threads/cant-find-pxe-and-tftp.11278/[/url]
-
Thanks for investing the time to write this up! I have been using FOG for a few years now, using a FOG server instance that originally I downloaded as a Virtual Appliance on a Hypervisor server. We recently moved all of our servers to Hyper-V on Windows 2012, so I followed your directions to install the latest version from scratch in a Hyper-V VM. I created another Hyper-V VM for setting up an image machine. However, when I went to upload the image (after spending considerable time getting the image’s OS prepared, including driverpacks, etc), I found that the VM wouldn’t boot to iPXE. After doing a bit of looking, I found that I’m not the only one having this problem on Hyper-V ([url]http://fogproject.org/forum/threads/change-needed-for-vm-to-pxe-boot-to-fog.10146/[/url]).
What VM platform did you use to create your image machine VM?
-
I used Oracle virtualbox. Free and works perfectly every time
-
@Mike Stoltzfus
I think there are many of us the use Virtualbox for the image building vm -
@Liam thanks for the great step by step guide really appreciate it. But I am quite new to Fog and struggle sometimes with the basic of things. You lost me between creating the unattended.xml file and the creating the iso to boot the test pc from.
My question is where did you save this .xml file too? and how was this incorporated into the iso too b used in a VM or physical box. did u use software? If you could explain this step in detail it will be mush appreciated.oh and BTW for all other noobs out there please ensure that you download the [COLOR=#ff0000]exact[/COLOR] version of WAIK that you are trying to use e.g. win7 sp1 WAIK isn’t compatible with win 7 WAIK and visa versa. Windows has released a supplement but it has no install files
-
Hi
You are quite correct I did gloss over that a bit, sorry. Basically, I saved the unattend.xml file on to a shared drive/folder on my network. You just install windows as you normally do either with a disc or mounted ISO in a VM. I would always use a VM btw unless there really is a reason not to. Snapshots are the key
Now, because your VM/machine will also be on your network in order to pull an image from it, you just access the shared drive where you saved the unattend.xml file from the VM and drag into the \System32\SysPrep folder as described in the walkthrough. Thats all it is, no need to modify any ISO’s.Good call on the WAIK tip, something else to note with that is that I found it wouldn’t let me create a 32 bit answer file on a 64 bit machine and vice versa either. Gotta love Microsoft.
Good Luck
-
@Sully yes that would make sense. So I can re-use this unattend.xml over and over gain and just copy it to \System32\SysPrep folder. Thanks
-
Hello
i’m trying to make the install but i’m having a lot of troble with the tftp, if i’m in the fog server i can test the transference successful with this command:
tftp -v ds.feb.br -c get undionly.kpxebut when i try to do the same from a host i get a time out i already tried two tftp clients for windows and get time out from both, i can connect to the fog and ping it but not use tftp.
I already tried to disable ufw and i get the same error.
I’m using Ubuntu server 10.04.4
-
[quote=“Leandro Silva, post: 35095, member: 24513”]Hello
i’m trying to make the install but i’m having a lot of troble with the tftp, if i’m in the fog server i can test the transference successful with this command:
tftp -v ds.feb.br -c get undionly.kpxebut when i try to do the same from a host i get a time out i already tried two tftp clients for windows and get time out from both, i can connect to the fog and ping it but not use tftp.
I already tried to disable ufw and i get the same error.
I’m using Ubuntu server 10.04.4[/quote]
Open a thread in the correct section, this thread is suppose to be the instructions to set up only, not a discussion on the issues and how to solve them.
-
Excellent job on documenting all of this - I know it took time. Much appreciated!
-
Is there a tutorial on how to add images to the PXE menu?
-
This post is deleted! -
Great tutorial. I was trying to follow some of the hyperlinks in the guide, but they’re not working?
" So what we want to do is look at the DriverPacks repository - here"
“20. First download the Windows Automated Installation Kit (WAIK) for Windows 7 – Here”
“vi. You can also configure Taskbar and Start Menu settings to apply to all users. Technet Article”Question about the driver packs. Does it search for the best driver out of that /inf/ folder or the first one it comes to? I’m planning on dumping the extracted driver cab files from Dell’s website for each model.
-
None of the -here links seem to be active in the howto?
-
I would also mention a part in the guide to check the box in [B]Host Menu > Join Domain after image task.[/B]
-
Why do you use undionly.kpxe instead of pxelinux.0 for the bootimage? When I used the value you gave, the PXE boot could never find the file. Is this a file that got generated someplace else?
Thanks!
-
[quote=“SouperGrover, post: 38925, member: 27066”]Why do you use undionly.kpxe instead of pxelinux.0 for the bootimage? When I used the value you gave, the PXE boot could never find the file. Is this a file that got generated someplace else?
Thanks![/quote]
Starting with 0.33B(?) FOG moved to iPXE from PXE. iPXE is using undionly.kpxe whereas PXE uses pxelinux.0 from /tftpboot. Assuming you’re running 0.33B or later, your DHCP option 67 should be undionly.kpxe, not pxelinux.0 as FOG used to use - option 66 should still be the FOG server IP. Sounds like your DHCP server isn’t set to the correct bootfile (undionly.kpxe)
