- 
				adam.paradis
 - Novice
 - Posts: 8
 - Liked: never
 - Joined: Jan 27, 2021 8:33 pm
 - Full Name: Adam Paradis
 - Contact:
 
Test Guest OS Connectivity with PowerShell
Is there a way to test Guest OS connectivity with PowerShell (the equivalent of the Test Now button on the Guest Processing tab in a backup job)?  I've looked through the cmdlets but the only one I can find that seems like it might fit is Test-VBRGuestServiceConnection, but it says in Get-Help that it is for internal use only.  Thanks.
			
			
									
						
										
						- 
				david.domask
 - Veeam Software
 - Posts: 3043
 - Liked: 704 times
 - Joined: Jun 28, 2016 12:12 pm
 - Contact:
 
Re: Test Guest OS Connectivity with PowerShell
Hi Adam, 
No officially supported cmdlet I'm aware of; I did not know about Test-VBRGuestServiceConnection, but it theoretically does what you want, but at least for me it's bugged and won't print results to the shell. If you run it with -Debug flag, it will print the results to shell and you can maybe grab it with the Powershell transcript, but I'm doubtful, and parsing the log file VeeamPowerShell_{DOMAIN}_{USER}.log in %localappdata%/Veeam/Backup/Powershell might work. (you can use the switch feature in Powershell with the -Regex flag to quickly parse data out; the entries for this cmdlet get logged with a tag [TaskLog], so you can just write an expression to capture lines starting with that and see the results and use -ErrorAction SilentlyContinue to swallow the errors in your script)
@oleg.feoktistov are you able to share a bit more about the history of this cmdlet? I get the idea of it being a fast check that the credentials work and saves a lot of failed job runs potentially, so not sure if it was ever intended for production testing or not.
			
			
									
						
							No officially supported cmdlet I'm aware of; I did not know about Test-VBRGuestServiceConnection, but it theoretically does what you want, but at least for me it's bugged and won't print results to the shell. If you run it with -Debug flag, it will print the results to shell and you can maybe grab it with the Powershell transcript, but I'm doubtful, and parsing the log file VeeamPowerShell_{DOMAIN}_{USER}.log in %localappdata%/Veeam/Backup/Powershell might work. (you can use the switch feature in Powershell with the -Regex flag to quickly parse data out; the entries for this cmdlet get logged with a tag [TaskLog], so you can just write an expression to capture lines starting with that and see the results and use -ErrorAction SilentlyContinue to swallow the errors in your script)
@oleg.feoktistov are you able to share a bit more about the history of this cmdlet? I get the idea of it being a fast check that the credentials work and saves a lot of failed job runs potentially, so not sure if it was ever intended for production testing or not.
David Domask | Product Management: Principal Analyst
			
						Who is online
Users browsing this forum: No registered users and 4 guests