Access rules are typically defining access in a From/To arrangement. The next step will be to build some access rules. My implementation at this time does not include a View Transfer Server, so if your deployment includes this, please refer to the installation guide.Д¬reating Access Rules for VMware View in TMG 2010 Hopefully, what I provide will help bridge the gap on anything confusing in the manual. I appreciate the detail, and it is all technically correct, but it can be a little confusing. of the VMware View Security Reference will detail the ports and access needed. Here was the list (as I named them) that was used as a part of my rule sets. For the sake of keeping track of all of the user defined protocols, I always included the name вЂњViewвЂќ (to remember itвЂ™s purpose), the direction, type, and the port number. In order to build the rules properly, you will first need to define some вЂњUser-DefinedвЂќ protocols. It will make the work later on easier.Д¬reating Custom Protocols for VMware View in TMG 2010 For clarity, I will just show the rules that are used for getting VMware View to work.Д«efore you get started, make sure you have planned out all of the system names and IP addresses of the various Connection Servers, VMвЂ™s running the View Agent. vCenter, and SQL databases providing services for vCenter, and View Composer.ДЇor those who have their vSphere Management network on a separate network by way of a simple VLAN, your rules will be simpler than mine. View connection server dedicated for communication with the Security Server. View connection server dedicated for access from the inside. (a pretty picture of this can be seen in Part 2) Network LegДЄll users connecting to our View environment. My network design was a fairly straightforward, 4 legged topology. Sometimes this is not always practical, but in this case, I found that I only had to make a few adjustments before things were working perfectly with all of the components. Since all of the supporting components of VMware View will need to communicate across network segments anyway, I suggest making accommodations in your firewall before you start building the View components. While the screen captures are directly from TMG, much of the information here would apply to other security solutions. For me, access to these segments are managed by a Celestix MSA 5200i, 6 port Firewall running Microsoft ForeFront Threat Management Gateway (TMG) 2010. This post is simply going to focus on the security rules to do such a thing. We are almost at the point of installing and configuring the VMware View components, but before that is addressed, the most prudent step is to ensure that the right type of traffic can communicate across the different isolated network segments. Part 2, I left off with how VMware View was going to be constructed in my environment.

Microsoft forefront tmg