Posts made by CamGreezy

The process you described below worked great, feel free to mark this as solved and thanks again for your help and support, this software is going to make things a lot easier and more efficient for us here!!

Thank you, this is very helpful. I am thinking due to time constraints and a fairly static environment I’ll give option 1 a try first, then as time permits I can work on option 2 and have it ready for next year.

Just to be clear, I should install all drivers on the reference image, run sysprep, then register the host and capture the image through fog?

I’ll give this a go and report back with the results.

Thanks again,
Cam

Server

• FOG Version: 1.4.4
• OS: Ubuntu 16.04

Client

• OS: Windows 7

Description

I am new to FOG and to imaging in general and am having trouble following the wiki on how to create a master image for my environment. I am at a school and I’d like to create one staff image and one student image that will both work on 4 different pieces of hardware (HP workstation Z210, Z220, Z230, Z240). In searching through the wiki, I’ve found 3 different pages that each seem to outline slightly different processes and I’m having trouble getting any of them to work. The pages I’ve been following are:

https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#FOG_Client_with_Sysprep

https://wiki.fogproject.org/wiki/index.php?title=What_do_I_have_to_do_to_an_image_before_capturing%3F#Windows_Vista_and_Windows_7

https://wiki.fogproject.org/wiki/index.php?title=Client_Setup#Setup_a_Default_Profile

So far I have the image I’d like to sysprep captured pre-sysprep and everything I’ve tried has resulted in me needing to re-deploy that image to the workstation I’m using and try again. If there is another post somewhere I missed or if someone can confirm one or multiple sets of instructions to follow, I have no problem putting some more hours into troubleshooting this issue, just trying not to spend too much more time following guides I don’t fully understand/I’m unsure are up to date.

Thanks in advance,
Cam

Nothing specific, just know it’s something I have to do that I haven’t yet. I was having trouble finding anything referring to that specifically on the wiki so if you have a link to any documentation that would be helpful, otherwise I’ll put some time into it and make a new post if I hit any specific issues.

I expect the 2nd file didn’t give any output because it was from a different subnet. Could you please point me to the info I need to configure FOG to run across subnets before you mark this as solved?

Thanks again, feel a little silly but now I know!

Oh ok, that’s exactly the issue. Have not worked with PXE much before and thought the option 66 and 67 info would replicate to our 2nd DC, but that was not the case. Fixing that lets me boot right into FOG. Thanks for the help!

https://drive.google.com/file/d/0B7KKPwLD3OQQU3l5RGg5MTNpSGs/view?usp=sharing Is the output file when trying to boot from the same subnet.

https://drive.google.com/file/d/0B7KKPwLD3OQQZGNEdFc0WmF2Smc/view?usp=sharing Is the output file when trying to boot from the workstation subnet.

That was correct, but I recently moved the FOG server to a different subnet for testing purposes. Ideally I’d like to house it on the 172.16.50.x/24 subnet, so I’ll move it back since the issues still exists.

Server

• FOG Version: 1.4.4
• OS: Ubuntu 16.04

Description

I’d like to start off by saying I’m pretty new to this stuff so thanks in advance for your help and patience. I’ve been playing with this the past 3 days and am having trouble getting any clients to boot into FOG. I’m using my own DHCP server which is on the server subnet and most of my clients are a separate workstation subnet. Initially the FOG server was on the server subnet. Trying to PXE boot would timeout from the client subnet. Trying to boot from the server subnet got a little further, but still ended up timing out as seen below.

The 172.16.50.23 IP corresponds to our system center server which PXE used to boot into but that server is offline now. DHCP Option 66 is no longer pointing to it, but it looks like somehow PXE is still getting that IP address from somewhere.

After this happened, I changed the IP of the FOG server to be on the workstation subnet. Now PXE boot from the workstation subnet times out with PXE-E32 and trying from the server subnet gives PXE-E11 followed by PXE-E38.

I’ve tried resetting and updating the fog user password, checked my permissions, and tested the tftp connection from windows and Linux (Linux succeeded, windows gives “can’t write to the local file ‘undionly.kpxe’”). I been banging my head against the wall for hours and seems like I get stuck at this point every time despite rebuilding the server using different versions of FOG and different versions of Linux. I’d appreciate any advice anyone can give and please let me know if you need any more info or screenshots from me.

Thanks,
Cam