If You disabled the integrated windows firewall, you should get this following error message, but fortunately the installation success!
1: Failed to update Windows Firewall for BLAST. Please contact your administrator for the support.
I've found something on VMware Horizon View 5.2 Feature Pack 1 Windows Release Notes at known issues, but I think this isn't a direct solution for this warning...
You are not really stating your exact problem but I suspect it does not work after the installation?
Is the Windows Firewall service running?
I am encountering the same issue, I get 1: Failed to update Windows Firewall for Blast and am not successful connecting VDI using HTML access. (Firewall is ON on the View Connection Server)
Telnet between View Desktops and View Connection using port 22443 server fails.
I could see no port esablishment for 22443 while running netstat -a on the View Connection server.
Anyone have fix to this problem, will certaily value.
windows firewall needs to be enabled on the parent virtual machine for the installer to complete - it creates a firewall rule inbound to allow blast. Check that the blast rules have been enabled into the windows firewall on both parent virtual machine and also on the view connection server - i recall having to manually enable the rules on the VCS before
We disable the windows firewall as part of the domain policy for servers. I'm not understanding why we would need to turn it ON for Blast to turn it OFF for this port to work, but this is what my engineer is telling me. The service is enabled, but the firewall is off. Any info is appreciated.
I'm unsure why exactly blast needs the firewall enabled, but with an exception to allow the traffic. However this is what it states in the admin guide, and for various customers of mine who have faced the same issue enabling the firewall and then the blast exception has resolved the issue.
Most of my customers are only using blast externally with View Security Servers, which also require that the connection server has the firewall enabled anyway, to create the IPSEC tunnel between connection and security server. You could put your Connection servers in their own OU and create a new group policy to enable the firewall just for these servers