Posts made by Gael

@george1421 @Sebastian-Roth

Ok,

All is ok with kernel 4.19.64

Very thank for you help

@george1421 Very sorry to forgot tell the kernel update part.
We updated to 5.1.16 because we will shortly receive new DELL optiplex 3070 that have NvMe SSD.

@george1421 Contrôleur Realtek PCIe GBE Family
PCI\VEN_10EC&DEV_8168&SUBSYS_085C1028&REV_15\4&1285CEFC&0&00E0
PCI\VEN_10EC&DEV_8168&SUBSYS_085C1028&REV_15
PCI\VEN_10EC&DEV_8168&SUBSYS_085C1028
PCI\VEN_10EC&DEV_8168&CC_020000
PCI\VEN_10EC&DEV_8168&CC_0200
PCI\VEN_10EC&DEV_8168&REV_15
PCI\VEN_10EC&DEV_8168
PCI\VEN_10EC&CC_020000
PCI\VEN_10EC&CC_0200
PCI\VEN_10EC
PCI\CC_020000
PCI\CC_0200

@george1421 That’s work!

1.5.2 :
file bzImage
bzImage: Linux kernel x86 boot executable bzImage, version 4.19.1 (jenkins-agent@Tollana) #1 SMP Mon Nov 12 18:23:08 CST 2018, RO-rootFS, swap_dev 0x8, Normal VGA
file bzImage32
bzImage32: Linux kernel x86 boot executable bzImage, version 4.15.2 (builder@c38bc0acaeb4) #5 SMP Tue Feb 13 18:32:54 UTC 2018, RO-rootFS, swap_dev 0x7, Normal VGA

1.5.7 :
file bzImage
bzImage: Linux kernel x86 boot executable bzImage, version 5.1.16 (sebastian@Tollana) #2 SMP Wed Aug 28 17:12:41 CDT 2019, RO-rootFS, swap_dev 0x8, Normal VGA
file bzImage32
bzImage32: Linux kernel x86 boot executable bzImage, version 4.19.64 (jenkins-agent@Tollana) #1 SMP Mon Aug 5 09:59:10 CDT 2019, RO-rootFS, swap_dev 0x7, Normal VGA

Ok, i will do that.

But for information, another test i have juste done:

I only asked fog 1.5.7 to capture a working dell optiplex 3060 (without sysprep or anythink else), after capture was done i shutdown computer and: the network card was shutdown!

@george1421 Sorry typo, Optiplex 3060 not 3050

@Sebastian-Roth Done. Network card was shutdown too

I will scp image from old fog to new and report here the result.

@george1421 It’s not a WOL packet problem because the network card is shutdown (leds powered off)
Can the fog client have any impact?

@Sebastian-Roth I think I can say that I already did it because, at first, I thought that my updated master image was the problem. I recovered a copy of my Fog server before it was updated (and before my image was updated) from backup, then i deployed the image to a VM, then I captured it (without powering-on the image) with my Fog 1.5.7 server.

@george1421 Hi, thank for answer but fast startup is already off in all my master image.

Also understand this exemple:

-> I take one of my Dell Optiplex 3060 computer, he is running ok, (faststartup is disabled), I shutdown windows and i see network card is keep on.
-> I power on my Fog 1.5.2 server and ask it to deploy my master image (same image that is already running on the computer, also with faststartup disabled)
Wol work computer was reimaged and I shutdown windows and see network card is keep on.
-> Now I shutdown my Fog 1.5.2 server and I power on my Fog 1.5.7 server and ask it to deploy my master image (same image that is already running on the computer, also with faststartup disabled)
Wol don’t work, i power on computer myself, computer was reimaged BUT when I shutdown windows I see network card is shutdown…
->Now I shutdown my Fog 1.5.7 server and I power on my Fog 1.5.2 server and ask it to deploy my master image (same image that is already running on the computer, also with faststartup disabled)
Wol work computer was reimaged and I shutdown windows and see network card is keep on.

Like you, i don’t understand…

I have a problem that I do not explain.

I have Dell Optiplex 3060 computers.
I have a Windows 10 master. image

Since I updated FOG from 1.5.2 to 1.5.7, on each PC I remastered, Windows turn off the network card when it shut down, preventing further WOL.
This is Windows because if I remove the power and I put it back, the network card is turned on (so setting bios out of cause).
You will tell me that it is my image, what I thought as well except that here are the facts: (checked several times to be certain):

I restored from the backup my FOG while it was still in 1.5.2
I captured back my master image updated last week.

I therefore have:
FOG 1.5.2 with:
-the master image of January (currently deployed everywhere)
-the master image updated last week

From a FOG 1.5.7 with:
-the master image of January (currently deployed everywhere)
-the master image updated last week

If I deploy any of my 2 masters images from the fog 1.5.2 the network card remains on after shutting down Windows.
If I deploy any of my 2 masters images from the fog 1.5.7 the network card turns off after shutting down Windows

The problem does not come from the image, nor the bios or AD GPO.
I do not understand how the way used to deploy the same image can affect how Windows turns off the machine …

If you have an idea?

Thank you