Gpupdate: Windows Could Not Locate the Directory Object
Dec06

Gpupdate: Windows Could Not Locate the Directory Object

KB ID 0001625 Problem Saw this on a Windows client on my test network; User Policy update has completed successfully. Computer policy could not be updated successfully. The following errors were encountered: The processing of Group Policy failed. Windows could not locate the directory object OU=Top-Level,OU=computers,DC=PeteNetLive,DC=com. Group Policy settings will not be enforced until this event is resolved. View the event details...

Read More
Stop Windows Asking For Password After Sleep / Standby
Dec05

Stop Windows Asking For Password After Sleep / Standby

KB ID 0001624 Problem I’ve done a few posts that involve me demonstrating how to disable a security feature, and people have messaged me with a mix of disgust/distain/horror. But I’m sick and tired of all the machines on my test network getting locked while I’m dragged onto something else, they are test machines, with no live data on them, and there’s only me uses them anyway!  And some people just want to log...

Read More
RDS Gateway Connection Error
Nov29

RDS Gateway Connection Error

KB ID 0001623 Problem I had to deploy a Remote Desktop Gateway Server into an existing RDS farm for a client this week, the RDS farm was presenting Windows Desktops (VDI) from Hyper-V. All went well until I tested the Gateway Server Externally, this is the error I got. Remote Desktop can’t connect to the remote computer ‘server/farm-name} for one of these reasons. 1) Your user account is not listed in the RD...

Read More
Error: 0x8007232B DNS Name Does Not Exist
Nov23

Error: 0x8007232B DNS Name Does Not Exist

KB ID 0001622 Problem Seen when attempting to ‘Activate’ a Window machine; Error: 0x8007232B DNS name does not exist Solution The reason for this error is the Windows machine has looked for a KMS (Key Management Server) in its local DNS, and not found one. This is because (out of the box) it has a Windows KMS licence code installed. Now if you have a KMS server you need to work out why you cant see it, I’ve covered...

Read More
Cluster: Not Reachable On UDP Port 3433
Nov19

Cluster: Not Reachable On UDP Port 3433

KB ID 0001621 Problem Seen on a Microsoft Hyper-V failover cluster (Server 2019); Network Interfaces {Node-Name} {Interface-Name} and {Node-Name} {Interface-Name} are on the same cluster network, yet address {IP-Address} is not reachable from {IP-Address} using UDP port 3433 Solution I’ve seen this error before, and usually you just need to disable the firewall or open UDP port 3433 and then re-validate the cluster (job done)....

Read More