Well done ​@jcolonfzenpr ! Thank you for your efforts for this great tool, and thanks for sharing it here.

Looking forward to these updates as I have been following it for VCC as documenting that will be fun.  Looking forward to the changes and release for testing.

​@jcolonfzenpr - I tested out the report on a VCC server.  Diagrams and document came out good.  Couple of things -

1. I am not seeing the version number or the DB type like your example above - why would that be?
2. The top part of the diagram has the IP and Description offset for each component - see example below where the VEM is IP/Role and VCC is Role/IP - can these be aligned to be the same format?

The error I am seeing which could be causing the Veeam version and database type not being report in the diagrams is probably this but WinRM is configured -

Get-VBRBackupServerInfo : Veeam.Diagrammer: New-PSSession: Unable to connect to servername, WinRM disabled or not configured.

​@jcolonfzenpr - I tested out the report on a VCC server.  Diagrams and document came out good.  Couple of things -

1. I am not seeing the version number or the DB type like your example above - why would that be?
2. The top part of the diagram has the IP and Description offset for each component - see example below where the VEM is IP/Role and VCC is Role/IP - can these be aligned to be the same format?

 

1. I am not seeing the version number or the DB type like your example above - why would that be? I'm pretty sure this is an issue with WinRM. I've seen this kind of behavior when the recommended best practices for hardening are applied.
2. The top part of the diagram has the IP and Description offset for each component - see example below where the VEM is IP/Role and VCC is Role/IP - can these be aligned to be the same format? Good catch! That's a bug.

Could you please confirm that the diagrams for the Tenants ran successfully and look similar to the included images?

Thank you very much for your valuable feedback!

Sure I will check and report back.

​@jcolonfzenpr  - I ran the report script again.

1. The WinRM service is running so not sure why the script is throwing the error.  I ran the Get-VBRBackupServerInfo manually and it worked to show me the details.  I had to run the Connect-VBRServer first but it worked.  Is there possibly a bug in the code?
2. Great that is a bug and will be fixed.
3. I can confirm the Tenant diagrams worked and look similar to the images you have shown. 😁

Looking forward to helping sort out the other minor issues.  Let me know if there is anything else you want me to test or try.

Can you run the Test-WSMan powershell cmdlet from the VBR server to check if WinRM is enabled?

I have my doubts about the code and I want to validate it first before making changes. Please review the following code and confirm if the WinRM is configured.

Test-WSMan
Test-WSMan -ComputerName ServerName

Test-WSMan
Test-WSMan -ComputerName ServerName

Here is the results of the two commands

PS C:\Windows\system32> Test-WSMan


wsmid           : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor   : Microsoft Corporation
ProductVersion  : OS: 0.0.0 SP: 0.0 Stack: 3.0



PS C:\Windows\system32> Test-WSMan -ComputerName ccvbk01


wsmid           : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor   : Microsoft Corporation
ProductVersion  : OS: 0.0.0 SP: 0.0 Stack: 3.0

Test-WSMan
Test-WSMan -ComputerName ServerName

PS C:\Windows\system32> Test-WSMan


wsmid           : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor   : Microsoft Corporation
ProductVersion  : OS: 0.0.0 SP: 0.0 Stack: 3.0



PS C:\Windows\system32> Test-WSMan -ComputerName ccvbk01


wsmid           : http://schemas.dmtf.org/wbem/wsman/identity/1/wsmanidentity.xsd
ProtocolVersion : http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd
ProductVendor   : Microsoft Corporation
ProductVersion  : OS: 0.0.0 SP: 0.0 Stack: 3.0

I'm still unsure why the version and database information aren't being displayed. However, I've updated the module to generate an error, which should help us identify the issue.

You can update the module using the following command:

Update-Module -Name Veeam.Diagrammer -Force
Import-Module Veeam.Diagrammer -Force

After updating, please run the test again and share the results.
 

​@jcolonfzenpr - so the error add helped.  I got the following error about the FQDN that it was trying to connect to.  I added the FQDN of the server to the TrustedHosts list as noted and it seems to be working now without the errors.  Thanks for the help. 😁

Get-VbrBackupServerInformation : Connecting to remote server FQDN failed with the following error message : WinRM cannot process the request. The following error with error code 0x8009030e occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated.

This can occur if the provided credentials are not valid on the target server, or if the server identity could not be verified.  If you trust the server identity, add the server name to the TrustedHosts list, and then retry the request.

Use winrm.cmd to view or edit the TrustedHosts list. Note that computers in the TrustedHosts list might not be authenticated. For more information about how to edit the TrustedHosts list, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.

Get-VbrBackupServerInformation : Connecting to remote server FQDN failed with the following error message : WinRM cannot process the request. The following error with error code 0x8009030e occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated.

This can occur if the provided credentials are not valid on the target server, or if the server identity could not be verified.  If you trust the server identity, add the server name to the TrustedHosts list, and then retry the request.

Use winrm.cmd to view or edit the TrustedHosts list. Note that computers in the TrustedHosts list might not be authenticated. For more information about how to edit the TrustedHosts list, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.

I'm glad to hear that you've successfully resolved the issue.