BPA Nightmare

Question

I am tending to a virtual machine that is functioning as a ADDS, DNS, and File Storage Server for a client. Every month when I perform maintenance there is the same block of BPA errors and I am at a loss on how to get them cleared. I am attaching 2 photos of some of the errors, there are about 30 all together with "The AD DS BPA should be able to collect data about"... The DC runs with no issues reported from the client but I am just at a loss on how to clear or if these need to be cleared from the BPA.

C:\Windows\system32>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : SMEC-DC-01
Primary Dns Suffix . . . . . . . : stmarksjax.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : stmarksjax.local

Ethernet adapter Ethernet0:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connection
Physical Address. . . . . . . . . : 00-0C-29-C3-CA-71
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::60bc:43a2:220:547e%5(Preferred)
IPv4 Address. . . . . . . . . . . : 172.16.3.1(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.16.3.254
DHCPv6 IAID . . . . . . . . . . . : 50334761
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-23-23-7A-94-00-0C-29-C3-CA-71
DNS Servers . . . . . . . . . . . : 172.16.3.1
127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{EAF0EB59-7282-423A-939F-D45A4E4A0E11}:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes

C:\Windows\system32>dcdiag

Directory Server Diagnosis

Performing initial setup:
Trying to find home server...
Home Server = SMEC-DC-01
* Identified AD Forest.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SMEC-DC-01
Starting test: Connectivity
......................... SMEC-DC-01 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SMEC-DC-01
Starting test: Advertising
......................... SMEC-DC-01 passed test Advertising
Starting test: FrsEvent
......................... SMEC-DC-01 passed test FrsEvent
Starting test: DFSREvent
There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL
replication problems may cause Group Policy problems.
......................... SMEC-DC-01 failed test DFSREvent
Starting test: SysVolCheck
......................... SMEC-DC-01 passed test SysVolCheck
Starting test: KccEvent
......................... SMEC-DC-01 passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... SMEC-DC-01 passed test KnowsOfRoleHolders
Starting test: MachineAccount
......................... SMEC-DC-01 passed test MachineAccount
Starting test: NCSecDesc
......................... SMEC-DC-01 passed test NCSecDesc
Starting test: NetLogons
......................... SMEC-DC-01 passed test NetLogons
Starting test: ObjectsReplicated
......................... SMEC-DC-01 passed test ObjectsReplicated
Starting test: Replications
......................... SMEC-DC-01 passed test Replications
Starting test: RidManager
......................... SMEC-DC-01 passed test RidManager
Starting test: Services
......................... SMEC-DC-01 passed test Services
Starting test: SystemLog
An error event occurred. EventID: 0x00002720
Time Generated: 02/05/2021 11:39:50
Event String:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
A warning event occurred. EventID: 0x00000087
Time Generated: 02/05/2021 11:49:52
Event String:
NtpClient was unable to set a manual peer to use as a time source because of duplicate error on '0.ro.pool.ntp.org'. The same time source '1.ro.pool.ntp.org' has been either specified as manual peer in NtpServer or selected as domain peer. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry already exists. (0x800706E0)
A warning event occurred. EventID: 0x00000087
Time Generated: 02/05/2021 11:49:53
Event String:
NtpClient was unable to set a manual peer to use as a time source because of duplicate error on '1.ro.pool.ntp.org'. The same time source '0.ro.pool.ntp.org' has been either specified as manual peer in NtpServer or selected as domain peer. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry already exists. (0x800706E0)
A warning event occurred. EventID: 0x00000087
Time Generated: 02/05/2021 11:49:53
Event String:
NtpClient was unable to set a manual peer to use as a time source because of duplicate error on '2.ro.pool.ntp.org'. The same time source '0.ro.pool.ntp.org' has been either specified as manual peer in NtpServer or selected as domain peer. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry already exists. (0x800706E0)
A warning event occurred. EventID: 0x00000087
Time Generated: 02/05/2021 11:54:45
Event String:
NtpClient was unable to set a manual peer to use as a time source because of duplicate error on '2.ro.pool.ntp.org,0x9'. The same time source '1.ro.pool.ntp.org,0x9' has been either specified as manual peer in NtpServer or selected as domain peer. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: The entry already exists. (0x800706E0)
......................... SMEC-DC-01 failed test SystemLog
Starting test: VerifyReferences
......................... SMEC-DC-01 passed test VerifyReferences

Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation

Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation

Running partition tests on : Schema
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation

Running partition tests on : Configuration
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation

Running partition tests on : stmarksjax
Starting test: CheckSDRefDom
......................... stmarksjax passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... stmarksjax passed test CrossRefValidation

Running enterprise tests on : stmarksjax.local
Starting test: LocatorCheck
......................... stmarksjax.local passed test LocatorCheck
Starting test: Intersite
......................... stmarksjax.local passed test Intersite

Answer 1

Hi,
In order to better help you solve the problem, I want to know some information with you
1What is wrong with the report during normal use
2 What are the specific impacts
Best wishes
Vicky