Rebranding AppSense Management Suite to DesktopNow Requires a Fresh Look at AppSense User Virtualization! Part 4

Share Button

If you’ve just stumbled upon this article, I recommend you start from the beginning by clicking the Part 1 link below.  For easy reading, I’ve broken this blog post into four parts:

Part 1: AppSense DesktopNow Single Server Installation
Part 2: AppSense DesktopNow Single Server Configuration
Part 3: Importing the Base Configuration
Part 4: Deploying the Client Communications Agent < YOU ARE HERE!

From an AppSense Managed System, navigate to http://%appsenseservername%/ManagementServer in a Web Browser. Click either AppSense CCA 32 Bit or AppSense CCA 64 Bit:

1060

Click Run:

1070

Click Run:

1080

Click Next:

1090

Accept the License Agreement and click Next:

1100

Click Next:

1110

Enter the management server URL and click Next:

1120

Click Install:

1130

Click Finish:

1140

Once the AppSense Client Communications Agent (CCA) has been installed, reboot the server to start the Environment Manager agent install and pull down the initial policies:

1150

In the AppSense Management Console, you can navigate to the Computers node of the deployment group to monitor the Deployed Percentage (Green when 100%, Yellow when packages have yet to be deployed). This is also where you can select computers and click Poll Now to push configurations immediately:

1160

Repeat the CCA installation on any desired systems to start managing user personalization across multiple devices! The last and most important thing is to thoroughly test the configuration. A couple simple tests I usually perform involve logging into managed systems, watching the profiles get created under C:\Users and the ProfileList registry key. Then, equally important, logging off the managed systems should remove the local user profile from C:\Users and the ProfileList key. Logging on subsequent times should keep important user data such as desktop wallpapers, any data stored in the redirected folders, and application data changes. An example of application data changes would involve modifying the Office 2010 ribbon to add custom actions. All these settings should persist across logons, despite the local profiles being removed from the C:\Users and ProfileList locations. That just about covers all the components for getting a basic AppSense DesktopNow deployment setup for Virtual Desktop Infrastructure or Server Based Computing.

To review any section, please choose from the following:

Part 1: AppSense DesktopNow Single Server Installation
Part 2: AppSense DesktopNow Single Server Configuration
Part 3: Importing the Base Configuration
Part 4: Deploying the Client Communications Agent < YOU ARE HERE!

If you have any questions, comments, or just want to leave feedback, please do so below. Thanks for reading!

–youngtech

Share Button
  1. Lokesh MajjiLokesh Majji05-28-2014

    Good One. Thank you for providing the insight to DesktopNow.

  2. Andy SulakAndy Sulak01-29-2013

    Nice Job! Most of the time, organizations don’t use the manual install procedure you have above, though it’s always available to them.

    They will usually push out the clients with the AppSense Management Console or through SCCM or other deployment tools to easily handle hundred and thousands of endpoints.

    But, for a small test environment, installing from the browser interface works!

    • Dane YoungDane Young01-29-2013

      Awesome. Thanks for the feedback Andy!
      –youngtech

Leave a Reply to Dane Young Click here to cancel reply.