Posts made by Psycholiquid

ok, doing it now. Sorry roaming profiles migration making me manic…

@george1421 Stupid thing requires I constantly touch it. I hate these surfaces. in order to boot from anything other than Windows Boot I have to swipe the screen I need those white gloves jewelers use.

02_efi_timer_ipxe_wo_debug: No hang on init.xz

02_efi_timer_ipxe.efi: No hang on init.xz

Hating you right now and you must feel in my pain of how small the text is on these dang Surfaces. 4K FTL

I am out today but will do this first thing tomorrow morning.

@themcv Well if they were reimaged and the computer was not removed from the domain first the workstation will sometimes still be able to talk to the domain (Shouldnt be able to but does)

I would delete it form the domain and drop the computer from the domain at the workstation and see if it resolves itself.

Was the machine already part of the domain when reimaged or something. If the machine thinks it is not joined and the Domain thinks it is (not deleted before imaging) it can cause this reaction I have seen in my environment.

@george1421 Yeah I am not versed in DNSmasq but it sounds like I need to be I will start looking at that also

OK ok ok , I am an idiot… (go ahead take the stab)

So i forgot I have load balanced / failover DHCP in my environment. SO even if the fog server is set to one DHCP server it will still be pushed to the other in case of high utilization… (damn it me!!!)

So I was able to get it working more granular down to the UNDI. With what @george1421 said this could be a problem later but I am thinking it will be fine for now as the versions will probably only go up from here for change dramatically. So here is the setup for clairity.

DHCP (Windows Server 2012 R2) 'Failover is on your to configure"

Set Vendor Class for hardware. (You can get this from Wireshark easily if you run it on the DHCP server and set ip.src == IP of client PC)

Cant really copy and paste but here you go anyway: PXEClient:Arch:00007:UNDI:003016

Then goto Policies for either your whole server or for your scope depending on how your network is setup:

Make a new Policy, name it and description.

Add Condition:

Set Options:

Now if you refresh your Scope Options you will see the new options:

I have tested and this works specifically for the Surface Pro 4s with the dock. I am not sure about the dongle yet because I don’t have one.But I will see about getting one.

This isn’t a resolvable post really. More of a testing platform post for him to see what his files are doing.

Not sure exactly what SR is looking for, he just requested that I try each file and let him know the result as posted. Using his template.

We have about the same time frame work wise so I told him I would test them all for him today

svn5938_ipxe: hang on init.xz

He requested me to test them and put weather it hung or not.

@Sebastian-Roth

svn5918_ipxe: hang on init.xz

svn5902_ipxe: hang on init.xz

svn5901_ipxe: hang on init.xz

svn5836_ipxe: hang on init.xz

svn5835_ipxe: no hang on init.xz

Server

• FOG Version: 1.5.0 Rev 8
• OS: Ubuntu 16.04.3 LTS

Client

• Service Version:
• OS:

Description

02_efi_timer_ipxe.efi: no hang on init.xz

@psycholiquid and DHCP failed (This doesnt have the secondary NIC plugged in