VDI – No Virtual Desktop Templates (Windows server 2012 R2 )

Session-based

Session-based refers to Microsoft’s implementation of session virtualisation, isolation which is what was previously called Terminal Services.

• Each user runs on a server operating system (OS) desktop that is semi-isolated from the other user.
• Each session shares the same OS kernel.
• A RDS server is normally a locked down secured environment because configuration changes can affect all users.

Virtual machine-based

Virtual machine-based refers to full x86 hardware virtualisation where:

• Each virtual machine runs separate virtualised hardware that is then interpreted and mapped to physical hardware. This runs on one or more Hyper-V servers.
• Each client connects to a separate operating system environment running a client OS like Windows 8.
• Client Oss are normally secured the same as a regular Management Operating Environment (MOE) base changes don’t affect other users because they run in a separate OS instance.

The different between Pooled and Personal for Virtual machine-based is that:

1. Pooled shares VMs between users. When a user logs off that VM is available for another person to use or can be rebuilt. This is good for regular users that use a lot of the same applications. http://technet.microsoft.com/en-us/library/dd883265(v=ws.10).aspx
2. A Personal VM is only used for one user. This is good for power users that require specific applications that might be manually installed. http://technet.microsoft.com/en-us/library/dd883277(v=ws.10).aspx

This link and it’s sub-links give some examples: http://technet.microsoft.com/en-us/library/hh831447.aspx

Also see:

• http://technet.microsoft.com/en-us/library/dd736539(v=ws.10).aspx
• http://www.microsoft.com/en-us/server-cloud/windows-server/virtual-desktop-infrastructure-features.aspx

Hope that helps.

Check that the connection broker can actually contact the DC. It needs the same ports for AD as everything else and access to a non-RODC.

The permission your server account needs is simple. In the delegation dialogue for your domain, create a custom delegation. The permission you need for it is create computer objects; look under computer objects and select the grant checkbox for create. You can delegate it for your whole domain, or just the OU containing your RDP pool.

Although you don't currently have any OUs, you really ought to create a new one for tasks like this. That way, if you want to apply a GPO to your RDP boxes (to force RDP authentication, rename local admin, etc.), they are all in one place and isolated from other computers (like your servers and workstations).

Make sure your naming convention is appropriate and not creating duplicates, like the error says, as well. Duplicates can be created when you attempt to reuse old names as well, if the computer accounts have not been deleted, though I don't ever recall this being a real practical problem.