nope, was not aware!

perfect i guess. Although to keep a std you could move it down and call it protect…
job done and easier to identity tick box.

Yep you are correct.

not sure how I missed it. I searched for my hostname in the reg with no matches.
It was 64 and i didn’t look under the Wow6432Node folder.

Oh well, thanks

Please note that it’s been said that the DisplayManager has been built back into the client.

https://forums.fogproject.org/topic/8383/svn-5949-screenres-manager/8?loggedin

@Joe-Schmitt said in Host Screen Resolution:

@networkguy 0.10.0+ removed DisplayManager from the client. As @Sebastian-Roth pointed at, its a very “Windows only” thing and never received much use compared to how much effort went into maintaining it. @Tom-Elliott, perhaps we can add some kind of “warning” next to display manager stating it isn’t present in 0.10.0+ ?

Obviously if there is enough support for it, we can add back display manager, but we won’t be porting it to OSX or Linux.

i’ve got to version 1.5.0.16

using: git checkout working-1.5.1

that right?

@george1421

Thank you, perfect followup…
worked well as well L13 Yoga success.

Thanks to all.

@george1421

And if i want to go back to another kernel due to other hardware having issues, i can just download from the in fog menu?

Sorry if i’m missing something here but I have this same issue with the same device.

I wish to use UEFI so ipxe.efi?

How do I as a N00b get this to work?

I’ve updated my kernal to 4.19.101, but i don’t see any 5 versions ?

update - i’ve updated fog to 1.5.7, using ipxe.efi but still a little stuck.

I mean a USB NIC Dongle.

the 1st again works fine and then it boot loops.

so during the image process:-

You boot and it downloads the image then it reboots to complete sysprep of our image but gets stuck. We eaither switch off the PC and back on (continues) or remove the USB NIC and it continues…

But we have seen this on a few internal NIC devices also.

No, we get it with other devices. Some being fogged via a USB dongle. could that be an issue?

I find that a lot of our machines (Dell) and virtual machines seem to boot loop if they are restarted, but not from cold boot?? can anyone explain or suggest a resolution.

The screenshot is just before a loop. (THANKS)

I tried to find it again and I can’t.
I’ll have another look.

Regardless, please can it be made possible.

When we add a new host, can this tick be enabled by default, without having to say yes to AD at registration?

I wish to force logout automatically on new host registration.
The tick box is under Active Directory but can be used without the rest of the AD items.

Can you force this on in FOG_Settings or do i need to say add to domain after setting the defaults. Issue there is the “Join Domain” will also be ticket and is not desired.

Thanks in advance.

I looked into the forum and found this being requested but it didn’t look like it was completed.

When i add machines to a group, it adds random machines at the same time.
We have had this issue for some time and thought it was a bug, but this would have been fixed by now if it was. We do complete the DB maintenance tasks as well and from memory this helped but this also don’t seem to resole it anymore.

Please advise.