Install Windows Server 2012


This document lists the steps to install Windows Server 2012.

Attach the media (if its a virtual machine) or insert the DVD into the DVD drive and then boot the Virtual/Physical Machine.

A screen will show loading. When it completes you will get the screen below.


  • Select your language, time and Keyboard method.
  • Click Next.


  • Click on the “Install Now” button to start the installation.


  • Enter in your product key and then click Next.


  • Make your select if you want a GUI or Core installation and then click Next.


  • Click on the checkbox to accept the license terms and then click Next.


  • We are going to do an Custom Installation as this is a new install on a system with no OS.


  • Select the partition you want to install on or create your custom partitions and then click Next.


  • Progress screen. Sit back and wait for the install to complete.


  • Once the setup has completed and after several reboots you will get to this screen. Enter in the local Administrator password and confirm it. Once done click Finish.


  • Once done you will get the login screen. Press any key on the keyboard for the screen to show display the screen below.


  • Type in the password you just created to login to the system.

Exchange 2013 Setup Step by Step

This guide shows you how to install Exchange 2013 step by step. It shows how to configure Active Directory and create a DAG with its network requirements.

The document shows you how to do the following:

  • Prepare & Configure Active Directory.
  • DNS Setup (Internal & External)
  • Exchange Installation.
  • Network Setup/Preparation for your DAG.
  • DAG setup.
  • Accepted Domain Setup.
  • Send/Receive Connector setup.
  • Setup SSL Certificate (I could not create this in my sandbox environment but provided links)
  • Public Folder Setup.
  • Create a Distribution List.
  • Create a Contact.
  • Create a Shared Mailbox.
  • Monitoring Queue and DAG Status.

Active Directory and DNS Preparation:

Minimum Domain Requirements:

  • Windows Server 2003 Standard with Service Pack 2 (SP2)
  • Support for Windows Server 2012 R2
  • Active Directory Forest Level – Windows Server 2003 or Higher
  • User Account member of the Domain, Schema and Enterprise Admins Groups.

Internal DNS Setup


  • Create a CNAME record for Autodiscover that points to your server.
  • Alias Name will be autodiscover (as shown above)
  • FQDN will be the full name in the forward lookup zone you added the CNAME in. for example, if it was then autodiscover would be autodiscover.domain.dom.
  • FQDN for Target host is your primary exchange server.

External DNS Setup

  •  Create an A record that will point to your public IP for that exchange server.

Server Preparation:

  • Server 2012 Operating System (Need to be the same version as we going to setup a DAG)
  • Join Server to Domain.
  • All Windows Updates installed.

Windows Features to be installed via Windows Powershell:

  • Install-WindowsFeature RSAT-ADDS
  • Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

Once the above features have installed restart your server.

Exchange Prerequisites:

**After installing the 3 Prerequisites reboot**

Prepare Active Directory and Schema:

Open up an elevated command prompt and run the following commands.

Schema Preparation:

  • E:\Setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms

AD Preparation:

  • E:\Setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms

**Replace E:\ with your own drive letter.

Install Exchange 2013

Open up ISO that you mounted and double click the Setup File. Always run the setup “As Administrator”.


  • Select whether you want to download updates and then click the Next.


  • If any updates are found it will list them, no updates found in this setup, click the Next button.


  • Exchange setup copying files, wait for it to finish.


  • Server Setup is initializing.


  • Introduction page, click the Next button.


  • Accept the License Agreement and then click Next.


  • Make your choice, this installation we went with the default settings. Click Next.


  • Select the roles you want to install, in this installation all roles were chosen. Click Next.


  • You can accept the default location or click Browse change the install location. Once done click Next.


  • Malware settings left on, you can make your selection here and then click next.


  • Once the readiness checks are complete, click on the Install Button to start the Exchange 2013 installation.


  • Exchange 2013 setup has 14 steps to complete. This can take a little while.


  • Once the installation is complete you will see the screen above. You can launch the Exchange Management Center by selecting the checkbox.
  • I recommend rebooting the server.
  • Once you have rebooted, you can login to the Exchange Admin Center as follows:


Post installation and setup tasks:

  • Setup Network.
  • Setup Permissions.
  • Create a DAG, Add servers to the DAG, create mailbox copies.
  • Accepted Domains.
  • Setup Send/Receive Connectors.
  • Setup SSL Certificate.
  • Public Folders.

