Computer Group policy seems to not apply at bootup.

Home Forums Microsoft Networking and Management Services GPO Computer Group policy seems to not apply at bootup.

This topic contains 3 replies, has 3 voices, and was last updated by  weirdo 4 weeks, 1 day ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts

  • jason0923
    Participant
    #167758

    We’re having a new problem now. We have a process of imaging machines with SCCM. It installs Windows 10, adds it to the domain and etc. And all that still works. We have a Radius WIFI policy deployed in Group policy that makes the laptops connect to the WIfi and that has “sort of” stopped working. So up until last week we’d image machines plugged into the lan and you could unplug them once done and login to them via the wifi but now when we unplug them they cannot connect to the Wifi. If I login locally I see event IDs that says “the authenticator is no longer present”

    Heres the stranger part. If I plug them into the LAN and login as any user then disconnect the cable it somehow gets some sort of GP update fix and then the Wifi connects. And all the thousands of existing machines still connect fine so I don’t think its a problem with the policy itself but its as if its no longer applying at boot up anymore. I don’t know what may have changed to cause this. Anyone have any ideas. We image a lot of machines and having to manually login to each one just to get the wifi to connect takes a lot of time.


    Ossian
    Moderator
    #192163

    What does an RSoP on the machine show? It will tell you in detail which policies have been applied.


    weirdo
    Member
    #390586

    Nothing, I can only troubleshoot them in this state logged in as a local user. In that login the RSOP does not show any computer policies in RASOP or GPresult. and if I login as a domain user on a cable it fixes the problem but it doesn’t let me determine what the problem was


    weirdo
    Member
    #390587

    We did still have the Windows v 1709 version in our SCCM collection. i tried that and it works fine. Must just be a bug in 1803. Progress…

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.