New Functionality of AD-RMS in Windows Server 2012
Hello Friends, I am back with one of my article on AD-RMS enhancements in Windows Server 2012. I hope you like my articles, so I request you kindly subscribe my blog and leave your valuable comments so I can improve required changes in my new articles.
Microsoft made significant changes to AD RMS in Windows Server 2012. These changes included an updated set of SQL Server requirements, Server Core support, a remote deployment option and an option to deploy with powershell commands.
For Windows Server 2012, AD RMS now has the following requirements for access to SQL Server.
- The AD RMS installer account must have sysadmin permissions in the SQL Server installation.
- The SQL Server Browser service must be running to locate available SQL instances.
- Firewall exceptions should be enabled on the SQL server computer for ports that will be used by AD RMS setup. The TCP port for the SQL instance that will host the AD RMS databases should be enabled. The UDP port for the SQL Server Browser service should also be enabled. For example, the default ports are usually TCP port 1433 for the SQL Server instance and UDP port 1434 for the SQL Server Browser service.
In addition to the previous access requirements, for Windows Server 2012 the following versions of Microsoft SQL Server have been tested and are supported for use with AD RMS deployment.
- SQL Server 2005 Service Pack 3
- SQL Server 2008 Service Pack 3
- SQL Server 2008 R2 Service Pack 1
- SQL Server 2012
In previous releases, AD RMS Setup supported only deployment at the same server computer where AD RMS was to be installed. Based on customer feedback, this has been changed. For Windows Server 2012, AD RMS now supports remote deployment at targeted server computers. In previous releases, AD RMS Setup supported only deployment at the same server computer where AD RMS was to be installed. Based on customer feedback, this has been changed. For Windows Server 2012, AD RMS now supports remote deployment at targeted server computers.
For Windows Server 2012, Server Manager has been redesigned to provide support for remote deployment of AD RMS as part of a two-step process that can be summarized as follows:
- Launch the Add Roles and Features Wizard in Server Manager to add the AD RMS role. This will add and install the files necessary for AD RMS.
- After adding the AD RMS role, launch the AD RMS Configuration wizard to select deployment options and configure the AD RMS cluster.
When the AD RMS configuration wizard first launches, if you are installing AD RMS on a remote server you will be prompted for the credentials needed to complete AD RMS configuration.
The requirements for selecting the credentials that you enter here are as follows:
- The account used to deploy AD RMS must have membership in the local Administrators group on the server computer where you are installing and configuring AD RMS.
- The account used must also have sysadmin permissions on the server that hosts the configuration database for the AD RMS cluster.
AD RMS now supports mobile devices when you install and configure AD-RMS mobile device extention, like for MAC computers
AD RMS fails to install if multiple installations are active simultaneously in Server Manager
In previous releases of AD RMS included with Windows Server® 2008 and Windows Server® 2008 R2 it was not possible to launch more than a single instance of the AD RMS Configuration wizard to install or update multiple AD RMS deployments from the same server computer. Because of design changes to Server Manager for Windows Server 2012, multiple instances of the Add Roles and Features Wizard can now be run simultaneously, making it possible to launch two or more instances of the AD RMS Configuration wizard.
Server Core Support for AD RMS
For Windows Server 2012, AD RMS now joins the list of server roles such as Active Directory Domain Services (AD DS) and Active Directory Certificate Services (AD CS) that are supported for Server Core deployment. Server Core is an installation option that enables you to perform a minimal installation of the Windows Server operating system which can be useful for reducing total cost of ownership (TCO) in deploying and managing servers.