Prerequisites: – AD

  • Create a computer account in Active Directory; you can call it EX2013DAG for example.
  • Disable the computer account.
  • Open up Active Directory Users and Computers. Make sure you have Advanced Features Enabled. Right click on the computer account just created and select properties. Click on the Security Tab.
  • Grant the Exchange Trusted Subsystem Full Control.
  • Add the DAG Members with Full Control.

Prerequisites: – Network


  • One NIC that has Internet Access.


  • Second NIC purely for DAG traffic. No Default Gateway to be setup or DNS servers. (Shown Above)


**Vitally important that you remove the checkbox that says “Registers this connection’s addresses in DNS on the Second NIC.

  • Make sure that your Binding Order is correct with NIC 1 first on the list.

For example, if you setup this server NIC 2 IP as then your second server should be with the same subnet.

Remember that the Second NIC needs to be on a different subnet to that of your LAN.


  • This is an IP address assigned to the DAG that is separate from the Server itself. Reserve an IP address in DHCP or give it an IP that is part of an exclusion range.

Witness Server:

  • Best practice is to use an Exchange 2013 CAS server. Any windows server will do, but you need to add the Exchange Trusted Subsystem as an administrator to that local PC before you can use it.
  • The file share witness also requires the File Server feature installed. (if not an exchange server)

Assign Permissions:

Login to the EAC -> Click on Permissions -> Admin Roles


  • Click on Organization Management and click the Pencil button next to the + button.
  • Scroll down and by Members click the + button and add in the users that will be managing exchange.
  • Click on “Outlook Web App Policies and modify or create a policy.
  • You can also define user roles.

Create a DAG:

GUI Setup: Click on Servers -> Database Availability Groups -> + button.


Exchange Management Shell Setup:

Open up the EMS and type in the following command:

  • New-DatabaseAvailabilityGroup –Name <DAGNAME> –WitnessServer <ServerName> –WitnessDirectory “C:\FSW” – DatabaseAvailabilityGroupIPAddresses <IP Address>

Add Servers to the DAG:

GUI -> Add Servers:


Exchange Management Shell Command:

  • Add-DatabaseAvailabilityGroupServer –Identity <DAGNAME> –MailboxServer <ServerName>

Once the command completes add in the second server.

Create Database Copies:

Now that your DAG has been created, you can add copies of mailbox databases to other mailbox servers.

GUI Setup.


  • Click browse to select the server.

If you have a Database called Database1 you can add it to Ex2013b server as an example.

Exchange Management Shell Command:

  • Add-MailboxDatabaseCopy –Identity <DatabaseName> –MailboxServer <ServerName>

Create a user mailbox:

GUI Setup: Click on Mailboxes -> + button -> User Mailbox.


  • Enter in all the information for the user, you can also specify a specific mailbox database and whether or not to show/hide the user from address lists.

Exchange Management Shell Setup:

  • New-Mailbox-Alias EdTest -Name “Ed Test” -Firstname Edward -LastName Test -DisplayName “Edward Test” -UserPrincipalName -Password <ConvertTo-SercureString -String ‘TestPassword’ -AsPlainText -Force> -Database <ServerName>

Setup Accepted Domains:

In the ECP click on Mail Flow -> Accepted Domains.


  • Click the + sign to add in a new accepted domain.
  • Type in the Name (descriptive).
  • Type in the Domain.
  • Select if this is either Authoritative, Internal Relay or External Relay.
  • Click Save.

Configure Default Frontend Receive Connector:

In the ECP click on Mail Flow -> receive connectors.


  • Click on Default Frontend <ServerName> and then click the Pencil next to the +
  • Go to the security tab as shown above and make sure “Anonymous Users” checkbox is selected.
  • Click on save.

Create Send Connector:

In the ECP click on Mail Flow -> send connectors.


  • Click on the + to add a new Send Connector.
  • Type in a descriptive name and then select the Type.
  • Click Next.


  • Select your Network settings, if you routing mail through a smarthost then click the + button.


  • Type in the smart host info and then click save.
  • After that click Next.


  • Specify the authentication as per your ISP and click Next.


  • Click on the + button to setup the Address Space.


  • Enter your FQDN and your Type.
  • Click Save.
  • Click Next.


  • Click on the + button to add in a Source server. When the window comes up select your exchange server, click the Add -> button and then click ok.
  • Click finish and you have now have a send connector setup.

