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 < YOU ARE HERE!
Part 3: Importing the Base Configuration
Part 4: Deploying the Client Communications Agent
Click Launch Management Server Configuration once the install has finished:
Review the Welcome screen and click Next:
Review the prerequisites and click View:
Click Repair All to remedy any required prerequisites:
Click Refresh:
Once all requirements have been remediated, click Close:
Click Next:
Click Next:
Leave Use Windows Authentication (Recommended) selected and click Next:
Enter the SQL Server Name (and instance if applicable), and Database Name and click Next:
Typically I will prefer to create a service account to tie to the SQL database and install agents on managed systems. For smaller environments, this can be a Domain Admin account for simplicity as it requires local administrative privileges to each managed system for agent updates. Enter the credentials and click Next:
Click Accept:
Uncheck Launch the Server Configuration Utility on exit and click Finish:
Click Launch Personalization Server Configuration:
Click Next:
Click View:
Click Repair All:
Click Refresh:
Once all requirements have been remediated, click Close:
Click Next:
Click Next:
Leave Use Windows Authentication (Recommended) selected and click Next:
Enter the SQL Server Name (and instance if applicable), and Database Name and click Next:
Enter the service account credentials for database connectivity and click Next:
Review and click Accept:
Click Finish:
Click Finish:
From the Start Menu, launch the AppSense Management Console. The first time you use the Management Console, you will need to create the server connection. Click Connect to get started:
Click the + icon in the top ribbon to add the server connection:
Enter the FQDN and a description and click Add:
Click Connect:
Leave Current User selected and click OK:
Navigate the tree to Overview –> Deployment Groups –> (Default) –> Settings –> AssignedPackages. For this demonstration, I will cover deployment and configuration of Environment Manager only. Therefore, select Environment Manager and on the Actions pane, click Quick Setup:
Highlight the latest agent and click Next:
Highlight the latest agent and click Finish:
We will come back to this screen to deploy Environment Manager configurations, for now simply review that 32-bit and 64-bit agents are assigned to the default deployment group. Click Review and Submit to commit the changes:
Click Yes to confirm:
Click Submit:
Click Yes:
Select the Client Access Credentials section and click Add Credential:
Enter the service account credentials (for deploying new agents to managed systems) and click OK:
Review the credentials have been added successfully:
Select the Installation Schedule section and change the following settings:
Agent Schedule: At Computer Startup
Configuration Schedule: Immediately
Once the changes have been made, click Submit to commit the changes:
Verify the Submit button is grayed out:
To continue reading, please choose from the following:
Part 1: AppSense DesktopNow Single Server Installation
Part 2: AppSense DesktopNow Single Server Configuration < YOU ARE HERE!
Part 3: Importing the Base Configuration
Part 4: Deploying the Client Communications Agent
If you have any questions, comments, or just want to leave feedback, please do so below. Thanks for reading!
–youngtech
Leave A Comment