Forum Discussion
GPO processing fails
Okay, that's great news and really helpful.
The one you've found seems to be a few days recent than your error, which was from the 15th. Are you able to find one from the same timestamp as an error?
It doesn't have to be from the 15th. If you have more recent errors, that's fine, just have a look and see if you can find the matching event 5308.
If you know how to "filter" the "GroupPolicy/Operational" node, then it will be easier for you to find a matching pair if you filter on events 1058 and 5308 as shown below.
If the server is still showing up as uztassrv01.sm.local then it may not be name-related - we're just checking the basics at the moment.
If we find it's not related to names then we can shift our focus over to the actual files, and check things like permissions and even that the files themselves do actually exist (GPO's definitely going to fail if the files don't exist!)
Cheers,
Lain
Also, since UZTASSVR02 keeps popping up, it might pay to find and delete any orphaned DNS records - particularly those that play an important role in service discovery.
Here's three commands that will help you find any orphaned DNS records belonging to UZTASSVR02:
# Look for orphaned service locator records.
Get-DnsServerResourceRecord -ComputerName uztassrv01.sm.local -ZoneName _msdcs.sm.local -RRType SRV | Where-Object { $_.RecordData.DomainName -like "uztassrv02*" }
# Look for orphaned AD replication locator records.
Get-DnsServerResourceRecord -ComputerName uztassrv01.sm.local -ZoneName _msdcs.sm.local -RRType CNAME | Where-Object { $_.RecordData.HostNameAlias -like "uztassrv02*" }
# Look for orphaned name server records.
Get-DnsServerResourceRecord -ComputerName uztassrv01.sm.local -ZoneName sm.local -RRType NS | Where-Object { $_.RecordData.NameServer -like "uztassrv02*" }
Cheers,
Lain
Here is the outcome:
May be it also worth mentioning that every view minutes there appears 5504 event mentioning different internal dynamic addresses
