Microsoft Exchange Server is a widely adopted mail server, contact manager and calendaring software. Although in recent years many companies preferred to migrate their email management to public cloud services like Office 365 or Google+, a large market segment still prefers to manage email mailboxes directly, often in a private cloud. Our Exchange charms provides all the benefits of both worlds: the ease of management of public clouds along with the privacy offered by a private cloud, including transparent scalability with Data Availability Groups (DAG) on multiple nodes.
juju deploy exchange
juju add-relation exchange active-directory
If the deployment is set to “ClientAccess”, only the Client Access role will be deployed on that unit. This deployment type supports scaling using the NLB(Network Load Balancer).
If the deployment is set to “Mailbox”, only the Mailbox role will be installed. This deployment type supports scaling using DAG(Database Availability Groups).
|The path for the Exchange ISO file. It can be an URL or an SMB share path.
|Database Availability Group static IP.
|Network Load Balancer static IP.
If CAS deployment type is used, this will be the IP for the network load
balancer. For example, if there is only one CAS, this IP will be
associated to its network card, as a second IP.
|Exchange Outlook Web Access name
|Exchange product key. If empty string, the key registration will not be performed
|Exchange database name
|Exchange organization name
|Exchange deployment type. Can be:
– ClientAccess, Mailbox: It will deploy all the Exchange roles on
a single machine. This type of deployment does not support scaling.
– Mailbox: It will deploy only the mailbox role.
Every other unit will become part of a Database Availability Group(DAG).
A separate network card is required for this deployment type,
through which data replication will be performed.
– ClientAccess: It will deploy a Client Access Server.
Every other unit will become part of a CAS Array.
A fixed IP is required for this deployment type.
To have a working Exchange deployment, either of the following are required:
– A single ClientAccess & Mailbox node
– At least one Mailbox node and one ClientAccess node
|The identity of the Database Availability Group.
Please fill out the form below for pricing information and for a free trial: