- #MASTER GAIN WINDOWS 10 SERIAL#
- #MASTER GAIN WINDOWS 10 UPDATE#
- #MASTER GAIN WINDOWS 10 WINDOWS 10#
- #MASTER GAIN WINDOWS 10 LICENSE#
This is no longer true IF you use what I use in this lab: Windows 10 Enterprise and VMware Blast. Remote Desktop Services are required for Horizon Agent installation, SSO, and other Horizon session-management operations.
Remote Desktop Services must be started on the virtual machine that you use to create pools and on the virtual machines that are deployed in the pools. In the link above to Prevent Access to Horizon 7 Desktops Through RDP, VMware states: In my case, and done throughout this lab, everything uses the VMware Blast protocol.
#MASTER GAIN WINDOWS 10 UPDATE#
UPDATE 1: In my testing, RDP does not appear to be required for anything I tested: Agent install, printing, USB Redirection, or Single Sign-On. If I MUST enable Remote Desktop capability, which I assume enables RDP, why does VMware show a way to Prevent Access to Horizon 7 Desktops Through RDP?Īfter this series is complete, I will test what happens with the Remote Desktop capability not enabled, build a desktop pool, and attempt to access the desktop and applications. Since, at least for me, this master image was built with Windows 10 Enterprise, the Blast Extreme protocol should be used for everything, not the Remote Desktop Protocol (RDP). VMware doesn’t state WHY you must enable it or what happens if you don’t and then build a desktop pool with Remote Desktop still disabled. The VMware documentation states that if you do not enable the Remote Desktop capability, you must enable it manually later. Figure 11įor this lab, select Enable the Remote Desktop capability on this computer and click Next, as shown in Figure 12. Figure 10Ĭlick Next, as shown in Figure 11. Figure 9Ĭlick on VMware Horizon Instant Clone and select This feature, and all subfeatures, will be installed on local hard drive, as shown in Figure 10. Figure 8Ĭlick on VMware View Composer, select This feature will not be available, as shown in Figure 9. Select IPv4 and click Next, as shown in Figure 8.
#MASTER GAIN WINDOWS 10 LICENSE#
Select I accept the terms in the license agreement and click Next, as shown in Figure 7. Figure 5Ĭlick Next, as shown in Figure 6. Right-click the Agent installer and select Run as administrator, as shown in Figure 5. Give the computer a name, join the AD domain, and restart the VM.Ĭopy the Horizon Agent installer to the VM. Make sure Receive Side Scaling is Enabled, as shown in Figure 4. Once the VM build is complete, make sure Power Management is disabled for the NIC, as shown in Figure 3. Figure 1įor the network card, select the correct network, verify Connect At Power On is selected, Adapter Type must be vmxnet3, and deselect DirectPath I/O, as shown in Figure 2. Make sure the hard disk is Thin Provisioned, as shown in Figure 1.
#MASTER GAIN WINDOWS 10 SERIAL#
If you have the options, remove any floppy drive and serial ports. Use the following options.įor CPU and Memory, use what works for your environment. In vCenter, create a new VM using Microsoft Windows 10 (64-bit). You should always follow the policies, processes, and procedures required for your environment. Your users, applications, and requirements are unique to your environment. Therefore, you should always lab, test, and learn BEFORE you put anything into production. Never blindly take the information from any website, article, or blog as gospel. You should follow the processes required for your environment. I am using the minimum number of options and steps so I can build and test quickly. There are also different opinions on when the master image should join the AD domain, what OU the image should reside in, and what GPOs (if any) should be applied to the OU and master image. Note: Every person has their opinion on how a master image is built, optimized, and delivered to users. For this article, I used Windows 10 1909 Enterprise Edition. With the Connection Server installed and configured, it is time to build master images.
0 kommentar(er)
