Posts made by Boyan Biandov

@george1421 said in Is there a way to make one's FOG server PXE boot native UEFI clients?:

For uefi systems you need to send the uefi boot loader name to the pxe booting client

Thanks for the great answers george1421. I must ask for clarification. First forget 1.2.0 - it’s an old release and I get it, will bite the bullet and upgrade to the latest release.

However even then I’m confused; the file name is passed to the PXE client via DHCP option. Since legacy BIOS (undionly.kpxe) and UEFI (ipxe.efi) clients require different file name to boot how does that work? How would each client get the correct file name? The DHCP option can only pass one file name?

Thanks
~B

Hi guys

Is there a way to make one’s FOG server PXE boot native UEFI clients?

I do have a UEFI ready client, it starts the PXE boot but it goes nowhere? I do have a functional FOG server and legacy BIOS clients boot up via PXE just fine. However the UEFI PXE client does not? It just times out. No errors, no nothing. This is an inspiron 2-in-1 with the properly UEFI-recognized USB-Ethernet dongle and after selecting IPv4 PXE boot from the F12 menu upon boot:

Thanks everyone
~B

I know this is an old topic but I wanted to keep the continuity of knowledge. I’m testing Inspiron 2-in-1 7573 for a first time and although I did get the “recommended” USB-to-Ethernet dock from DELL, even though it is seen in the UEFI as a bootable device after enabling the “network network stack” and even though it starts the IPv4 PXE boot process it does NOT PXE boot. It times out eventually.

So I am assuming I need the USB-to-PXE method and then specify my FOG IP and from there it would be a smooth sailing. My problem is that I do NOT have /tftpboot/ipxe.efi on my existing FOG server (I’m at 1.2.0)? How do I get that EFI file so I can follow the guide and make the USB stick? Otherwise my FOG server runs fine, has been for the past 15 years and legacy BIOS PXE clients boot just fine?

Thank you
~B

Hi everyone,

I’ve been running 1.2.0 for years. Solid and happy. However I would like to upgrade it to the latest 2017 release but I don’t want to do an in-place upgrade. Back in the day I’ve moved many FOG servers from one box to another following a very simple process:

a) mysql dump the database from one server and import it onto another “blank freshly installed FOG” server.
b) copy the image files using simple rsync

This time however I want the new “recipient” server to be the latest version of FOG.

What anyone tell me whether this would work? If not what would you suggest as a good way to move my existing FOG onto another box and run the latest version?

Thanks
~B

the restart did it for me:

[09-14-17 8:44:09 pm] * Starting FOG Multicast Manager Service
[09-14-17 8:44:14 pm] * Checking for new tasks every 10 seconds.
[09-14-17 8:44:14 pm] * Starting service loop.
[09-14-17 8:44:14 pm] * No tasks found!
[09-14-17 8:44:24 pm] * No tasks found!
[09-14-17 8:44:34 pm] * No tasks found!

@Psycholiquid I did see it in your script but I have NEVER put it in \panther just the \sysprep as you posted your command so maybe your habit saved you from facing my “challenges” lol

@MRCUR said in Windows 10 unattend.xml (sysprep answer file) challenge:

@Boyan-Biandov That’s the directory that sysprep is actually run from & where logs are sent. I don’t believe the directory location is your issue.

You’ve been super patient so I really want to thank you for that and I don’t mean to contradict every post, I mean it. So it was exactly that, I had to copy my xml file to BOTH locations and then everything worked. Either I’m nuts or nobody had tested the November build of Windows 10 Pro ISO (the one that comes with SP1 integrated so to speak; version 1511 build 10586.420) to discover all those regularities. The ISO is MAK license specific (not retail) straight off eOpen under an EA (same key, few thousand activation allowed). I’ve monkeyed with sysprep for a decades and this is the first I see crazy crap like this

@Psycholiquid

Thanks, driver I don’t know about but there’s definitely something that baffles me: why would it look for the xml in this directory? I’m stumped on this one…Do you all have to copy the xml file to both locations before running sysprep against one of the copies?

2016-07-09 08:11:52, Error                        [oobeldr.exe] User input error was detected in unattend file. Error: [0x0]
2016-07-09 08:11:52, Info                  IBS    UnattendErrorFromResults: Hit an unattend error; dumping any info we have about the failure...
2016-07-09 08:11:52, Info                  IBS    UnattendDumpSetting: ------Unattend setting error / warning------
2016-07-09 08:11:52, Info                  IBS    UnattendDumpSetting: Error code = 0x8030000b
2016-07-09 08:11:52, Info                  IBS    UnattendDumpSetting: Pass = oobeSystem
2016-07-09 08:11:52, Info                  IBS    UnattendDumpSetting: Component name = [Microsoft-Windows-Shell-Setup]
2016-07-09 08:11:52, Info                  IBS    UnattendDumpSetting: --------------------------------------------
2016-07-09 08:11:52, Info                  IBS    UnattendErrorFromResults: Error text = Windows could not parse or process unattend answer file [C:\Windows\Panther\unattend.xml] for pass [oobeSystem]. The settings specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].

