Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest
Please, try again later.
If the server from which Veeam ONE is failing to collect events (e.g., Veeam Backup & Replication or Hyper-V) is the same server on which Veeam ONE is installed, try one of the following solutions in addition to the steps mentioned above:
$networkConnections = Get-NetConnectionProfile
foreach ($connection in $networkConnections)
{
Write-Output "Network Name: $($connection.Name), Network Category: $($connection.NetworkCategory)"
if ($connection.NetworkCategory -eq 'Public')
{
Set-NetConnectionProfile -InterfaceIndex $connection.InterfaceIndex -NetworkCategory Private
Write-Output " -> Network category changed to Private."
}
}
Get-NetFireWallRule | Where {$_.Name -eq 'RemoteEventLogSvc-NP-In-TCP'}
Get-NetFireWallRule | Where {$_.Name -eq 'RemoteEventLogSvc-In-TCP'}
Get-NetFireWallRule | Where {$_.Name -eq 'RemoteEventLogSvc-RPCSS-In-TCP'}
Get-NetFireWallRule | Where {$_.Name -eq 'ComPlusNetworkAccess-DCOM-In'}
Set-NetFirewallRule -Name 'RemoteEventLogSvc-NP-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'RemoteEventLogSvc-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'RemoteEventLogSvc-RPCSS-In-TCP' -Enabled True
Set-NetFirewallRule -Name 'ComPlusNetworkAccess-DCOM-In' -Enabled True
Your feedback has been received and will be reviewed.
Please, try again later.
Please try select less.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case
Your feedback has been received and will be reviewed.
Please, try again later.