Posts made by Taspharel

@wayne-workman

Yeah, their working on it …

But as a NGO we are none of the “big payers” so it’s not always easy to “urge” them to do something in a timely manner

But they are great for working with us of course.

We are planning a big rollout on the 20th of october, so its the timeline that is making me try to work around restrictions.

So … both DHCP requests go to the second Domain Controller, the one that has Server 2008 on it … crap.

I guess there is no way to make the request somehow go back to the other DC when it reaches the fog server?

I would love to avoid having to have the company that manages our Domain Controllers have to install a new Domain Controller

So, I managed to look at the pcap file and get the vendor ID from it.

The HP PC that only runs on legacy bios has the vendor id PXEClient:Arch:00000:UNDI:00201 which should be caught when I add the Vendor ID PXEClient:Arch:00000 with a following Asterisk, but to make sure I added it as a separate Option in the DHCP server and it still wont boot with undionly.kpxe

I changed the default (you were right) from ipxe.efi to undionly.kpxe and that machine boots to undionly.kpxe

So trying the other side I checked that Vendor ID and it is PXEClient:Arch:00007:UNDI:003016 - added a rule to specifically adress this -> still tries to load undionly.kpxe instead of ipxe.efi

I will check if the DHCP request goes to the Windows Server 2012 or the Server 2008, maybe it requests it from the “older” DC

Hi.

So, my situation is as follows:
In our network we have two Domain Controllers, one based on Win Server 2012, the other on Server 2008.

I read the wiki in regards to making UEFI and Legacy coexist and have all the settings set according to the guide there - and I saw that it says it wont work on Server 2008. In general though, every change I make on our DC1 (the one with Server 2012) will be taken up by the hosts when booting without me having to change the settings on DC2 (the Server 2008), I guess its prioritized that way…

When I try to boot a Non-UEFI PC via the LAN, it tries to get the ipxe.efi file - which is too big for its memory - and aborts the boot process. Even though the Policies are in place to send the fitting ipxe.efi or undionly.kpxe to the host depending on Vendor ID.

Can anybody give me a hand and help me find a possible solution?

I made a tcpdump that might say something - https://drive.google.com/file/d/0B0TWuKtXovQOaEJTcDI4MFVHZVk/view?usp=sharing - but I cant seem to understand it …

Thanks for any support you can give.

@jim-graczyk said in FOG Client Cannot Connect to FOG Server:

• Build the image PC with OS, applications, etc. - whatever you want already installed. I subscribe to the notion that a windows image should contain the MS OS CD installed, FOGService Installed and then the rest of the content should come from Snapins. As little as possible should be done by hand because can seldom repeat the process if we have to. For this process, however, it doesn’t matter.

On a side note - check out chocolatey(.org) … I make sure that service is installed on all our hosts. Then all I need to do for new programs or updates is make a simple batch-file as snapin for fog that sends the command

choco update all -y
or
choco install xxxy -y

to have all programs brought up to date or a new program to be installed silently. And to make sure I add a > C:\Somepath\Choco-log.txt to the command to be able to check on errors etc.

It is even possible to make windows 10 use the chocolatey repository in apt-get without having to install the chocolatey service if you want to keep it even more simple.

If you want to go fancy - and automate the process further - have a look at the postdownload script, for example here:

https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script/7

The process would probably be along the lines of:

Image the machine -> FOG Postdownloadscript runs before boot -> Harddrive is mounted -> Certs are copied similar to your process above -> Setupcomplete script only has to add the certificates to the certificate store (or possibly the postdownloadscript can be modified to do that too)

All you would need then is to keep the certificate scripts up to date - which FOG probably does by itself after updates etc. - and they would be copied to your host without any further interaction needed.

Any you would save having to mount the harddrive to another machine to copy stuff … seems like its worth it to have a look at?

@taspharel Or of course you use Group Policies and add the correct Certificates there?

Don’t have a lot of time sorry, but maybe what I had to do will help here?

During my attempts to make my setup work for us, I at some point had to make sure that the correct Certificates are in the windows store.

So in my Setupcomplete.cmd I have:

certutil -addstore “Root” “C:\Windows\System32\Sysprep\fog.ca.cer”
certutil -addstore “Root” “C:\Windows\System32\Sysprep\ca.cert.der”

The cert files I copy to the folders above in my golden image and they are imported into windows then. Possibly the location could be on a network share as well - or automated via FOGs scripting options if setupcomplete isnt able to access them?

This way you would have to only change the certificate files in one location and they would be pulled by either your setupcomplete script or the fog post-install scripting after imaging.

Sorry if I missed the point though, totally possible

Moderator edit: #wiki worthy

I would need the german keyboard layout for our setup.

But I get that its difficult within the current system, thanks for clearing that up

