Citrix CPSM V10 Integration Manual

ManualsBrandsAcronis ManualsApplicationsBackupAgent

BackupAgent Service Manager

Installation Guide

Customer Name

Cortex Release Version

Document Version

1.4 Last updated: 12 Aug 13

1.1 Prerequisites

Citrix CPSM v10 (formerly known as Cortex) integrates with BackupAgent using the

BackupAgent Active Directory Synchronisation feature. This feature needs to be working for

BackupAgent before the Cortex Integration will succeed.

1.2 Create the initial set of Service Access Levels

BackupAgent’s Active Directory Synchronisation relies on users being made member of Active

Directory Security groups with specially crafted names. These groups have to be in the format:

BackupAgent_<Plan>_<Quota>_<Storage Group ID>

Where:

 <Plan> is either Home or Professional where Home is for desktop backups and

Professional is for Server backups including Microsoft Exchange and Microsoft SQL

server.

 <Quota> is the maximum storage space in gigabytes or megabytes e.g 500MB or 10GB

 <Storage Group ID> is the internal BackupAgent ID for the particular storage group.

CloudPortal puts users in and out of these groups as part of the actions when a user is put in a

specific Service Access Level. For this to occur, each Service Access Level needs to have the

following properties set

Summary of content (8 pages)

PAGE 1
Citrix CPSM V10 Integration Manual BackupAgent Service Manager Installation Guide Customer Name Cortex Release Version 10 Document Version 1.4 Last updated: 12 Aug 13 1.1 Prerequisites Citrix CPSM v10 (formerly known as Cortex) integrates with BackupAgent using the BackupAgent Active Directory Synchronisation feature. This feature needs to be working for BackupAgent before the Cortex Integration will succeed. 1.
PAGE 2
Therefore we would expect an access level to have the following properties analogous to the group name format: 1. Plan (either Home or Professional) 2. Quota (Integer number) 3. Quota unit(either MB or GB) 4. Storage Group ID The location of the Security groups that the Service Provider has created when testing the BackupAgent service is set out in the Preparation Form. As a courtesy, it is usual to create a Service Access Level for the groups that they are managing.
PAGE 3
1. Configured Cortex to put users at the root of the customer’s OU, or 2. Discussed the other option with the Service Provider. 1.4 Configuring the OU structure for the customer As described in the paragraph above users should be placed in the root OU. To do so run the following SQL command on the SQL Server where the cortexdatabases are installed: Use [OLMReports] Update Settings set Value = '' where Property = 'OrganisationalStructure' Go Do an iisreset on frontend server after this command 1.
PAGE 4
9. Click on “Import” to import the service 10. Restart Cortex Queue Monitor 1.6 Configure the Service Properties Many of the Service Properties of this service set the properties of the BackupAgent Administrator User that Cortex automatically creates for each customer and in general these will not need to be changed. The properties that are usually set are: 1. Go to Configuration-System Manager->Service Deployment 2.
PAGE 5
work the clients must be renamed to have the .ems extension and placed in a certain directory under the Cortex Web Site path. This property points to the default location of this path. It is expected that this property will be overridden at the level of the Reseller service. This information should be provided in the Preparation Form.
PAGE 6
The handler only needs to be enabled once for each instance of the Cortex Web Site that you are hosting so the handler may already be enabled. If you do need to enable this handler for your Cortex site you need to do the following: 1. On the web server, open IIS manager (Start > Run: inetmgr) 2. Under “Web Sites”, expand the “Cortex Management” virtual server and right-click on “CortexDotNet” to edit the properties: 3.
PAGE 7
4. You need to add a mapping: 5. The mapping should have an extension of .ems and the path to the aspnet_isapi.dll executable. It is usually “c:\windows\microsoft.net\framework\v2.0.50727 \aspnet_isapi.dll” 1.7 Creating and Configuring the User Plans 1. Go to Configuration-System Manager->Service Deployment 2.
PAGE 8
3. If there are no userplans configured yet, enter a name for the user plan and then click on “Create” If you already have one click on it to see its properties 4. Make sure following properties are filled in: 1. BackupAgent plan: “Professional” or “Home” 2. BackupAgent Quota Unit: “MB” or “GB” 3. BackupAgent Quota Size: “The size chosen for the package” 4. BackupAgent StorageID: The ID of the storage associated with the plan inside backupagent.