Creating an AppSense Management Center Turbo Container

Creating an AppSense Management Center Turbo Container

Creating an AppSense Management Center Turbo Container

This post has already been read 15707 times!

In this post I will walk you through creating a Turbo Container for the AppSense Management Center Application, uploading it to your hub, securing the application with Network Routes and deploying the Container to your workload servers.

In my previous post I walked you through adding a pre-defined Turbo application to your hub and securing that.  This will follow the same process with the exception that you will be adding your own custom application to the hub and securing that.

Lets get going

First – this procedure has already been written about by Eric and can be found here:

http://xenappblog.com/2016/install-custom-applications-in-turbo/

But, not all users end up on the same page and use the same search terms so I figured I would document my process for the AppSense Management Center application.

First get your software you intend to install in a local folder

01 - software

Open a command prompt as an Administrator and start a new container mounting your installer location

02 - new container

Once the container is open make a note of the Container ID

03 - container created

Install the Pre-Req’s from your mount point

04 - run install

Let the install run through as normal

05 - install pre reqs

Install your AppSense Management Center

06 - install app

Run through the installer wizard as normal

07 - install wizard

NOTE: When prompted for a management server use http://server.domain.com, when the application runs for the first time you can add your server in there.

08 - install complete

Let the application install finish then exit the container

09 - exit container

Ensure you get an exit code of 0 for a clean exit

10 - clean exit

Commit the new Container

11 - commit container

Change the Container startup file to equal the exe file you wish to launch

12 - overwrite startup file

Ensure you are logged in as your Turbo User

13 - ensure logged in

Push the new Container to your portal

14 - push container

Wait for the push to complete

15 - push complete

Switch to your Turbo Management Console to view your application

16 - application live

Click on the Application title to edit the Container properties

17 - make private

Click the Application icon to change the icon

18 - add icon

Give the Application a Name

19 - give name

Hover over the application in your portal and click Add to add it to your hub

20 - add app

Select the Network Layer then Routes.  At this point we are going to Secure the Management Center.  In this example I am going to ONLY allow IP Traffic to my AppSense Management Server.  In a real world this would not work as it is FAR to restrictive! I am just using it as an example as to the power of network routes in Turbo.  In the real worls you would probably restrict this at a minimum to your AppSense Management Server, SQL Server and the Endpoints with the AppSense Agents on.

Get the IP Address of your Management Server

21 - as server name

Add this as an allowed route

22 - add routes

OK the routes and then switch back to your workload server and subscribe to your applications

23 - subscribe

Wait for the command to complete

24 - apps added

You will see the new application on your workload server, click it ro download the container

25 - apps available

Wait for the download to complete

26 - download container

Hey presto! You can now add your management server to the console and use your new turbo containerized application.

27 - add server

That’s it, once again thanks to Eric from xenappblog.com for making this learning curve a LOAD easier for me and I hope this helps some of you out.

As always please comment and share

Laters,

b@m

One thought on “Creating an AppSense Management Center Turbo Container

  1. Pingback: Having Some Fun With Turbo Containers - Windows XP 3D Pinball | Bretty.me.uk

Leave a Reply

Your email address will not be published. Required fields are marked *