At least Microsoft released the Exchange Server 2010 Architecture Poster.
To download just click on the picture.
One another thing to tomorrow: find the biggest printer 
Author: Ward
Exchange 2007 OWA Redirect Bug Introduced with Exchange 2010 SP1
The Customer where I now work has a mix of Exchange 2007 and Exchange 2010 users. It seems that SP1 has introduced a obvious bug. Before I get into that, I’ll give some background on how Exchange 2010 coexists with previous versions of Exchange.
When you have a mix of Exchange 2010 and older versions in your environment, you have to do a bit of work to make the two work together for your external users. In a nutshell, you use Exchange 2010 Client Access Server (CAS) as your primary entry point for all external users.
Say you use webmail.wardvissers.nl as your externally accessible URL. If an Exchange 2010 user logs in from the Internet, the Exchange 2010 CAS will do its thing and the user will get a nice Outlook Web App screen.
If an Exchange 2007 user logs in using webmail.wardvissers.nl, the Exchange 2010 CAS will redirect the user to an externally accessible Exchange 2007 CAS using a different URL (like legacy.wardvissers.nl). The redirection is silent, but the user may notice their browser changed to legacy.wardvissers.nl
How the redirect is handled is managed by the LegacyRedirectType setting in the Exchange 2010 OWA virtual directory. In most cases, LegacyRedirectType is set to Silent. To see what the setting is in your environment, run:Get-OWAVirtualDirectory -Server <CASservername> | FL Identity, LegacyRedirectType
In SP1, this redirection is no longer silent. When your Exchange 2007 user logs in via webmail.wardvissers.nl, they are presented with this screen:
The text reads:
A temporary change has occurred that requires you to connect to a different server. To connect, click the button below. For security reasons, you’ll be asked to enter your user name and password again.
Sure enough, when you click Connect, you are redirected to legacy.wardvissers.nl, where you have to re-enter your user information.
Thankfully, the same sort of thing doesn’t seem to happen with Outlook Anywhere or ActiveSync clients.
I checked the LegacyRedirectType value on my 2010 SP1 CAS boxes and they are all still set to Silent. The issue occurs because the OWA virtual directory value for LegacyRedirectType is being ignored. This is an extraordinarily unfortunate thing to have been introduced with SP1. If you have a mixed Exchange 2007/2010 environment, I suggest you wait until the rollup 2 is out before deploying SP1.
Update 15 December 2010
Update 2 for Exchange 2010 and the fix is there described 2458419 "A temporary change has occurred that requires you to connect to a different server" error message when Exchange Server 2007 mailbox users try to access their mailboxes by using an Exchange Server 2010 Client Access server
You can download the rollup HERE
Rollup 1 for Exchange Server 2010 SP1
Microsoft released Rollup 1 for Exchange Server 2010 SP1 that fixes the following things.
2028967 Event ID 3022 is logged and you still cannot replicate a public folder from one Exchange Server 2010 server to another
2251610 The email address of a user is updated unexpectedly after you run the Update-Recipient cmdlet on an Exchange Server 2010 server
978292 An IMAP4 client cannot send an email message that has a large attachment in a mixed Exchange Server 2010 and Exchange Server 2003 environment
982004 Exchange Server 2010 users cannot access the public folder
983549 Exchange Server 2010 removes the sender’s email address from the recipient list in a redirected email message
983492 You cannot view updated content of an Exchange Server 2010 public folder
Download Rollup 1 for Exchange Server 2010 SP1 HERE
Exchange SP1 2010 Setting rights with Public Folder Management Console
For Exchange 2007 you had PFDAVAdmin to set rights on the Public Folder store.
For Exchange 2010 (RTM & SP1) you have the tool ExFolder to set rights on the public Folder store.
But the Exchange Team did a great job to add Public Folder Rights to the Public Folder Management Console.
When you right click on the a public folder you can set permission on two ways.
1. Right click on the public folder and choose Manage Settings
I give my self Owner rights for this little demo.
2. Select Properties from the public folder and then select the Permissions tab. 
Data Protection Manager 2010 Operations Guide
Microsoft released a nice manual for monitoring and managing DPM servers and tape libraries, and protected computers that are running Microsoft Exchange Server, Microsoft SQL Server, Windows SharePoint Services, Microsoft Virtual Server, or the Hyper-V role in Windows Server 2008 or Windows Server 2008 R2. This guide also provides instructions for setting up protection of data on desktop computers that are connected to the network, and portable computers that are connected to the network intermittently, and for setting up disaster recovery.
Removing the Browser Choice option During deployment with MDT 2010
The Deployment Guys created a nice script to remove the Browser Choice option.
If you are in the European Union, you will have seen the installation of the Browser Choice option from Windows Update. This is a good thing if you are a consumer, however if you are managing Volume Licensed (VL) builds and you don’t want the Browser Choice in your deployment image.
But you do want to make use of the MDT 2010 ability to go off to Windows Update or your WSUS Server and install patches automatically during your deployment task sequence.
Check HERE how to config MDT to use your WSUS server
MDT 2010 comes with a number of task sequence templates. The one I used many times is the standard client task sequence template. As part of this template there are two tasks for applying Windows updates (Pre-Application Installation and Post-Application Installation).
These tasks are really useful as part of the deployment of a client machine because you have always an up to date image.
As part of this automated Windows Update process KB976002 will be downloaded and installed giving the options shown below in your core image.
Recently KB2019411 has been released which provides information about the Browser Choice update for system administrators who are in managed environments that are under a Volume Licensing program . De Deploymentsguys have created a MDT based script for implementing the suggestions in the article KB2019411. Adding the registry entries to control the display of the Browser Choice screen and to remove the Browser Choice icon from the desktop.
The script (CFG-HideBrowserChoice.wsf) should be placed in the MDT Distribution Share\Scripts folder and then a “Run Command Line” task should be added to your image engineering task sequence (after the last Windows Update task but before the sysprep and image capture tasks). The command you should run is cscript.exe CFG-HideBrowserChoice.wsf.
An example of this is shown below.
When the task runs, the script will turn off the Browser Choice and removes the icon from the desktop. You will also find a log file that the script generates in the usual MDT log location (MININT\SMSOSD\OSDLOGS\CFG-HideBrowserChoice.log)
You can get the CFG-HideBrowserChoice.wsf script from the Deployment Guys SkyDrive by clicking HERE
Tested and I worked great
Source: blogs.technet.com
Free Hyper9 GuessMyOSToo Plug-in for VI3 and vSphere4
This plug-in replaces generic VM icons in the VI3 and vSphere4 client inventory trees with OS-specific icons for both Windows and Linux guests.
System Requirements
The only requirement is Virtual Center 2.5 or higher. The Hyper9 product is NOT required.
Download HERE
Update 1 for Microsoft Forefront Threat Management Gateway (TMG) 2010 Service Pack 1
Microsoft released some days ago Forefront TMG Update 1:
SafeSearch Enforcement. Forefront TMG can enforce blocking adult text, images and videos from search results by popular search engines. SafeSearch can be enforced on specific groups or to the entire organization.
Including non-primary URL filtering categorizations. Forefront TMG uses an algorithm to select a URL’s “primary” category from among up to four categorizations provided by Microsoft Reputation Services (MRS). In Update 1 you can control access to sites that match any of the non-primary categorizations provided by MRS. For example, a URL with a primary categorization of News can now match a rule by any of its non-primary categorizations (such as Web Mail).
Support for Exchange 2010 SP1
Bug fixes and various other improvements. For details, see http://go.microsoft.com/fwlink/?LinkId=201151.
MDT The task sequence has been suspended.
The error was: The task sequence has been suspended.
LiteTouch has encountered and Environment Error (Boot into WinPE)
I had a strange problem with MDT. When I booted the in WinPE.
Rebooting and again started the WinPE image did nothing same error again.
Solution is very simple.
You have to remove two directory’s C:\_SMSTaskSequence\nul and C:\MININT
After that you can resume deploying the OS TaskSequence you want.
For sure I cleaned the Disk with Diskpart.
Rollup 1 for Exchange Server 2007 Service Pack 3
Microsoft had released some day’s ago Rollup 1 for Exchange Server 2007 Service Pack 3
In this release two important things are fixed when you have a CCR Cluster
– Log Truncation is failing on a CCR cluster after installing SP3
– Exchange Writer should return TRUE for retry able errors
The whole list with fixes can you find HERE
Download Rollup 1 for Exchange Server 2007 Service Pack 3 HERE