Anderson Patricio Get-news Blog

Exchange Server 2007 will be supported on Windows Server 2008 R2

Anderson Patricio — Wed, 04 Nov 2009 21:58:55 GMT

Hi Folks,

If you are planning to upgrade your entire infrastructure to Windows Server 2008 R2, then Exchange Server 2007 (in case you still have it :)) won't be an issue. Today, it was posted a note about that in the MSExchangeTeam, as follows:

We always talk about listening to customers and sometimes this is written off by many as 'marketing speak'. In fact, we do take feedback seriously and no input is more important to our engineering processes than your voice.

Earlier this year we made a decision in one direction, and due to the feedback we have received on this blog and elsewhere, we have reconsidered. In the coming calendar year we will issue an update for Exchange 2007 enabling full support of Windows Server 2008 R2. We heard from many customers that this was important for streamlining their operations and reducing administrative challenges, so we have changed course and will add R2 support. We are still working through the specifics and will let you know once we have more to share on the timing of this update.

Talking about Windows Server 2008 R2 and UC products, at this point OCS 2007 R2 is not supported on Windows Server 2008 R2, so keep your OCS infrastructure running on Windows Server 2008 for now. :)

Cheers,
Anderson Patricio
http://msmvps.org/blogs/AndersonPatricio

Technorati : Exchange Server 2007, Windows Server 2008 R2, support
Del.icio.us : Exchange Server 2007, Windows Server 2008 R2, support
Zooomr : Exchange Server 2007, Windows Server 2008 R2, support
Flickr : Exchange Server 2007, Windows Server 2008 R2, support

Programmatic Access via Remote PowerShell in Exchange Server 2010

Anderson Patricio — Tue, 03 Nov 2009 15:09:47 GMT

MSExchangeTeam posted about Remote PowerShell and some examples of scripts using remote access (exchange 2010) instead of local one (exchange 2007).

The management experience given by Exchange 2010 through PowerShell has been moved all the way from Local to Remote. This will mean that enterprise Admins will have to adjust their regular scripts to connect to Remote PowerShell instead of creating a local session.

Technorati : Exchange Server 2010, PowerShell v2, Remote PowerShell
Del.icio.us : Exchange Server 2010, PowerShell v2, Remote PowerShell
Zooomr : Exchange Server 2010, PowerShell v2, Remote PowerShell
Flickr : Exchange Server 2010, PowerShell v2, Remote PowerShell

DAG in Exchange Server 2010

Anderson Patricio — Tue, 27 Oct 2009 19:45:56 GMT

Hello folks,

I've just read In the UC blog an entry where the UC team states that DAG will be supported on Exchange Server 2010 Standard Edition. Isn't that cool? :)

On the server side, Exchange Server Standard will now support high availability, so all customers can take full advantage of the new database availability group capabilities. Exchange Server Enterprise enables configurations with up to 100 databases per server.

Technorati : DAG, Exchange Server 2010, Standard Edition
Del.icio.us : DAG, Exchange Server 2010, Standard Edition
Zooomr : DAG, Exchange Server 2010, Standard Edition
Flickr : DAG, Exchange Server 2010, Standard Edition

ForeFront Administrators: Action Required by Dec 1st

Anderson Patricio — Thu, 22 Oct 2009 19:35:36 GMT

Hi Folks,

If you use Antigen/ForeFront Security and you are using any of these engines: AhnLab, CA, Sophos and also SpamCure, then you must read the post that the ForeFront Team published. Basically, those ones won't be longer updated as explained below:

The AhnLab, CA, and Sophos engines will be retired on Dec. 1, 2009. After December 1^st, customers will not receive any updates for these retired engines. In order to make sure your Antigen and Forefront products continue to scan efficiently and effectively for malware, any customers running the AhnLab, CA, or Sophos engines must DISABLE these engines before Dec. 1, 2009 and select from the new set of five engines - Authentium, Kaspersky, Microsoft, Norman, and VirusBuster.

Technorati : ForeFront
Del.icio.us : ForeFront
Zooomr : ForeFront
Flickr : ForeFront

Configuring DAG witness in a non-Exchange Server

Anderson Patricio — Fri, 16 Oct 2009 14:48:27 GMT

Hi folks,

Exchange Server 2010 is just around the corner and today we are going over the witness server/directory creation in a regular member server. The first question is why? Well, we already know that in this new release we can have only 2 servers and provide high availability for all roles the essential roles with those two servers. Remember that the same thing was accomplished with 4 servers in Exchange Server 2007 (2 CAS/HUB and 2 MBX - CCR).

