Tranquil IT Forum

Hello everyone, and a big thank you for this forum.
I just migrated my PCs to Windows 10 version 1709, managed by an Active Directory Samba 4 version 4.6.7.
I'm encountering a strange issue with my Windows 10 clients using DHCP: my Group Policy Objects (GPOs) aren't being applied, even though the TCP/IP configuration is correct. When I switch to a static IP address, everything works fine.
I have the impression that the DHCP client isn't starting correctly or at the right time.
Has anyone else experienced this?

Regards

Good morning,

djehin wrote: ↑Feb 2, 2018 - 12:02 PM Hello everyone and a big thank you for this forum.
I just migrated my PCs to Windows 10 version 1709, administered by an AD Samba 4 version 4.6.7.
I'm encountering a strange issue with my Windows 10 clients using DHCP; my GPOs aren't being applied, even though the TCP/IP configuration is correct. When I switch to a static IP address, everything works fine.
I have the impression that the DHCP client isn't starting correctly or at the right time.
Has anyone else experienced this?

There's no reason why GPOs shouldn't apply to DHCP. What does `gpresult /z` return on a machine using DHCP?
Is the GPO that isn't being applied a startup GPO? If the machines are on Wi-Fi (or if there's 802.1x), it's possible that the network interface comes up after the GPO client starts, and therefore the startup GPOs won't execute.

Sincerely,

Denis

Hello,

thank you for your reply.
The gpresult indicates that the computer GPOs are being applied.
My Windows logs show errors 1129 and 1130, indicating that the AD server is not accessible.
I suspect a problem on the 802.1X side.
Is there a way to configure the switch to make the DHCP server assign DHCP leases faster?
I believe spanning tree might solve the problem; my switch is an HP 4208 Procurve.
Thank you for your help.