RES Workspace Manager Enterprise readiness

Up to now we have seen a lot of debate about the RES Workspace Manager enterprise readiness especially in regard to AppSense Environment Manager. In a couple of rare cases I agreed with the statements made but most of time I did not.

Without going into the details and start the discussion all over again I would like to focus on the changes in RES Workspace Manager 2012 and why I think Workspace Manager is now truly enterprise ready for all use cases.

One of the new features that comes with RES Workspace Manager is the addition of a new component called “Relay Server”.

Relay Server

The Relay Server is a new component that sits between a Workspace Manager (WM) agent and the WM databases. For those of you familiar with RES Automation Manager, think of it as a Dispatcher.

When you use the Relay Server the agent no longer talks directly to the database and the database only has 1 connection per relay server instead of 1 connection per agent.
The number of database connections has a direct relation to the maximum number of agents in your environment. For example, In a SQL scenario the maximum number of concurrent connections is just over 32.000 and with 2 connections per agent this limits the maximum amount of agents in your environment to 16.000. Although you can work around this issue you will run into scalibility issues eventually.

With RES Workspace Manager Relay Servers you can now handle a virtually unlimited amount of agents (users).

Of course this scenario also covers remote locations to minimize data traffic between sites by setting up relay servers on remote locations.

Ease of management

How convenient the relay server might be there are a lot of customers where you just don’t need the Relay Server because of a small scale or a one site scenario. The great thing about the relay server is is that it’s not mandatory to use it! You don’t need it? Don’t do it and your architecture will look the same as it always did!

The greatest fun I had while testing the relay server is that it is so incredibly easy to use. If you know how the agent configuration works in previous (and this) version you also know how to configure a relay server!

Another great new feature is called “Quick Edit” which makes it possible to do standard actions to more then one object at a time. For example you can now select multiple applications at once to change thins like “Workspace Container” membership. This is a major improvement for daily system administration tasks!

The addition of Reporting Services makes it possible to create extensive reports about what your users are doing, when they do it and how they do it. This is great for automatic reporting especially knowing that RES Workspace Manager is now Microsoft SAM certified!

So in the end my conclusion is that there is no need to think RES Workspace Manager 2012 is anything but Enterprise Ready for even the largest of your customers.

If you like to go into more detail please take a look at another article about the Relay Server by Max Ranzau on Res Guru! http://resguru.com/technote-library/rg046-all-about-the-wm-relay-server-2/ . I would like to thank Max for some of the detailed numbers I used in this article.

RES Workspace Manager Enterprise

Tagged , . Bookmark the permalink.

About Barry Schiffer

Barry is an IT Architect with 15 years of IT experience. He has gained both a broad and deep knowledge in the sphere of IT. Throughout the years, Barry has developed into a specialist in the field of Microsoft Windows, Server Based Computing, desktop and server virtualisation.Barry is co-founder and member of the Board of the Dutch Citrix User Group.Barry is awarded with the Citrix Technology Professional award in 2015 and received the RES Software Valued Professional award in 2012.

One Response to RES Workspace Manager Enterprise readiness

  1. A great and fair article Barry,

    You are right, with the old topology we could only handle the maximum number of concurrent connections as defined by the database vendor (32767 for SQL and 100s of thousands for Oracle)

    We have no binding in this respect anymore, so are in theory infinitely scalable in terms of concurrent connections.

    Don’t forget though, connectivity is not a prerequisite since there is a local cache on each device that has a Workspace Manager agent installed. Perfect for offline scenarios (like laptops) but also good when there is a heavily congested network, as it means the user is not impacted by whatever is going on at the network layer.

    Keep up the great articles!

Leave a Reply