CSR Creation: 

SSL Installation:

Public Folder Mailbox Setup:

In the ECP click on Public Folders -> Public Folders Mailbox.


  • Click on the + button.
  • Enter in the name for the PF Mailbox.
  • Select an Organizational Unit by clicking the browse button.
  • Select a Mailbox Database by clicking the browse button

Public Folder Setup:

In the ECP click on Public Folders -> Public Folders


  • Click on the + button.
  • Type in a folder name.
  • Click the Save button.

Additional Tasks:

  • Create Distribution List.
  • Create Contacts.
  • Create Shared Mailbox.

Distribution list creation:

In the EAC Click on Recipients -> Groups

Add DL
  • Click on the + button and select Distribution group.

Add DL1

  • Type in the display Name
  • Type in the Alias
  • Click the browse button to add it to a specific OU.
  • Click the + button to add a owner.
  • Scroll down to add in more info (screen shot below)

Add DL2

  • click the + button to add in the members of this group.
  • Select your option regarding the approval of this Distribution Group.

You can also create a distribution list using the EMS:

  • New-DistributionGroup -Name “Managers” -OrganizationalUnit “” -SamAccountName “Managers” -Type “Distribution”

Contact creation:

In the EAC Click on Recipients -> Contacts

Add cont1

  • Click on the + button and select Mail Contact.

Add cont2

  • Type in the information and then click Save.

Shared Mailbox creation:

In the EAC Click on Recipients -> Shared

add shared mailbox1

  • Click on the + button.

add shared mailbox2

  • Enter in the Display Name and Alias.
  • Click browse to select an OU.
  • Click on the + button to grant Send As Permissions.
  • If you click the More Options button you can set the Mailbox Database where this mailbox should be housed.
  • You can also select a policy.
  • Once done click Save.

Monitoring Queues and DAG:

Open up the Exchange Management Shell.

To find the status of the email Queue type in the following command:

  • Get-Queue

This will give output the status, Message Count, DeliveryType and NextHopDomain.

You can also use Exchange Queue Viewer located in the Exchange Toolbox.

To check the DAG status type in the following command:

  • Get-MailboxDatabaseCopyStatus * (This will show all servers)
  • Get-MailboxDatabaseCopyStatus (without the * it will show the current server)

Configure DHCP Failover for Server 2012 R2

Prerequisites List:

  • Install Server 2012 R2operating system on 2 servers.
  • Join server to the domain.
  • Install the DHCP role on both servers.
  • One of the servers needs to be configured with your DHCP Scopes.

Login to your main DHCP server that you configured and then go to Control Panel -> Administrative Tools -> DHCP


Open Server Manager and then click on Tools -> DHCP



  • Expand the DHCP server and then right click on IPv4 and select “Configure Failover” as shown above.


  • Review the information (removed from screenshot) and then click on “Select All” to select specific scopes. Leave as default if you want all the scopes and then click Next.


  • Click on the “Add Server” Button, another screen will appear as below:


  • Click on the “This authorized DHCP Server”, select the server you want as the failover server and then click on okay.


  • The server name will show next to the “Partner Server” and then click Next.


  • Enter a Descriptive Relationship Name.
  • **NB** If your other DHCP server is on the same subnet then It is recommended to setup Loadbalancing. If your other DHCP server on another network then setup the mode to Hot Standby.
  • Modify the rest of the settings as per your network.
  • Add in a password for the Shared Secret to be used to authenticate the failover between your servers.


  • A summary is shown with the configuration you just set. In the scopes box it will show the scopes you chose and above that the name of the servers the failover is between.
  • Click on Finish.


  • A Dialog box will show. Click Close.

Login to your secondary DHCP Server. Go to Control Panel -> Administrative Tools -> DHCP


Open Server Manager and then click on Tools -> DHCP


  • Expand the DHCP server and then right click on IPv4 and select “Properties” as shown above.


  • Click on the “Failover” tab and you should see the “Relationship Name” and “Partner Server” and it will display the mode you setup etc.

Hope it helps.

System Center Configuration Manager 2012 R2 Installation with local SQL 2012 SP1

Active Directory Setup:

Create the following accounts/Groups in Active Directory.

  • DOMAIN\ConfigMgrAdmins            ConfigMgr Administrators security group
  • DOMAIN\ConfigMgrLocalAdmin     ConfigMgr Client Push account

Add your account or any other member that is going to administer SCCM to the “ConfigMgrAdmins” group.

Prerequisites List (SCCM Server):

  • Install Server 2012 OS
  • Join server to the domain
  • Install all windows updates so the server is fully patched.
  • Install Windows Assessment and Deployment Kit (Windows ADK) for Windows 8.1
  • Install SQL 2012 SP1.
  • Add the “ConfigMgrAdmins” domain global group to the Local Administrators group.

Windows Features Requirement:

Run the following from PowerShell (run as Administrator):

  • Add-WindowsFeature Web-Windows-Auth,Web-ISAPI-Ext,Web-Metabase,Web-WMI,BITS,RDC,NET-Framework-Features,Web-Asp-Net,Web-Asp-Net45,NET-HTTP-Activation,NET-Non-HTTP-Activ,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Redirect,Web-App-Dev,Web-Net-Ext,Web-Net-Ext45,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-HTTP-Tracing,Web-Security,Web-Filtering,Web-Performance,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Mgmt-Compat –Source D:\sources\sxs –Restart

After installing these roles/features, you might have to register ASP.NET with IIS.  The simplest way is to open an elevated command prompt: C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe –r

 Prepare Active Directory for Configuration Manager



  • Connect to a domain controller in your environment and load ADSIEdit. ADSIEdit is found under Administrative Tools. Expand Default Naming Context and then expand the DC name and under the System OU create a new Object as Shown Above.

create Object



  • Click on container and then click Next.

create object 2


  • Enter in System Management and click the Next button.
  • Complete the Wizard and then close ADSIEdit.

Delegate control on the newly created container.

  • Open up ADUC.MSC (Active Directory Users and Computers)
  • Expand the System Container. You will see the System Management container you just created above.
  • Right click on the System Management Container and select Delegate Control.

delegation of control


  • Click on “Create a custom task to delegate” and click the Next Button.

delegation of control 1


  • Make sure the first option is selected and click the Next Button.

delegation of control 3


  • Check all Permission boxes and click Next and then complete the delegate wizard.

Extend the Schema.

Open up the ISO file that contains the SCCM 2012 R2 installation files and navigate to the following directory.

  • \SMSSetup\Bin\x64\

Or open up and elevated command prompt and Navigate to that folder.

If you opened up the directory using explorer then Right Click on the Extadsch.exe and “Run as Administrator” or from the prompt run the same file.

A log file ‘ExtADSch.log’ will be generated on the root of the C:\ Drive. Look for the entry ‘Successfully extended the Active Directory schema.’

**Note that replication can take time so rather wait or force replication**

Install Windows Assessment and Deployment Kit for Windows 8.1 (ADK)

Click on the link below to download the ADK



  • Click on the checkbox to accept the terms for .NET and then click on the “Accept & Install” button for .NET Framework 4.5 to install.

adk confirmation


  • When you get prompted to restart click the Ok button.

adk setup 1


  • After the server has rebooted the installation will resume. You can choose the default option as shown above or Download the ADK to a share and run the install from there. I chose the default, click the Next Button to proceed.

adk ceip


  • Make your selection and then click the Next button.

adk license agreement


  • Accept the License agreement for the installation to continue.

adk feature setup


  • Only install the following options above:
  • Deployment Tools
  • Windows Preinstallation Environment (Windows PE)
  • User State Migration Tool (USMT)
  • Click the Install button.

adk installation progres


  • Progress screen..

adk setup complete


  • Once the installation finishes you will get the screen above. Click the close button. The ADK is now setup.

Install SQL Server (2012 SP1)

sql server setup 1


  • Double click the setup file located in the SQL 2012 SP1 Media
  • The screen above will show, click on “New SQL Server Stand-alone installation or add features to an existing installation”

sql server setup 2


  • The above screen will show, if there are any warnings or errors it will list them. Click Ok to continue.

sql server setup 3


  • Here you can enter a product key that you received from MS found on the media.
  • In this Sandbox setup we will choose “Evaluation” and then click the Next button.