However DAG witness has some requirements, such as: it cannot be a member of the DAG; must be in the same forest; it can run on top of Windows Server 2003/2008/2008 R2.

So, if you have only two Exchange Servers and wants to create a DAG a member server must be used as DAG witness server. In order to do that make sure that the group Exchange Trusted Subsystem is added to the local administrators of the server that will be the witness server, as shown in the figure below. After that you will be able to create a DAG using Exchange Management Console.

Cheers,
Anderson Patricio
http://msmvps.org/blogs/AndersonPatricio
http://www.andersonpatricio.org

Technorati : DAG, Exchange Server 2010
Del.icio.us : DAG, Exchange Server 2010
Zooomr : DAG, Exchange Server 2010
Flickr : DAG, Exchange Server 2010

Exchange Server 2010 version-based routing

Anderson Patricio — Thu, 15 Oct 2009 03:10:18 GMT

Hi Folks,

Really nice post from MSExchangeTeam explaining the Exchange 2010 version-based routing. Long story short, Exchange 2010 Hub will communicate only with a Mailbox Exchange 2010, if you have an Exchange Server 2007 Mailbox a Hub 2007 is required to communicate with the legacy mailbox.

By now, you've seen a few of our Spotlight on Exchange 2010 postings. If you have, hopefully you're excited about the great work that has been going on to make Exchange 2010 the best version of Exchange yet. So then the practical side of you kicks in and starts to wonder what it is going to take to start utilizing these new features when the time comes. Certainly, rolling out a new version of Exchange is rarely an endeavor to be entered into lightly.

In the interest of making certain that you can begin planning early and as informed as possible, I want to call out a requirement that we had to put in place for Transport server roles in order to deliver a quality product with cool new features. This requirement is often referred to as "version-based routing" or just "versioned routing."

What this requirement means

Simply put, this requirement means that Exchange 2010 Hub Transport servers and Exchange 2010 Mailbox servers will only communicate with each other. Also, it means that Exchange 2007 Hub Transport servers and Exchange 2007 mailbox servers will only communicate with each other. However, any version Hub is able to communicate (via SMTP) to any other Hub server. So, for a user on Exchange 2007 to be able to send to a user on Exchange 2010 in the same site, the mail must pass through both Hub servers.

Technorati : Exchange Server 2010, interoperability between Mailbox and Hub on 2010
Del.icio.us : Exchange Server 2010, interoperability between Mailbox and Hub on 2010
Zooomr : Exchange Server 2010, interoperability between Mailbox and Hub on 2010
Flickr : Exchange Server 2010, interoperability between Mailbox and Hub on 2010

ForeFront names .. confused? Don't be!

Anderson Patricio — Fri, 02 Oct 2009 18:13:00 GMT

Hi Folks,

Some of the ForeFront names, such as ForeFront Server Security Management Console, ForeFront Protection Manager, ILM or ForeFront Identity Manager make you crazy to figure out which is the name of current version and the next version? Well, the product family is not small and specially at this point they may cause some confusion with so many names.

This page can help you out to memorize the current product names and their future names: http://www.microsoft.com/Forefront/en/us/trial-software.aspx.

Cheers,
Anderson Patricio
http://msmvps.org/blogs/AndersonPatricio
http:/www.andersonpatricio.org

Technorati : ForeFront
Del.icio.us : ForeFront
Zooomr : ForeFront
Flickr : ForeFront

How to renew the self-signed certificate using Exchange 2010 console

Anderson Patricio — Fri, 02 Oct 2009 13:14:38 GMT

Hi Folks,

Exchange Server 2010 introduced the certificate management through Exchange Management Console. In order to manage it, just expand Server Configuration and click on the required server on the left and on the bottom you will see certificates available for that server and at the Toolbox actions you will be able to all available options.

In this post we are going to renew the certificate created during the server installation. Let's click on Renew Exchange Certificate as shown in the figure above, and in the first wizard page we can select the services associated to the certificate.

The renew of the self-signed certiicate will overwrite the current certificate, the console requires a confirmation, just click Yes.

Then, a three step will be performed in background and the results will be displayed in the Completion page. Just click Finish and enjoy your new renewed certificate.

