AndersonPatricio.ca

How to Deploy and configure OpsMgr 2012 SP1 – Part 8 - How to Install the first Management Server OpsMgr 2012

Introduction

In this document we will install the First OpsMgr 2012 SP1 on MTLMS01 Server

Installation

Install the First OpsMgr 2012 SP1

Now you are ready to install the first Management Server on server MTLMS01. We will not now install the web console on the server, because we want secure communication with SSL. A certificate must be installed on IIS before to be able to install the Web Console in SSL. We will install later in this series

· Open a session on MTLMS01 Server with the OmAdmin user

· Double click on Setup to start the Installation

· Click Yes

We will use the Installation Log file to follow the Installation. To open the Installation Log file Go to D:\Users\omadmin\AppData\Local\SCOM\LOGS\

AppData is a Hidden Folder, to see this folder.

· Click View

· In the menu select Hidden Items

Now the ApplData folder will appear

To read log in real time we will use the utility Trace32.exe. It is a free tool from Microsoft

· Click Install to begin the installation

Open the Installation log file to fallow the Installation. We can find this log C:\Users\omadmin\AppData\Local\SCOM\LOGS\OpsMgrSetupWizard

· Select Manager Server

· Select Operation Console

Do not select the Web Console, because we will secure the Web Console with SSL later.

· Click Next

· Change the Path to D:\Program Files\System Center 2012\Operations Manager

· Click Next

We can ignore this Warning. For a Production server you must have at minimum 8G of RAM

· Click Next

Be sure that Create the first Management Server in a new management group is selected.

· Type ACGLGroupProduction in Management Goup name. Note This Name is case sensitive

· Click Next

· Select I Have read, understood …

.

· Click Next

· Type MTLSQL01\OpsMgrOM in SQL Server Name and instance name

If the MS server can connect to the SQL, all other data will be populated automatically. Adjust the Database Size with the value that you got from the Sizing helper. Note It is possible to adjust it later. For the Lab I accept the default 1000

· Validate the information and

· Click Next

· Type MTLRS01\OpsMgrRS in Server Name and instance name. If the MS server can connect to the SQL, all other data will be populated automatically. Adjust the Database Size with the value that you got from the Sizing helper. Note It is possible to adjust it later For the Lab I accept the default 1000

· Validate the information and

· Click Next

· Select to Domain Account for System Center Configuration Service and System Center Data Access

· In Management server action account Type ACGL\OMAA and the password

· In the System Center Configuration service and System Center Access service Type ACGL\OMDAS and the password

· In the Data Reader account type ACGL\OMDWR en the Password

· In Data Writer account type ACGL\OMDWW and the password

· Click Next

· Select No, I am not Willing …

· Select No, I am not willing to participate

· Click Next

· Select Off

· Click Next

· Validate that all information are correct

· Click Install

The global Installation will take about 30 minutes to be completed. You can fallow the installation in the Log file

· Click Close when the Installation finish.

We have Install the first Manager Server 2012 SP1

In the Next Document

In the next document we will validate the Health on the first Manager server on MTLMS01

Cheers,
Alain Laventure
Senior Consultant
Exchange Expert, SCOM Expert and Lync specialist
Allain’s Bio: http://msmvps.com/blogs/andersonpatricio/pages/bio-alain-laventure.aspx

How to Deploy and configure OpsMgr 2012 SP1 – Part 7 - How to validate the communication between OpsMgr 2012 SP1 and the SQL Servers

Introduction

In this document we will validate that from MTLMS01 and MTLMS02 you communicate with both SQL Servers. It is very important that the user OMAdmin can be connect with both SQL servers because OMAdmin will create the Database OperationsManager and the OperationsManagerDW Database during the installation.We will use ODBC Data Access Source to validate if the user can have access to both SQL servers

Validate the communication with SQL Servers

Validate that the OMAdmin User can connect to the MTLSQL01 Server from Server MTLMS01

• Open a session on MTLMS01 with OMAdmin user
• Click Start
• Click Administrative Tools
• Click Data Source(ODBC)
• Click Add

We will have only one choice

• Click Finish

• Type a description in name
• It can be anything
• Type MTLSQL01\OpsMgrOM
• The SQL name Server with the instance name
• Click Next

• Leave the default
• Here we will use the with Windows NT authentication ( the OMAdmin)
• Click Next

• Leave the default
• Click Next

• Leave the default
• Click Finish

• Click Test data Source

If the user OMAdmin can connect you will get Test Completed Succufully

• Click Cancel 3 times to close the SQL Server ODBC Data Source Test

Validate that the OMAdmin User can connect to the MTLRS01 Server From Server MTLMS01

Repeat the same step to connect to the MTLRS01

