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

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 < 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:

230

Review the Welcome screen and click Next:

240

Review the prerequisites and click View:

250

Click Repair All to remedy any required prerequisites:

260

Click Refresh:

270

Once all requirements have been remediated, click Close:

280

Click Next:

290

Click Next:

300

Leave Use Windows Authentication (Recommended) selected and click Next:

310

Enter the SQL Server Name (and instance if applicable), and Database Name and click Next:

320

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:

330

Click Accept:

340

Uncheck Launch the Server Configuration Utility on exit and click Finish:

350

Click Launch Personalization Server Configuration:

360

Click Next:

370

Click View:

380

Click Repair All:

390

Click Refresh:

400

Once all requirements have been remediated, click Close:

410

Click Next:

420

Click Next:

430

Leave Use Windows Authentication (Recommended) selected and click Next:

440

Enter the SQL Server Name (and instance if applicable), and Database Name and click Next:

450

Enter the service account credentials for database connectivity and click Next:

460

Review and click Accept:

470

Click Finish:

480

Click Finish:

490

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:

500

Click the + icon in the top ribbon to add the server connection:

501

Enter the FQDN and a description and click Add:

502

Click Connect:

503

Leave Current User selected and click OK:

510

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:

520

Highlight the latest agent and click Next:

530

Highlight the latest agent and click Finish:

540

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:

550

Click Yes to confirm:

560

Click Submit:

570

Click Yes:

580

Select the Client Access Credentials section and click Add Credential:

590

Enter the service account credentials (for deploying new agents to managed systems) and click OK:

600

Review the credentials have been added successfully:

610

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:

620

Verify the Submit button is grayed out:

630

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

Share Button

Leave a Reply