Hi folks,
If you follow this blog you may have noticed that I started a simple script and it had an updated a couple of weeks ago. Now, fellow MVP Pat Richard (http://www.ucblogs.net/blogs/exchange/default.aspx) added some nice features and I've been using and it saves a lot of time for sure! Thanks Pat Richard!
Read more at source: http://www.ucblogs.net/blogs/exchange/archive/2009/12/12/Automated-prerequisite-installation-via-PowerShell-for-Exchange-Server-2010-on-Windows-Server-2008-R2.aspx
You can also download the script from here: http://www.ucblogs.net/files/folders/powershell/entry125.aspx
Cheers,
Anderson Patricio
http://msmvps.org/Blog/AndersonPatricio
http://www.andersonpatricio.org
Twitter: @apatricio
Hi Folks,
RU 1 was released ( http://support.microsoft.com/kb/976573) and BES is also fully supported on Exchange Server 2010.
Read more at source: http://msexchangeteam.com/archive/2009/12/09/453486.aspx and http://msexchangeteam.com/archive/2009/12/09/453485.aspx
Cheers,
Anderson Patricio
Technorati : BES, Exchange Server 2010, Rollup Update 1
Del.icio.us : BES, Exchange Server 2010, Rollup Update 1
Zooomr : BES, Exchange Server 2010, Rollup Update 1
Flickr : BES, Exchange Server 2010, Rollup Update 1
PFDAVAdmin is not around anymore with Exchange Server 2010 however the exchange team created a new tool called ExFolders.
Six or seven years ago, I was faced with several cases where the permissions on public folders had been made non-canonical by programs running against the M: drive. This was back in the Exchange 2000 days when IFS was still around, and it exposed the M: drive by default. At the time, the only fix we had for this situation was a painful manual process that had to be done one folder at a time. Since I was trying to learn C# at the time, I decided to write a tool to do a bulk fix as a learning exercise. That tool became PFDAVAdmin, so named because it used WebDAV to access and make changes to public folders, and because I kind of saw it as the successor to the old pfadmin/pfinfo tools. The tool soon grew to incorporate other functionality, including exporting/importing permissions and replica lists, exporting properties, enumerating items, accessing mailboxes, etc. PFDAVAdmin gained wide usage in Exchange Support, and an updated version was later released publicly. It wasn't a pretty or polished tool, but it was extremely good at dealing with certain customer scenarios.
A few years later, PFDAVAdmin began showing its age. It had been written for .NET Framework 1.1, and because of Framework 2.0's more restrictive XML parsing, I could not easily move it to the new Framework. It also relied on the presence of certain directory objects which were always there in Exchange 2000 and 2003, but were associated only with the CAS role in 2007.
Read more at source: http://msexchangeteam.com/archive/2009/12/04/453399.aspx
Cheers,
Anderson Patricio
http://msmvps.org/blog/andersonpatricio
Technorati : ExFolders, Exchange Server 2010, PFDavAdmin
Del.icio.us : ExFolders, Exchange Server 2010, PFDavAdmin
Zooomr : ExFolders, Exchange Server 2010, PFDavAdmin
Flickr : ExFolders, Exchange Server 2010, PFDavAdmin
Hi folks,
A friend of mine just asked me about Quota Information to the end-user on the new products. So here a small brief how to retrieve quota information using Outlook 2010 and Outlook Web App.
If you are a happy user and you are using the Outlook Web App, you can hover your mouse over your name on the right side and you will se the current size of your mailbox and limits assigned to you.
If you are using Outlook 2010 there is Quota Information feature that can be turned on or off. Basically, righ click on the bottom bar of your Outlook 2010 and click on Quota Information.
Then, you will notice a quota status on the bottom left corner of your Outloo. Nice, isn't it?
Cheers,
Anderson Patricio
http://msmvps.org/blogs/AndersonPatricio
http://www.andersonpatricio.org
Technorati : Outlook 2010, Outlook Web App, Quota Information
Del.icio.us : Outlook 2010, Outlook Web App, Quota Information
Zooomr : Outlook 2010, Outlook Web App, Quota Information
Flickr : Outlook 2010, Outlook Web App, Quota Information
Update Rollup 1 for Exchange Server 2007 Service Pack 2 (SP2) resolves issues that were found in Exchange Server 2007 SP2 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP2 customers.
For a list of changes that are included in this update rollup, see KB971534.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052.
Get it here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=de91f994-6263-47ef-89d7-6d344997459d
Technorati : Download, Exchange Server 2007 SP2, RU 1
Del.icio.us : Download, Exchange Server 2007 SP2, RU 1
Zooomr : Download, Exchange Server 2007 SP2, RU 1
Flickr : Download, Exchange Server 2007 SP2, RU 1
Hi Folks,
The best way to understand a product is to study its architecture. If you want to learn a little bit more about Hub Transport, then this download is for you.
Many components are involved in the transport of messages through the Exchange Server 2010 mail flow pipeline. The Hub Transport server role diagram can help you understand the role each component plays in the processing of messages that enter the Exchange 2010 mail flow pipeline. Exchange administrators can use this information to help diagnose mail flow problems. The Hub Transport extensibility diagram can help you understand how the agents process a message that is in the Exchange 2010 mail flow pipeline. Developers can use this information to help create third-party agents and applications to work with Exchange 2010.
Get it here: http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6eb8c09a-6ea4-442a-9faa-de33265ceb84&utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+MicrosoftDownloadCenter+%28Microsoft+Download+Center%29#tm
Cheers,
Anderson Patricio
Technorati : Architecture Diagrams, Exchange Server 2010, Transport Server Role
Del.icio.us : Architecture Diagrams, Exchange Server 2010, Transport Server Role
Zooomr : Architecture Diagrams, Exchange Server 2010, Transport Server Role
Flickr : Architecture Diagrams, Exchange Server 2010, Transport Server Role
Hi folks,
Bhargav Shukla (http://www.bhargavs.com) added the Filter Pack installation on the current script and now the script can download and install the Filter Pack.
Great job Bhargav and thanks for sharing this with the community. His blog entry with the script can be seen at his blog http://www.bhargavs.com/index.php/powershell/2009/11/script-to-install-exchange-2010-pre-requisites-for-windows-server-2008-r2/ and also saved his script on this location: http://cid-a9fab8a859bc28e5.skydrive.live.com/self.aspx/.Public/Ex2010-PreRequisites-v2.ps1?ccr=6123
Cheers,
Anderson Patricio
Hi folks,
If you have ever tried to use ServerManagerCMD on Windows Server 2008 R2 probably you will remember this message:
"Servermanagercmd.exe is deprecated, and is not guaranteed to be supported in future releases of Windows. We recommend that you use the Windows PowerShell cmdlets that are available for Server Manager"
So.. which means that we can use the XML files to install the pre-requisites but we should start using the new method which is PowerShell. In order to use PowerShell to add Windows Features we need to know three cmdlets: Get-WindowsFeature, Add-WindowsFeature and Remove-WindowsFeature. If you open a PowerShell prompt on your Windows Server 2008 R2 and you try it won't work because you must enable the modules first, you can accomplish that task using Import-Module ServerManager cmdlet.
Using Exchange Server 2010 documentation has all the code to install all features using PowerShell capabilities, you can find this information at this page: http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2
I'm a kind of lazy guy and I always trt to create scripts to automate regular process like the Exchange Server 2010 pre-requisites. So, using Microsoft documentation I created a script that asks you what you want to install for each role, also configures the NetTCPPortSharing service and gives you the TinyURL to download the Office 2007 Converter. The script is really simple and it can be seen in the figure below:
Get it here: http://msmvps.com/media/p/1739558.aspx] and make sure to rename it to .ps1 before using it.
Get it here: http://cid-a9fab8a859bc28e5.skydrive.live.com/self.aspx/.Public/Ex2010-PreRequisites.rename?sa=717015916 and make sure to rename it to .ps1 before using it.
Thanks to Phil Grainger and Robbie for telling me that MSMVPs.org required password to download. Thank you guys!
Cheers,
Anderson Patricio
Technorati : Add-WindowsFeature, Get-WindowsFeature, PowerShell, Script
Del.icio.us : Add-WindowsFeature, Get-WindowsFeature, PowerShell, Script
Zooomr : Add-WindowsFeature, Get-WindowsFeature, PowerShell, Script
Flickr : Add-WindowsFeature, Get-WindowsFeature, PowerShell, Script
Hi folks,
MSExchange Team released a great tool to help mail administrators to move from their current environment to Exchange Server 2010. The name of this web interface tool is Exchange Deployment Assistant and it can be found at http://technet.microsoft.com/en-ca/exdeploy2010/default.aspx#Home.
At this point the only option available is Upgrade from Exchange Server 2003 and the other transition scenarios will be covered soon.
You will be asked a couple of questions about your environment and based on your answers you will have a list of steps to be performed and those tasks are explained step-by-step which makes really easy a migration procedure.
You can also send a lind of the current step by e-mail clicking on Send or download the checklist (Download Checklist link).
Cheers,
Anderson Patricio
Technorati : Deployment Assistant, Exchange Server 2010, RTM
Del.icio.us : Deployment Assistant, Exchange Server 2010, RTM
Zooomr : Deployment Assistant, Exchange Server 2010, RTM
Flickr : Deployment Assistant, Exchange Server 2010, RTM
Microsoft Forefront Protection 2010 for Exchange Server (FPE) provides fast and effective protection against malware and spam by including multiple scanning engines from industry-leading security partners. It also integrates with Forefront Online Protection for Exchange to provide the defense-in-depth benefits of hosted and on-premise filtering in a single solution.
Get it here: http://www.microsoft.com/downloads/details.aspx?FamilyID=b8a7d36f-cc8d-4335-ae60-8f27c48f3a37&displaylang=en&hash=cAyQs16hHEBYVnB%2bP3agzqA51Mb0PGLnQg%2b%2bugdWiPe0six3xFieUb5SYqPaSRR9Nfw34kg6oUKYiufP%2fPqX0Q%3d%3d#filelist
Technorati : FPE 2010, ForeFront Protection for Exchange Server
Del.icio.us : FPE 2010, ForeFront Protection for Exchange Server
Zooomr : FPE 2010, ForeFront Protection for Exchange Server
Flickr : FPE 2010, ForeFront Protection for Exchange Server
Hi Folks,
MSExchangeTeam released the Storage Calculator for the new version just one day after the release of the RTM version.
The Exchange Mailbox Server role is arguably one of the most important roles within an Exchange deployment for it stores the data that users will ultimately access on a daily basis. Therefore, ensuring that you design the mailbox server role correctly is critical to your design.
With Exchange 2010 you can deploy a solution that leverages mailbox resiliency and has multiple database copies deployed across datacenters, implements single item recovery for data recovery, and has the flexibility in storage design to allow you to deploy on storage area networks utilizing fibre-channel or SATA class disks or on direct attached storage utilizing SAS or SATA class disks with or without RAID protection. But, in order to design your solution, you need to understand the following criteria:
- User profile - the message profile, the mailbox size, and the number of users
- High availability architecture - the number of database copies you plant to deploy, whether the solution will be site resilient, the desired number of mailbox servers
- Server's CPU platform
- Storage architecture - the disk capacity / type and storage solution
- Backup architecture - whether to use hardware or software VSS and the frequency of the backups, or leverage the Exchange native data protection features
- Network architecture - the utilization, throughput, and latency aspects
Read more at source: http://msexchangeteam.com/archive/2009/11/09/453117.aspx
Technorati : Exchange Server 2010, Storage Calculator
Del.icio.us : Exchange Server 2010, Storage Calculator
Zooomr : Exchange Server 2010, Storage Calculator
Flickr : Exchange Server 2010, Storage Calculator
Hi folks,
Exchange Server 2010 RTM has just been released for download at Microsoft download site.
Microsoft Exchange Server 2010 helps IT Professionals achieve new levels of reliability with greater flexibility, enhanced user experiences, and increased protection for business communications.
- Flexible and reliable - Exchange Server 2010 gives you the flexibility to tailor your deployment based on your company's unique needs and a simplified way to keep e-mail continuously available for your users.
- Anywhere access - Exchange Server 2010 helps your users get more done by giving them the freedom to securely access all their communications - e-mail, voice mail, instant messaging, and more - from virtually any platform, Web browser, or device.
- Protection and compliance - Exchange Server 2010 delivers integrated information loss prevention, and compliance tools aimed at helping you simplify the process of protecting your company's communications and meeting regulatory requirements.
This software is intended for evaluation purposes only. You must accept the license terms before you are authorized to use the software. There is no product support for this trial software. You are welcome to participate in the forums to share your trial experiences with others and to ask for advice.
Get it here: http://www.microsoft.com/downloads/details.aspx?familyid=05741f65-2a7b-4070-879f-d74208d6171d&displaylang=en&Hash=p7EU0gyhY4DEbH1Kipa3uP2uqNEJBU6x8oXNokye62E1aoNzVuAdGKn5z%2bpQxA0UMZ9tlXMiGQL%2bhmwYy1%2btbA%3d%3d
Technorati : Exchange Server 2010, RTM, download
Del.icio.us : Exchange Server 2010, RTM, download
Zooomr : Exchange Server 2010, RTM, download
Flickr : Exchange Server 2010, RTM, download
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. :)
Read more at source: http://msexchangeteam.com/archive/2009/11/04/453026.aspx
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
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.
Read more at source: http://msexchangeteam.com/archive/2009/11/02/453016.aspx
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
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.
Read more at source: http://blogs.technet.com/uc/archive/2009/10/27/exchange-2010-revving-the-engines-for-launch.aspx
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
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 1st, 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.
Read more at source: http://blogs.technet.com/fss/archive/2009/10/21/action-required-by-dec-1-2009-keep-your-protection-current.aspx
Technorati : ForeFront
Del.icio.us : ForeFront
Zooomr : ForeFront
Flickr : ForeFront
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
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.
Read more at source: http://msexchangeteam.com/archive/2009/10/14/452859.aspx
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
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
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
More Posts
Next page »