12/1/2023 0 Comments Vmware virtual desktop![]() ![]() Type a name for the profile in the Name field, then select the DMZ network you plan to use: ![]() Logon to the vSphere Web Client and click Hosts and Clusters:Ĭlick the Datacentre you plan to deploy the Access Point to and then click the Manage tab. The following must also be allowed between the Access Point and the subnet containing the virtual desktops:Īdditionally, the following traffic must be allowed through to the subnet containing the RDSH servers (VLAN60 in our example):Īdditionally, a number of components need to talk back to the Access Point:īefore the Access Point can be deployed a network profile needs to be created on the vCenter. To enable communication between the Access Point and view3, the following traffic must be allowed through the firewall: The Access Point will be deployed with the following IP details (substitute accordingly): Users accessing the View Connection Servers from the LAN must be granted access using just their Active Directory credentials: Getting started However only remote users must be forced to authenticate using RSA SecurID. To enhance security, the following design decision has also been made: The Access Point will connect to the view3 connection server: The design assumes this is in place and has been secured accordingly ( part 1, Assumptions, A5). The Access Point will be placed in the DMZ network. Therefore this single point of failure must be flagged as a risk and recorded. Unfortunately, the design is constrained by budget ( part 1, Constraints, C4), so whilst deploying multiple Access Points would not increase costs, to make use of them would require an additional load-balancer. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |