Vildar

Just trying to go through them now. We have a lot. Though the powers that be have decided to not spend a lot of time on this now. And just disable sleep for these machines. That was going to be my next step. But the higher ups have decided to ignore it for now, and roll them out with sleep disabled. As sleep is the only thing effected, it will be something ill have to do another time.

Interestingly.. This has worked. Which is baffling. As when joined to the Domain, the OU its in has no GP objects applied to it. Has opened more questions.. but its a start. Thanks!

Hi all. Not sure where to start with this. But here goes. We have a bunch of these new HP Omni desk Slim Desktop PC's. Model S03-0001Na equipped with 14th Gen Intel processors. That we have proceeded to put our Windows 11 Edu 24H2 install onto using SCCM. This image is one we use across the entire site. The issue here is we can not put them in sleep mode. They just crash and we cant get them out of sleep. Have to force shutdown by holding the power button. Only events in event viewer are about the previous shutdown was improper. All drivers are installed. Both taken from the original factory image. And from HP's website. Bios is at its latest. And we have no GP's effecting anything to do with power. I've looked at disabling S0 modern standby. But that doesn't help. Still hangs and crashing when going to sleep. This is the only model of machine out of 300-400 total computers that shows this kind of issue. But after trying all drivers and even a 23H2 image there has been no luck. Factory installed image of Windows 11 Home seems to work fine. It will sleep and wake on command every time. Anything I'm possibly missing here? Other than recreating our stock 24H2 image on the hardware I'm at a loss. Thanks in advance

We do actually. Though like you im not sure its needed anymore with Office 365. So ill look into getting rid, and who knows. Thanks for the suggestion

Unfortunately it seems this did not work. But i am now looking into the Hardened UNC path option. So will give that a try and see what comes of it

Ive currently got them set to one roomk that was particulally troublesome. So will see over the day how that goes.

Interesting, thanks for the reply. Where would you set these, on the DC or on the PC's themselves? We have a room of new PC's where this keeps beeing an issue. So i can set it to just that room for now and see how things go.

We thought this too. So we altered the named policy it was referencing. Even deleted and remade but unfortunatly didnt seem to have an effect.

It is yes, as this was one of the first things we checked

Thanks for the replys. We have checked both DNS and DHCP. We have 2 of each. Server IP'S are what they are meant to be, and the entries in DNS and DHCP point directly to them.

Greetings to all. Apologies if this is in the wrong area. Lately ive been coming accross the same Group policy error over multiple machines. Both Windows 10 and Windows 11. Though on only select machines. And all atemps to find out whats going on are stumping me. The error is below: "The processing of Group Policy failed. Windows attempted to read the file \\******\sysvol\******\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini from a domain controller and was not successful. Group Policy settings may not be applied until this event is resolved. This issue may be transient and could be caused by one or more of the following: a) Name Resolution/Network Connectivity to the current domain controller. b) File Replication Service Latency (a file created on another domain controller has not replicated to the current domain controller). c) The Distributed File System (DFS) client has been disabled." Bit of background. We have 2 domain controllers. All PC's are imaged with either Windows 10 or recently Windows 11 using SCCM. Which has been syspreped before capture. Then joined to the domain using SCCM. Have been using the same Windows 10 image for a while now, and only recently have we started getting problems. Specifically on brand new machines that are much newer than anything else we have. Ive checked for duplicate SID's and thats clear. We have no doplicates. The issue is it seems to hit at random times. We could have 10-15 machines in a room and about half of them will come up with this. Then an hour later they are working fine no issues. All PCs are the same version (Win10 Edu 22H2) going through the same switch. When i get this error, i can manually get to the policy in question and it opens fine. I look for it on both domain controllers and its there. Ive checked for duplicate SID's. DNS seems fine and resolves both domain controllers. Replication between both domain controllers seems to be working ok. DC Diag on the domain controllers shows no errors. We have a GP that specifies to wait for network before processing anything. Anything i may have missed here? As stupid as it sounds, could these PC's be too quick for the domain controllers? As they are far better than anything else we have on site. Any help would be apreciated. If this is the wrong area, just point me in the right place and ill post there. Thanks