AppSense Management Suite Version 8 Service Pack 2 is Released!

August 24, 2009

Based on great feedback from our customers and partners, along with our own internal examinations, we have further enhanced the AppSense Management Suite Version 8.0 and are pleased to announce the release of Service Pack 2.

This service pack will improve the performance and provide greater flexibility and control options.  It also contains many new features, of which I shall detail a new feature each day, the first of which can be found here.

(Details of the enhancements included in this Service Pack can be found in the release notes as part of the software download.)

We strongly recommend that all AppSense Version 8 customers, including those using Version 8 Service Pack 1, upgrade to this latest version of our software.

It is available for download* from here – please use your existing account login details to access. 

*Please note that you must have valid software subscription in order to be eligible for this Service Pack.

If you have any questions, or would like to enquire about software subscription, please do not hesitate to contact AppSense Customer Services at

Customer Service Contact Details:
Tel: +44 (0)845 839 9085

(GMT) time zone: Monday to Friday, 09.00am – 17.30pm standard business working hours.

International Contact Numbers: 
USA, South America and Canada 886 APPSENSE
Germany, Austria and Switzerland 0800 0007 290
Australasia 1800 631 386
Worldwide +44 (0)845 839 9075

As this is an ever growing blog topic, the new features we have detailed can be found below:

NEW FEATURE No. 1 – AppSense Environment Manager 8.0 Service Pack 2 – Run As

NEW FEATURE No. 2 – AppSense Environment Manager 8.0 Service Pack 2 – Connect As

NEW FEATURE No. 3 – AppSense Environment Manager 8.0 Service Pack 2 – Improved compression and data handling protocol

NEW FEATURE No. 4 – AppSense Environment Manager 8.0 Service Pack 2 – Manipulation of files in Personalization Analysis

NEW FEATURE No. 5 – AppSense Environment Manager 8.0 Service Pack 2 – Run Once

NEW FEATURE No. 6 – AppSense Environment Manager 8.0 Service Pack 2 – Group SID Refresh

NEW FEATURE No. 7 – AppSense Environment Manager 8.0 Service Pack 2 – Trigger Action Time Audit Event

NEW FEATURE No. 8 – AppSense Environment Manager 8.0 Service Pack 2 – Stop If Fails

NEW FEATURE No. 9 – AppSense Environment Manager 8.0 Service Pack 2 – New Application Categories in the User Interface

NEW FEATURE No. 10 – AppSense Environment Manager 8.0 Service Pack 2 – Refresh

NEW FEATURE No. 11 – AppSense Environment Manager 8.0 Service Pack 2 – Registry Hive Exclusions

VDI Personalization and Configuration: Profile Management & Logon Scripts – not enough for multiple delivery mechanisms & OS platforms?

July 24, 2009

As a leading user environment management vendor, AppSense are in a unique position in that we have been involved many VDI projects and rollouts, of which the majority vary in architecture, technology and requirements.  One thing that does however remain the same between such projects is that of the requirement for user personalization management.

For many years the roaming profile provided user personalization in SBC environments, however as VDI deployments become more and more complex, with varying methods of desktop and applications delivery, along with multiple desktop operating systems and subsequently, profile versions, the roaming profile is no longer able to provide the user with their required settings in such (complex?) scenarios.

Furthermore, these desktops must now be constructed and configured based on the context of the user and/or connecting device.  i.e. mapping specific printers local to the user and device dependent on the location of the user logging on, or applying security policies to hide or remove access to network drives, folders, data and functionality such as copy and paste or print, again, based on the location of the user.  Whereby the desktop delivered to a user when connected locally inside the corporate LAN is different to that of the desktop delivered to the same user when connecting remotely from outside of the LAN.

One more point to consider is that of enabling the user to freely roam between the server hosted or provisioned virtual desktop, and the users local desktop device such as their PC or roaming laptop.  How do you as IT enable user settings to automically follow the user between different platforms?

AppSense Environment Manager was designed from the ground-up with functionality to accommodate the above requirements, making it, or, other user environment management solutions essential to the mass adoption of VDI on an enterprise scale.  In essence, AppSense provides the ability to encompass multiple delivery technologies and OS platforms by allowing the user to roam between the paradigms without any noticeable change to their desktop or user experience, enabling IT and the organization to benefit from flexibility, agility and lower TCO.  I do at this point want to highlight that this is different to the personalization management provided by the leading VDI vendors (Citrix, Microsoft, VMware etc), as their in-built functionality is typically designed for their delivery platform, not each other’s.   In essence, further to the advanced personalization and simplification of desktop management, AppSense also enables an organization to use combinations of both existing technologies, and (potentially) more importantly, any future VDI delivery technologies and vendors.
I have just found a very nice blog covering the functionality of not only AppSense Environment Manager, but also the base technology inherent within the leading VDI service providers – Citrix, VMware and Microsoft.  Hopefully from this blog post, and the information over at GenerationV, you will see how AppSense bridges the gap between the roaming user and a dynamic, flexible VDI model..

For more information on this, the GenerationV Profile Management blog can be found here

Fair-Sharing CPU usage on Citrix XenApp to ensure Quality of Service and Faster Response Times (With AppSense Performance Manager)

July 23, 2009

The Server Based Computing (SBC) such as Microsoft Terminal Server and Citrix XenApp model offers many unique challenges for both architects and administrators. There are concerns of security, availability of resources, performance and the costs of hardware, licensing and ongoing management. Due primarily to opportunities for cost reduction in hardware purchases however, server consolidation through ‘optimizing performance’ has been the main area addressed. Fewer servers also result in lower licensing costs, lower maintenance overhead, and reduced electricity and cooling costs. However, it has now become apparent the real issue with performance is not just financial, but one of user experience. There is an ongoing tradeoff betweenensuring users receive a consistent ‘end-user experience’ while maintaining the minimum amount of hardware. 


Before considering CPU usage, management and optimization, it is first necessary to clarify CPU usage. When a figure such as 60% CPU usage is quoted, what is actually meant is the CPU is being utilized at 100% for 60% of the time. This shows a high CPU value is actually an efficient use of resource, rather than a problem.


A CPU utilization of 100%, while considered a problem by many, actually means maximum use is being made of this resource, and therefore achieving maximum return on investment. Problems occur when requests exceed 100% CPU utilization, whereby resource contention and bottlenecks are formed – although, this can be solved by efficiently allocating the resource between the users and running applications.

AppSense Performance Manager is able to control CPU usage in many ways, and may be used to not only resolve CPU usage issues, but also to ensure CPU resource to mission critical applications and users.  In this post I want to cover one specific feature function within AppSense Performance Manager – Smart Scheduling, or sometimes known as CPU Fair Sharing.

Smart Scheduling
With Microsoft operating systems, during process initialization, a priority is assigned for the process to run under. Microsoft Windows 2003 has the following priorities:-
Realtime, High, Above Normal, Normal, Below Normal, Low.

A process which has a higher priority will be allocated CPU prior to a process with a lower priority. Most applications when launched are given a ‘normal’ priority. This means that these processes form a ‘queue’ for the CPU and will receive CPU time only when it is their turn. There are a few standard system processes which are assigned a higher priority, such as the ‘Windows Task Manager’ which is automatically assigned a ‘high’ priority. This ensures should the Task Manager process require CPU time it will be given it immediately.

A process may consume a maximum amount of CPU time, known as the quantum time. If the process does not require the full quantum time, for example if it requires further data, it is able to release the process prior to completion of the quantum time, thereby allowing another process access to CPU resource.

When an application Launches, there are many calls to the disk to access new data, and therefore the process consumes small parts of the quantum time. Processes which involve a large number of calculations, such as highly mathematical applications, tend to use all of the CPU quantum time and are therefore CPU intensive.  If the timeline of processes within the CPU are mapped out the problems become immediately apparent.

For example – Below, Process A is Microsoft Word launching; Process B is a resource intensive Microsoft Excel macro.



Scenario 1:- Only Process A is running in this scenario, the application performs at full speed as it gets CPU resource when required and disk resource when required.


Scenario 2:- Process A and Process B running. In this scenario it is evident that process A has been dramatically slowed down as there is a length of time where it is waiting for process B to relinquish the CPU. This can have dramatic effects on the responsiveness of the process, and obviously increases the time to wait. As process A and B both have equal priorities one process has to wait for the other to finish.

AppSense Performance Manager includes ‘smart scheduling’ technology that is able to share the CPU resource more efficiently between running applications. The priorities of the process are altered dynamically. The result being that processes requiring a small amount of CPU time tend to be given a higher priority than those which tend to monopolize the CPU.


In this way the CPU time is divided equally amongst both processes ensuring that each has a share and no one process is hogging the CPU, causing others to wait. Process B receives much smaller chunks of CPU time but similarly its waiting time is also short, ensuring that the application appears responsive to the user, and therefore still falls within its time to wait. The effect of this process is greatly reduces the CPU queue length.

By interpolating between standard priorities, and dynamically adjusting the priority of each process, AppSense Performance Manager is able to ensure more efficient processor usage. More importantly, from a user perspective, no application is seen to “freeze”, ensuring application responsiveness falls within the acceptable ‘time to wait’ period.

Share Factors
In the above examples we assumed both process A and B are equally important and therefore require an equal use of resources. In most cases this is not a true representation of applications and users. Servers contain both mission critical applications and also users with varying degrees of ‘importance’. By implementing share factors within AppSense Performance Manager, these applications and/or users may be given a higher or lower share of CPU time.

If the process A is a mission critical process then it may be assigned a higher share factor. The effect of this is to raise the priority of the process so that it may have a longer CPU time before process A is given a higher priority.


Here process B has been given a higher share factor resulting in process A waiting on process B. The difference now is the time process A has to wait is a value which is configurable by the Administrator. A further function of AppSense Performance Manager is the ability to apply application or system state control. An application may be defined as having a high share factor when in the foreground, a medium share factor when in the background, and a low share factor when minimized.

If we now look at things from a user point of view, the application they are currently working on will always be guaranteed to receive CPU time, and can therefore always be made to function within its required time to wait, hence “performing well”. Other processes continue to receive a share of CPU time ensuring that they also function. One key system state for SBC systems is the ‘disconnected’ state.

By assigning a relatively low priority to all other states we can ensure that users who disconnect from the server without logging out properly, do not continue to consume valuable CPU resource which is then made available to all other users.

In conclusion, Microsoft Windows operating systems go some way to addressing how applications make use of system resources, but it is clear that in situations of high resource usage, such as in SBC environments, they are challenged. AppSense Performance Manager addresses these shortcomings. It provides many methods of controlling critical system resources such as CPU, Memory (both physical and virtual) and Disk. It’s CPU scheduling algorithm ensures that even in times of maximum CPU usage the server remains responsive for each user and application. If necessary, weighting may be given to ensure minimum response times for mission critical applications and/ or users.

BriForum 2009! – Independent Desktop & Application Virtualization Conference

July 22, 2009

This years BriForum is well underway, and already there are many blog’s keeping us who were not fortunate enough to attend up to date with all the breaking news and gossip.

Rene Vester has kindly grouped together the BriForum blogs he is aware of –  here

BriForum can also be followed on Twitter, by either following the BriForum hashtag – #BriForum , or, following the official BriForum Twitter feed @BriForum

Brian and the team have also started uploading photos from the event to their Flickr account – here

Of course as world leading User Environment Management solution provider, AppSense are in attendance, so please pop over to the booth if you have not yet seen or do not yet use AppSense Management Suite Version 8

AppSense Management Suite Version 8 Training for our US Partners

July 10, 2009

AppSense will be running the new 2 Day Training Course for the AppSense Management Suite Version 8 in July, 2009.
It is a requirement for all members of the AppSense Certified Solutions Partner (CSP) Program to complete training on the current version of the AppSense Management Suite (AMS). On completion of this training course you will be able to assist your prospects and customers with installation and configuration of all AppSense products.

For full training course information, please download the following AppSense Training Course Overview

