Virtual Launch Event for the new Office 365 for business.

When? Wednesday, February 27th 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

clip_image002

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

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

clip_image002

· Expand Local Users and Groups

· Open Administrators Local Group

clip_image004

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

clip_image006

· Close Session

clip_image008

Re-open a session with OmAdmin user

clip_image010

· 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

clip_image012

· 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

clip_image014

clip_image016

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

clip_image018

· 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

clip_image020

· 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.

image

 

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

image

  • user12 has Send on behalf permissions on user14 mailbox

image

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.

image

The Sent Items of User12 will be like this:

image

And the cool part is the Sent Items folder of User13 which now has the original message and he/she is able to keep track what they are sending on his name.

image

Test #02: User12 send on behalf of user 14..

Our User12 sends a message on behalf of user 14 as show in the figure below.

image

In the Sent Items folder of user12 will show up the message.

image

Voilà, the same message appeared on the Sent Items folder of user14 as well.

image

 

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

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

image

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

image

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.

image

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.

image

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

image

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.

image

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

image

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

clip_image002

· Close the session

· Open a new session with the OMAdmin user

· Click Setup

· Click Installation

clip_image004

· Click New SQL Server stand-alone …..

clip_image006

· Click Show Details

clip_image008

· Validate that all Status are Passed

· Click OK

clip_image010

· 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

clip_image012

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

· Select Send feature data to Microsoft …..

· Click Next

clip_image014

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

· Click Next

clip_image016

The update is downloading and installing

clip_image018

· Click Show Details

clip_image020

· Validate that all status are Passed

· Click Next

clip_image022

· Select SQL Server Feature Installation

· Click Next

clip_image024

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:

clip_image026

· Select Management Tools Basic

· Select Management Tools – Basic

· This will install all tool needed to manage SQL Server

· Click Next

clip_image028

· Click Show Details

clip_image029

· Validate that the Status is passed

· Click Next

clip_image031

· 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

clip_image033

· Click Next

clip_image035

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

clip_image037

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

clip_image039

· Select Windows authentication Mode

· Click Add and Select the OMAdmins Group

· Select Next

Or take our company standard

clip_image041

· Click Next

clip_image043

· Click Show Details

clip_image045

· Validate that all Status are Passed

· Click Next

clip_image047

· Click Install

clip_image049

· Installation is beginning

clip_image051

· Validate that all Status are Succeeded

· Click Close

clip_image053

Validate that you can open SQL

On MTLSQL01 Server, your session is open with OMAdmin user

· Press Windows Key

· Select SQL Server Management Studio

clip_image055

· Select MTLSQL01\OPSMGROM

· Click Connect

clip_image057

· Expand the Server

· Expand Databases

Validate that the 4 Databases are created are mounted

clip_image059

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 Smile)

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.

clip_image002

A confirmation will be required, just click on yes

clip_image003

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.

clip_image004

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.

clip_image006

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

clip_image007

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.

clip_image008

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.

clip_image010

 

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

Managing Mailbox Owner Audit in Exchange Server 2010

Hi there,

In Today’s post we are going over a a feature that is not used very often which is the mailbox owner audit in Exchange Server 2010. This feature can be used for legal reasons to make sure that we have audit not just from Delegates, Administrator but also owners.

In some companies we have users that open restore tickets because the message “disappeared” from their mailbox and since IT department by default don’t have anything to proof that wasn’t the mail system fault we just need to start restoring data (of course when they open the ticket the Recover Deleted Item period is long gone Smile).

So, the first step is to enable Audit on a mailbox and we can do that by running Set-Mailbox <Mailbox> –AuditEnabled $True

After enabling Auditing on the mailbox we will have by default some actions being logged when the source is Delegates or Administrators on the audited mailbox. The default logged actions are deletions (soft and hard), send as, new and updated items basically.

Enabling Mailbox Owner Audit…

Time to audit the mailbox owner and for that we can use the cmdlet below. Bear in mind that Update,MoveToDeletedItems,SoftDelete and HardDelete are all our options to the owner.

image

Note: You must have the AuditEnabled set to True to have the data being recorded.

Visualizing the Audit on a mailbox…

Okay we configured the Audit for a user and we want to see what is being logged on. A good way to do that is by running the following cmdlet where we will have all Audit details about that specific mailbox.

image

Checking the logs…

Okay, finally on a Friday afternoon our beloved user open a ticket asking for a restore of an item that disappeared, time for Exchange Show time!

Run the following cmdlet: Search-Mailbox –Identity <Mailbox> –LogonType Owner and voilà we have all entries containing who, where, which client and so forth. You can export the content or play with PowerShell to narrow down the results but you get all the proof to inform the end-user that items do not disappear without a reason.

image

By the way, you can use three values for LogonType which are: Owner, Delegate and Admin.

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