By the way, the process to renew the self-signed certificate using Exchange Management Shell was posted a long time ago but can still be used in Exchange 2010: http://msmvps.com/blogs/andersonpatricio/archive/2008/04/08/how-to-renew-a-built-in-certificate-in-exchange-server-2007.aspx

Cheers,
Anderson Patricio
http://msmvps.org/blogs/AndersonPatricio
http://www.andersonpatricio.org

Technorati : Exchange Server 2010, Managing Certificate, renew, self-signed
Del.icio.us : Exchange Server 2010, Managing Certificate, renew, self-signed
Zooomr : Exchange Server 2010, Managing Certificate, renew, self-signed
Flickr : Exchange Server 2010, Managing Certificate, renew, self-signed

Download Microsoft Forefront Identity Manager 2010 RC1

Anderson Patricio — Thu, 01 Oct 2009 14:47:04 GMT

Forefront Identity Manager 2010 (FIM), formerly known as Identity Lifecycle Manager "2" delivers an integrated identity management solution with powerful self-service capabilities for Office end-users, rich administrative tools and enhanced automation for IT professionals and .NET and WS-* based extensibility for developers. FIM 2010 provides organizations with unique workflow driven solutions to manage user accounts, passwords, groups and distribution lists as well as certificate-based credentials such as smart cards, using identity-based policies that can span across Windows and heterogeneous environments. And when you download the latest beta software, you're automatically registered to access valuable resources assembled in one convenient location.

Microsoft Forefront Identity Manager 2010 is the official name for Microsoft Identity Lifecycle Manager "2". This was announced as part of Microsoft's strategy for Business Ready Security. You will continue to see the ILM "2" name for some time including in the software available below.

Get it from here: http://technet.microsoft.com/en-us/evalcenter/cc872861.aspx

Technorati : ForeFront Identity Manager 2010 RC1, ILM v2, RC1, download
Del.icio.us : ForeFront Identity Manager 2010 RC1, ILM v2, RC1, download
Zooomr : ForeFront Identity Manager 2010 RC1, ILM v2, RC1, download
Flickr : ForeFront Identity Manager 2010 RC1, ILM v2, RC1, download

DPM 2010 Beta available for download

Anderson Patricio — Wed, 30 Sep 2009 21:29:05 GMT

Hello folks,

DPM 2010 beta is available and this beta supports Exchange Server 2010 DAG protection! :)

Overview of DPM 2010: http://www.microsoft.com/systemcenter/dataprotectionmanager/en/us/2010beta-overview.aspx

You can download it from here: https://connect.microsoft.com/Downloads/DownloadDetails.aspx?SiteID=840&DownloadID=22070

Cheers,
Anderson Patricio
http://msmvps.org/blogs/AndersonPatricio
http://www.andersonpatricio.org

Technorati : DAG backup, DPM 2010, Exchange Server 2010
Del.icio.us : DAG backup, DPM 2010, Exchange Server 2010
Zooomr : DAG backup, DPM 2010, Exchange Server 2010
Flickr : DAG backup, DPM 2010, Exchange Server 2010

Exchange Server 2010 and Dumpster 2.0

Anderson Patricio — Mon, 28 Sep 2009 15:54:21 GMT

Hi folks,

MSExchangeTeam blogged about the architectural changes in the Recover Deleted items in Exchange Server 2010.

Users often delete data from their mailboxes that they later want recovered. Recovery of these deleted items is the most common reason for IT admins to recover data from traditional point-in-time backups today.

With previous versions of Exchange Server, administrators implemented two solutions to enable single item recovery, dumpster and restores. Both had their issues, unfortunately.

Exchange 2010 aims to reduce the complexity and administrative costs associated with single item recovery.

Exchange Server 2010: Managing Archive feature #03

Anderson Patricio — Fri, 25 Sep 2009 19:42:17 GMT

Hi folks,

Continuing the Archive Mailbox Week.. Today, we are going to talk about Archive Mailbox Name and Quota.

Change the Archive Mailbox name...

Using Exchange Management Console, we can double click on an user and go to the Mailbox Features tab, and get Properties of Archive item.

Then, we can change the name of the Archive Mailbox ...

and the results can be seen on either Outlook Web App or Outlook 2010.

Changing the warning quota for the Archive Mailbox...

We can also use Exchange Management console to change que Quota Warning, we just need to go to Mailbox Settings and get properties of Archive Quota item.

On the new dialog box we can define the new arning threshold in MB. By the way, we don't have the total quota using GUI, if you want to do that, just use the following syntax: Set-Mailbox <UserName> -ArchiveQuota 2GB

Cheers,
Anderson Patricio
http://www.andersonpatricio.org
http://msmvps.org/blogs/AndersonPatricio

Technorati : Archive Mailbox, Exchange Server 2010, RC
Del.icio.us : Archive Mailbox, Exchange Server 2010, RC
Zooomr : Archive Mailbox, Exchange Server 2010, RC
Flickr : Archive Mailbox, Exchange Server 2010, RC

Exchange Server 2010: Managing Archive feature #02

Anderson Patricio — Wed, 23 Sep 2009 16:07:29 GMT

Hi folks,

In the previous post we saw how to create an Archive Mailbox and also how to enable it in an existent mailbox. Today's post we are going to identify a mailbox that has an Archive Mailbox using Exchange Management Shell and Console and also how to get statistics from an Archive Mailbox.

Identifying an Archive Mailbox...

That is really easy, basically a Mailbox that has an Archive Mailbox has a different icon. We can notice that the user Anderson.Patricio has a different icon than a regular account (Lidiana.Patricio in this example)

We can also use Exchange Management Shell to retrieve that information, we just need the Archive attributes of the mailbox, then let's run the following cmdlet: Get-Mailbox <UserName> | Select archive* | fl. Again, we can notice the differences between those two users (Anderson.Patricio = Archive and Lidiana.Patricio = Just Mailbox).

Getting mailbox statistics from Archive Mailbox...

When the subject is archive the -Archive parameter does the trick as we saw in the previous post. In order to retrieve Mailbox statistics is the same rule, the following syntax will help us out:

Get-MailboxStatistics <UserName> -Archive

Cheers,
Anderson Patricio
http://msmvps.org/blogs/AndersonPatricio
http://www.andersonpatricio.org

Technorati : Archive Mailbox, Exchange Server 2010
Del.icio.us : Archive Mailbox, Exchange Server 2010
Zooomr : Archive Mailbox, Exchange Server 2010
Flickr : Archive Mailbox, Exchange Server 2010

Exchange Server 2010: Managing Archive feature #01

Anderson Patricio — Tue, 22 Sep 2009 15:51:27 GMT

Hi folks,

This week we are going over one of the new features of Exchange Server 2010 which is the Archive Mailbox. In this first post we are going to cover how to create the Archive during the Mailbox creation and also how to enable it afterwards.

Creating and Archive Mailbox during the Mailbox creation...

Using the Release Candidate of Exchange Server 2010 you may have notice that we have a new page called Archive Settings and just clicking on the Create an Archive mailbox for this account will do the trick.

If you are using Exchange Management Shell to do this process, then it is really simple to create the Archive Mailbox in the same process just add the switch -Archive without parameters and the new mailbox will have an Archive Mailbox as well.

Enabling Archive for existent mailboxes...

If you already have the mailboxes created and you want to add Archive mailboxes to them, you can use Exchange Management Console and just click on Enable Archive item on the Toolbox Options and the dialog box shown below will be displayed, just click on Yes.

If you want to do the same using Exchange Management Shell, the cmdlet Enable-Mailbox will be useful. The syntax is:

Enable-Mailbox <Username> -Archive, where <Username> is the username that you want to enable Archive Mailbox.

Cheers,
Anderson Patricio
http://msmvps.org/blogs/AndersonPatricio
http://www.andersonpatricio.org

Technorati : Archive, Exchange Management Console, Exchange Server 2010
Del.icio.us : Archive, Exchange Management Console, Exchange Server 2010
Zooomr : Archive, Exchange Management Console, Exchange Server 2010
Flickr : Archive, Exchange Management Console, Exchange Server 2010

How to broadcast a message from OCS console

Anderson Patricio — Thu, 10 Sep 2009 19:29:00 GMT

Hi folks,

In this post I'm going over the process to broadcast a message using LCScmd to all OCS users. Sometimes you want to warn all users that a server is going down and you can do that in several different sending messages, instant messages and etc. In this post I will go over the process to send a broadcast message to all logged users on OCS.

The first step is make sure that the user that is going to run the LCScmd utility belongs to the RTCUniversalServerAdmins group.

Second step is to open the command promtp and go to X:\Program Files\Common Files\Microsoft Office Communications SErver 2007 R2 folder and run the following syntax and after that hit enter.

LCScmd /Server /Action:BroadcastMessage /Role:SE /Message:"Type here your message"

