© 2010 EMS-Cortex
Table of Contents
Part I Introduction
7
... 7 1 Logging on to the Cortex Control Panel
... 9 2 Resetting Your Password
... 9 3 Navigating around the Cortex Control Panel
... 10 4 Provisioning Status Indicators
... 11 5 Types of Customers
... 11 6 Types of Users
Part II System Configuration
12
... 12 1 Content Management
... 12 Branding
... 13 Managing Customer Brands
... 16 Stylesheet Management
... 20 Em ail Notifications
Part III Customer Management
25
... 27 1 Create a New Customer
... 32 2 Create a Reseller Customer
... 34 3 Customer Hierarchy Screen
... 35 4 Customer Services Management
... 36 BlackBerry
... 36 Add BlackBerry to a Reseller
... 36 Add BlackBerry to a Customer
... 37 BroadWorks
... 37 Add BroadWorks to a Reseller
... 39 Add BroadWorks to a Customer
... 40 Citrix
... 41 Add Citrix to a Reseller
... 43 Add Citrix to a Customer
... 44 CRM
... 44 CRM 3.0
... 44 Add CRM 3.0 Service to a Reseller
... 44 Add CRM 3.0 Service to a Customer
... 45 Limitations and know n errors
... 46 CRM 4.0
... 46 Add CRM 4.0 Service to a Reseller
... 46 Add CRM 4.0 Service to a Customer
... 48 DNS Hosting
... 48 Add DNS Hosting to a Customer
... 49 Exchange
... 50 Add Exchange to a Reseller
... 51 Add Exchange to a Customer
... 54 File Sharing
... 54 Add File Sharing to a Reseller
... 54 Add File Sharing to a Customer
... 56 Mail Archving
... 56 Add Mail Archiving to a Reseller
... 56 Add Mail Archiving to a Customer
... 58 Microsoft SQL Server Hosting
... 59 Add SQL Hosting to a Reseller
... 59 Configure Resources
... 60 Add SQL Hosting to a Customer
... 61 MySQL
... 61 Add MySQL to a Reseller
... 61 Configure Resources
... 62 Add MySQL to a Customer
... 62 Office Com m unications Server 2007
... 63 Add OCS to a Reseller
... 63 Add OCS to a Customer
... 65 SharePoint
... 65 Add a SharePoint Instance to a Customer
... 69 Limitations and Know n Errors
... 70 SharePoint 2010
... 70 Configure Resources (SharePoint Farms & Feature Packs)
... 71 Add a SharePoint 2010 Instance to a Customer
... 73 User Sync
... 73 Add User Sync to a Customer
... 73 Troubleshooting Customer issues w ith ADSync Tool
... 75 Virtual Machine
... 75 Add Virtual Machine to a Customer
... 77 Web Hosting
... 77 Add Web Hosting to a Reseller
... 79 Add Web Hosting to a Customer
... 82 5 Customer Search
... 82 Custom er Filter
... 82 Advanced Custom er Search
... 84 Sm art Custom er Search
... 84 6 Customer Functions ... 85 Disable / Enable ... 86 De-Provision ... 86 Delete ... 87 Edit Custom er ... 87 7 Customer DNS Records ... 88 Enabling Custom er Dom ains for DNS Tem plates
... 88 8 Trial (Demo) Customer Accounts
... 89 Sales Force Adm inistration
... 89 Add a Sales Force
... 91 Add Users
... 92 Demo Customers Summary
... 93 Setup a Trial Account via Dem ow eb
Part IV User Management
95
... 96 1 Create a New User
... 100 Exchange
... 100 Add Exchange Service to a User
... 102 Advanced Exchange Settings for a User
... 105 Exchange User Summary
... 106 Send Window s Mobile CAB file to your mobile phone
... 107 Outlook Dow nload Profile
... 108 Outlook Functions
... 108 Setting delegated user permissions in Outlook
... 110 Configuring to another user's mailbox in Outlook
... 112 Configuring Outlook - "From Button"
... 113 BlackBerry
... 113 Add BlackBerry Service to a User
... 114 Provisioned User's BlackBerry Details
... 116 BroadWorks
... 116 Add BroadWorks to a user
... 117 Citrix
... 117 Add Citrix Service to a User
... 118 CRM
... 118 CRM 3
... 118 Add CRM 3 Service to a User
... 120 Disable CRM 3 Service for a User
... 121 CRM 4
... 121 Add CRM 4 Service to a User
... 122 CRM4 Summary
... 122 File Sharing
... 123 Add File Sharing Service to a User
... 125 Mail Archiving
... 125 Add Mail Archiving Service to a User
... 125 Microsoft SQL Server
... 125 Add Microsoft SQL Hosting Service to a User
... 126 SQL User Summary
... 127 Office Com m unications Server (OCS)
... 127 Add OCS Service to a User
... 128 Reporting
... 128 Cortex Default Reports
... 131 View ing the Reports
... 131 SharePoint
... 132 Add SharePoint Service to a User
... 133 Add SharePoint Service to an External User
... 135 Accessing the SharePoint Site
... 135 SQL Authenticated Users - Change of Passw ord
... 136 SharePoint 2010
... 136 Add SharePoint 2010 to a User
... 137 Web Hosting
... 137 Add Web Hosting Service to a User
... 140 3 User Search
... 140 User Filter
... 140 Advanced User Search
... 142 Sm art User Search
... 143 4 User Functions ... 144 Edit User ... 145 Disable / Enable
... 146 Copy User ... 147 De-provision ... 148 Provision ... 148 Account Status ... 149 5 Multiple User Provisioning
... 151 6 Bulk User Import
... 154 7 Email Configuration
... 156 8 Locations & Departments
... 157 Locations
... 158 Departm ents
... 159 9 User Sync Function
... 159 User Sync Dow nload
... 162 Change user's status from AD Sync to Hosting
Part V OU Management
162
... 163 1 Organizational Structure
... 164 2 User Groups
Part VI Service Administration Features
166
... 166 1 Exchange ... 166 Public Folders ... 170 Contacts ... 172 Distribution Groups ... 176 Mail Disclaim ers
... 178 Resource Mailboxes
... 179 Mailbox Export & Im port
... 181 Send Window Mobile CAB files to m ultiple users via SMS
... 182 2 File Sharing
... 182 File Sharing Folder Manager
... 183 Security Group Managem ent
... 185 3 Citrix
... 185 Provision an application to m ultiple users
... 185 Create Custom er Level Application Groups
... 187 4 Web Hosting
... 187 Security Group Managem ent
... 188 IIS Site Manager
... 189 Directory Management
... 190 IIS Attributes Management
... 192 Advanced IIS Attributes
... 193 Sub-Domain Management
... 194 5 DNS
... 194 Managem ent of DNS Zones
... 195 Managem ent of DNS Sub Zones
... 195 6 Virtual Machine
... 195 Managem ent of Virtual Machines
... 198 Resource Sum m ary
... 199 Netw orks
... 199 MySQL Database Managem ent
... 200 MySQL User Managem ent
1
Introduction
This guide contains detailed instructions on how to configure hosted services within Cortex and how to set up customers and users with those services.
It also provides helpful tips and information on how to navigate around the Cortex user interface and use the features that Cortex offers.
1.1
Logging on to the Cortex Control Panel
Before you can log-on to the Cortex Administration Control Panel, you require the following details:
· The URL details to browse to the Log-on screen
· Confirmation of your User Name and Password
How to login to Cortex
1. Browse to the URL site.
2. Enter your User Name and Password and select Login.
Most often the user name that you will use will be your UPN. This is usually your primary e-mail address.
The Password field is case-sensitive.
Enabling the "Remember Me" property will ensure that your User Name is remembered when you next visit the site's Login Page using the the same computer.
3. Cortex allows a user to change their password at login. Select Change Password to display the password reset feature.
4. Enter a new password that meets the system's security requirements. Re-enter the new password to verify and select Login. The new password will be saved against the user's account.
An AD-Sync user will not be able to change their password on the Control Panel. Their passwords are managed in the remote domain controller and the user should be prompted to use their company's change of password process.
Cortex's Security Requirements for New Passwords
For the security of all users, password policies exist within Cortex which govern the type of passwords that can be used.
A new user password must conform to the following requirements:
· Must be a minimum of 8 characters long
· Must contain 3 of the following 4 character types: o Lower Case (e.g. lower case)
o Upper Case (e.g. UPPER CASE) o Numbers (e.g. 1, 2, 3) o Symbols (e.g. @, $, !)
· In addition to the above password requirements there is usually a requirement that your password cannot be too close to a password that you have already used. For example, in the past you may have a password like “Passw0rd1” and every time you changed the password you would increase the number e.g. to “Passw0rd2”. While this made it easier to remember what your password was, it is also regarded as a high security risk. The system will verify your new password to ensure that it is not a password that you have used before.
If a user name and/or password are entered incorrectly three times, the user account may become "locked out". When an account is locked out, the system will not allow the end-user to log-on even when entering the correct user name and password. The user account will unlock automatically after ten minutes at which point you can re-attempt to log-on.
If a user has forgotten their password, they must contact their System Administrator who will be able to reset it for them.
Password Expired
For the majority of users, a password will be associated with an expiration date. When a user attempts to log onto Cortex, after the expiration date has passed, the system will navigate them to the Password screen where they are required to enter their old password and a new password.
Password Management
The user can change their password whilst logged onto the Control Panel. Select Password >> Change Password. The next time that the user logs on to the portal, the new password will take effect.
Multiple Language Options
On the Control Panel's Login screen, an additional field called "Language" may appear. The default language is normally configured to English (United States). To select a different language, expand the language drop down list and select the required language. Only languages that have been configured within the Control Panel will appear in the drop down list.
The Control Panel will automatically remember the selected language the next time the user logs on using the the same computer.
1.2
Resetting Your Password
The Control Panel will allow an end-user to reset their user password if it has been forgotten. The availability of this feature is dependent on how the system has been configured by your Service Provider. To reset a forgotten password, Cortex will request the end user provides correct answers to a series of user-defined questions before allowing the user to create a new password. The configuration of the specific user questions is completed via Password >> Manage Security Questions.
Managing your security questions
1. Select Change Password >> Manage Security Questions.
2. Select a question from the drop down list or create your own question by selecting "- Type your own -". 3. Enter your answer to the question. Repeat until all questions and answers have been configured. 4. Select Update to confirm your answers. You will now be able to use the Forget Password? feature that
is available on the Login screen.
Resetting your password
1. Select "Forget Password?" on the Cortex Login screen.
2. Ensure that your username is entered and key in the five character Captcha value that Cortex displays on screen, Select "Validate". If the value is illegible, select the Refresh icon to display a new value. 3. Enter your answers to your pre-defined security questions and select "Validate". Cortex will validate
your answers, if the answers are correct, you will be prompted to change your password. You are allowed several attempts at answering the questions. After a number of unsuccessful attempts, you must contact your User Administrator to reset your password. The number of attempts you are allowed is configured by your Service Provider.
4. Enter your new password. By default, the "Login After Changing Password" will be enabled and after selecting "Update" you will be navigated to the Control Panel's home page.
1.3
Navigating around the Cortex Control Panel
The Cortex Control Panel is made up of different web pages that relate to specific functions and services. The availability of these pages are dependent on the end-user's security permissions and the services that have been provisioned to the user or customer.
Icon
Description
Home:
Navigates the user back to the Home Page
Customers:
Allows the user to complete customer management tasks including:
New Customer; Edit Customer; View Customer Hierarchy; Organization Structure management
Users:
Allows the user to complete user management tasks including:
Services:
Allow Service Administrators to complete service related admin tasks including:
Exchange - Manage distribution groups / contacts / public folders; Citrix Application Groups; Security Groups
Reporting:
All users to request and view available Reports. The availability of the reports will be dependent on the user's security permissions
Configuration:
Allow Administrators to configure specific system settings including:
Branding & Content Management; Services, Web Services & Servers, User Security Permissions
Help:
This icon links to your Service Provider's Support Site.
Password:
Allows the user to change their password and save their answers for the Security Questions (forgot password) feature.
Logout:
Will close the user's Cortex session and navigate to the Cortex Logon page.
1.4
Provisioning Status Indicators
The provisioning status Indicators allows users to monitor the progress of their individual provisioning requests.
Some provisioning requests can take a considerable amount of time to change from one status to another due to:
· the complexity of the request
· the number of requests that the system is processing
Status Descriptions:
Status
Description
Not Provisioned
Item has a) never been provisioned or b) has been de-provisioned.
Queued
Request submitted to the Provisioning Engine. Item has been queued for provisioning or de-provisioning.
Provisioning In Progress
The provisioning engine is working on the request.
Provisioned
Pending Changes
The request requires further configuration before it can be provisioned. This status can appear when copying an existing user's services.
Provisioning Failed
An error occurred while processing the provisioning request. Select the item to view it's configuration properties and the provisioning error description.
1.5
Types of Customers
Customer Descriptions:
User Icon Description
Reseller Customer
A customer who can create sub customers and on-sell configured services to its sub customers.
Standard Customer
A standard customerDisabled Customer
The customer and all of its users are disabled and will not be able to access their accounts.
Trial (Demo) Customer
A trial customer account has been set up for a defined period of time. The customer will be able to trial the services provisioned to them. The account will be de-provisioned and deleted after the expiry date and retention period have been met.
1.6
Types of Users
Cortex supports different user security access levels. These security access levels are linked to different icons, allowing easy identification of a user's role when reviewing a list of users.
User Descriptions:
User Icon Description
Enabled User
Includes Standard User / Partial User Administrator / Partial Service Administrator.
Customer Service Administrator
Full Service Administrator.
Customer User Administrator
Full User Administrator.
Customer User and Service Administrator
These users have Full User and Full Service Administration security rights. When a new customer is created, the first user added to the customer will automatically inherit this role.
Account Disabled
The user role has been disabled and the user can no longer log onto the Control Panel or hosted services. The user's services remain provisioned to the user's account.
Select Enable to re-enable the user account.
Account Expired
The user's system account has expired and the user can no longer log onto the Control Panel or hosted services. The user's services remain provisioned to the user's account.
To re-enable the user, change or remove the user account's expiration date.
Remote Active Directory / AD Sync User
The user's details, including password, are saved and managed on an external Active Directory Forest. The user's password cannot be updated on the Cortex Control Panel.
2
System Configuration
2.1
Content Management
This is the text and graphics that make up the Cortex user interface, display characteristics like font size, colours, positioning, borders, etc. This allows you to easily organize and control the front end content of Cortex as per your Customers requirements.
2.1.1
Branding
The Cortex control panel has been enhanced in Release 7.3 to increase the usability of managing brands. Brands can now be managed by the Service Provider, Reseller and the end-customer. A customer's brand can be configured to:
· A specific URL (host header)
· The user's login name (i.e. the brand will become effective when the user logs into Cortex)
· or inherit the parent customer's brand settings
To be able to access the Brand Management pages, the user must be attached to the Content Management Administrator security role. The first user that is automatically created when a new customer is
provisioned, will be configured with the Content Management Administrator role.
A customer will inherit all brands that have been saved in the higher hierarchy (by the Reseller / Service Provider). These are called System Brands. The customer can create it's own brands, these are called Customer Brands (these will become system brands for any sub customers that are created).
The difference between a System Brand and a Customer Brand is that a customer id is attached to each Customer Brand.
2.1.1.1 Managing Customer Brands
The Brand Management tool consists of two tabs; "Brands" & "Customer Settings", that the Reseller & Customer can use to manage their brands. Click here to find out how to set up a customer with permissions to add a url brand.
To access the Brand Management screens, select Operational Support from the Cortex Menu Bar and select "Brand Managment". There are two web pages available to support the configuration of individuals brands onto Cortex:
· Brands: allows the user to create new and update existing brands
· Customer Brand: allows the user to configure the branding for a specific customer
·
This page displays the available system brands that can be applied to the customer and allows the administrator to create a new customer brand(s). The system brands are read only and can only be changed by the content administrator for the customer that is linked to the brand.
To view where a Brand is being used, click on "In Use". Below the System Brands Table, a list of Customers and URL's that are attached to the Brand will appear.
1. To create a new Brand, select "New Brand".
2. Enter a Brand Code (a short reference code that is unique). 3. Enter a Brand Name. This can be more descriptive.
4. Browse and add the location for the defined css file that will be configured to the template. If no stylesheet is associated with a Brand then the default stylesheet will be used.
5. Browse and add the location for the Top Logo image that will be configured to the template. The Top Logo will appear as the banner image across the system pages. It must be in GIF format, with a maximum size of 592 x 52 pixels.
Cortex will allow a template to be created without a top logo. When editing the template, a warning message will appear advising that the "Image not uploaded"
6. Add the textual content for the Title heading that will appear on the Login page (only effective if brand is configured to URL)
7. Add the textual content for the Login Page such as instructions on how to log-in onto the system (only effective if brand is configured to URL)
8. Add the textual content for the Home Page, this is the default page that appears after the user has logged onto the system. Information regarding latest news, system status and availability can be added here
Customer Brands table. The Brand Code has been updated with the customer's numeric id.
Example: Brand Code "Brand May 2008" will appear as "Brand_May_200810" where 10 is the customer's numeric id
The "Customer Brand" web page
This page allows the Customer to define how the brand will be applied to the customer's users. This can also be set when adding a new customer to the control panel.
There are three options available:
URL (set as default setting)
The brand applied to the customer will be dependent on URL that the user enters. When a brand is linked to a URL, both the Login Page and Home Page will be branded in the appropriate brand.
Customers can be set up with additional permissions so that they can create their own URL and assign an appropriate brand. Click here to find out how to apply these additional permissions.
Default
The default setting inherits the branding settings that have been set higher up in the customer's hierarchy i.e) the customer will inherit its Reseller's branding.
Reseller A has been configured with a Custom Brand of "Brand Y". This means when any user of Reseller A logs onto the system, they will see "Brand Y's" top logo and style sheet.
A sub customer of Reseller A, Customer B is configured with "Default" and will inherit Reseller A's permissions. Therefore all users of Customer B will see "Brand Y's" top log and style sheet when they log on the system.
Custom
The Custom option, determines the brand that the customer user's will view after they have logged onto the system. This setting will override any brand setting that has been configured to the URL.
1. Select the relevant option, if "Custom" is selected, choose the brand that will be displayed when the user is logged onto the interface.
2. Select "Update" to save the changes. This changes will take immediate effect.
2.1.1.2 Stylesheet Management
The following section describes the process of creating a basic Cortex theme.
Cortex uses stylesheets to control brands. All elements are defined in the top level Cortex.css. Using inheritance, a customized brand can be defined to override the elements in the base stylesheet.
For example, if .pageTitle is defined in the top level Cortex.css as shown below, we could change the font colour from Green to Orange by updating the color attribute of the stylesheet element.
01 Headings
The main page headings.
.heading1, .heading2, .heading3, .heading3box, .pageTitle {
color: Blue; }
02 Page Title
The sub-heading under the main page heading.
.pageSubTitle {
color: Navy; }
03 Rounded Sidebox
The rounded sidebar boxes.topleft, topright, bottomleft, .boxAlt-bottomright, .boxAlt-inside
{
background-color: Orange; }
The main image displaying the service provider's logo. The hightlighted text is the name of the brand. For example, if we upload a top logo image for brand "MyBrand" then the background image location should be "/CortexDotNet/pics/toplogoMyBrand.jpg" or .gif depending on the image format.
.top_banner {
background-image:url('/CortexDotNet/pics/toplogoGreen.jpg'); }
05 Menu Hover
Specify the background and text colour when the user hovers over a menu item.
A.MainMenuHover, A.MainMenuHover:link, A.MainMenuHover:active, A. MainMenuHover:hover, A.MainMenuHover:visited, .MainMenuHover {
background-color: Green; color: White;
}
06 Menu Item
Specify the attributes for menu items.
.MainMenu, .MainMenuHover, .MainMenuStyle {
background-color: White; }
07 Page Background
Cortex allows administratros to upload a background image for their site. The highlightest text is hte name of the brand. In the sample, we have added a background colour to smooth out the gradient background image. .pageBackground { background-image: url('/CortexDotNet/pics/bg_Green.jpg'); background-color: Green; }
08 Logged in User
The logged in user label indicates which user is currently logged into the system.
A.loginlabel, A.loginlabel:link, A.loginlabel:active, A.loginlabel:hover , A.loginlabel:visited, .loginlabel
color: White; }
Expandable Table Elements
09 Row
An information row in the expand table.
td.rowA {
background-color: #e9f6dd; }
10 Alternate Row
An alternate row in the expand table. Make suble changes to the background colour for the best effect.
td.rowAalt {
background-color: #f4fdec; }
11 Expand Row
The cell that will expand when a user click's on an information row.
td.rowB, td.rowBE {
background-color: #e9f6dd; }
12 Alt Expand Row
The alternative cell that will expand when a user click's on an information row.
td.rowBEAlt {
background-color: #f4fdec; }
13 Highlight Row
The current expanded cell after a user clicked on an information row.
background-color: #c9e9aa; }
14 Expand Frame
The frame around the expanded information cell.
td.frame {
border:3px solid #abd285; }
15 Expand Table
The header and footer of the expand table.
.tableheading2, .tableheading2tl, .tableheading2tr, .tableheading2bl, . tableheading2br, .tableheading2spacer { background-color: #57a055; color: White; }
2.1.2
Email Notifications
The Email Notification screen allows Service Providers, Resellers and customers to set up and configure email templates that are triggered and sent out automatically when a specific event takes place on Cortex.
For Example:
A new customer is saved on Cortex. A provisioning request will be created and trigger the "New Customer Information Welcome Email" to be sent to the Customer's primary contact's email address.
Email Notification templates can be overridden throughout the customer hierarchy. If a template exists at a Reseller Level, this template will be sent to all of the Reseller's sub customers. If no templates exist, Cortex will send out the default template that is configured at the Service Provider level.
The screen is accessed via the Main Cortex Menu Bar, by selecting Operational Support >> Email Notification.
Search Filter
The Search Filter allows the end-user to filter the results in the email notification table. By selecting a value one of the drop down lists will refresh the table and only display the email templates that have the specified filter as one of its attributes.
· Event - This is the provisioning action that will trigger the email to be sent, E.g.) User Provision; User Service Provision
· Recipient - This is target audience of the email. There are four types of recipients: Service Provider / Reseller / Customer / User.
· Service - This option will list all templates that have been configured to the specific service.
Customer Management
The Customer Management sub menu allows the Service Provider and Reseller Administrators to manage email notifications for themselves and their sub customers, Use the Customer Search feature to find a customer. The screen will be updated with email notifications that have been configured to the specified customer. If no email templates have been configured, the screen will be blank and the customer's users will be receiving email templates that have been configured higher up in the customer hierarchy.
Create a New Email Template
1. Under the sub menu "Create Messages" select the type(s) for the new email:
Event - The Event is the trigger that will send the email. The drop down list includes events such as Customer Provision, Customer Service Provision & User Provision. A new email template must be attached to an event
a recipient
Service - This is an optional attribute and allows the Service Provider to create specific service emails when provisioning a service to a customer/user. The content of the emails can vary between the services that have been provisioned.
2. Select "New Message". The screen will refresh and the detailed Email Content iframe will be displayed.
3. To enable the email template, check the Enabled box for "Status".
4. The frequency property determines how often the email should be sent to the recipient for the same event. If the property is not checked for "Sent Once", every time the object (user) is re-provisioned, the email template will be sent to the recipient. When "Sent Once" is checked, the email will only be sent out on the first event trigger.
5. The Modification property allows the Service Provider to control whether it's sub customer's can update the email content. This feature is not available until 8.2 release.
6. The Recipients section allows the Service Provider to define who will be receiving the email and where the email will be sent from.
For properties "To", "CC" and "BCC", there are five types of recipients that can be configured for the template. More than one recipient type can be configured for an email template.
Custom - The Custom type allows the Service Provider to add a customized email address or a common pattern that uses key system properties. For example {UserExternalEmail} will send the email to the value that was specified in the user's External Email Address property.
User - The User type will allow the Administrator to select a user name that is active within the Administrator's customer. For version 8.1, this will always be the users that are saved at the Root Customer level. Release 8.2 will allow Resellers to create and manage email templates.
Customer - This type allows the Service Provider to select a specific Customer's contact person. Enter the Customer Name and when "Add" is selected, the customer's contact person's details will be populated beside the Customer Name.
Role - The Role type allows the Service Provider to add a role as a recipient. All of the customer's users that are attached to the selected role will receive the email
Reseller Role - This role type differs to the role type as the email will be sent to the customer's reseller's role. For example, if the Service Provider
7. Enter a "From Address" The user of this email address will be notified when emails have failed to be sent to the recipients.
Address" value
.
9. Select the "Language" from the drop down list that is required for the email. 10.Insert a email title in the "Subject" field.
11.Enable any attachments that are to attached to the email. The listed attachments are added to the system via the Attachments screen.
12.Add the detailed content for the email, using the rich text editor. Specific data values that are captured when a transaction is processed can be inserted into the template using {} brackets. Refer to the table below for common parameters that can be inserted into email templates.
13.Select the relevant Message Type.
14.Select "Save" to save the changes to the email template
Common Email Template Parameters
Parameter
Description
{CustomerShortName} Customer Code
{PrimaryDomain} Primary Customer Domain
{ServiceAccessLevels} Service Access Level System Name (This may differ to the Service Access Level's Display Name).
{ServiceLabel} Name of the Service {ServicePackage}
(MailBoxDiskLimit)
Total Mail disk space allocated to the customer (KB) {ServicePackage}
(PublicFolderPostLimit}
Total Public Folder disk space allocated to the customer (KB) {ServicePackage}
(SalesPrice)
Sales price for the service package {ServicePackage}
(StockCode)
Stock Code for the service package {ServiceProperties}
(InboxLimit)
User's mailbox limit (KB) {ServiceProperties}(OWA
URL)
URL for logging onto Exchange 2003 OWA {ServiceProperties}(OWA
URL 2007)
URL for logging onto Exchange 2007 OWA {ServiceProperties}
(SalesPrice)
Sales price for the Service Access Level {ServiceProperties}
(StockCode)
Stock Code for the Service Access Level {UserEmail} User's email address
(Userfullname} User Display Name
{Username} User's SamAccount Name
3
Customer Management
Customers can be viewed using the Customer Management icon on the Cortex Menu Bar. This icon is available to Service Provider Administrators, Reseller Full Administrators and Reseller Partial Administrators. The Reseller Partial Administrator will have limited access to some of the features.
The Service Provider and Reseller Customers can complete several customer-related functions from this icon including:
· Create a new Customer
· View all customers via i) a customer table
ii) a customer hierarchy structure
· Edit a Customer's properties
· Export all customer information to a Microsoft Excel spreadsheet
· Disable a Customer and it's users
3.1
Create a New Customer
1. Select the "Customer Management" icon from the Cortex Menu Bar and menu option "New Customer". Alternatively, select "New Customer" from the Customers web page.
2. Under the sub-heading "Customer Details", if more than one Location has been configured to Cortex, the property "Location" will appear. Select the required location that the customer will be attached to. The customer's location cannot be changed after it has been saved.
3. Add the Customer's Full Name.
The user interface will auto generate a customer short code. This code can be manually overridden before the customer is saved.
4. Add a Contact Name for the customer. 5. Add the Contact's Email Address.
"Address" - Enter the Customer's address.
"Phone Number" - Enter the Customer's Phone Number. "Fax Number" - Enter the Customer's Fax Number.
"Billing Identifier" - Enter a unique identifier for the customer that can be used to link back to a billing system.
"Prepay Customer" - The property determines the payment method that will be applied to the customer. A Pre-pay customer is typically a customer who will sign up to a service via a web shop and pay up front for the services that they will be using in the following month. A Post-pay customer will be charged at the end of a defined period for the actual usage that they have utilized.
A Pre-pay customer's payment method can be changed to post-pay. However a Post-pay customer cannot be changed to Pre-pay.
"Language" - If multiple languages have been configured on Cortex, the language field will appear and the customer can be configured to a specific language. All new users will be associated with the configured language, for example: if a email template has been configured to the selected language, the end user will receive this version of the template and not the default template.
"Minimum Password Length" - For each individual Customer the minimum password length can be defined.
The property will be automatically populated with the Active Directory's Group Security Policy setting. The property can be updated as long as the amended value is greater than than the default Active Directory value.
"Password Banner Display Days" - This is used to determine the point at which a reminder will be displayed to a User that their password is due to expire. The Password Banner will be displayed on the user's Home Page.
"Customer OU" - Select the Customer Organization Unit that the new Customer and all of its properties will be saved under in the Active Directory.
7. Under the sub heading "Domains", add the Customer's domain.
8. Optional, click on the Advanced Properties drop down arrow, to change the miscellaneous, non-mandatory settings for the customer:
"Change Password at next logon" - If enabled all of the customer's users will be prompted to create a new password when logging onto Cortex for the first time.
"Header Display Name" - This property determines whether or not the full Customer Name or the abbreviated Customer Name is displayed in the header (top right hand corner)of the Cortex page when the user is logged onto Cortex.
"Allow passwords to Never Expire" - If enabled, the Customer's User Administrator will have the ability to set user password to never expire.
"Organizational Structure" - If selected, Department or/and Location organizational nits (OU's) will be created under the User Structure OU. Users will be grouped under these OU's depending on their individual department and location settings.
"Brand" - This property configures the brand that the customer's users will view whilst accessing the control panel. There are three options available:
· URL (set as the default setting)
The brand applied to the customer will be dependent on URL that the user enters. When a brand is linked to a URL, both the Login Page and Home Page will be branded in the appropriate brand.
· Default
The default setting inherits the branding settings that have been set higher up in the customer's hierarchy i.e) the customer will inherit its Reseller's branding.
Example:
Reseller A has been configured with a Custom Brand of "Brand Y". This means when any user
of Reseller A logs onto the system, they will see "Brand Y's" top logo and style sheet.
A sub customer of Reseller A, Customer B is configured with "Default" and will inherit Reseller
A's permissions. Therefore all users of Customer B will see "Brand Y's" top log and style sheet
when they log on the system.
· Custom
The Custom option, determines the brand that the customer user's will view after they have logged onto the system. This setting will override any brand setting that has been configured to the URL.
"Demo Customer" - If yes is selected, the system will regard this customer as a trial customer account and an expiry date for the account must be specified. By default the system will set the trial period for one calendar month. When that date is met, the Control Panel will automatically de-provision the customer. The customer will be deleted from the system after the retention period has exceeded. Different email notifications can be sent to these trial customer accounts.
"Restricted Roles" - Security roles can be restricted at customer level. Restricting a role will prevent the role from being assigned to any user that is attached to the customer.
"Allowed Roles" - Security roles can be applied to specific customers. Enabling a role will allow a Customer User Administrator to assign the role to one of their users. This property can also be applied to Resellers, if a role is enabled, the Reseller can add this role to its sub-customers.
9. Select "Provision" to save the customer on Cortex. The user interface will navigate to the New User Wizard so that first administrator can be entered on to the system.
Note:
The User Details section may differ to the example in the Help User Guide. This is due to the configurations that have been set at Service Provider level on how a user-id is generated.
10.Add the user's UPN, inputting the user name and selecting a domain from the drop down list.
11.Cortex will auto populated the "Username". The value can be manually overridden before the user is saved to the customer.
12.The "First Names" and "Last Name" properties will be populated with the Contact Person's details that were inputted on the Customer page. These values can be overwritten. The "Display Name" will be automatically populated with these values and can be manually overridden.
13.Select "Additional User Properties" to add non mandatory user information.
The property "External Email" will be populated with the Contact Person's email address that was inputted on the Customer page.
14.Enter a Password and re-enter the password again to verify.
16.Under "Advanced Options", all available security roles will be enabled as this user is the customer's first Administrator.
17.Optional, expand "Email Addresses" section to add an email address for the user. If no email address is added, Cortex will add the UPN as a default.
18.Select "Provision" to save the user to the customer. The user interface will navigate the end user to the Customer Services screen where the specific services can be configured to the customer. Please refer to the Customer Services Management Section for configuration of customer services.
3.2
Create a Reseller Customer
Any customer can be amended to Reseller Customer status, by adding the Reseller Service to the customer's existing services.
The Reseller Customer must have the Reseller service provisioned to it before it can create and manage it's own sub-customers. The Reseller Service defines what services the Reseller Customer can sell to its sub customers, whether the customer can manage its own url.
Cortex allows services to be configured differently for each Reseller. This flexibility allows you to retain as much control over a Reseller as you wish. You can also control which resources a Reseller can use and limit how much resource they are allowed to sell.
Reseller settings are configured when provisioning the Reseller Service to a Customer. Each individual Service can be expanded and modified for the Reseller at this point.
The following items can be configured for each Service:
Service Name:
· Rename the Service; e.g. Hosted Exchange could be changed to Advanced Email.
Service Access Levels:
· User Level templates for the Service.
· Enabled or disable for an individual Reseller.
· Rename the Service Access Level.
· Override settings associated with the Service Access Level.
Packages:
· Service Templates that are used to define Service Settings.
· Rename the Service Access Level.
· Override settings associated with the Service Access Level.
Resource Limit:
· Set Any resources associated with a Service, for example Disk Space.
Service Settings:
· Any specific parameters associated with a Service, for example the name.
Add the Reseller Service to a Customer
2. Select the newly created Reseller Customer. 3. Select Services.
4. Select the "Reseller" service to expand the service' properties. If Cortex is installed with multiple locations, a reseller service will appear for each location. A Reseller Customer can be configured to multiple reseller services.
5. Enable the services that the Reseller Customer will be able to sell to it's sub customers.
6. Optional, select Advanced Settings and Service Settings to configure whether the sub-customers will have the ability to configure a brand to their own system generated url.
7. Select Provision to save the reseller service to the Reseller Customer.
Add the Reseller Administrator security role to a user
Once the Reseller service is provisioned to the customer, the list of available security roles will be updated with "Reseller Full Administrator" and "Reseller Partial Administrator". One of the reseller customer's users must be assigned with the Reseller Full Administrator role before a sub-customer can be created.
1. Select the User Management icon from the Cortex Menu Bar and select "Users". 2. Select the user that is to be updated with reseller permissions.
3. Select "Edit User".
4. Expand the Account Settings and select Advanced Options. 5. Enable the security role "Reseller - Reseller Full Administrator".
6. Select "Provision" to save the changes.
7. The user can now create and manage sub-customers.
3.3
Customer Hierarchy Screen
The Customer Hierarchy screen allows you to view all of your customers. The screen has been enhanced so that you can navigate directly to the customer itself, one of its services or users. The provisioning status of each of the customer's objects is now displayed on the customer hierarchy screen.
A Reseller customer who has sub customers provisioned to it will be displayed in bold font and highlighted with yellow shading on the screen (this formatting can be changed by updating the Cortex stylesheet). Expand the Reseller customer to view its sub customers.
3.4
Customer Services Management
There are two types of customer services that can be provisioned to a customer:
· A standard service - where once provisioned the customer can provision their users to the service. The only exception would be if the service has been configured as a customer only service. If this was the case, the service would not be displayed on the User Services screen (e.g. DNS service)
· Multiple instances of a service - These services are marked with a yellow star on the Customer Services screen. These services allow the customer to have multiple instances of the same service (applies to web hosting, SharePoint and SQL hosting). Once an instance is provisioned, the customer can provision their users to that service instance.
Instance Names
For services that have multiple instances, the instance’s name is defined by:
· If Instance Name property is populated but no instance description has been added. The instance name that is displayed on the Customer Services table will equal the Name specified. This value cannot contain spaces or special characters.
· If the Instance Name and Description are both populated, the instance name displayed on the Customer Services table will be the description. The description property allows spaces and special characters.
For SharePoint, if the description is not present, the SharePoint’s url will appear on the Customer Services Table. When a description has been entered, the description will be displayed.
3.4.1
BlackBerry
The Cortex Control Panel offers a BlackBerry service that simplifies the BlackBerry user management processes.
To ensure that BlackBerry works successfully, the customer and user must be provisioned with the Hosted Exchange service before they are provisioned with the BlackBerry service.
Key Features of BlackBerry Service:
· All of BlackBerry's standard management tasks can be performed within the Cortex Control Panel.
· BlackBerry user provisioning can be delegated to the end-customer.
· The BlackBerry service is compatible with Exchange 2003 and Exchange 2007.
3.4.1.1 Add BlackBerry to a Reseller
1. Select the Customer Management icon from the Cortex Menu Bar and select "Customers". 2. Select the relevant Reseller Customer to view the customer functions and select "Services". 3. Select Reseller Service.
4. Enable the BlackBerry service and select BlackBerry service name to configure the details service properties.
5. Select the Service Access Levels that the Reseller can sell to it's sub customers. A BlackBerry Service Access Levels determines which BlackBerry server will be used to store the user’s BlackBerry account.
Cortex allows a user limit to be set against each service access level that the Reseller can sell. To add a limit for maximum number of users, select the required Service Access Level and add a value. 6. Select “Apply Changes” to save the changes to the Service Access Level.
7. Select “Apply Changes” to save configurations that have been made to the BlackBerry service. 8. Select “Provision”. The Reseller Customer is now able to provision BlackBerry to its sub-customers.
3.4.1.2 Add BlackBerry to a Customer
The customer must be provisioned with the Hosted Exchange service before the BlackBerry service can be configured and saved for the customer.
1. Select the Customer Management icon on the Cortex Menu Bar and select “Customer Services”. 2. Use the Customer Search function to display the available services for the impacted customer.
3. Select the BlackBerry service. If Hosted Exchange is not already provisioned to the customer, an error message will appear - ”The prerequisite service(s) must be provisioned”
4. Enable the Service Access Levels that the customer can use to provision BlackBerry to its users. The service access level will determine which BlackBerry server will be used to store the user’s account.
A limit on the number of users assigned to a Service Access Level can be defined.
To set the limit, select a Service Access Level, add the maximum number of users that can be provisioned to this access level. Select “Apply Changes” to save the changes made to the Service Access Level.
5. Specify, if required, the maximum number of users that can have access to BlackBerry service and whether the BlackBerry service is chargeable. All chargeable services will appear on the Customer Billing Reports.
6. Select “Provision”. The Customer will now be provisioned with the BlackBerry service.
3.4.2
BroadWorks
BroadWorks provisioning functionality supported in Cortex includes the ability to: · Associate Cortex Customers with BroadWorks Groups
· Provision New Users
· Provision Existing Users (and change passwords) · Provision Default Services and Service Packs to Users
· Deprovision Users (delete the User and assigned Services and Service Packs)
3.4.2.1 Add BroadWorks to a Reseller
Before a Reseller customer can sell BroadWorks to its sub customer, it needs to be configured to a BroadWorks Service Provider account by your Service Provider. If the reseller is not configured to an account, the “Unable to load the authorized BroadWorks services” error will appear.
1. Select the Reseller service on the Customer Services screen and enable the BroadWorks service. 2. Click on the Broadworks to configure the settings for the reseller.
3. Select Service Settings
4. Open up the Service Access Level, the services and service packs that have been configured on Broadworks for the Reseller to sell will appear under Authorized Services.
The resource limits for each feature are displayed:
Limit: The limit imposed on the number of users that can be configured to the feature in the reseller’s hierarchy
Allowed (Service Packs only): The maximum number of users that can be configured to the feature Usage (Service Packs only): the number of customers that have been assigned this feature for
provisioning to their end-users
Allocated (Services): The number of user accounts that have been authorised to the reseller's customer.
Packs (Services): The number of user accounts that have been assigned to a Service Group for provisioning
Select the features that by default will be provisioned to the all customer's users, if the feature has been authorized for the customer's BroadWorks group
5. Enable the Default Access level if you want this access level to be selected as the default when the user services screen appears.
6. Select Apply Changes to save the configurations to the service access level.
reseller customer. The reseller can now assign customers to BroadWorks Groups.
3.4.2.2 Add BroadWorks to a Customer
The customer should be assigned to a pre-defined BroadWorks Group that has been created in the BroadWorks Portal. The Broadworks Group should already been configured with its resource services (service packs and services) where the Broadworks Service Provider has authorized the services that are to be applied to the Group and set limits on each feature (the maximum number of users that can have this feature).
1. Select the BroadWorks service on the Customer Services screen.
2. Select one of the p BroadWorks Group that is to be associated to the customer account. Once a Group has been assigned to a customer, it cannot be assigned to another one.
3. Select "Advanced Settings" to define which BroadWorks will be provisioned by default when the user is provisioned with the service. The BroadWorks features are configurable in the service access levels. 4. Select the Service Access Level Name to display its properties. The property "Authorized Services" will
display all features that have been authorized for the selected BroadWorks Group. The feature's limits are also displayed:
Limit: The maximum number of users that can be allocated to the feature
Allowed:The total number of user accounts for the specific feature that the Reseller can sell to it's sub customers.
Usage: Actual number of users that have been assigned to the feature
Enable the property to override the settings that have been inherited from the Reseller's configuration. Services and service packs that are selected will be assigned to all of the customer's users during provisioning. The Customer Administrator will have access to this property and will be able to enable/disable the features on an individual user basis.
If a Limit has been met for a feature, any further users assigned to the service access level will provision successfully but will be assigned to the fully allocated feature in BroadWorks.
5. Select "Apply Changes" to save the changes to the Authorized Services property.
6. Optional, set the the maximum number of users that can be provisioned to the service via the portal and the billing status of this customer service.
7. Select Provision.
3.4.3
Citrix
Cortex eases the administration associated with operating a Hosted Citrix environment. The Cortex Citrix Service is designed primarily to allow Service Providers to delegate the end-user administration of Citrix Applications to their Customers.
Key benefits include:
·
· Enables Application Group based delivery; publishing new applications is as simple as adding the applications to appropriate applications groups and assigning them to Customers and Users.
· Flexibility to select pre-defined configured Security Account Groups or create new security account groups for application publishing.
· Supports Public and Private Applications, Application Groups and Resources.
· Setting of Applications, Application Groups, Resources to a default setting when provisioning Citrix to a Customer and Users.
· Ability to add and manage Resources to a Citrix Farm such as; - User Profile and Home Drives.
- Shared Drives – Allow Users to share information with other Users within their Customer. - Printers.
- Program files which are configured to run applications.
Citrix Applications:
·
· They can be assigned default Citrix Applications for Customer and Users.
Resources:
· User Profile and Home Drives.
· Shared Drives – Allow Users to share information with other Users within their Customer.
· Printers.
· Program files which are configured to run applications.
Application Groups:
· Here we can manage different application access to different group of Customers and there Users.
Configure Active Directory User Properties
Manage Citrix Delivered Applications
Cortex allows access to Citrix applications to be easily controlled through the standard Cortex Control Panel.
Key functions:
Function
Description
Assign applications to Customer Define which Citrix applications a Customer can use. Assign Resources to one or more Customers
and Resellers
Resource groups can be created and assigned to Customers for them to use.
3.4.3.1 Add Citrix to a Reseller
Note:
The Citrix Applications, Application Groups and Resources must be configured and enabled within Cortex by the Service Provider before they can be provisioned to a customer to resell.
How to Provision Citrix Service to a Reseller
1. Select the Customer Management icon on the Cortex Menu Bar and select menu option “Customer Services”.
2. Select the relevant Reseller Customer using the Customer Search function. 3. Select the “Reseller” Service.
4. Enable the “Citrix” service and select the Citrix service name to configure what applications, resources and groups that the Reseller can provision to it’s sub customers.
5. If more than one Server Collection has been configured to Cortex, select the Server Collection that you want to provision to the Reseller to sell from the drop down list.
More than one Server Collection can be added to a Reseller.
6. Enable or disable the applications, resources and application groups as required. Repeat this step for all server collections that the Reseller customer will be able to provision.
7. Leave Service Access Level "Full" enabled. This is the only service access level that is configured to the Citrix service.
8. Select “Apply Changes” to save the service settings.
3.4.3.2 Add Citrix to a Customer
Note: The Citrix Applications, Application Groups and Resources must be configured and enabled within Cortex and provisioned to the Reseller Customer before they can be provisioned to a Customer.
How to Provision Citrix Service to a Customer
1. Select the Customer Management icon on the Cortex Menu Bar and select menu option “Customer Services”.
2. Select the relevant Customer using the Customer Search function.
3. Select the “Citrix” service to configure the applications, resources and applications groups to the customer.
4. If the reseller customer is configured to provision multiple Server Collections, a “Server Collection” drop down list will appear. Select the Server Collection that the customer will be configured to. The screen will refresh, displaying the available objects.
A customer can only be provisioned to one Server Collection at a time.
5. Enable the Applications Groups, Applications and Resources that you want to assign to the Customer. Objects that have been configured as “Default” will be automatically selected.
The Access and Default settings and Full Description can be viewed when selecting the object’s expand icon.
6. Select “Provision”. The customer will now be configured with the selected applications, resources and groups.
3.4.4
CRM
3.4.4.1 CRM 3.0
Cortex supports CRM by adding and managing user profiles onto the system, including preserving an audit trail and historical information on CRM users.
Each CRM server has a defined number of user licenses. When all of the licences have been used, no additional users can be enabled. Disabling a user will free up a license.
3.4.4.1.1 Add CRM 3.0 Service to a Reseller
1. Select the Customer Management icon on the Cortex Menu Bar and select menu option “Customer Services”.
2. Select the relevant Reseller Customer using the Customer Search function. 3. Select the “Reseller” service.
4. Enable the “CRM” and select the CRM service name to configure the detailed service properties such as the CRM servers that the reseller can provision to it’s sub-customers.
5. Select “Service Settings”
6. Enable the property "CRM Servers" and select the CRM servers that the Reseller can provision. 7. Select “Apply Changes” to save the changes to the service settings.
8. Ensure Service Access Level "Full" is selected. This is the only service access level that is applicable to the CRM service.
9. Select “Provision”. The Reseller Customer is now able to provision CRM to its sub-customers.
3.4.4.1.2 Add CRM 3.0 Service to a Customer
1. Select the Customer Management icon on the Cortex Menu Bar and select menu option “Customer Services”.
2. Select the relevant Reseller Customer using the Customer Search function. 3. Select the CRM service to configure the customer’s service settings.
4. Select the server that will host the customer's CRM system.
This is the front-end server. This server will have been configured to a back-end SQL database during installation. The server cannot be changed after a customer is provisioned with CRM. This ensures that the customer's users are not provisioned across multiple CRM servers and consume unnecessary CRM user licences.
To change the server, the customer must be de-provisioned from the CRM service.
It is recommended that one customer is provisioned to one CRM server as CRM Version 3.0 does not offer complete isolation between multiple customers in a hosting environment.
5. If required, select “Advanced Settings” to specify the maximum number of users that can have access to CRM and whether the CRM service is chargeable and will appear on the Customer Billing Reports.
Note:
The maximum number of users field is not linked to CRM Licence Manager and the following error message will appear, if all CRM licences have been used when adding a new user:
"Failed to Create / Update User. The maximum number of user licences has been reached"
6. Select “Provision”. The Customer will now be provisioned with the CRM service.3.4.4.1.3 Limitations and know n errors
CRM Version 3.0 does not offer complete isolation between multiple
customers in a hosting environment:
As a result of the above issue, it is recommended that each customer must be provisioned to their own CRM server.
When provisioning a customer to CRM on Cortex, no logic is enforced to stop multiple CRM customers being provisioned to the same CRM server.
Sharing a CRM server between customers is ideal for corporate situations where an organisation consists of multiple Cortex managed customers. A new business unit can be created manually on the CRM server for each customer to provide user clustering.
3.4.4.2 CRM 4.0
Microsoft Dynamics CRM 4.0 continues to enhance the Customer Relationship Management experience. This product provides a tool which allows the customer to manage their customers in totality, from Marketing & Sales through to Customer Services.
The main difference between CRM and MS Dynamics CRM 4.0, is CRM 4.0's ability to manage multi-tenant architecture where multi organizations can be hosted on one CRM server but each organization's data remains confidential and restricted to only their assigned users. This improves operational costs from a Service Provider's perspective.
Other benefits that CRM 4.0 brings to the end user are:
· Improved user interface
· Data connections with MS Excel allowing users to analysis and evaluate the data using familiar excel tools
· Reports and work-flows can be created with minimum IT knowledge
3.4.4.2.1 Add CRM 4.0 Service to a Reseller
1. Select the Customer Management icon on the Cortex Menu Bar and select menu option “Customer Services”.
2. Select the relevant Reseller Customer using the Customer Search function. 3. Select the “Reseller” service.
4. Enable the “Customer Relationship Management 4” service and select the service name to configure the detailed service settings.
5. Enable the relevant packages that the Reseller Customer can sell. The service packages will determine what CRM 4 servers the Reseller can provision it’s sub customers to.
The packages will inherit configurations from Top & Active Directory Services. Click on the package to overwrite a property at Reseller level (this change will be effective for all of the Reseller’s sub customers' instances).
6. Select “Apply Changes” to save the changes for the package.
7. Ensure Service Access Level "Full" is selected. This is the only service access level that is applicable for CRM 4.
8. Select “Provision”. The Reseller Customer is now able to provision the CRM 4.0 to its sub-customers.
3.4.4.2.2 Add CRM 4.0 Service to a Customer
1. Select the Customer Management icon on the Cortex Menu Bar and select menu option “Customer Services”.
2. Select the relevant Customer using the Customer Search function.
3. Select the "Customer Relationship Management 4" service and enter an Instance Name. The Description field is optional. Select “Create”.
4. Select the service package that is to be provisioned to the customer. The CRM 4.0 service package will determine what CRM 4.0 server the customer’s database is saved on and how Cortex will set up the database. The type of package will determine what further service properties will need configuring (the user screen will be updated automatically) before provisioning the CRM 4.0 service to the customer. 5. If the package selected is configured by the Service Provider with the property "Create
Organizations" enabled
(recommended configuration), complete the following service configurations:Select the server that will host the customer's CRM 4.0 system. This is the front-end server. The back-end SQL server is configured within the package properties.
Select the required SQL Collation.
Select the required Currency Code (the base currency for the organization's installation). After the currency has been set it cannot be changed. Once the Currency Code is selected, Cortex will update the Currency Name and Symbol fields.
When the service is provisioned, Cortex will create a CRM organization for the customer on the CRM server. The organization's Name will be {CustomerLongName} {InstanceName}
