Leverage the Mobile Device Extension for ad rms

Deploying the database server

The SQL1 computer provides a SQL Server installation on a member server within litware369.com domain that will later host the AD RMS configuration and logging databases.

This section walks you through the deployment of SQL Server 2012 on the SQL1 computer with the following steps:

1. 
   Opening a remote desktop connection on the target computer.
   
2. 
   Adding the LITWARE369\AzureAdmin user as a SQL login and assign it sysadmin rights.
   
3. 
   Starting the SQL Server Browser service.
   
4. 
   Adding Windows Firewall exceptions for SQL Server ports.
   

The following subsections describe each of these steps in the context of our test lab environment.

Opening a remote desktop connection on the target computer

To open a remote desktop connection on the SQL1 computer, proceed as illustrated before with the DC1 computer but with the SQL1 computer instead. However, log on this time as SQL1\AzureAdmin with “pass@word1” as password. The local account SQL1\AzureAdmin sysadmin rights on the SQL Server instance.

Next, we will continue working on SQL1 using SQL Server Management Studio and other administrative tools to make some configuration changes to support SQL Server access before we install AD RMS later in this document. First, the LITWARE369\AzureAdmin account needs to be given sysadmin rights on the SQL Server instance in order to be able to create the AD RMS databases during AD RMS setup.

Adding the LITWARE369\AzureAdmin user as a SQL login and assign it sysadmin rights

To add the LITWARE369\AzureAdmin user as a SQL login and assign it sysadmin rights, proceed with the following steps:

1. 
   Open a remote desktop session as per previous section.
   
2. 
   Right-click the taskbar and select Task Manager.
   
3. 
   In Task Manager, from the File menu, select Run new task.
   

4. 
   Type in the following command to open SQL Server Management Studio and then click OK:
   

"C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe"

5. 
   SQL Server Management Studio launches. A Connect to Server dialog pops up.
   

6. 
   Click Connect to connect to the SQL Server instance on SQL1.
   
7. 
   In the console tree, expand SQL1, then expand Security, and then click Logins.
   
8. 
   Right-click and select New Login. A Login – New dialog pops up.
   

9. 
   For Login Name, click Search. A Select User or Group dialog pops up.
   

10. 
    In Enter the object name to select, type “LITWARE369\AzureAdmin” and then click Check Names. A Windows Security dialog pops up.
    

11. 
    Type “AzureAdmin” for the name of the account with “pass@word1” as password and click OK.
    

12. 
    Click OK.
    
13. 
    Back in Login - New, in the navigation pane, select Server Roles.
    

14. 
    In Server roles, check sysadmin.
    
15. 
    Click OK.
    
16. 
    Close SQL Server Management Studio.
    

Starting the SQL Server Browser service

To start the SQL Server Browser service, proceed with the following steps:

1. 
   While still being logged on to the SQL1 computer with the previous remote desktop session, in Task Manager, from the File menu, select Run new task, type in the following to open the Services console and then click OK:
   

Services.msc

2. 
   Scroll in the list of services and select SQL Server Browser.
   
3. 
   Right-click and select Properties. A SQL Server Browser Properties dialog pops up.
   

4. 
   In SQL Server Browser Properties, for Startup type, select Automatic and then click Apply.
   
5. 
   Click Start to start the SQL Server Browser service.
   
6. 
   Click OK and then close the Services console.
   

Adding Windows Firewall exceptions for SQL Server ports

To add Windows Firewall exceptions for SQL Server ports, while still being logged on to the SQL1 computer with the previous remote desktop session, open an elevated Windows PowerShell command prompt if none, and run the following command:
PS C:\Users\AzureAdmin.LITWARE369> New-NetFirewallRule -DisplayName "SQL Server" -Direction Inbound –Protocol TCP –LocalPort 1433-1434,5022 -Action allow

Name : {82a6cf85-72ef-4322-aa0d-50481e278878}

DisplayName : SQL Server

Description :

DisplayGroup :

Group :

Enabled : True

Profile : Any

Platform : {}

Direction : Inbound

Action : Allow

EdgeTraversalPolicy : Block

LooseSourceMapping : False

LocalOnlyMapping : False

Owner :

PrimaryStatus : OK

Status : The rule was parsed successfully from the store. (65536)

EnforcementStatus : NotApplicable

PolicyStoreSource : PersistentStore

PolicyStoreSourceType : Local

PS C:\Users\AzureAdmin.LITWARE369>

The forthcoming configuration of the AD RMS cluster can use Microsoft SQL Server 2012.