Where you used to have some conflicts with Terminal Services, you can now use application virtualization to stream those and avoid that issue. Those aggravating printer driver installs needed before? Gone, as print jobs now turn into an XPS (XML Paper Specification) file to print like a PDF file, rather than relying on a particular print driver on a particular client matching a particular printer.īoth Vecchiet and Kleef recommend looking closely at application virtualization, which they admit was a bit of a pain point in WS2003. Microsoft has planning documents in their KnowledgeBase to help configure your server, but those recommendations tend to underestimate the need for their own code to suck resources. Microsoft recommends 8-16GB of RAM, meaning you need 32GB of RAM. Some users can get a pooled VDI connection, while others can be configured for a personal customized session. Remote users have options for a personal VDI profile. You can access both from the same client through a portal, but you can't host both on the same server. Session Host scales significantly more users, up to 100s of users when running a limited set of applications.
0 kommentar(er)
