Chat now with support
Chat with Support

Metalogix Archive Manager for Exchange 8.1.1 - Advanced Installation Guide (with Exchange 2010)

Introduction Getting started Pre-installation tasks Installing Archive Manager for Exchange Post-installation tasks Addendum

Creating an MS SQL database with a database user

 

When planning to install Archive Manager, an empty database(s) and an appropriate database user must be created before running the setup. The database providers supported by Archive Manager are MS SQL Server 2008 and higher and Oracle 11g, 12c and 18c.

NOTE: This section guides you through the configuration of SQL Server 2012 and creation of a database with a database user. In case of SQL 2008 you can use the “SQL Server 2008 Configuration for Archive Manager” guide.

To configure your SQL Server 2012:

1.Open the SQL Server Configuration Manager and click the SQL Server Services node. Both the SQL Server (SERVERNAME) and the SQL Server Browser services have to run.

Snap1-DB

 

2.If the SQL Server Browser service is not started and the Start option available in its context menu, it means that this service is disabled. To enable the service, right-click it and from the context menu select Properties.

Snap2-DB

 

3.The Properties window opens. Switch over to the Service tab and change the Start Mode from Disabled to Manual. Conclude by clicking Apply and OK and then try to start the service again.

Snap3-DB

 

4.In the SQL Server Configuration Manager expand the SQL Server Network Configuration node from the navigation tree. On the Protocols for SQL node you need to enable the Named Pipes, the Shared Memory and the TCP/IP protocols.

Snap4-DB

 

5.Instead of enabling the TCP/IP using the context menu, we recommend opening its Properties window. This window has two tabs, Protocol and IP Addresses. On the Protocol tab set the Enabled to Yes.

Snap5-DB

6.On the IP Addresses tab you will see several sections - one for each network connection and a local loopback connection indicated by the standard address of 127.0.0.1 For remote access to the SQL Server Express 2012 instance the loopback connection is of no interest.

For the desired network connection the Active option should say Yes as should the Enabled option. The IP address will probably be filled in for you (by Windows) and will be different on your machine.

Snap6-DB

If you wish to enable dynamic ports for your SQL Server Express 2012 instance then the TCP Dynamic Ports option should be 0. To disable this option and use a fixed port change this field to a blank value and fill in the port on the TCP Port option. Disabling dynamic ports is non standard for named instances and should really only be done if you know exactly what you are doing and why you want to do it.

Conclude by clicking Apply and then OK.

Snap7-DB

 

7.For the changes to take effect you need to restart both the SQL Server (SERVERNAME) and SQL Server Browser services have to be restarted switching over to the SQL Server Services node.

8.Check the Shared Memory, the TCP/IP and the Named Pipes client protocols on the SQL Native Client Configuration node in the SQL Server Configuration Manager too. They should all be enabled.

Snap8-DB

 

Furthermore you will need to create an empty database and a database user for your Archive Manager. To do so:

1.Connect to your SQL Server 2012 with the Microsoft SQL Server Management Studio, then expand its tree and right-click on the Databases node. From the context menu choose to create a new database.

2.In the New Database dialog, give the new database a name (e.g. exchangeDB) and you can leave the owner to be the <default>. This owner will be changed later on, when you will create a new login with table owner rights over the database you are creating. You can also choose to change the default location for the Data file and Log file, if needed. Finish by clicking OK.

Snap9-DB

 

3.To create the Table Owner for the exchangeDB database you will need to create a new login, a new scheme and a new user as well. We will name each of them “srv_exchange”.

To create a new login, expand the tree of the MS SQL Server Management Studio tool and right-click on the Security tab and choose New/Login.

4.The new dialog opens. Before proceeding further on the General tab decide on the type of authentication to be used:

Windows authentication - the user (e.g. “srv_exchange”) must already exist in the Active Directory. Use the Search button to find your desired user in AD. It can be your Archive Manager super-user as is described in the section “Creating a super-user account”.

SQL authentication – specify the login name (“srv_exchange” in our example). Make sure to uncheck the Enforce password policy check box.

Snap10-DB

As for the Default database, select the exchangeDB database and set the Default language to be English.

 

5.Once this is done, you can switch over to the User Mapping tab. Here map to the exchangeDB database a user (it will be automatically created and named with the same name as the login) and select also the db_owner and public membership role for the exchangeDB database.

Snap11-DB

 

6.Switching over to the Status tab. Make sure that the Permission to connect to database engine is granted and also that the Login is enabled. Conclude by clicking OK.

Snap12-DB

 

7.Next you will need to create a schema for your new database login. To do so, expand the tree on the new created database (exchangeDB) in the Microsoft SQL Server Management Studio tool down to Security/Schemas. Right-click on Schemas and choose New Schema from the context menu.

In the New schema dialog just give a name to the schema you want to create (e.g. srv_exchange) and click the Browse button to select the schema owner. Select the schema owner to be the previous user you have specified in step 4 (srv_exchange). Click OK.

Snap13-DB

 

8.Furthermore you will need to assign the new created schema to your new database user. The new database user (srv_exchange) was automatically created when creating the new login and mapping a user to the exchangeDB database.

To locate this new user, expand the tree of the exchangeDB database in the MS SQL Server Management Studio tool down to Security/Users.

By clicking on the Users node you will see the user called srv_exchange on the right pane of the tool. Double-click on it to open its Properties window.

A new dialog opens on the General tab. Click the browse button next to the Default Schema text box and select the previously created user “srv_exchange”.

Snap14-DB

 

9.Switch to Owned Schemas node where you will see that the one called srv_exchange is selected. Make sure that the db_owner is selected too.

Now switch to the Membership node and make sure that db_owner is selected here, too. Save the changes you have made by clicking OK.

Snap15-DB

 

Metalogix makes every effort to perform comprehensive testing but cannot guarantee, due to environmental differences, that all functions will work in every environment. It is always recommended that testing be conducted within your own environment to confirm functionality and compatibility.

Organizational Forms Library troubleshooting

Sometimes the Organizational Forms Library may not be accessible in Outlook after Archive Manager installation. This error may occur if there are too many mailboxes with full access permission for the given user and as a result, Public Folders become inaccessible. To handle this error, use the following workaroud:

a.        Close Outlook

b.        Run Exchange Management Shell

c.        Execute the thefollowing command where #USERALIAS is alias  for given user and #USEREMAIL isthe email address of the given user:

Get-Mailbox -ResultSize unlimited -Filter {(RecipientTypeDetails -eq 'UserMailbox') -and (Alias -ne '#USERALIAS')} | Remove-MailboxPermission -User #USEREMAIL -AccessRights fullaccess -InheritanceType all

d.        Open Outlook with profile of the given user. Now Organizational Forms Library should be accessible and you may complete required operations

e.        (Optional, if required) Open Exchange Management Shell and execute the following command to give full access permissions to all mailboxes for the given user where same notation is used as in point c:

Get-Mailbox -ResultSize unlimited -Filter {(RecipientTypeDetails -eq 'UserMailbox') -and (Alias -ne '#USERALIAS')} | Add-MailboxPermission -User #USEREMAIL -AccessRights fullaccess -InheritanceType all

Related Documents