Thursday, 27 February 2014

Changing the Management Console User Postponement Values

This post is going to describe a mechanism to extend the default user postponement options within the Management Center console.

AppSense introduced a feature within the Management Center console to allow end users the ability to postpone a reboot following the installation of an AppSense DesktopNow agent. By default Administrators can provide their users with the ability to postpone the reboot by anything from 0 to 8 hours. This allowed a large number of customers who previously couldn't use the Management Center because it would simply reboot the machine as soon as it was ready to. This had the ability to lose data if the user was in the process of working on a document, etc.

To see the steps required to configure this continue reading.

Wednesday, 12 February 2014

Performance Manager 8.2... Whats new and some tips!

AppSense Performance Manager 8.2 was recently released and one of the nice new features introduced in Performance Manager 8.2 was the default configuration templates that ship with the product.


These templates provide a great starting point for anyone looking to implement AppSense Performance Manager within their estate. That said, performance must still be assessed on a case by case basis and the configuration that works for my environment may not necessarily work within your environment.

This post will share a few tips that I follow when implementing AppSense Performance Manager.

Tuesday, 11 February 2014

Environment Manager Post Logon Trigger

I've sat through a lot of workshops both internally and externally were logon times are a major problem. I've had customers tell me about C-Level executives who phone their assistants and ask them to logon so that when they get to the office they can start working, users logging on and then walking off to make their morning coffee whilst their system logs on, etc. With this in mind a lot of the customers I speak to are not prepared to add anything into the logon trigger.

For years people have recommended using AppSense Environment Manager and creating a set of actions that run on the process started trigger when explorer.exe runs. Others recommend assessing the logon process and find something that runs in the user context immediately after logon. These are both acceptable recommendations but in my experience are not ideal. Builds vary and you cannot always rely on a specific application running on all platforms to trigger these actions from.

This post will show you what I do instead and to date... this hasn't failed:

Monday, 10 February 2014

VMware ThinApp 5 Build modifications for AppSense Personalization

If you follow @AppSense on twitter, read the blog, etc you would have seen that AppSense now supports VMware ThinApp 5.

AppSense has always supported personalizing ThinApp applications but up until now this mean roaming the ThinApp sandbox instead of just the application settings like they do for native and App-V applications. The latest changes allow AppSense to manage ThinApp applications in exactly the same way as native applications.

That said, there are a few things you need to be aware of: