SharePoint v3.0 User Groups are not supported by Cortex 7.0. Users will be provisioned onto the SharePoint site with the defined SharePoint role. SharePoint Administrators can assign these users to User Groups after they have been assigned. If the User Group permissions differ to the user's original role permissions, these will not be displayed in Cortex.
If the user is removed from a SharePoint Role and/or User Group, a error message advising the user's status will not appear in Cortex. The user will still remain provisioned to the SharePoint site and can be reassigned to a role or group by using the search function.
This only applies for SharePoint v3.0.
3.4.13 SharePoint 2010
SharePoint 2010 (Foundation and Enterprise) is now supported in the Cortex Control Panel.
Customers are configured with a SharePoint Feature Pack(s) which determine the functionality that will be available to the site's end users.
The standard install of SharePoint 2010, includes 6 pre-configured service package templates. These package templates determine how the site will be configured and saved on the SharePoint 2010 server and their availability for selection is control by your Service Provider. They are:
· Customer Site
The site will be attached to a web application that is configured just for the customer. If further sites are configured with the same package, these sites will be assigned to the same web application. The site will have it's own content database.
· Customer Site (anonymous)
The settings are the same as the Customer Site but with anonymous authentication enabled.
· Shared Site
This site will be attached to a shared web application where other customer SharePoint sites will also be configured to. The site will have it's own content database.
· Shared Site (anonymous)
The settings are the same as the Shared Site but with anonymous authentication enabled.
· Dedicated Site
This site will be attached to it's own web application. No other SharePoint sites will be configured to this web application pool unless the web application is manually overridden with the web application's name. The site will have it's own content database.
· Dedicated Site (anonymous)
The settings are the same as the Dedicated Site but with anonymous authentication enabled.
3.4.13.1 Configure Resources (SharePoint Farms & Feature Packs)
At least one SharePoint Farm and Feature Pack must be configured to a customer, before a SharePoint site can be added to the customer's account. The configuration of these attributes is completed on the
Customer Services screen under the option "SharePoint 2010 configure resources".
A customer can be configured to multiple Farms and feature packs but can only be configured to one feature pack within a Sharepoint Farm at any point of time.
1. Navigate to the Customer Services screen and select "SharePoint 2010 - configure resources".
2. Click "Add" and select a SharePoint Farm from the drop down list. The Feature Pack column will be auto populated with all feature packs that are configured to the selected Farm. Select "Update" to save the configuration.
3. Repeat Step 2 if you want to configure further Farms and feature packs to the customer's account.
Select Save to save all configurations. A SharePoint 2010 site can now be provisioned to the customer.
3.4.13.2 Add a SharePoint 2010 Instance to a Customer
A SharePoint 2010 instance can only be provisioned to a customer after its resources have been configured and saved (SharePoint Farm & Feature Packs).
To add a SharePoint 2010 instance to a customer, navigate to the Customer Services screen and complete the following steps:
1. Select "SharePoint 2010 create an instance"
2. Add an instance name. This value cannot contain spaces or special characters. A description for the instance can also be entered; This is optional and if not completed, the site's instance name will be added to the description. The Description will appear on the User Services screen so should be meaningful to the end users.
3. Select "Create". The Control Panel will open a new window where specific configurations for the instance need to be entered.
4. Select the Package Template from which the site will inherit pre-defined service settings. To override an existing service setting, select "Edit", override the relevant property and click on "Apply Changes". The availability of service settings that are available for overwriting is determined by your Service Provider's configuration.
The SharePoint 2010 Package Template determines the size of the SharePoint site, whether anonymous authentication is enabled and the patterns that will be used to save the site's content database and web application. Pricing is also specified in the Package Template i.e. the unit cost of a specific site.
5. Add the Site Administrator. This user will have full Administration rights on the SharePoint site and must be a user that is present in the customer's organization unit. By entering the first few characters of a user name, the Control Panel will return all users that match the input criteria.
A second Site Administrator can also be configured to the site.
6. Select the SharePoint Farm (servers) that the site will be configured on.
7. Select the site template that will be configured to the site.
Depending on your Service Provider's configuration, one of the entries within the drop down list will be blank. If this is selected, no template will be configured to the site and the Site Administrator must log-on to the site to select the template and security groups manually before standard end users can log onto the site. This should not be confused with the template "Blank Site:" which is a predefined SharePoint template.
8. Enter the host header for the site.
9. Select Advanced Settings to define a) the maximum number of users that can be provisioned to the instance and b) whether the service will be billable.
10.Select Provision to save the instance. The site will now be provisioned on the SharePoint Farm. The provisioning process is a lengthy process and will take several minutes to complete.
Once the provisioning status turns green, the Administrator can access the site and users can be provisioned to the site using the Cortex Control Panel.
Once provisioned, the package template cannot be amended for the SharePoint instance.
3.4.14 User Sync
The User Sync service allows customers to synchronize their own localized Domain Controller to the Hosted Domain Controller. The customer's OU in the hosted Domain Controller will be regularly updated with any user changes that have been saved in the customer's domain controller. All hosted services that are provisioned to the users will be configured directly to the user objects that are saved in the hosted domain controller.
The service is a customer only service. Once provisioned to a customer, the customer's administrator will have access to download and configure the Cortex User Sync Tool to their existing Domain Controller.
There is one pre-requisite for the customer before downloading the user synch tool. The customer's account property "Allow Passwords to never Expire" is set to True. If this is set to false, errors will appear in the customer's Event Viewer and no users will appear on Cortex.
3.4.14.1 Add User Sync 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 "User Sync" service. There are no service properties to configure.
4. Select Provision. The customer's Administrator will now be able to download the Cortex User Sync Tool from the Cortex Control Panel.
3.4.14.2 Troubleshooting Customer issues with ADSync Tool
This section provides an overview of the possible issues that may arise after the ADSync Tool has been installed on a client’s remote domain controller(s).
Note: if the customer has multiple remote domain controllers, the following resolution should be applied to each instance where the ADSync tool has been installed