Training Course Details:
27th – 28th July, 2009
New Horizons
43 West 42nd Street
Between 5th and 6th Ave
New York
NY 10036
Registration 8:30am – 9:00am
Course Duration 9:00am – 4:30pm

To register your place, please email and please title your email subject as ‘Please book my place on the US AppSense Management Suite V8.0 Training Course’

Look forward to seeing you all there!

Citrix XenApp/XenDesktop & VMware View: joint AppSense Customer Case Studies.

July 8, 2009

Despite current economic climate conditions, many IT projects (therefore the vendors involved in such projects) are proving to remain a key focus for many organizations and as such, being in the right place at the right time, means for some, Business is still Booming.

So what projects are securing the ever decreasing IT budget? – Well, the ones that have proven benefit to the organization by saving hard costs and providing proven return on investment… In other words, Virtualization.

AppSense are a critical part to desktop virtualization (VDI), thereby including us as one of the vendors incorporated in the remaining projects.  With that said, I am proud to support this with the inclusion of another 3 large, household names as customers and case studies on our website.

Please visit our customer page  for more information on our case studies and reference sites.

Review of AppSense Environment Manager 8 by vExpert Tom Howarth

July 8, 2009

Tom Howarth (a VCP/vExpert specializing in Thin Client & Virtualization solutions) and author of has published a comprehensive review of AppSense Environment Manager Version 8.0

Tom is well known and highly respected within the VMware and Citrix communities and as such, this positive review comes with high regards.  In Tom’s concluding words he describes AppSense Environment Manager as, “It is a Ronseal product – it does what it says on the tin.”

The article can be viewed at

Citrix & VMware VDI webinar by AppSense & Virtera

July 8, 2009

Leading Citrix & VMware partner and AppSense Gold Level CSP Virtera hosted a joint webinar with AppSense covering main considerations when looking at introducing Desktop Virtualization (VDI) into an enterprise.

Andy Cohen, Solutions Architect for Virtera covers the high level requirements for VDI adoption, including OS and Application delivery, storage and optimization.  Followed by Dan Palmer, Senior Systems Engineer for AppSense who details how user environment management enables a componentized desktop model, while also showing how to avoid many of the user centric and IT focused headaches which are typical in VDI.

View this recorded webinar to learn how to avoid the pitfalls and obstacles organizations are not aware of at the outside, but inevitably run into during VDI proof of concepts, pilots, and roll-outs.

Other AppSense media, including a AppSense Management Suite tutorial by Brian Madden, and many other demonstrations and webinars by Doug Brown (of DABCC) can be found at the AppSense Media Center

The cost of long user logon times to Citrix and VDI

July 3, 2009

Most of us at some point have experienced a long logon time when waiting to connect to a Windows Terminal Server or Citrix XenApp session.  And for most part, we just put up with it.  But on further inspection and if we scale this from just us, one user, to out across an enterprise, say, 10,000 users.. Then what is the cost there? 

10,000 users, all waiting 2 minutes to log on and start their shift work.. That’s 20,000 minutes per day!  Over 300 hours of lost productivity and paid for salary, everyday!!  At just 2 minutes per day, a typical user can expect to lose 30 hours worth of work over 3 years.

So what can be done about this?  First, let’s understand what causes the lengthy logon process…

One of the major causes of long logon times is unnecessarily large user profiles being loaded wholesale into the user session at logon. User profiles can grow to 100’s of megabytes in size, and if not managed correctly, can continue to grow further.  It is this large amount of information which causes the long wait as the system drags all your files, folders and personal settings across a network to load into your session.  But again, this is not just for you, it is also happening for everyone else logging onto the system too.  The solution therefore, reduce the amount of network traffic at logon, and reduce user logon times..

AppSense technology prevents the need for the whole profile to be loaded at logon, thus significantly speeding up user logon times. So what are the options?

AppSense Environment Manager streams in user settings on demand as they interact with their desktop session and applies user personalization to applications as they are launched. By selectively loading in settings required to set up and personalize the initial desktop, no application settings need be transferred across the network and into the user session as part of the logon procedure.

In most cases, this will reduce your logon time to just a few seconds.. As Conexus Credit Union found out..Conexus