- Configure PowerShell virtual directory on at least one Exchange Server with the following:
a) Set the RequireSSL to false.
b) Use https for PowerShell URL.
c) Do not use same URL for Internal and External PowerShell URLs.
d) Authentication method (internal/external) should be "Ntlm, WindowsIntegrated"
You can use below command for quick global a) and d) configuration:
get-powershellvirtualdirectory | Set-PowerShellVirtualDirectory -WindowsAuthentication $true -RequireSSL $false
- Ensure that you have Public Folder Master hierarchy. This article will help you (works for both Exchange 2013 and 2016).
- Ensure that you have at least 1 mounted healthy Mailbox Database.
- Ensure that your Exchange environment is healthy and error-free.
- Go through the Hosted Organization module configuration.
- Go through the Deployment Guide.
- Perform installation only on Exchange Server machine (CAS or MBX for E2013, CAS for E2016).
- On step 4 choose just Server
- On step 6 ensure that you create user in Active Directory and not the local one.
- Skip steps 8-13 and 17-22.
- Ensure that newly created User (the one from step 6 of deployment guide) added to Organization Management, Server Management, Recipient Management, and Help Desk security groups in Active Directory.
- Ensure that mentioned user enabled for remote PowerShell. This command will help you with the configuration: Set-User MSPControl-Server-User -RemotePowerShellEnabled $True (usually it's ok by default)
- Go to MSPControl Portal > Settings > Servers and add your new server with password from step 7 of deployment guide. Leave Search Installed Software unchecked.
- Go to added server, expand Active Directory Settings and setup it like on picture below.
Security Mode: Create Active Directory Accounts
Authentication Type: none
Root domain: <your active directory domain> (expert.local in our example)
Username and password are not required.
- Click Update button on the bottom of this page
- Go back to Server and click Add button near Hosted Exchange:
- Choose required Hosted Exchange Server Service provider. In this article we configure Exchange 2013 or 2016 – process is the same for both. Click Add Service.
- Provide PowerShell URL and Database Availability Group name as on the picture below. Click Update
- Use only https for PowerShell URL
- We support 3 targets for Mailbox creation:
- Whole Exchange environment: MSPControl will use all Mailbox Databases in your Exchange environment across all Database Availability Groups.
Format: blank. Just leave a Database Availability Group field empty.
- Database Availability Group: MSPControl will use all Mailbox Databases within provided Database Availability Group.
Format: <Database Availability Group name> (like on our picture: DAG01)
- Mailbox Database: MSPControl will use only one Mailbox Database.
Format: <Database Availability Group name>\<Mailbox Database name> (example: DAG01\HostedDB01)
Done! Now you can add this service to your Virtual Server, select Hosted Exchange in Hosting Plan and start making your Exchange stuff (mailboxes, distribution groups, contacts, public folders etc).