With either option, the administrator can configure the pool to store the user profiles on User Profile disks separate from the machines.
Select the Pooled Virtual desktop collection and Click Next. Specify the Virtual Desktop Template which you must have already configured in Hyper V making sure to have syspreped the virtual machine after installing the software required by users and Click Next. Note If you do not have an image then it can be easily created using the following command:.
Specify Virtual Desktop allocation and Click Next. On the Specify the virtual desktop template page, click Virtual Desktop Template , and then click Next. On the Specify the virtual desktop settings page, click Provide unattended settings , and then click Next. In this step of the wizard, you can also choose to provide an answer file. On the Specify the unattended settings page, enter the following information and retain the default settings for the options that are not specified, and then click Next.
In the Local Administrator account password and Confirm password boxes, type the same strong password. In the Time zone box, click the time zone that is appropriate for your location. On the Specify users and collection size page, accept the default selections, and then click Next. On the Specify virtual desktop allocation page, accept the default selections, and then click Next.
On the Specify virtual desktop storage page, accept the default selections, and then click Next. Make sure that the RD Virtualization Host computer accounts have read and write access to this location. You can ensure the managed pooled virtual desktop collection was created successfully by connecting to the RD Web Access server and then connecting to the virtual desktop in the Contoso Managed Pool collection.
Open Internet Explorer. This completes the managed pooled virtual desktop collection test lab guide. To save this configuration so that you can quickly return to a working managed pooled virtual desktop collection configuration from which you can test other Remote Desktop Services modular test lab guides TLGs , TLG extensions, or for your own experimentation and learning, do the following:.
On all physical computers or virtual machines in the test lab, close all windows and then turn them off. If your lab is based on virtual machines, save a snapshot of each virtual machine and name the snapshots. If your lab uses physical computers, create disk images to save the managed pooled virtual desktop collection test lab configuration.
There is a process in the same section of Server Manager to recreate desktops. MS killed VMware View 5. MS VDI is a lot easier to deploy. Just my opinion. In my opinion and view of the virtualization landscape, pound Microsoft gorilla is back with rock solid systems and strategy. I got it working on a test enviroment and can access the desktops just fine on the LAN. If I connect from the internet to the webbroker, it spawns a RDP session to the machine name on the local network.
Do I need to open firewall ports to each individual VDI machine and give them internet names? Great article. It helped me setup a test environment. I have one question about resource management. Is it possible that the Connection Broker or the Virtualization Host shuts down the VM automatically when the user logs off.
I try on somehow old equipment with limited amounts of RAM and a new user can get denied access to a new VM due to the previous ones having been left running. I should note I am trying with personalized Virtual Desktop and not pooled.
If i have only single win8 template and created the pooled VDI infra and some days later and i patch it for MS patches etc and want fresh desktops with this image, then simply running the recreate desktop will work here? Or i have to again manually sysprep the win8 desktop and shutitdown and then coose the option of creating desktops? On the specify the unattended installation settings screen is there a way to configure the collection to use precreated AD computer accounts or do you have to use a user that has permission to create accounts in the OU that you specify?
For the Microsoft VDI scenarios you definitely need the wizard to create the accounts. We are in the starting stages of this, and i am wondering about the Enterprise SSL. It always seemed like a hookey process to me. We do not use self signed we always get outside signed? Thank you,. Yes, I imagine this is entirely possible.
The RDS infrastructure would then be created in the parent domain and using a custom ADSI string, you could create the computer accounts in the subdomain. Queation; If I do this Hyper-V can I have different machines boot directly to this server and not have an OS on the machine, just do a network boot to the server?
Care to elaborate? Thanks, —youngtech. Always seems like Microsoft leaves out compatibility for Mac. This is an accurate statement and one of the many ways that Citrix and VMware are continuing to differentiate their VDI efforts from the Microsoft approach. This would be for an open lab type use where the VDI machines would autologon as a generic domain user and would get recreated whenever someone logged of or rebooted the machine.
Absolutely, this is definitely a common deployment scenario for our customers. Thanks Dane! This is a great article! I have since upgraded to Server , and found this article. Your procedure worked the first time through. Now I can work through testing the issues of configuration and maintenance that will need to be answered in order to sell it to customers.
I confirmed that at that moment: 1. The collection creation process times out eventually. Questions: 1. How to fix it? The clean domain idea is my preference when I suspect there is something environment or domain specific causing complications with my deployments. I have followed your all steps. I manually logged into each VMs.
Now when I try to access via web,. Try different credentials Note: All the time I was using domain administrator account, I also changed the password, but same result. When using testuser login regular domain user , it shows error: There are no available computers in the pool, try connecting again or contact Network Administrator.
Additional troubleshooting steps followed: — Have allowed Remote desktop manually for domain users in the VMs as well and added RDP users to be domain users.
I stumbled across this blog and loved the detailed steps to provision desktops. Have you come up with a solution since this issue was brought up? Heard anyone else come across this issue and the common causes of it? I did fresh installs on everything in an isolated lab environment. I could go into more detail if you would like. I finally found the problem and thought I would post it here if someone else came looking for it.
When I left the VM in a workgroup, the creation of the VDs hung up at that point and 2 hours later I got an error was about not finding the domain. Thanks a lot for your recommendations, Dane! I will try to start over again in the new environment. This is avery good article. I have been successful with this.
All works fine in the LAN environment. Could someone assist please? Thanks in advance…. Nice article. What about the OS license? How would I configure it for KMS? Sysprep strips it out. I typically require the customer to setup KMS infrastructure prior to the beginning of the project to avoid these activation snags. Thanks for the comment, —youngtech. Out of the 3 servers, which would be the best choice to install the RD Licensing Role? Do you have any change to deploy company windows 7 for the VDI image.
Any idea? They want students to bring their own devices, but allow them to connect to a virtual windows desktop to get to our domain resources such as printing and file shares. This guide has been the only real instruction on setting this all up. Windows machines work great. I purchased iTap for the Mac, but it always crashes when trying to connect to the VM. I can RDP the server fine if I try.
Any insight on how to get a Mac OS X machine to connect? Thanks for all your help! Take care and good luck! If I want to have possiblity for my team of 4 coworkers to work with these machines from home, do I need just to let them login through Web interface? How can Broker distinguish those IP addresses? I speak spanish, sorry my english.
In short, to start, on the RDS server for example , create a folder that you will share later on the network. There is no need to change permissions because Windows Server will do this when creating the virtual desktop collection. So, just click on Share. The wizard displays the network link for this shared folder. Note : you will need it a little later.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L. Index System admin Virtualization. Registration Password lost? Preparing the virtual machine for creating virtual desktops Before creating your virtual machine on your Hyper-V server, be aware that virtual desktops can only be created for Generation 1 virtual machines.
0コメント