• Open a session on MTLMS01 with OMAdmin
• From MTLMS01 To connect to the MTLRS01
• Type MTLRS01\OpsMgrRS

Validate that the OMAdmin User can connect to the MTLSQL01 Server From Server MTLMS02

• Open a session on MTLMS02 with OMAdmin
• From MTLMS02 To connect to MTLSQL01
• Type MTLSQL01\OpsMgrOM
• Click Next

Validate that the OMAdmin User can connect to the MTLRS01 Server From Server MTLMS02

• Open a session on MTLMS02 with OMAdmin
• From MTLMS02 To connect to MTLSQL01
• Type MTLSQL01\OpsMgrOM
• Click Next

In the Next Document

In the next document we will install the first management Server 2012 SP1 server on MTLMS01

Cheers,
Alain Laventure
Senior Consultant
Exchange Expert, SCOM Expert and Lync specialist
Allain’s Bio: http://msmvps.com/blogs/andersonpatricio/pages/bio-alain-laventure.aspx

Virtual Launch Event for the new Office 365 for business.

When? Wednesday, February 27^th 8 am PDT and 5 pm PDT

Why Attend?

• Learn how the new Office 365 can help people do
their best work in a world of devices and services

• Hear customers talk about how Office 365
is transforming the way they deliver productivity
tools across their organization

• See how Office 365 delivers new experiences
combining the power of social with collaboration,
email and unified communications

• Join in a live Q&A with Microsoft executives
and product experts

Hosting and Multi-Tenancy Guidance for Exchange Server 2013 Now Available

Hi folks (MVP Summit is over so it’s time to go back to work :) )

Exchange Team has just released the Multi-Tenancy Guidance for Exchange Server 2013, good stuff and there is a couple of new stuff to help the ABP segmentation.

We are pleased to be able to announce the oft-requested Hosting and Multi-Tenancy Guidance for Exchange Server 2013 document. It is available for download here.

As the keen eyed reader will observe, it is very similar to the guidance for Exchange Server 2010. That’s not because all we did was a find, copy and replace, but because the strategy we decided upon for Exchange 2010 holds true for Exchange 2013. That is, you should only use the built in tools, cmdlets and interfaces for configuring your solution, and you should not under any circumstances directly manipulate objects in AD to meet your desired configuration.

Download it here: http://technet.microsoft.com/en-us/exchange/jj720331

Read more at source: http://blogs.technet.com/b/exchange/archive/2013/02/20/hosting-and-multi-tenancy-guidance-for-exchange-server-2013-now-available.aspx

Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio

How to Deploy and configure OpsMgr 2012 SP1 - Part 6 - How to Install Prerequisites for OpsMgr 2012 SP1

Introduction

In this document you will install all prerequisites for OpsMgr 2012 SP1for both management Server MTLMS01 and MTLMS02

• Add the OMAdmins Group in the Administrators Local group of all MS Servers and SQL Servers
• Install IIS
• Install Report Viewer

Install Prerequisites on the MTLMS01 Server

Add OMAdmins group in the Adminitrators Local group

· Open a session on MTLMS01 with OMAdmin user

· Pin the Computer management

· Click Computer Management

· Expand Local Users and Groups

· Open Administrators Local Group

· Add the Omadmins Group in the Administrators Local group if it is not present

· Close Session

Re-open a session with OmAdmin user

· Repeat for MTLMS02 Server

· Repeat for MTLSQL01 Server

· Repeat for MTLRS01 Server

Install IIS for the SCOM 2012 Web console

· Open a session on MTLMS01 with OMAdmin user

We will install on this server the OpsMgr 2012 SP1 Web Console and the IIS need to be installed

· Open power Shell as Run as Administrator

· Type Add-WindowsFeature NET-WCF-HTTP-Activation45,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Logging,Web-Request-Monitor,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Metabase,Web-Asp-Net,Web-Windows-Auth –Restart

· As we can see no restart is needed Reboot the Server

· Repeat for the MTLMS02 Server

Install Report Viewer

· Open a session on MTLMS01 with OMAdmin user

· Install the Report Viewer controls to all Management Servers. Install them from http://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=6442

· Repeat for the MTLMS02

· Repeat for the MTLRS01

In the Next Document

In the next document we will validate that from MTLMS01 and MTLMS02 you communicate with the SQL Server MTLSQL01 and MTLRS01. It is very important that the user OMAdmin can be able to communicate with both SQL because OMAdmin will be used to Install OpsMgr 2012 SP1 and during the installation the Database OperationsManager will be created on MTLSQL01 and the Database OperationsManagerDW will be created on MTLRS01

Cheers,
Alain Laventure
Senior Consultant
Exchange Expert, SCOM Expert and Lync specialist
Allain’s Bio: http://msmvps.com/blogs/andersonpatricio/pages/bio-alain-laventure.aspx

Using Send Items feature of Exchange Server 2010 SP3

Good morning folks (Great morning for me, my Surface Pro 128GB arrived!)

In Today’s post we are going over the new feature introduced in Exchange Server 2010 Service Pack 3 which is the Send Items that can be found on the Options using OWA. If we click on Options and then See All Options on the main page. After that, click on Settings and then Sent Items.

Here is the new feature works, basically you can decide that if someone uses the Send As or Send on behalf feature using your mailbox you can decide how the message sent will behave. By default for either way is: Sender mailbox however I do like the option Sender and From Mailboxes where any message sent using your account will have a copy on your mailbox.

In order to facilitate the demonstration let’s say we have the mailbox user12 and this mailbox has the following rights:

• user12 has Send As permissions on user13 mailbox

• user12 has Send on behalf permissions on user14 mailbox

Just to be clear, I configured the Sent Items on both user13 and user14.

Are we good so far? Let’s do some testing…

Test #01: User12 Send as User13 …

Logged as User12 we send a message as user13.

The Sent Items of User12 will be like this:

And the cool part is the Sent Items folder of User13 which now has the

Deploying Exchange Server 2010 Service Pack 3

Hi There (I’m so excited Exchange 2010 SP3 testing and also Champions League games Today!)

Yesterday the Exchange Team released the Exchange Server 2010 Service Pack 3 and in this post we are going over the process to upgrade an existent Exchange Server 2010 with the new SP3.

Before going there a few key points about this upgrade:

• Please read the Release Notes: http://technet.microsoft.com/en-us/library/jj965774%28v=exchg.141%29.aspx
• Exchange Server 2010 can be installed on top of Windows Server 2012.
  Just to make sure that we are on the same page, you need to run this SP3 on brand new Windows Server 2012 in order to work.
• There are schema changes in this upgrade which means that you need Schema Admins privileges to do that. You can do either through GUI Setup interface or command-line. In this Tutorial our user has enough permissions and we will do everything from the GUI
• You can install this Service Pack on OS running Windows Server 2008 SP2 or Windows Server 2008 R2
• There is a database schema upgrades which means that we can’t mount an upgraded database in a previous version of the product and that applies to DAGs as well.
• Based on the MS documentation, each database upgrade could take 30 minutes to be upgraded
• There is a new feature called Sent Items Management feature that we are going over in a future post
• That is just the first step towards integration, a new Exchange Server 2013 CU1 (not released yet) is required to join Exchange Server 2013 into your organization

Also, before deploying in production you must make sure that all those best practices are in place, such as:

• Perform the upgrade in your lab first
• Make sure that you have backups
• In production the upgrade order is important: Edge (if you have it), then facing Internet CAS, Hub and then finally mailboxes and UM.
• Make sure that you are not running any instance of Exchange Management Console or Exchange Management Shell on the server
• Your Backup software is compatible with Service Pack 3
• Your Backup service is stopped during the upgrade
• Your AV/Antispam is compatible with Service Pack 3
• You may want to stop AV during the upgrade
• Any other third-party software is compatible with Service Pack 3

Here are the steps to upgrade to the SP3. Let's double click on setup.exe that can be found on the root of the extracted files from our download. In the main page, just click on Install Microsoft Exchange Server upgrade

In the Introduction page. Just a welcome to the new SP3, just click on Next.

In the License Agreement page. If you read and you are okay with it, please click on I accept the terms in the license agreement and click Next.

In the Readiness Checks page. Make sure that everything is green or at least yellow, as a best practice make sure that everything is green before moving forward. If there is need for any update, you can download and install. Click on Upgrade when you are ready.

Wait a few minutes (perhaps more than that depending of your databases) and the results should be something similar to this.

Have you had any issues? You can always look at the C:\ExchangeSetupLogs to see what is going on behind the curtains, as shown in the figure below.

If we look at the version of the server we will see 14.3 (Build 123.4)

Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio

Exchange Server 2010 Service Pack 3

Microsoft Exchange Server 2010 helps you achieve new levels of reliability and performance by delivering features that help to simplify your administration, protect your communications, and delight your customers by meeting their demands for greater business mobility

Read more at source: http://blogs.technet.com/b/exchange/archive/2013/02/12/released-exchange-server-2010-sp3.aspx

Download it from there: http://www.microsoft.com/en-us/download/details.aspx?id=36768

Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio

How to deploy and configure OpsMgr 2012 Sp1 - Part 4 - How to Install SQL 2012 Server for Operation Manager Database

Introduction

In this document we will Install SQL 2012 for Operations Manager database. This Database is the Short term Database.

The long Term Database is the Data Warehouse Database, this Database can be Installed on the same server than the Operation Management Database, but in the Series you will install the data warehouse Database on an another Server MTLRS01

Installation

How to Install SQL Server 2012

Setup is fairly straightforward. This document will not go into details and best practices for SQL configuration. Consult your DBA team to ensure your SQL deployment is configured for best practices according to your corporate standards

· On MTLSQL01, open a session with Administrator

· Add the Omadmins Group in the Administrators Local group of the MTLSQL01 Server

· Close the session

· Open a new session with the OMAdmin user

· Click Setup

· Click Installation

· Click New SQL Server stand-alone …..

· Click Show Details

· Validate that all Status are Passed

· Click OK

· Select Specify a free edition if you have an evaluation or if you have a Serial number

· Select Enter the Product Key and type your Product key

· Click Next

· Select I accept the Licence terms If you want to send usage data to Microsoft

· Select Send feature data to Microsoft …..

· Click Next

· If you want to install this Update Select Include SQL Server Setup Update

· Click Next

The update is downloading and installing

· Click Show Details

· Validate that all status are Passed

· Click Next

· Select SQL Server Feature Installation

· Click Next

This server will be used only by the Operations Manager Database. The short time database The SQL reporting Services will be installed on the other server MTLRS01

· Select Database Engine Services

· Select Full-Text and Extraction ….

· Change the Path to D:

· Replace C: by D:

· Select Management Tools Basic

· Select Management Tools – Basic

· This will install all tool needed to manage SQL Server

· Click Next

· Click Show Details

· Validate that the Status is passed

· Click Next

· Select name Instance

· Type OpsMgrOM as Instance Name If you want you can install SQL without any Instance

· Change the Path to D:

· Click Next

· Click Next

For both Service SQL Service Agent and SQL Server Database Engine

· Select the SRVCSQL user. This user is only a Domain User and this user does not have any Administrators right on the SQL Server

This service must be started and automatically

· Select both Startup Type Automatic

· Click the Collation TAB

You can use the default which is SQL_Latin1_General_CP1_CI_AS or choose another supported collation

· Click Next

Note the Collation cannot be changed after SQL installation. It is very important to select the collation that is supported

· Select Windows authentication Mode

· Click Add and Select the OMAdmins Group

· Select Next

Or take our company standard

· Click Next

· Click Show Details

· Validate that all Status are Passed

· Click Next

· Click Install

· Installation is beginning

· Validate that all Status are Succeeded

· Click Close

Validate that you can open SQL

On MTLSQL01 Server, your session is open with OMAdmin user

· Press Windows Key

· Select SQL Server Management Studio

· Select MTLSQL01\OPSMGROM

· Click Connect

· Expand the Server

· Expand Databases

Validate that the 4 Databases are created are mounted

Note

Install the Last Service pack and Cumulative roll up for SQL 2012 before to install OpsMgr 2012

In the Next Document

In the next Document we will install the SQL 2012 Server and the SQL reporting Services

The SQL reporting Services will be used by OpsMgr 2012 Reporting Server Role

This is the Long Term Data Warehouse Database

Cheers,
Alain Laventure
Senior Consultant
Exchange Expert, SCOM Expert and Lync specialist
Allain’s Bio: http://msmvps.com/blogs/andersonpatricio/pages/bio-alain-laventure.aspx

How to remove a DAG member in Exchange Server 2013

Bonjour mes amis (What a nice snow day here in Toronto, eh? We got around 25cm of snow in some areas including my way to the subway this morning )

In Today’s post we are going over the process to remove a DAG member when they have a regular database copy previously configured on Exchange Server 2013.

You may want to do this procedure as part of your maintenance tasks, decommission of a server or in some cases when you want to move Database and Log files of a DB in a DAG.

The first step after identifying the server that is to be removed is to list all databases that the server has on the DAG which it belongs to. In our scenario here the server that is going to be removed is POAEX16.

For each database, let’s click on it and then click on Remove on the database properties to remove the copy from the server that we want to.

A confirmation will be required, just click on yes

After removing the database we need to go to the affected server and remove the files. Click on ok on the message that informs us to do exactly that.

Time to remove the member from the DAG, let’s click on servers, then database availability groups select the DAG where the server belongs to, and click on the 5 (fifth) button from the left. When selecting the DAG we can see the members on the details page located on the right side.

In the new page, let’s select the server that we want to remove and click on the remove button (- minus icon) and then click save

Wait a little bit for all testing to be validated and the server will be removed from the DAG. Click on Close.

Note: If you have any issues during the process an error message with the reason why it failed will be displayed.

If you look at the Database availability groups tab and we will see that the DAG now has a single server and our server was removed as planned.

Cheers,
Anderson Patricio
http://www.andersonpatricio.ca
http://www.andersonpatricio.org (Portuguese)
Twitter: @apatricio