A Closer Look at 2X Publishing Filters

0
Share on FacebookTweet about this on TwitterShare on LinkedInShare on Google+Email this to someonePrint this pagePin on PinterestShare on TumblrBuffer this pageShare on RedditShare on StumbleUpon

The 2X Remote Application Server console comes with the ability to allow Administrators to publish applications and desktops and also set different filters on this published material.

In this article we explain in few simple steps how these filters actually work.

The main concept of filtering is for ‘filters’ to be set on published applications or desktops so that Administrators can outline which users are allowed to access which published applications. This way, Administrators are allowed to define users or groups in Active Directory so that they can set a more granular set of rules for accessing applications.

How can an Administrator set these filters?

Filtering is applied in the 2X ASXG Console from the Publishing Pane. Once an application has been published, the Administrator would need to click on the application or desktop and change to the Filtering tab. On the “Select Filtering Type” dropdown box, the administrator is able to select between adding a rule on a particular user, group, client or IP address, using LDAP or WinNT as browsing methods.

The filtering options can also be added when trying to publish a new application or desktop as outlined here.

If an Administrator would like to add Organizational Units or Groups and further expand to Nested Groups, using LDAP mode is preferred.

Once all rules have been setup, the Administrator can have complete control over which applications are accessed and by whom.

Keep in mind that every filter set on a published item will involve a query against Active Directory so that the user or members of a group are cataloged . If a lot of queries are needed to be passed along, the actual resolving of these queries might cause a bit of a delay on some of the client machines trying to access this published material.

For example, let’s say a user is trying to access published material from his workstation via the 2X Client. The larger the number of filters set, the longer the resolving of the queries will take, meaning the client might take longer than usual to display the published material. This is usually an issue when a large number of filters are set. In these cases, we recommend creating a bit of a hierarchy so that the number of queries performed is reduced.

This usually involves creating a Folder in the Publishing node and assigning different filters on the folders themselves, rather than on the single applications one by one. This not only saves time in creating the rules themselves, but also reduces the amount of queries the Application Server needs to perform.

Giorgio Bonuccelli is a Marketing and Communications Director at Parallels. Giorgio has extensive experience in cloud computing and virtualization, with a background of many years in multinational corporations (Dell, EMC and McAfee). In his career he has filled different roles, from sales to training and marketing. This wide-ranging experience and flexibility helps him simplify concepts and write content that is easy to read and understandable even by newcomers to the subject. As a blogger and technical writer he has published more than 1000 papers.