Just click on the picture 
Windows Server 2008 R2 Hyper-V Component Architecture Poster with Service Pack 1
Just click on the picture
Category: Microsoft
Deploy office 2010 and a previous office version together on one PC with MDT 2010
Deploy office 2010 and a previous office version together on one PC with MDT 2010. Then you need to do the following things
Needed.
– Office 2010 ISO
– Office 2010 Administrative Template files (ADM, ADMX/ADML) and Office Customization Tool
1. Make sure you have a working Office 2007 deployment. Check this How to deploy Office 2007 with MDT
2. Extract the Office 2010 ISO to the application folder on de MDT Server
2. Extract AdminTemplates_32.exe or AdminTemplates_64.exe to a folder.
3. Copy the Admin folder that you can find in the extracted folder to the Office 2010 folder that you created at step 1.
4. Run setup.exe /admin
5. Check the Screenshots for the settings 
6. Save the file in Updates folder that you find in Office folder. I named the file setup.MSP
7. Create a new application without source files.
Command Line is:
setup.exe /adminfile “\\mdtservername\deploymentshare$\Applications\Microsoft Office 2010 x86\Updates\setup.msp”
Exchange 2010 RPC Encryption Requirement
Current Status: Non-issue
Exchange 2010 SP1
With Exchange 2010 RTM, the RPC encryption requirement was an issue with mitigation. However, in Exchange Server 2010 Service Pack 1, the RPC encryption requirement has been disabled by default. This means that any new Exchange 2010 SP1 Client Access Servers (CAS) deployed in the organization won’t require encryption and Outlook 2003 clients will connect without the need to enable the RPC encryption feature in the Outlook profile.
Important
Having the RPC encryption requirement on an Exchange 2010 CAS server disabled doesn’t lower the security between Outlook 2007/2010 and any Exchange 2010 CAS server. RPC communication for these Outlook versions will remain encrypted as long as the client has the RPC encryption feature enabled. It’s only the requirement itself that is disabled on the Exchange 2010 CAS server.
Exchange 2010 CAS servers deployed prior to Service Pack 1, or upgraded to Service Pack 1, will retain the existing RPC encryption requirement setting.
Exchange 2010 RTM
When upgrading or migrating an organization that fully or partly uses Outlook 2003 to Exchange 2010, we hear there are out of the box problems, when trying to connect an Outlook 2003 client to an Exchange 2010 RTM mailbox? We heard this is because an Exchange 2010 RTM Client Access Server by default requires an Outlook client to support RPC encrypted traffic in order to be able to connect.
While it’s true the default configuration of an Outlook 2003 client doesn’t have support for RPC encryption, this requirement is fully supported with Outlook 2003.
There are two methods that can be used in order to have Outlook 2003 clients connect to an Exchange 2010 RTM mailbox:
Method 1: Enable the RPC encryption support in Outlook 2003
If “Encrypt data between Microsoft Office Outlook and Microsoft Exchange Server” is enabled under the “Security” tab in the Outlook 2003 profile (see figure 1), the client will be able to connect to an Exchange 2010 RTM mailbox.
Figure 1: RPC Encryption enabled in Outlook 2003
If you are working with or for a small organization, it may be acceptable the end user enables this feature manually, but if you have thousands of users in the organization, you would want to enable it using a group policy (GPO). The steps necessary to implement a GPO to enable this setting are included in this KB article.
Important
The “EnableRPCEncryption” registry key mentioned in the KB article was originally introduced via a hotfix for Outlook 2003 SP2. This means that clients that either runs Outlook 2003 SP2 or an older version of Outlook 2003 doesn’t respect this registry key. In addition, Outlook 2003 clients not running SP3 are not supported by Microsoft.
Method 2: Disable the RPC Encryption requirement on the Client Access Servers
Instead of enabling support for RPC encryption in the Outlook 2003 profiles, you also have the option of disabling the requirement for RPC encryption on all Exchange 2010 RTM Client Access Servers in the organization.
This can be accomplished using the Set-RpcClientAccess cmdlet:
Set-RpcClientAccess –Server Exchange_server_name –EncryptionRequired $False
Figure 2: RPC Encryption requirement disabled on Exchange 2010 CAS servers
As mentioned earlier Exchange 2010 SP1 servers that hasn’t been upgraded from Exchange 2010 RTM has the RPC encryption requirement disabled by default.
The following KB article describes the symptoms and remediation in detail:
The core Exchange 2010 TechNet documentation also describes the configuration that can be used to remediate the issue:
Important
Unmanaged client machines cannot be controlled using GPOs or login scripts. If you have unmanaged machines connecting to Exchange 2010 using Outlook 2003, one solution would be to send those users a script or a registry file which they can run manually on their machine to enable the RPC encryption setting.
Special Thanks to Henrik Walther
Exchange 2010 Exchange Server name appears as Instance – <GUID>
Current Status: Issue – no issue
A few customers, partners, and individual folks in the Exchange community have reported that a few of the Exchange 2010 users running Outlook 2003 randomly have issues connecting to their mailbox. After examining the mail profile in Outlook 2003, you can see the Exchange server name appears as Instance-<GUID> where <GUID> is a randomly generated GUID (or number). Re-resolving (‘Check Name’) the appropriate server name in the Outlook mail profile resolves the issue.
Figure 11: Instance-GUID issue in Outlook 2003
Note
Seeing Instance-<GUID> in conversation between an Outlook 2003 client and an Exchange 2010 server is normal (when Instance-<GUID> appears inside Outlook in the folders list view on left hand side); It does NOT mean you are hitting this particular issue. You experience this issue if the Outlook mail profile gets updated to refer to the Exchange server as Instance-GUID.
The problem behavior can be triggered by networking issues, patch applications, server reboots, etc. It requires Outlook 2003 to lose connectivity to Exchange and have a delegate mailbox logon attempted on a connection before the primary mailbox logon is attempted on that connection. This can affect users who are accessing shared mailboxes or folders of other users from their Outlook 2003 while connecting to Exchange 2010.
Currently there is no proper resolution available for this issue. However, to remediate this issue temporarily, simply re-resolve the Exchange server name in the Outlook mail profile. If possible, you may also remove the shared mailboxes or shared folders (like calendars) from the profile, preventing this issue from occurring in the future or create a new mail profile in Outlook.
Microsoft is working to investigate this issue for a fix. You can contact Microsoft Support to report this issue and request further assistance. Currently no KB article exists for this issue.
Update:
Microsoft has confirmed this to be a bug and the bug was assigned to the Outlook team within Microsoft. It has been fixed and a hotfix can be downloaded here: http://support.microsoft.com/kb/2510153
Special Thanks to Henrik Walther & Jaap Wesselius
SCVMM RDS Connection Broker plugin released
SCVMM RDV plug-in enables dynamic placement of VDI VMs for both personal and pooled VMs. The key benefit of using this plug-in is that it reduces the number of Hyper-V servers required since VMs are placed on demand rather than statically placed. Dynamic placement is achieved by integrating SCVMM 2008 R2 with the RDS Connection Broker in Windows Server 2008 R2.
Dynamic Placement for Personal VM is available in Windows Server 2008 R2. Pooled VM requires Windows Server 2008 R2 SP1.
Figure below shows the integration:
The bits and content are available at: http://go.microsoft.com/fwlink/?LinkID=195952
For those of you that don’t understand how this works Ill write a little process workflow so you understand.
1. The VDI client tries to connect to the last VM it was using via the Connection Broker.
2. The Broker, knowing where it was in the cluster, in communication with SCVMM, tries to wake the VM from a save state
3. Problem is that the server its trying to start the VM on is already at capacity and it cant start there
4. SCVMM gets involved as part of this and moves the VM to another node in the cluster based on its dynamic placement algorithm, via a SAN move
5. The Connection Broker is then told which host the VM is now on and running
6. The user connects to the VM
Nice huh 
Microsoft Desktop Virtualization is going to be a real competitor against VMware View
Microsoft Lync Server 2010 Documentation
Migrating from Communications Server 2007 to Lync Server 2010
This document provides guidance from migration from Office Communications Server 2007 to Microsoft Lync Server 2010.
Microsoft Lync Server 2010 Device Management and Troubleshooting Guide
The purpose of the Microsoft Lync Server 2010 Device Management and Troubleshooting Guide is to provide guidance on how to manage and update devices. It is also intended to answer frequently asked questions. This document identifies supported topologies, configurations, and scenarios described in detail in the Lync Server device deployment and planning documentation.
Microsoft Lync Server 2010 Reference: Call Data Recording and Quality of Experience Database Schema
This document describes the call detail recording (CDR) and the Quality of Experience (QoE) databases schemas in Microsoft Lync Server 2010.
Microsoft Lync Server 2010 Group Chat Administration Guide
This document guides you through the process of administering Lync Server 2010 Group Chat Server and the related components that are required to let organizations set up searchable, topic-based chat rooms that persist over time, allowing geographically distributed teams to better collaborate with one another while preserving organizational knowledge.
Migrating from Communications Server 2007 R2 to Lync Server 2010
This document provides guidance from migration from Office Communications Server 2007 R2 to Microsoft Lync Server 2010.
Microsoft Lync Server 2010 Monitoring Deployment Guide
This document guides you through the process of deploying Lync Server 2010 Monitoring Server.
Microsoft Lync Server 2010 Announcement Deployment Guide
This download guides you through the process of configuring the Announcement call management feature for Enterprise Voice.
Microsoft Lync Server 2010 Archiving Deployment Guide
The purpose of the Microsoft Lync Server 2010 Archiving Deployment Guide is to guide you through the process of deploying Lync Server 2010 Archiving Server and the related components that are required to support archiving of instant messaging and web conferencing (meeting) content.
Microsoft Lync Server 2010 Group Chat Deployment Guide
This document guides you through the process of migrating and deploying Lync Server 2010 Group Chat Server and the related components that are required to let organizations set up searchable, topic-based chat rooms that persist over time, allowing geographically distributed teams to better collaborate with one another while preserving organizational knowledge.
Microsoft Lync Server 2010 Client and Device Deployment Guide
This download guides you through the process of deploying client software and devices for Lync 2010.
Microsoft Lync Server 2010 Call Park Deployment Guide
This download guides you through the process of configuring the Call Park call management feature for Enterprise Voice.
Microsoft Lync Server 2010 Enterprise Voice Guide
This download contains two documents: Deploying Enterprise Voice at Central sites and Deploying Branch Sites
Enabling QoS with Microsoft Lync Server 2010
If your Windows Server network supports Quality of Service (QoS) management, you can take advantage of this functionality to optimize media traffic in your Microsoft Lync Server 2010 deployment. This guide shows you how.
Microsoft Lync Server 2010 Response Group Deployment Guide
This download guides you through the process of configuring the Response Group feature for Enterprise Voice.
Microsoft Lync Server 2010 Edge Server Deployment Guide
This document guides you through the process of deploying Lync Server 2010 edge servers and Directors.
Microsoft Lync Server 2010 Standard Edition Deployment Guide
This document guides you through the process of deploying Lync Server 2010 Standard Edition and configuring dial-in conferencing.
Microsoft Lync Server 2010 Active Directory Guide
This document guides you through the process of preparing Active Directory for Microsoft Lync Server 2010 and includes the Active Directory schema reference.
Microsoft Lync Server 2010 Enterprise Edition Deployment Guide
This document guides you through the process of deploying Lync Server 2010 Enterprise Edition and configuring dial-in conferencing for Lync Server 2010.
Microsoft Lync Server 2010 Supportability Guide
This guide provides a central, high-level reference for supported server topologies and configurations and supported client configurations. It is also intended to answer frequently asked questions. This document identifies supported topologies, configurations, and scenarios described in detail in the Lync Server deployment and planning documentation.
Microsoft Lync Server 2010 Planning Guide
This document contains information for planning a deployment of Lync Server 2010 and Lync clients.
Storage Solutions for Exchange 2010
Compellent
5000 Mailboxes or greater
Dell
1-1000 Mailboxes
1001-5000 Mailboxes
- Dell PowerEdge R510 Near line SAS 1100 Mailboxes using Mailbox Resiliency Exchange 2010 Storage Solution (Oct 3, 2010)
- Dell PowerEdge R510 near line SAS 4000 mailbox Exchange 2010 Mailbox Resiliency Storage Solution (June 23, 2010)
5000 Mailboxes or greater
- Dell PowerVault MD1200 Nearline SAS 7,200 Mailbox Microsoft Exchange 2010 Mailbox Resiliency Storage Solution (Jun 8, 2010)
- Dell PowerVault MD1200 7200 Mailbox Resiliency Exchange 2010 Storage Solution (April 25, 2010)
EMC
1-1000 Mailboxes
- EMC Celerra NX4 500 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Aug 31, 2010)
- EMC Iomega ix12-300r 260 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Jun 16, 2010)
- EMC CLARiiON CX4-120 1,000 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Jun 7, 2010)
- EMC CLARiiON AX4-5i 500 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (March 3, 2010)
1001-5000 Mailboxes
5000 Mailboxes or greater
Fujitsu
1001-5000 Mailboxes
HDS
5000 Mailboxes or greater
- Hitachi Adaptable Modular Storage 2500 Dynamically Provisioned 22,880 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Dec 8, 2010)
- Hitachi Adaptable Modular Storage 2300 Dynamically Provisioned 58,400 User Exchange 2010 Mailbox Resiliency Storage Solution (Oct 30, 2010)
- Hitachi Adaptable Modular Storage 2500 Dynamically Provisioned 40,800 User Exchange 2010 Mailbox Resiliency Storage Solution (Oct 3, 2010)
- Hitachi Adaptable Modular Storage 2300 Dynamically Provisioned 20,000 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Aug 31, 2010)
- Hitachi Adaptable Modular Storage 2100 Dynamically Provisioned 5,800 mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Aug 3, 2010)
- Hitachi Adaptable Modular Storage 2100 Dynamically Provisioned 9,440 mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Aug 3, 2010)
- Hitachi Adaptable Modular Storage 2100 Dynamically Provisioned 28,000 mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Aug 3, 2010)
- Hitachi Adaptable Modular Storage 2500 Dynamically Provisioned 100,800 mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Aug 3, 2010)
- Hitachi Adaptable Modular Storage 2300 Dynamically Provisioned 34,300 User Exchange 2010 Resiliency Storage Solution (May 15, 2010)
- Hitachi Adaptable Modular Storage 2500 Dynamically Provisioned 68,800 User Exchange 2010 Resiliency Storage Solution (May 15, 2010)
- Hitachi Adaptable Modular Storage 2100 Dynamically Provisioned 17,200 User Exchange 2010 Mailbox Resiliency Storage Solution (May 4, 2010)
HP
1001-5000 Mailboxes
- HP StorageWorks P2000 G3 Serial Attached SCSI Modular Smart Array 2,000 mailbox Exchange Server 2010 Mailbox Resiliency storage solution (Oct 3, 2010)
- HP StorageWorks P2000 Fibre Channel Modular Smart Array 4,005 mailbox Exchange Server 2010 Mailbox Resiliency Storage Solution (Jul 20, 2010)
- HP Smart Array P411 controller and Storage Works D2600 disk enclosures 3,000 mailbox Exchange 2010 Mailbox Resiliency storage solution (June 21, 2010)
- HP StorageWorks 2000sa Modular Smart Array 4,000 user Exchange Server 2010 Mailbox Resiliency solution (May 20, 2010)
- HP StorageWorks 600 Modular Disk System 4,000 user – 3GB Mailbox Resiliency Exchange 2010 storage solution (May 10, 2010)
5000 Mailboxes or greater
- HP Smart Array P411 controller and Storage Works D2600 disk enclosures 6,000 mailbox Exchange 2010 Mailbox Resiliency storage solution (June 21, 2010)
- HP StorageWorks 600 Modular Disk System 7,500 user – 3GB Mailbox Resiliency Exchange 2010 storage solution (May 15, 2010)
- HP StorageWorks 8400 Enterprise Virtual Array 9,000 mailbox Exchange 2010 Mailbox Resiliency Storage Solution (March 25, 2010)
IBM
5000 Mailboxes or greater
- IBM System Storage DS8700 20,000 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Dec 16, 2010)
- IBM XIV Storage System Model 2810 40,000 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (June 21, 2010)
- IBM System Storage™ SAN Volume Controller 5.1 Entry Edition and DS3400 36,000 Mailbox Resiliency Exchange 2010 Storage Solution (Jan 20th, 2010)
- IBM XIV Storage System Model 2810 40,000 Mailbox Resiliency Exchange 2010 Storage Solution (Jan 10, 2010)
NetApp
1001-5000 Mailboxes
5000 Mailboxes or greater
- NetApp FAS3210 6,000 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Nov 20, 2010)
- NetApp FAS3140 12,000 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (July 15, 2010)
Oracle (Sun)
5000 Mailboxes or greater
- Sun ZFS Storage 7320 Appliance 10,000 Mailbox Exchange 2010 Mailbox Resiliency Solution (Jan 10, 2011)
- Sun ZFS Storage 7420 Appliance 32,000 Mailbox Exchange 2010 Mailbox Resiliency Storage Solution (Jan 10, 2011)
Xiotech
1-1000 Mailboxes
1001-5000 Mailboxes
- Xiotech Emprise 5000 4,000 Mailbox Microsoft Exchange 2010 Mailbox Resiliency Storage Solution (Sep 9, 2010)
- Xiotech Emprise 5000 3,000 Mailbox Microsoft Exchange 2010 Mailbox Storage Solution (Jun 8, 2010)
5000 Mailboxes or greater
Hardware Load Balancers for Exchange Server 2010
Listed below are hardware load balancers that have been tested by the vendor and reviewed by Microsoft to meet Exchange Server 2010 requirements. It is recommended that you visit the vendor’s web site for the latest information regarding product specifications, capacity, country support and documentation including release notes and known issues. Please contact the vendor for more information on these products.
Hardware Load Balancers for Exchange Server 2010
|
Vendor |
Qualified Product |
Software Version Tested |
Vendor’s Exchange Page |
|
Barracuda Load Balancer Model 340, 440, 640 |
3.3.1.005 |
||
|
Brocade |
ServerIron ADX 1000, 4000, 10000 |
V12.1 |
|
|
Cisco |
Application Control Engine (ACE) |
A2(3.0) |
|
|
Equalizer E250GX, E350GX, E450GX, E650GX |
8.6.0b |
||
|
Netscaler |
9.1.102.8 |
||
|
BIG-IP Local Traffic Manager (LTM) |
10.0.1 and 10.1 |
||
|
LoadMaster Models: 2200, 2500, 2600, 3500, 3600, 5500 |
5.1-28 |
Kemp Technologies is added to list. This is a nice thing because the customer where I work have 2 new load balancers 
.
How to demote a Exchange 2007 CCR Cluster with Load balanced CAS/HUB Servers
I used the following steps to do this.
1. All public folders and system folders that are housed on the Exchange 2007 CCR Cluster computer must be replicated to another Exchange 2007/2010 computer that is in the site.
2. Verify the contents of the public folder store with the following Powershell commands
Get-PublicFolderStatistics -server <Exchange 2007_Server_Name> | fl | out-file d:\PFstat.txt
Get-PublicFolder -server < Exchange 2007_Server_Name > \ -recurse | fl | out-file d:\PFIPMSub.txt
Get-PublicFolder -server < Exchange 2007_Server_Name > \non_ipm_subtree -recurse | fl | out-file d:\PFNonIPMSub.txt.
3. Remove the replicas from the public folder store
MoveAllReplicas.ps1 -Server ccrclustername –NewServer newservername
4. Remove the public folder store
Remove–PublicFolderDatabase –Identity "Public_Folder_Store_Name"
5. Change the server that is responsible for generating the Offline Address Lists
Move-OfflineAddressBook –Identity OfflineAddressBookIdParameter -Server ServerIdParameter
6. Move the Routing Group Connectors by using the following command:
Get-RoutingGroupConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -SourceTransportServers "<Second Exchange 2007 server>"
Get-RoutingGroupConnector | where {$_.TargetTransportServers -like "<First Exchange 2007 server>"} | Set-RoutingGroupConnector -TargetTransportServers <Second Exchange 2007 server>
7. To modify any Send connectors that have the first Exchange 2007 server as the source transport server, run the following commands:
Get-SendConnector | where {$_.SourceTransportServers -like "<First Exchange 2007 server>"} | Set-SendConnector -SourceTransportServers "<Second Exchange 2007 server>"
8.Important:
How to use the Exchange Server SP1 2007 Setup wizard to remove Exchange 2007
-
Log on to the server from which you want to remove Exchange 2007.
-
Open Control Panel, and then double-click Programs and Features.
-
In Programs and Features, select Microsoft Exchange Server 2007, and then click Uninstall.
If you click Change instead of Uninstall, you can add server roles, but you cannot remove server roles.
-
In the Exchange Server 2007 SP1 Setup wizard, on the Exchange Maintenance Mode page, click Next.
-
On the Server Role Selection page, clear all the server role check boxes, clear the Management Tools check box, and then click Next.
By default, all server roles are selected. This indicates that no server roles will be removed. To remove a server role, you must clear the appropriate check box.
-
On the Readiness Checks page, after the check completes, click Uninstall.
-
On the Completion page, click Finish.
-
(Optional) If you are removing Exchange from a Mailbox server, remove the Exchange database files (*.edb) and storage group log files (*.log).
If you reinstall the Mailbox server role on this server, you must first remove the database and log files from the server.
-
(Optional) Remove the setup log files that are located at %systemdrive%\ExchangeSetupLogs.
-
(Optional) Remove the following virtual servers that are created for Exchange 2007 under the Default Web Site in IIS:
- Microsoft-Server-ActiveSync
- OAB
- Owa
When you remove Exchange 2007, neither IIS nor these virtual servers are removed
9. First Remove the Passive Mailbox Node
10. Second the Primary Mailbox Role
11. Remove the CAS/HUB’s Role on the nodes
Important: NOT AT THE SAME TIME
12. Demote the Cluster
13. Demote the NLB Cluster
14. Remove the Servers from the domain
15. Shutdown the Servers
16. Take a cold bier when you are don with testing and everything works 
Exchange 2010 Free space within a Mailbox Database
In previous versions of Exchange Server there was a process called "online maintenance". This process ran at night and one of the tasks was to an online defragmentation to do within the database. The task was that the empty spaces are grouped together resulting in more efficient use of the Mailbox Database.
In Exchange 2010 has changed and there is a 24×7 online process. There is also the option of online, direct to see how much space is available within the databases with the Powershell command:
Get-MailboxDatabase –Status | fl Name,AvailableNewMailboxSpace
Output:
If we were to do an offline defragmentation on the Mailbox Database the mailbox database would be approximately a 90MB smaller.
This is on my test Exchange 2010 server with only a few mailboxes. In normal production enjoinment this will be a lot more.
In Exchange 2010 you can you a online mailbox move. There fore you can
better create a new mailbox database en move all the mailboxes to the new mailbox database.
Then you have the same result with no down time.