Imaging PCs with AppSense Environment Agent PreInstalled
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.
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.
Ok, so this happens fairly infrequently but the following command is useful for when it does - it saves having to reboot the controller. You either get one or more voicemail ports lock up and this manifests itself normally when your users stat to complain that they cant dial into voicemail. If your voicemail group is set as a Terminal group and it is the first port that is locked/crashed it is easy to identify when there is a problem - because your helpdesk gets pummeled by frustrated users.
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?
Ok, so I have a little obsessive compulsion when it comes to cleaning up old config files that are no longer needed. I notice the msi files build up a fair amount in the “%ProgramFiles%\AppSense\Management Center\Communications Agent\download” directory. I wanted to delete any files that are older than 30 days ( I figured I would never have to roll back any further than 30 days..gamble I know.)
Here is how I done it with my fav Microsoft executable..Robocopy
Well, today it was brought to my attention that we weren’t personalizing Internet Explorer Trusted Sites..woops. But as we are still rolling out AppSense I forgave myself. We added the following registry key to our Application Group “Internet_Explorer” under the Registry Tab - Includes (see image below)
Welcome to my blog. I have spent countless hours head scratching various problems so I have decided to share them (and the solutions) in my blog. If I can offer any help take it as a free gift but I would appreciate a link back to my site if you post it onto other blogs/forums. I’ll cover topics including AppSense, Datacentre, VMware VSphere, Active Directory, Exchange, XenApp, Landesk, Cisco, SAN, Mitel VOIP and more.
Thanks :)