Learn More Download Free Trial Pricing & Buy

Posts Tagged ‘how to’


How you can use Terminal Services Log to optimize licensing costs

In a Terminal Services (Remote Desktop Services) or Citrix Environments users can use a number of different applications. In a heavily used system there could be hundreds of applications running on the servers in a farm. Administrators in charge of such farms need to ensure all applications are properly licensed. But how are you going to monitor all these licenses and their usage across server farms?

This is where Terminal Services Log comes to rescue! Our comprehensive reporting infrastructure allows you to both define the number of licenses purchased and automatically track how these licenses are being used across your farm.

Tracking application licenses

Let’s say you want to track the number of used Office Licenses.

Here is what you need to do:

  1. Go to File > Preferences > Licenses [tab]
  2. Click Add License
  3. From the License Type Dropdown choose Application per Device License (We support tracking of per User and per Device licenses. )
  4. From the Process Dropdown choose Microsoft Office Word
  5. Enter the number of licenses you have purchased

I have entered 4x Word, 10x Excel and 20x Access licenses. Sample usage report is displayed on the figure below.

blog-license-compliance

This report gives me important information about the current licensing state of my farm. As the sample report shows: I am only license compliant with Word, there are too many Excel licenses and too few Access licenses.

Benefits

There is a number of benefits from having reports like this one:

  • You can optimize costs for licenses you do not really need. (e.g. I could cut the number of Excel licenses in the above given example as I have 5 more than I really need)
  • I can detect if I need to purchase more licenses on my annual renewal date
  • I can change between different licensing schemas to detect if I could save more money with different licensing schema (per user/device)

Different licensing schemas we can track

Terminal Services Log allows you to track five different licensing schemas:

For applications

  • Applications per User License
    This license schema is being used for applications that are licensed per user i.e. you have to purchase a license for each user that uses the application
  • Applications per Device License
    This license schema is being used for applications that are licensed on a per device basis i.e. you have to purchase a license for each device this application is being used from. (e.g. So in case you are remoting from two different laptops you need 2 licenses.)

For farms or servers
The following license schemas allow you to track licenses for a farm or single server. This typically includes Terminal Services (Remote Desktop Services) CALs or Citrix Licenses. There are 3 different schemas:

  • Farm per User License
    This license schema allows you to track the number of unique users that connected to a remote server.
  • Farm per Device License
    This license schema allows you to track the number of unique devices (e.g. laptops, workstations…) used to connect to a remote server.
  • Farm Concurrent User License
    This license schema allows you to track the maximal number of concurrent users that connected in the given period. This license type is typically used to track Citrix Access Licenses.

Monitor ‘Per Device’ licenses on your Terminal Server / Citrix

With the Terminal Services Log v.2.5 we released a new feature that allows you to monitor application licenses per device. One of the most popular applications being licensed per device for Terminal Services is Microsoft Office. (Learn more about Office licensing on TS). So let’s see how to configure this:

The first thing you need to do is to configure a new license type.

  1. Go to File > Preferences
  2. Switch to Licenses tab
  3. In the Application Name column select the application you want to monitor (e.g. Microsoft Office Word)
  4. In the License Type column choose Device License
  5. Enter the Number of licenses you have

license01
Add other Microsoft Office Applications if you want to monitor these. Let’s say I have 5 Office Standard licenses. Standard includes Word, Excel and Outlook but it does not include Access, so I have added 5 licenses for Word, Excel and Outlook and 0 licenses for Access.

licenses11

How does license compliance work for per device licenses? Our application will calculate the number of unique devices that were used to run these applications in a given time period and selected server.

Finally, let’s check if I am license compliant with Microsoft Office.

report11

Okey, looks good… my users are only using applications we have licensed. (They cannot even use Access since it is not installed.)

Let’s consider another situation. Let’s say I purchased Office Professional licenses, and I do have 5 Access licenses at hand. The report would then look like this:

report21

So as you can see, my users are not using Access, and we are over licensed for Access. Next time I might want to reconsider the optimal Microsoft Office suite for my needs.

