Speaking of which, let's talk just a little bit more about the client. Remote PC Desktop: This allows users to connect to their corporate desktops from anywhere in the world by using a web browser.Īfter defining remote connections, you then assign permissions to your users, and the users can interact with the published assets by using their client-side app.Virtual Desktop: This allows users to connect to their own server-based desktops (persistent remote access, in other words).

Terminal Server: This allows users to connect to generic OS desktops (they can get to their work files though).If you choose the Desktop option, Parallels asks which type of desktop you want to publish: You kick off the app or desktop publishing process by starting a wizard from the admin console I show you this in the dialog box below. The publishing workflow ^Īs I mentioned earlier in this review, Parallels does a great job simplifying what could be a stupendously complex process. Naturally, there is far more involved in deploying and managing a Parallels RAS farm you should read the Parallels RAS documentation (particularly the Administrator's Guide) for details. This is an e-mail that prompts your users to install the Parallels RAS agent on their desktops or mobile devices. What's cool here is that Parallels RAS includes many templates for common applications and operating systems. Define application and VDI desktop connections.Register your existing terminal server hosts (for instance, Windows Server-based Remote Desktop Services TS session hosts).As you can see, deploying a Parallels RAS solution in your environment involves three primary steps:

2x rdp client for windows