Apptimized Platform Admin Manual

Prerequisites and firewall rules

The following prerequisites apply for Apptimized Platform: 

1. Browsers:  

2. Enabled Java-script in browser

3. Endpoint PC or VM with access to the 80 and 443 port of app.apptimized.com host

4. Firewall white list:  

Component

Description 

https://app.apptimized.com/  Address for access to Apptimized Portal 
wss://rdp-gw-v2.apptimized.com 

Address for working with RDP connections in Apptimized Portal 

Granting permissions to communicate via WebSocket SSL protocol is needed 

https://auth.apptimized.com/

Address for single sign-on 

https://admin.apptimized.com/

Address for manage organization configurations

https://apptimizedportalshare.file.core.windows.net
Address for download files from Apptimized Portal 
https://screenshots.api.apptimized.technology  Address for screenshots storage 

https://docs.apptimized.com/ 

Address for Apptimized user documentation 

*.chatlio.com 

Address for access to support chat widget 

*.swarm.apptimized.com 

Address for Apptimized Portal virtualization service. 
Granting privileges on wildcards subdomains is needed. 

Granting permissions to connect via RDP protocol is needed 

The standard account credentials for Apptimized Platform on Apptimized VMs are: 

Login Password
apptimized apptimized
administrator apptimized

 

Requirements and limitations for Apptimized Whitelabeling

The following requirements need to be met for custom domain Whitelabeling configuration:

Component Description
CNAME Record created with customer's DNS provider using the following configuration:

CNAME %subdomain%.%customerdomain%.%TLD% = apptimized-portal.azurewebsites.net

Example: CNAME apps.greatcompany.com = apptimized-portal.azurewebsites.net
TXT Record created with customer's DNS provider using the following configuration:

TXT = verification code = %customerdomain%.%TLD%

Example: TXT=7D86E8C065D4002DA1DC8E74C921D1EDAFA = greatcompany.com
SSL certificate Certificate in a form of PFX file + password combined into a PWD file. 
Domain address Address for custom Apptimized Portal whitelabeling.
DNS host Name of Domain Name Server host.
Domain for mail sending Address for email sending configuration.

The prerequisites need to be provided to Apptimized staff or delivery managers in order to proceed with the configurational process.

 

Requirements and limitations for Apptimized Connectors

SCCM Connector

The following prerequisites apply for SCCM connector: 

Intune Connector

The following prerequisites apply for Intune connector: 

ServiceNow Connector

The following prerequisites apply for ServiceNow connector: 

Azure VDI Connector
Apptimized TO GO Connector

The following prerequisites apply for Apptimized TO GO connector: 

  1. Speed of internet connections – min 50 Mb/s.
  2. Enabled firewall white list:

    Component Description

    https://app.apptimized.com/

    Address for access to Apptimized Portal 

    https://rdp-gw.apptimized.com/

    Address for working with RDP connections in Apptimized Portal 

    https://rdproxy.apptimized.com/

    Address for working with DRP connections in Apptimized Portal via proxy
    https://screenshots.api.apptimized.technology/ Address for screenshots storage
    https://auth.apptimized.com/ Address for single sign-on 
    *.swarm.apptimized.com

    Address for Apptimized Portal virtualization service. 
    Granting privileges on wildcards subdomains is needed. 

    Granting permissions to connect via RDP protocol is needed 

    *.chatlio.com

    Address for access to support chat widget 

  3. Endpoint PC or VM with access to the 443 port of app.apptimized.com host;
  4. Microsoft Windows Desktop (Windows 7 and above) or Server OS (Windows Server 2012 R2 and above) with installed .NET Framework 4.6.1;
  5. Windows 7: Fallback via HTTPS - downloading files from Apptimized Portal to the temp folder on the C drive of the TO GO machine & mounting the folder as a Network drive;
  6. Windows 10: SMB 3+ presence - mounting Apptimized Portal as Network drive; if SMB 3+ is not present, see Windows 7 scenario above.

 

SCCM User Guide

SCCM User Guide

Push to SCCM as Application

Deployment starts from the project portfolio.

sccm_27.png

The application should have a package file produced during the Packaging step (Factory or Self-Service). If the required file is missing, Apptimized shows the notification.

sccm_15.png

After locating the application in the list, the deployment process can be triggered by clicking the extended menu in the Actions column and selecting Push to SCCM as Application.

sccm_20_01-(1).png

Apptimized shows the following screen when successful:

sccm_31_01.png

The option to continue the deploying process is available after selecting the SCCM environment and clicking the Confirm button.

Apptimized shows the following screen when successful:

sccm_25_01.png

 

 The application inherits default SCCM project settings. . Brief field descriptions are available by hovering the info icon (info.png)

 

An application is scheduled for deployment by clicking on the Save button. Apptimized shows the following notification when successful:

 

image-1612435302794.png

 

It takes a few minutes for SCCM objects to appear in the SCCM Admin Console.

Details of the deployment process components are described in the sections below.

Create the application in SCCM

The creation of applications can be enabled by Create Application switch and editing appropriate settings if required. Brief field descriptions are available by hovering the info icon (info.png) located near every field.

sccm_26_01.png

Table 4. Application settings

Settings 

Details 

Vendor name 

The vendor name equals the vendor field of application in the project portfolio. 

Application display name 

The application name equals the application field of application in the project portfolio. 

Localized Application name 

The name of the application to be shown in SCCM console. 

Application version 

The application version equals the application version of the application in the project portfolio. 

Application owner 

Package creator name. The default value is the name of a current user. 

Administrator Comments 

This term corresponds to the term Administrator comments in the SCCM admin console. 

SCCM optional reference 

Optional reference to the SCCM environment. 

Folder in the SCCM Console UI 

This setting indicates the folder for applications in SCCM Console UI. Applications can store in the main folder Applications (default) or any subfolders. 

Auto-install in task sequence of SCCM Console 

This setting corresponds to the setting Install or uninstall the application by default in the Connection and default configuration step (see Table 2). 

 
 

Create the deployment type in SCCM

The creation of deployment type can be enabled by Create Deployment Type switch and editing appropriate settings if required. Brief field descriptions are available by hovering the info icon (info.png) located near every field.

sccm_27_01.png

The list of created deployment type templates (see Integration > Connection and default configuration step) is available under the Deployment types block. All templates are disabled by default. A template becomes active when switched on.

sccm_28_01.png

The option to expand deployment type template is available under the sccm_changes_09.PNG symbol.

A user can change pre-configured template settings if needed. Template settings correspond to the SCCM integration settings.

Create the deployment in SCCM

Creation of deployment can be enabled by Create Deployment switch and editing appropriate settings if required. Brief field descriptions are available by hovering the info icon (info.png) located near every field.

sccm_29_01.png

Table 5. Deployment settings

Settings

Details

Name of default destribution group

This setting corresponds to the setting Name of a default distribution group шn the Connection and default configuration step (see Table 1).

Collection type

This setting corresponds to the setting Collection type in the Connection and default configuration step (see Table 1). 

Collection name

This setting corresponds to the setting Collection name in the Connection and default configuration step (see Table 1).

Install or uninstall the application by default

This setting corresponds to the setting Install or uninstall the application by default in the Connection and default configuration step (see Table 2).

Deploy the purpose of the installation by default

This setting corresponds to the setting Deploy purpose of the installation by default in the Connection and default configuration step (see Table 2).

Deadline time

This setting corresponds to the setting Deadline time in the Connection and default configuration step (see Table 2).

Time zone of deadline

This setting corresponds to the setting Time zone of a deadline in the Connection and default configuration step (see Table 1).