July 2010 - Posts
Today I'm going to talk about one of the new features of Exchange Server 2010 Service Pack 1 which allows us to install all Operating System prerequisites using just the Exchange Setup wizard.
In the past I helped to create a script (http://tinyurl.com/yjqf68y) to do all this process but in this new version that script is not required any more.
Basically, when we use the Exchange Server 2010 SP1 Setup wizard, there is a new option called Automatically install Windows Server roles and fetaures required for Exchange Server. Just by clickin on that option all prerequisites will be installed automatically, isn't that cool? :)
The Exchange Setup program will use our ServerManagerCMD in background using a XML answer file to install each Exchange Role prerequisite. All Exchange Setup log files are recorded in the folder C:\ExchangeSEtupLogs and if you look at that folder you will notice a log file for each role (AdminToolsPrereqs.log, CASPrereqs.log, hubprereqs.log, mbxprereqs.log and so forth).
If we open any of them we will validate the command used to install all prerequesites for that specific role.
Comparing the changes made by Exchange Setup..
Roles and Features before Exchange Setup...
Roles and Features after Exchange Setup...
By the way, all prerequs will be installing during the Configuration Prerequisites section in the Readiness Checks page.
BPOS Team released a new page consolidating most of the information required by administrator to start evaluating and planning for a BPOS migration/deployment.
The new deployment page will be a one-stop-shop for prospective and existing partners and customers to find BPOS standard deployment resources, guidance and support.
Some highlights of this first release of the page:
- Introducing the Microsoft Online Deployment Guide for Standard Service (MODG). The MODG is a comprehensive guide to deploying BPOS standard.
- Links to "Migration and Synchronization Help and How-To" as well as the "Setup Accelerator" deployment help wizard
- Links to the Pinpoint marketplace to find partners for deployment
- Links to partner solutions that fill current gaps in our product feature-set
- Links to TechNet deployment forums
Check this out at source: http://blogs.technet.com/b/msonline/archive/2010/07/06/announcing-bpos-deployment-central.aspx
One of the cool features of Exchange Server 2007 Service Pack 3 is the ability to allow end-users to change their expired passwords using Outlook Web Access.
Basically, when you have a user configured with the option User must change password at next logon, then the user won't be able to access OWA right away because it is required to change its password first. However enabling that new feature from Service Pack 3 the user will receive the following page where he is able to change his password.
After changing the password the user will be able to log on OWA without any issues.
By default that
It's a straight forward process, just open Regedit on the Client Acces Server and go to the following key:
Then, add a new DWORD (32-bit value) called ChangeExpiredPasswordEnabled and change the value to 1
Finally, we need to restart the IIS, we can use the IISReset /noforce and that's it.
If you don't want to perform the previous steps, you can use a really simple script that I created for that purpose, check this out: http://msmvps.com/blogs/andersonpatricio/pages/script-enableowapwd-ps1.aspx
Script Name: EnableOWAPwd.ps1 v1 Log: v1.0 - Initial script. Description: Add the ChangeExpiredPasswordEnable entry in the registry and restart IIS using /noforce option. Code: # # EnableOWAPwd.ps1 # Author: Anderson Patricio # http://msmvps.org/blogs...
Microsoft has released Hotfix Rollup 1 for Forefront Protection for Exchange. This article contains information about how to obtain the hotfix rollup and about the issues that are fixed by the hotfix rollup.
Read more at source: http://blogs.technet.com/b/fss/archive/2010/06/30/hotfix-rollup-1-for-forefront-protection-2010-for-exchange-server-is-available.aspx