Done, all users logged users will receive the message, as shown in the figure below. By the way, the output of the previous LCScmd gives you information which users received the message as well.

Cheers,
Anderson Patricio

Technorati : OCS 2007, broadcast message, lcscmd
Del.icio.us : OCS 2007, broadcast message, lcscmd
Zooomr : OCS 2007, broadcast message, lcscmd
Flickr : OCS 2007, broadcast message, lcscmd

OCS 2007 R2 Deploying Certificates document Availabe

Anderson Patricio — Fri, 04 Sep 2009 18:00:28 GMT

Hi folks,

The OCS Team has just blogged about a new document that covers the Certificate Deployment in OCS 2007 R2. It's worth while to read.

Download it here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=e9f86f96-aa09-4dca-9088-f64b4f01c703

Cheers,
Anderson Patricio

Technorati : Certificates, OCS 2007 R2
Del.icio.us : Certificates, OCS 2007 R2
Zooomr : Certificates, OCS 2007 R2
Flickr : Certificates, OCS 2007 R2

Exchange Server 2010 Management Pack (x86) Release Candidate

Anderson Patricio — Wed, 02 Sep 2009 21:54:00 GMT

The Microsoft Exchange Server 2010 management pack is designed for monitoring Exchange Server 2010 events, collecting Exchange component-specific performance counters in one central location, and for raising alerts for operator intervention as necessary. You will need System Center Operations Manager 2007 to run and monitor Exchange Server 2010 with this management pack.

Get it from here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a0047276-553c-4054-afc9-ec3b4ececf3c#tm

Technorati : Exchange Server 2010, RC, SCOM
Del.icio.us : Exchange Server 2010, RC, SCOM
Zooomr : Exchange Server 2010, RC, SCOM
Flickr : Exchange Server 2010, RC, SCOM

Exchange Server 2007 Service Pack 2

Anderson Patricio — Wed, 26 Aug 2009 15:27:10 GMT

Microsoft Exchange Server 2007 Service Pack 2 (SP2) has been designed specifically to help meet the challenges of any business and the needs of all the different groups with a stake in the messaging system. Exchange Server 2007 SP2 is a mission-critical communications tool that enables employees to be more productive and access their information anywhere and anytime while providing a messaging system that enables rich, efficient access to e-mail, calendar items, voice mail, and contacts. For the administrator, Exchange Server 2007 SP2 provides advanced protection options against e-mail security threats, such as spam and viruses, as well as the tools to help manage internal compliance and high availability needs. For an overview of the new features that are available in Exchange Server 2007 SP2, see "What's New in Exchange Server 2007 SP2".

Get it here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4c4bd2a3-5e50-42b0-8bbb-2cc9afe3216a

Technorati : Exchange Server 2007 Service Pack 2
Del.icio.us : Exchange Server 2007 Service Pack 2
Zooomr : Exchange Server 2007 Service Pack 2
Flickr : Exchange Server 2007 Service Pack 2

FPE vs FOPE and Exchange 2010 – Secure messaging with Forefront

Anderson Patricio — Sun, 23 Aug 2009 21:09:27 GMT

Mike Chan, PM for the Forefront team, breaks down the differences between security protection for Forefront Protection for Exchange (FPE), Forefront Online Protection for Exchange (FOPE), and the built-in protection which exists in Exchange 2010. We start out with a brief history of the messaging products and then dig into the details of differences between FPE, FOPE, and Exchange 2010 on the whiteboard at [4:22]. Should you run FPE alone or FPE and FOPE? Watch and decide.

Office Communications Server 2007 R2 Web Scheduler

Anderson Patricio — Sun, 23 Aug 2009 21:04:28 GMT

Web Scheduler is a 64-bit tool for Microsoft Office Communications Server 2007 R2. It provides a Web-based alternative to the add-in for the Microsoft Outlook messaging and collaboration client for the purpose of scheduling a meeting using Office Communications Server 2007 R2. It also provides a browser-based conference management experience that includes operations such as:

Scheduling a new Live Meeting conference or conference call.
Viewing and modifying details of an existing conference.
Listing all existing user schedules of a Microsoft Office conference.
Deleting an existing conference.
Sending an e-mail invitation to conference participants by using a configured SMTP mail server.
Joining an existing conference.

Get it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=6d6848ec-e7d6-41f4-82d9-5bed3526fcbd

Cheers,
Anderson Patricio