sql server setup 4


  • Click the checkbox to accept the license terms and then click the Next button.
  • If there are any updates on the next screen let them download and proceed with the install.

sql server setup 5


  • Again the support rules will run, click Next to continue

sql server setup 6


  • Select the first option and click the Next button.

sql server setup 7


  • On the feature selection screen, choose the following options:
    • Database Engine Services with Full-Text and Semantic Extractions for Search
    • Reporting Services – Native
    • Management Tools and its sub-feature.

sql server setup 8


  • Click Next to continue

sql server setup 9


  • I left the instance as default, click the Next button to continue.

sql server setup 10


  • Click Next to continue.

sql server setup 11


  • As this is a Sandbox environment the defaults were chosen but you will want to add in the Domain accounts that have access to SQL in a production Environment.
  • Don’t click next just yet, we need to set the Collation as with SCOM. Click the Collation Tab next to the Service Accounts Tab.

sql server setup 12


  • Click on the Customize button to change the collation.

sql server setup 13


  • Click on the radio button labelled “SQL Collation, used for backwards compatibility”
  • Scroll down until you see “SQL_Latin1_General_CP1_CI_AS”. Click on it and then click OK.

sql server setup 14


  • Add in the Current User and any other user that will be managing SQL. Click Next to continue.

sql server setup 15


  • Select the option “Install Only” and then click Next.

sql server setup 16


  • Make your selection and click Next.

sql server setup 17


  • Click Next to continue.

sql server setup 18


  • Review all the options you just made, if happy click the Install button.
  • Sit back and wait for the installation to finish, it can take a while.

Install System Center Configuration Manager 2012 R2 (SCCM)

sccm setup 1


  • Go to the folder where you extracted the SCCM setup files and double click the setup. The above screen will show. Click Next to continue.

sccm setup 2


  • Click on the option “Install a Configuration Manager Primary Site” and then click Next.

sccm setup 3


  • As this is a sandbox install we will install the evaluation edition of the product. Click next to continue.

sccm setup 4


  • Click tickbox to select and accept the license terms and click Next to continue.

sccm setup 5


  • Accept all the license terms (3 Tick Boxes) and then click Next to continue.

sccm setup 6


  • SCCM will required a number of files. I chose the default “C:\Downloads” but you can add in your own share or directory. If you have manually downloaded the files then you would select the 2 radio button and browse for them.

sccm setup 7


  • A new window opens and displays a progress bar of the downloads.

sccm setup 8

  • Select your desired Server language and then click Next to continue.

sccm setup 9

  • Select your desired client language and then click next to continue.

sccm setup 10

  • Enter in your site code and site name. Your site code needs to be unique, you cannot go and change it later on as all this information will be written to AD.
  • I used TLB for Test Lab and the site name as SCCM 2012 Test lab. Click Next to continue with the installation.

sccm setup 11

  • Select the radio button to install this as a stand-alone site and click Next to continue.

sccm setup 12

  • Click Yes to continue.

sccm setup 13

  • All the boxes will be populated, leave the defaults and click Next to continue.

sccm setup 14

  • You can leave the defaults where SQL is located or you can change the paths, in this setup the defaults were used. Click Next to continue.

sccm setup 15

  • Enter your current server as the SMS Provider and click Next to continue.

sccm setup 16

  • Select the 2nd radio button as shown above as we not running PKI. Click next to continue.

sccm setup 17

  • Install both Management Points and Distribution Points on the server, enter in the server FQDN. Click Next to continue.

sccm setup 18

  • Make your selection and click Next to continue.

sccm setup 19

  • Review the summary and then click Next to continue.

sccm setup 20

  • The setup will do a prerequisite check, the warnings above can be ignored but in a production environment you might want to make sure you have not errors/warnings. Click Next to continue.

sccm setup 21

  • The installation has started. Sit back and wait.

sccm setup 22

  • After a little while the installation completed. You can click the close button and launch the SCCM Console and start your configuration.

Install New AD Server & Move Active Directory Operations Master Role

Prerequisites List (Active Directory Server):

  • Install Server 2012 R2 Operating System.
  • Join server to the domain.
  • Install AD Services Roles
  • Promote the Server to a Domain Controller.

 Installing the Roles:

Open up Server Manager on your New 2012 R2 Server.


  • Once the server has initialized all its roles then click on Manage as shown above and then click on “Add Roles and Features”


  • Read through the information (if you knew to this), to continue click Next.


  • Select “Role-Based or feature-based installation” and click Next.


  • In my case I had multiple DC’s, I selected one, after that click Next.


  • Click on Active Directory Domain Services


  • Click “Add Features” and then click Next.


  • Review the summary and then click the Install Button.


  • Installation Starting.


  • Installation completed.
  • Click on “Promote this server to a domain controller”, you can either use the hyper-link above or click on the yellow exclamation in Server Manager next to the refresh button.


  • I chose option 1 “Add a domain controller to an existing domain”, then click on the select button to select your domain. After this click on change and enter the details of a Domain Admin. Once done click the Next button.


  • Select if this is a DNS server. Type in the DRSM password and store this password. Click the Next button.


  • Verify the information and click Next.
  • Review the options and then click Next.


  • The prerequisite check will run, you can view the warnings and click the Install Button.


  • Progress screen. This will replicate all information.


  • The above screen will appear when the installation is complete and your server will automatically restart after a min.
  • After the restart you will have a new domain controller in your environment.

Moving all Roles to the new DC:

To find which servers hosts what roles you can open up and elevated prompt and run the following:

  • netdom query FSMO

It will return the following information:

  • Schema Master                   DC Name
  • Domain Naming Master       DC Name
  • PDC                                    DC Name
  • RID Pool Manager               DC Name
  • Infrastructure Master           DC Name

After this we can run one command to move the roles to a new Domain Controller. Open up an elevated PowerShell Window and run the following:

  • Move-ADDirectoryServerOperationMasterRole -identity “DC Name” -OperationMasterRole 0,1,2,3,4

After that you can go back to your elevated prompt and query FSMO and it should show the name of the DC you moved the roles to.

SQL Server Reporting Services Error

Last week I upgraded one of my test servers from Windows Server 2012 to Windows Server 2012 R2. The upgrade went successfully except for one service. The SQL Server Reporting Services. I wanted to pull a report and the app I was using reported the service wasn’t started.

I clicked start only to get the famous error that some services stop and start if they have nothing to do. Okay, time to check the logs. Here was the error reported:

Service cannot be started. System.IO.FileLoadException: Could not load file or assembly ‘ReportingServicesNativeServer, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ or one of its dependencies. The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)
File name: ‘ReportingServicesNativeServer, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91’ —> System.Runtime.InteropServices.COMException (0x800736B1): The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log or use the command-line sxstrace.exe tool for more detail. (Exception from HRESULT: 0x800736B1)
at Microsoft.ReportingServices.Library.ServiceAppDomainController..ctor()
at Microsoft.ReportingServices.Library.ReportService.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedM…

Quite a long error. I simply opened up Programs and Features and ran a repair on SQL. After that the service started without any issues.

Hope it helps

CRM Dynamics 2011 on Windows Server 2012 R2

Today I tested an upgraded on my CRM system running server 2012. I first upgraded CRM Dynamics 2011 to RU15, after that I did a restart.

I ran the upgrade from Server 2012 to Server 2012 R2 (Note that CRM Dynamics 2011 is not supported on Server 2012 R2)

After the upgrade IIS issued an error saying that the WSS service was disabled as the server is running IIS 7.5 and not IIS 7.0.

When I checked my site was gone. No sweat, I navigated to the CRM Dynamics folder under programs files and ran the ServerSetup. It gave me 3 options, I chose repair and pointed to the install files. After it had finished I did an IISReset and navigated to the CRM URL only to be met with the following error:

“HTTP Error 500.19 – Internal Server Error

The requested page cannot be accessed because the related configuration
data for the page is invalid.

`Detailed Error Information`
Module IIS Web Core
Notification Unknown
Handler Not yet determined
Error Code 0x8007000d
Config Error
Config File \\?\C:\wwwroot\web.config
Requested URL http://localhost:80/Default.aspx
Physical Path
Logon Method Not yet determined
Logon User Not yet determined
Config Source

Quick check, IIS 7.0 uses the URL Rewrite Module and IIS 7.5 does not. I downloaded the file ( and ran the install, did an IIS reset and went back and CRM Dynamics 2011 was now running fully on Windows Server 2012 R2. 

Hope it helps.