No session data or Desktop Settings saved at Logoff? We came across this particular problem on about 30 of our Windows 7 PCs. They were all born from the same Gold image as the other working 300 or so desktops (we are about half way through our Windows 7 migration) but these few PCs all presented the same issue. We were seeing no Session Data, Desktop Settings or Logoff actions completing at User Logoff. Continue reading “AppSense Environment Manager Session Data Not Saved at Logoff – EmExit.bat” »
Hands up, fair cop. In a recent blog post on scripting Internet Explorer Favorites I forgot to mention using script exit codes when I dealt with the custom actions. Any custom script you include in your configuration is always interpreted as completing successfully by the agent on exit unless you specify otherwise in your code. Continue reading “AppSense Environment Manager Custom Action Script Exit Codes” »
Well this is certainly something we wanted to do in our environment. Based on different group memberships and user requirements for different web apps we wanted to post links into the users favorites folders in Internet Explorer. Historically, users managed their own app shortcuts in the Favorites folder but this led to inconsistencies especially when a url was updated server side. We decided to publish a folder called “!Corporate” in the users favorites folder. This folder (if sorted alphabetically) would appear at the top of the users favorites and we would leverage the ability to run vb script from an Environment Manager trigger. We could then add/delete/modify urls and keep a consistent-corporate approach to managing these items. Continue reading “Adding Corporate Favorite Items to a Users Profile using AppSense Environment Manager” »
Lets set the scene..You are rolling out hundreds of PCs with Windows 7 and you want all the agents preinstalled..naturally. Well the AppSense Environment Manager Agent is no exception.
Rolling out Windows 7 64bit prompted me to create an installation script for our PrairieFyre Contact Center Client. It is fairly basic, we install some prerequisites, the Contact Center Client (CCC) with the IP address of the server and then do a bit of cleaning up (vcredist is so messy and dumps its installation files into the root…blah). Ok, first of all we need to extract all the necessary setup files onto our server share.
Well, there I was trying to figure out how to create a silent install script for CutePDF on our Windows 7 64bit PCs. After losing a few hairs trying to work out why it wasn’t working silently it was because setup was looking for a 32bit installation of ghostscript. Answer?