Using PowerShell to add the necessary vWorkspace Firewall Exceptions on a Hyper-V Host Virtualization Server

Recently while adding a Windows Server 2012 R2 Hyper-V server as a host virtualization server in a vWorkspace 8.0.1 environment, I received the following error message:

1Connect to DC service timed out. Overlapped I/O operation is in progress. (997) Retry will occur
2automatically if necessary.

vworkspace-port5203-error1.jpg

That error message lead me to a Dell support article which stated that I needed to either disable the firewall <which is not going to happen on my watch> or open port 5203.

While the article wasn't specific, it gave me enough information to resolve the problem. In my environment, I was able to open inbound TCP port 5203 on the Hyper-V host virtualization server for the domain firewall profile since my Hyper-V host server is a domain member. You know that I accomplished that task with PowerShell <of course>.

1$cred = Get-Credential
2
3Invoke-Command -ComputerName HyperV01, HyperV02 {
4  New-NetFirewallRule -DisplayName 'vWorkSpace Connection Broker Access' -Direction Inbound LocalPort 5203 -Protocol TCP -Action Allow -Profile Domain
5} -Credential $cred

vworkspace-port5203-error2.jpg

Once the firewall exception was made on the Hyper-V host virtualization server, I reinitialized it from within the vWorkspace management console and it completed successfully:

vworkspace-port5203-error3.jpg

µ