Conclusion

Our license compliance reports help you to determine the ideal number of licenses you need to purchase for your users on a Terminal Services / Citrix server. If you are over licensed, we help you save  money when renewing licenses for business applications, and when you are under licensed… well we are also saving money for you, as you might need to purchase some licenses to resolve the problem before you are fined.

Our application allows you to monitor Per User / Per Devices licenses and we will be adding more types in the future versions of our application. For more details about licensing of your business application you should check with your vendor.


Sending emails using SMTP server that requires authentication

A number of our customers have SMTP servers that require authentication. I am happy to inform you that we have included this long awaited feature in the Terminal Services Log 2.4.1. Now you can use your internal or one of publicly available SMTP servers to send your email alerts.

Here is an example how to configure our application to use Google Mail as SMTP provider:

  • Check “Enable e-mail sending”
  • Check “My outgoing server (SMTP) requires authentication”
  • Check “Use encrypted connection (SSL)”

Type the following:

  • Server (:Port): smtp.gmail.com:587
  • Sender (email): your_email_address@gmail.com
  • Username: your_username (or your_email_address@gmail.com)
  • Password: your_password

smtp_settings1

Check this guide for more details on how to use GMail services from 3rd party tools.


Windows 2008 Terminal Services RemoteApp user or group filtering – Part 1

The most wanted feature for Windows 2008 Terminal Services is RemoteApp user filtering. You don’t want all users to see all applications on the web portal. This feature will probably be released in Windows Server 2008 R2 but till then, you are out of luck.

Citrix Web Access and Grouping allows Citrix users to do the same, but this article I am going to focus on Window 2008 Terminal Services. I am going to describe how you could publish certain application to specific users or groups via RDP files.

To control published applications you could deploy:

  • MSI files via GPO or
  • or simply inform end users about RDP files they need to run

MSI approach works OK in the domains but in case you do not have a domain or you do not know how to configure group policies you will have to use RDP files. Distributing RDP files to your users might be a tricky business as these change over time and it might be too complicated to make sure everyone has the latest version.

Publishing files to a centralized portal

The easiest way to redistribute RDP files is to place these on the server (centralized portal). By default IIS does not support RDP file name extension. To solve this problem simply add the RDP extension in the MIME Types on the IIS server.
Follow these steps:
  1. Navigate to the IIS manager
  2. Select your website
  3. Find MIME Types
  4. Add RDP extension in the following format (File name Extension:  .rdp ; MIME type: application/rdp)

iis-configuration

Now you are ready to deploy your RDP files from Program Files > Packed Programs (note you will need to create .rdp file in TS RemoteApp Manager for every published application) to root or some virtual directories on the IIS server.

In order to run the application go to the http://yourservername/application123.rdp or http://remoteapp.yourdomain.com/application123.rdp and you will be able to start the published application.

Configuring Portal Security

all-users-on-a-single-portal2

Problem: All applications are visible to the entire organization

When your RDP files are published to the server this might be a problem. Now every employee can connect to your server and run any RDP file you posted there.

In order to allow only a group of users to run an applications you will have to divide your applications to different subportals (virtual directories). As an example I created the following subportals:

  • http://yourservername/sales
  • http://yourservername/support
  • http://yourservername/management

These portals will be used by different groups of people. Each portal will contain different set applications as on picture below.

multiple-portals2

In order to secure your applications you will need configure security for these virtual folders. I have been using Basic Authentication but you may forms authentication, windows authentication or other.

When a user opens the http:// servername/management he(she) will be prompted for a username and password.

image5

Upon authentication the following screen will be shown to him:

final-look

So what’s shown at the picture above? It is a customized TSWeb Access portal that shows the list of applications you are allowed to use. In the next post I am going to describe how to build one on your own.

Conclusion

Currently you cannot filter published applications by particular users. To overcome that limitation I created an RDP file for each published application and deployed these to a custom portal on your IIS. This method allows you to easily filter application by group or user.

In the next post I am going to describe how to build this portal step-by-step.