@MRCUR Thanks for the XML, it does open up in SIM but produces this when tested in the real world:

@george1421 said in First time started using DeskPro 600 G2 P5U70UT#ABA and NIC compatibility fails; latest kernel:

We are seeing this model being trouble quite a bit lately.

You need kernels 4.1 or newer to activate that nic. If you have some linux skills I can tell you where to get the latest kernels for FOG.

YEP 4.1 worked. Thanks very much George!
~B

@Sebastian-Roth Thanks for the quick reply.

Actually this turned out to be a NIC problem. I am using the latest kernel:

Kernel - 3.19.3 TomElliottUSB

Date : July 22, 2015

Version : 3.19.3

And I get an incompatibility error:

First time started using DeskPro 600 G2 P5U70UT#ABA and registration hangs on “attemping to register host”

I’ve used the 600 G1 series for a year and it seems that the difference here is the G2 – they must have made some kind of hardware change or something to the bare metal which has caused the issue. Any help will be appreciated from the community!

I am on For 1.2.0 using the init_32.xz stock bzImage32 that came with 1.2.0 and undionly.kkpxe PXE boot file

The new PC is the latest HP Desk Pro:

HP ProDesk 600 G2 - Core i5 6500 3.2 GHz - 8 GB - 500 GB *
CDW Part #: 3845120 | Mfg Part #: P5U70UT#ABA

Thank you
~B

I wish Wayne

That’s 7. Sysprep 10 is completely messed up and what works on 7 doesn’t on 10. So I’m hoping for someone who actually uses 10. D

Same here; except my computer names start with lab-xxxxx

<ComputerName>lab-*</ComputerName>

Works like a charm!

Hi everyone,

I’ve been a huge proponent and user of FOG for close to 10 years starting with Windows XP. My beef is that it seems Microsoft (what a surprise) has changed the core structure of unattend.xml with the version of sysprep for Win 10.

I’m reaching out to those using FOG with Win 10 for some assistance. In prior versions of sysprep it used to be that one can auto-name (use * for machine name) the PC and auto-join it to the domain all within the xml. Now I read some craziness about having to run power shell scripts and how the naming step is AFTER the joining step in sysprep and stuff like that.

Do you use sysprep with FOG for auto naming and auto joining your Win 10 PCs? If yes how did you solve that sysprep craziness?

Thank you!

Good reminder; I also need to report that HP Pro Book 440 G2 requires the boot file changed to undionly.kkpxe

Yep I did; but here is what actually worked for me. I had to restart the FOG services in order for the log to start updating with the correct time zone

[CODE]boyan@fog4:/etc/php5/cli$ sudo service FOGScheduler restart

• Restarting FOG Computer Imaging Solution: FOGScheduler [ OK ]
  boyan@fog4:/etc/php5/cli$ sudo service FOGMulticastManager restart
• Restarting FOG Computer Imaging Solution: FOGMulticastManager [ OK ]
  boyan@fog4:/etc/php5/cli$ sudo service FOGImageReplicator restart
• Restarting FOG Computer Imaging Solution: FOGImageReplicator [ OK ]
  boyan@fog4:/etc/php5/cli$
  [/CODE]

Now all is good as expected:

[CODE][02-07-15 8:51:18 am] * Starting FOG Multicast Manager Service
[02-07-15 8:51:23 am] * Checking for new tasks every 10 seconds.
[02-07-15 8:51:23 am] * Starting service loop.
[02-07-15 8:51:23 am] * No tasks found!
[02-07-15 8:51:33 am] * No tasks found!
[02-07-15 8:51:43 am] * No tasks found![/CODE]

Yes Ubuntu and yes both placed were updated…any other ideas?

I discovered that changing the php.ini DOES correct the time zone issue for both the bandwidth graph and for imaging log. However the FOG log still goes by UTC? How does one change that? Here’s an example of the log which I am talking about:

[CODE][02-06-15 4:53:32 pm] * Starting Image Replication.
[02-06-15 4:53:32 pm] * We are group ID: #1
[02-06-15 4:53:32 pm] * We have node ID: #1
[02-06-15 4:53:32 pm] * I am the only member, no need to copy anything!.
[02-06-15 5:03:32 pm] * Starting Image Replication.
[02-06-15 5:03:32 pm] * We are group ID: #1
[02-06-15 5:03:32 pm] * We have node ID: #1
[/CODE]

YES the trick was [SIZE=5][B][FONT=Consolas]next-server <ip of PXE Server>[/FONT][/B][/SIZE]