Hi.

Maybe this is a thing and I just havent found it yet:

Is there an easy way to change the keyboard layout of the FOG Bootmenues?

I can work around the US keyboard layout of course, but it would be a great convenience

Just an end user, don’t know if there is a way.

Workaround that might work:

Create a group for every brand, desktops, laptops etc. and assign an image to those. Then when assigning that group to your machines they should get the corresponding image.

I’m not sure I get what the problem is, sorry

Did you read the links?

To sysprep an image you make sure you work in audit mode, set up the system the way it is supposed to be set up and then you sysprep the machine.

During the sysprep process an autounattend.xml file is called, within this you can create a user or activate an admin. Those users then have the same settings you specified in the Audit mode.

So: Audit mode, prepare the system in the way you want it to be for the user -> sysprep -> in Unattend File you create the user you want -> That user has all the settings you prepared for it. If you make a separate user within the Audit process, I dont think that will work well with the sysprep process?

There might be other ways to do this of course, just the way I’ve been working on our setup the last year.

Then again we have a setup with a domain, different users that have their mailadresses tied to their login etc. etc. - you might not need all of that.

If you create an answer file you can also create users within that answer file. And using the copyprofile setting in the answer file you can make sure that all users get the same settings.

So the user you create via the answer file will have the settings you used while sysprepping the machine and all users that use the computer will have those settings as well - if you have people joining within a domain for example.

Two links to some info - go from there:

https://technet.microsoft.com/en-us/library/cc749317(v=ws.10).aspx
General Advice on Answer File

And:
http://sybaspot.com/the-complete-guide-to-preparing-a-windows-7-deployment-image-using-audit-mode-and-sysprep-with-an-unattend-xml-answer-file/
They may be a little out of date, but you’ll get the general idea from it.

Also for a simple Answer file:
http://windowsafg.no-ip.org/

Ah well … turns out i’m just simply blind

I changed the path in the commands to my local folder structure but missed one spot … since it booted pretty far I thought everything must be written correctly, turns out: No.

Thanks for the help.

Hi.

Thanks for your time.

I followed these instructions: https://wiki.fogproject.org/wiki/index.php?title=Include_any_ISO_in_the_FOG_Bootmenu#System_Rescue_CD

Only difference that I can see: I dont have the files in the folder /srcd but in the folder /iso and adapted the commands accordingly … I’ll try changing that and see what happens.

No, was the first time I tried it.

And according to the mysql thing there should only be 3 active scheduled tasks?

I just ran the mysql cleanup commands from the fog-wiki … problem remains.

Just checked: Yes, all the other menu points in the tasks menu open correctly.

Maybe somebody has an idea.

I followed the instructions from the wiki to add the SystemRescueCD as an image to my fog server (latest RC, based on CentOS7). It starts up fine, but right after selecting the keyboard layout I get the following error:

Filesystem image sysrcd.dat is corrupt: md5sum incorrect

I redownloaded several times, checked the md5sum in windows and on CentOS7, recalculated the checksum and wrote it to sysrcd.md5 … anybody have a hint what else I could check?

Okay, here we go.

Doing this first thing in the morning yields:

MariaDB [fog]> SELECT * FROM scheduledTasks\G
*************************** 1. row ***************************
stID: 1
stName: Deploy Task
stDesc:
stType: C
stTaskTypeID: 1
stMinute: 50
stHour: 16
stDOM: 13
stMonth: 9
stDOW:
stIsGroup:
stGroupHostID: 2
stImageID: 0
stShutDown:
stOther1:
stOther2: -1
stOther3: fogadmin
stOther4: 1
stOther5:
stDateTime: 0
stActive: 1
*************************** 2. row ***************************
stID: 2
stName: Hardware Inventory Task
stDesc:
stType: C
stTaskTypeID: 10
stMinute: 10
stHour: 10
stDOM: 1
stMonth: 11
stDOW: 0
stIsGroup:
stGroupHostID: 82
stImageID: 0
stShutDown:
stOther1:
stOther2: -1
stOther3: fogadmin
stOther4:
stOther5:
stDateTime: 0
stActive: 1
2 rows in set (0.00 sec)

After that I scheduled a task, went to tasks view and waited for the freeze, after it shows the additional task:

*************************** 3. row ***************************
stID: 3
stName: Memtest86+ Task
stDesc:
stType: C
stTaskTypeID: 4
stMinute: 1
stHour: 1
stDOM: 1
stMonth: 1
stDOW: 1
stIsGroup:
stGroupHostID: 80
stImageID: 0
stShutDown:
stOther1:
stOther2: -1
stOther3: fogadmin
stOther4:
stOther5:
stDateTime: 0
stActive: 1
3 rows in set (0.00 sec)