1. Install the proper operating system and name the new server with the same name as the lost server. Recovery won’t succeed if the server on which recovery is being performed doesn’t have the same name as the lost server.

2. Join the server to the same domain as the lost server.

3. Install the following 2008 R2 HotFixes

The following hotfixes are required for the Client Access server for Windows Server 2008 R2:

• Install the update described in Knowledge Base article 979099, An update is available to remove the application manifest expiry feature from AD RMS clients. Without this update, the AD RMS features may stop working.
• Install the hotfix described in Knowledge Base article 982867, WCF services that are hosted by computers together with a NLB fail in .NET Framework 3.5 SP1. For more information, see these MSDN Code Gallery pages:
  • For additional background information, see KB982867 – WCF: Enable WebHeader settings on the RST/SCT.
  • For the available downloads, see KB982867 – WCF: Enable WebHeader settings on the RST/SCT.
• Install the update described in Knowledge Base article 979744, A .NET Framework 2.0-based Multi-AppDomain application stops responding when you run the application.
• Install the update described in Knowledge Base article 983440, An ASP.NET 2.0 hotfix rollup package is available for Windows 7 and for Windows Server 2008 R2. For more information, see these MSDN Code Gallery pages:
  • For additional background information, see KB983440 – Win7 rollup package (PR for QFE 810219).
  • For the available downloads, see KB983440 – Win7 rollup package (PR for QFE 810219).
• Install the update described in Knowledge Base article 977020, FIX: An application that is based on the Microsoft .NET Framework 2.0 Service Pack 2 and that invokes a Web service call asynchronously throws an exception on a computer that is running Windows 7.

4. Set-Service NetTcpPortSharing -StartupType Automatic

5. RUN –> E:\Setup.com /m:recoverserver /InstallWindowsComponents

Outlook 2003 Service Pack 3 Clients
Issue:
During normal working hours users randomly was unable to access their mailboxes when they launched their Outlook client.

The users were receiving the following Outlook message:

“Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.”
It was also reported that some users had issues expanding additional mailboxes. (Delegate Mailboxes )
The following Outlook message appeared.

Or users have issues opening Shared Calendars.

Solution:
http://support.microsoft.com/kb/2299468

With Get-ThrottlingPolicy you can see the value of RCAMaxConcurrency

(Exchange 2010 RTM default value 20) (Exchange 2010 SP1 default value 214748364)

I changed RCAMaxConcurrency to 214748364 and the problem is fixt:

Get-ThrottlingPolicy | set-ThrottlingPolicy -RCAMaxConcurrency 214748364

Today the Exchange Team released Rollup 2 for Exchange Server 2010 Service Pack 1 (KB2425179). This update raises Exchange 2010 version number to 14.1.270.1.

If your upgrading from Exchange 2007 you need to implement this rollup because the bug Exchange 2007 OWA redirect bug with Exchange 2010 sp1 is fixed check: kb2458419

The List with Fixes:

983186 The mailbox alias of a user contains the "?" character unexpectedly after you run the "Enable-Mailbox" cmdlet to create a mailbox for the user in an Exchange Server 2010 environment

2295902 An excepted occurrence is not excluded from a recurring iCalendar message for an Exchange Server 2010 mailbox user

2385017 You cannot edit public folder items even though you are the owner of the items in an Exchange Server 2010 environment

2385194 You cannot connect to an Exchange Server 2010 mailbox by using a MAPI application when a Mailbox server and a Client Access server are installed on different computers

2397171 You cannot reply or forward a large email message on an Exchange Server 2010 mailbox

2403783 An incorrect label is displayed in the date field in a public folder item when you open the item by using OWA in an Exchange Server 2010 environment

2408924 The subject of an item is deleted when you use the "UploadItems" operation together with the "Update" action or the "UpdateOrCreate" action in an Exchange Server 2010 environment

2409597 You cannot open a public folder item when the default public folder database for the mailbox database is unavailable in an Exchange Server 2010 environment

2423776 The Exchange Information Store service crashes frequently during a public folder replication process on an Exchange Server 2010 public folder

2431500 You cannot connect to an Exchange Server 2010 mailbox simultaneously by using Outlook Anywhere from several Windows XP-based computers

2433642 The "FETCH (BODYSTRUCTURE)" command returns a corrupted file name of an email message attachment on an Exchange Server 2010 computer

2452075 You cannot connect to mailboxes in a recovery database on a server after you install Exchange Server 2010 SP1

2458005  The Exchange Mailbox Replication service crashes when you use the "New-MailboxImportRequest" command to import a PST file to an Exchange Server 2010 mailbox

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

2322161 The replay queue length on passive copies of mailbox databases in Database Availability Group continues to increase in an Exchange Server 2010 environment

982004 Exchange Server 2010 users cannot access the public folder

983492 You cannot view updated content of an Exchange Server 2010 public folder

983549 Exchange Server 2010 removes the sender’s email address from the recipient list in a redirected email message

Download the Hotfix HERE

Before the rollup 1 they were previously multipart/alternative messages with both text/plain and text/html subparts.

Solution:
You can set in through in the GUI or using Powershell to set the value to 0 text only

ImapMessagesRetrievalMimeFormat:
0:Text Only
1:HTML Only
2:HTML and Alternative Text
3:Enriched Text Only
4:Enriched Text and Alternative Text
5:Best Body Format

Exchange Management Console:

1. In the console tree, expand Server Configuration, and then click Client Access.

2. In the work pane, click the POP3 and IMAP4 tab.

3. In the work pane, select IMAP4 and then, in the result pane, click Properties.

4. On the IMAP4 Properties page, click the Retrieval Settings tab.

5. In the Message Retrieval pane, select a message format from the drop-down list under Message MIME format. I choies for 0

6. Click Apply, and then click OK to save your changes.

Powershell:

Set-CASMailbox -Identity yourcasserverhere -PopMessagesRetrievalMimeFormat 0

MAPI or an unspecified service provider. ID no: 00000000-0000-00000000

Solution is very easy: Give yoursell full access rights to a mailbox

Add-MailboxPermission -identity "user" -Accessrights FULLACCESS -User "yourusername"

When you want to import some pst’s you need some rights from doing this. This is a one time setting.

New-ManagementRoleAssignment ?Role ?Mailbox Import Export? ?User Administrator

Name                           Role              RoleAssigneeName  RoleAssigneeType  AssignmentMethod  EffectiveUserName

—-                           —-              —————-  —————-  —————-  —————-

Mailbox Import Export-Admin… Mailbox Import… Administrator     User              Direc

Set Mailbox Language

Set-MailboxRegionalConfiguration -Identity ward -Language nl-nl -DateFormat "dd-mm-yyyy

If you want this for multiple mailboxes you case the following script

$a=get-Mailbox *
$a | Set-MailboxRegionalConfiguration -language nl-nl -DateFormat "dd-mm-yyyy

Import a mailbox

New-MailboxImportRequest -Mailbox ward -FilePath \\win701\c$\ward.pst

Remove  newmailimportRequest

Get-MailboxImportRequest -Status Completed | Remove-MailboxImportRequest

Status

Get-MailboxImportRequest | Get-MailboxImportRequestStatistics | ft TargetAlias,Percent*,BytesTransferred*

Multiple Mailboxes at the same time

Dir \\win701\c$\Exmerge-PSTS\*.pst | %{

    New-MailboxImportRequest ?Name ImportOfPst ?BatchName ImportPstFiles `

        ?Mailbox $_.BaseName ?FilePath $_.FullName

}

The property is MSExchDelegateListLink. You can check it with adsiedit.

When you open now Outlook 2010 you can now see that Wardtest is automatilly Added

And additional mailboxes is empty

When you migrating from Exchange 2007 to Exchange 2010 and upgraded the Clients to Outlook 2010
Use dis script to set the MSExchDelegateListLink object automatically. Test I first. It’s your own risk.

$a=get-MailboxPermission * | where {$_.IsInherited –eq $False –and $_.accessrights –eq “FullAccess”}
$a | remove-MailboxPermission –confirm:$false
$a | add-MailboxPermission

Save the scripts to MSExchDelegateListLink.ps1

It works great
Source

The Vid’s
TechNet Video: Advanced Deployment Scenarios using the Microsoft Deployment Toolkit 2010: (Part 1 of 7)Reviewing the Available Options in the Deployment Workbench

TechNet Video: Advanced Deployment Scenarios using the Microsoft Deployment Toolkit 2010: (Part 2 of 7)Create and Explore the Configuration Database

TechNet Video: Advanced Deployment Scenarios using the Microsoft Deployment Toolkit 2010: (Part 3 of 7)Configuring Role Methods in the Configuration Database

TechNet Video: Advanced Deployment Scenarios using the Microsoft Deployment Toolkit 2010: (Part 4 of 7)Configuring Other Methods in the Configuration Database

TechNet Video: Advanced Deployment Scenarios using the Microsoft Deployment Toolkit 2010: (Part 5 of 7)Configuring the Deployment Point to Use the Configuration Database

TechNet Video: Advanced Deployment Scenarios using the Microsoft Deployment Toolkit 2010: (Part 6 of 7)Using Linked Deployment Points

TechNet Video: Advanced Deployment Scenarios using the Microsoft Deployment Toolkit 2010: (Part 7 of 7)Custom Edit the Deployment Wizard to Add a New Page

If your are an Exchange Admin I can recommend the following book Microsoft Exchange Server 2010 Best Practices. It covers SP1. It  contains the following Chapters.

Part I  Preparing for Exchange Server 2010

Chapter 1: Introducing Exchange Server 2010

Chapter 2: Exchange Deployment Projects

Chapter 3: Exchange Environmental Considerations

Part II  Designing Exchange Server 2010

Chapter 4: Client Access in Exchange 2010

Chapter 5: Routing and Transporting

Chapter 6: Mailbox Services

Chapter 7: Edge Transport and Messaging Security

Chapter 8: Automated Message Processing, Compliance, and Archiving

Chapter 9: Unified Messaging

Chapter 10: Federated Delegation

Chapter 11: Designing High Availability

Chapter 12: Backup, Restore, and Disaster Recovery

Chapter 13: Hardware Planning for Exchange Server 2010

Part III  Upgrading to Exchange Server 2010

Chapter 14: Upgrading from Exchange Server 2003 and Exchange Server 2007

Part IV  Deploying and Managing Exchange Server 2010

Chapter 15: Preparing for a Deploying Exchange Server 2010

Chapter 16: Managing Exchange

Chapter 17: Operating and Troubleshooting Exchange Server 2010

This book is also not a preparation guide for Exam 70-662: TS: Microsoft Exchange Server 2010, Configuring, or Exam 70-663: Pro: Designing and Deploying Messaging Solutions with Microsoft Exchange Server 2010, even though when you apply the knowledge and experience covered in this book, it will help you to pass these exams.

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

Some of the hotfixes would have been rolled up in a Windows update or service pack. Given that the Exchange team released SP1 earlier than what was planned and announced earlier, it did not align with some of the work with the Windows platform. As a result, some hotfixes are available from MSDN/Connect, and some require that you request them online using the links in the corresponding KBs. All these updates may become available on the Download Center, and also through Windows Update.

These hotfixes have been tested extensively as part of Exchange 2010 SP1 deployments within Microsoft and by our TAP customers. They are fully supported by Microsoft.

The TechNet article Exchange 2010 Prerequisites is updated with the hotfixes and install the prerequisites required for your server version (the hotfixes are linked to in the above table).

You can use the Install the Windows Server 2008 SP2 operating system prerequisites on a Windows 2008 R2 server. Only you have to run the following powershell command: Import-Module ServerManager

Installed Exchange 2010 SP1 on a Windows 2008 R2 Server with problems. I feels that the MMC is faster. Tomorrow upgrading a DAG/NLB cluster to Exchange 2010 SP1.

So What’s New in Exchange SP1:

New Deployment Functionality

During an Exchange 2010 SP1 installation, you can now select a new option to install the required Windows roles and features for each selected Exchange 2010 SP1 server role. For more information, see New Deployment Functionality in Exchange 2010 SP1.

Exchange ActiveSync

In Exchange 2010 SP1, you can manage Exchange ActiveSync devices using the Exchange Control Panel (ECP). Administrators can perform the following tasks:

• Manage the default access level for all mobile phones and devices.
• Set up e-mail alerts when a mobile phone or device is quarantined.
• Personalize the message that users receive when their mobile phone or device is either recognized or quarantined.
• Provide a list of quarantined mobile phones or devices.
• Create and manage Exchange ActiveSync device access rules.
• Allow or block a specific mobile phone or device for a specific user.

For every user, the administrator can perform the following tasks from the user’s property pages:

• List the mobile phones or devices for a specific user.
• Initiate remote wipes on mobile phones or devices.
• Remove old mobile phone or device partnerships.
• Create a rule for all users of a specific mobile phone or device or mobile phone type.
• Allow or block a specific mobile phone or device for the specific user.

SMS Sync

SMS Sync is a new feature in Exchange ActiveSync that works with Windows Mobile 6.1 with the Outlook Mobile Update and with Windows Mobile 6.5. SMS Sync is the ability to synchronize messages between a mobile phone or device and an Exchange 2010 Inbox. When synchronizing a Windows Mobile phone with an Exchange 2010 mailbox, users can choose to synchronize their text messages in addition to their Inbox, Calendar, Contacts, Tasks, and Notes. When synchronizing text messages, users will be able to send and receive text messages from their Inbox. This feature is dependent on the user’s mobile phones or devices supporting this feature

Reset Virtual Directory

In Exchange 2010 SP1, you can use the new Reset Client Access Virtual Directory wizard to reset one or more Client Access server virtual directories. The new wizard makes it easier to reset a Client Access server virtual directory. One reason that you might want to reset a Client Access server virtual directory is to resolve an issue related to a damaged file on a virtual directory. In addition to resetting virtual directories, the wizard creates a log file that includes the settings for each virtual directory that you choose to reset. For more information, see Reset Client Access Virtual Directories.

Exchange Store and Mailbox Database Functionality

The following is a list of new store and mailbox database functionality in Exchange 2010 SP1:

• With the New-MailboxRepairRequest cmdlet, you can detect and repair mailbox and database corruption issues.
• Store limits were increased for administrative access.
• The Database Log Growth Troubleshooter (Troubleshoot-DatabaseSpace.ps1) is a new script that allows you to control excessive log growth of mailbox databases.
• Public Folders client permissions support was added to the Exchange Management Console (EMC).

Mailbox and Recipients Functionality

The following is a list of new mailbox and recipient functionality included in Exchange 2010 SP1:

• Calendar Repair Assistant supports more scenarios than were available in Exchange 2010 RTM.
• Mailbox Assistants are now all throttle-based (changed from time-based in Exchange 2010 RTM).
• Internet calendar publishing allows users in your Exchange organization to share their Outlook calendars with a broad Internet audience.
• Importing and exporting .pst files now uses the Mailbox Replication service and doesn’t require Outlook.
• Hierarchical address book support allows you to create and configure your address lists and offline address books in a hierarchical view.
• Distribution group naming policies allow you to configure string text that will be appended or prepended to a distribution group’s name when it’s created.
• Soft-delete of mailboxes after move completion

High Availability and Site Resilience Functionality

The following is a list of new high availability and site resilience functionality included in Exchange 2010 SP1:

• Continuous replication – block mode
• Active mailbox database redistribution
• Enhanced datacenter activation coordination mode support
• New and enhanced management and monitoring scripts
• Exchange Management Console user interface enhancements
• Improvements in failover performance

Messaging Policy and Compliance Functionality

The following is a list of new messaging policy and compliance functionality included in Exchange 2010 SP1:

• Provision personal archive on a different mailbox database
• Import historical mailbox data to personal archive
• Delegate access to personal archive
• New retention policy user interface
• Support for creating retention policy tags for Calendar and Tasks default folders
• Opt-in personal tags
• Multi-Mailbox Search preview
• Annotations in Multi-Mailbox Search
• Multi-Mailbox Search data de-duplication
• WebReady Document Viewing of IRM-protected messages in Outlook Web App
• IRM in Exchange ActiveSync for protocol-level IRM
• IRM logging
• Mailbox audit logging

Technet Exchange 2010 SP1 info
Release Notes for Exchange Server 2010 SP1
What’s New in Exchange 2010 SP1
Downloads:
Microsoft Exchange Server 2010 Service Pack 1
Microsoft Exchange Server 2010 SP1 Language Pack Bundle
Exchange Server 2010 SP1 UM Language Packs
Exchange Server 2010 SP1 Help

To Download: Click on the picture.

MailTips are work with the Scenarios given below.

1. If one of the recipients is out of office.
2. When the recipient’s mailbox is full
3. Message size exceeds sender’s send limit.
4. If The Message quota exceeds of the recipient.
5. When Sending email to a large number of recipients.
6. When trying to send email to restricted recipients.
7. When a booking a room with exceeded invitees.
8. When sending to External and invalid domains.
9. When trying to send to moderated recipients.
10. Attaching more attachments than allowed.

Configuring MailTips

Gather Organization wide configuration MailTips settings.

Get-OrganizationConfig | fl *mailtips*

Enable or Disable MailTips.

You must use “Set-OrganizationConfig” CmdLet to enable or disable mailTips. Mailtips are enabled by default.

Set-OrganizationConfig -MailTipsAllTipsEnabled $true

Configure the large audience size for MailTips.

You must use “Set-OrganizationConfig” Cmdlet to configure large audience size. With a fresh Exchange Server 2010 installation it would be 25 by default. If we decrease it to 15, then Mailtip would be display to sender if sender add more than 15 recipients. See figure 3.

Set-OrganizationConfig -MailTipsLargeAudienceThreshold 15

Large Audience Threshold MailTip will display after adding more than 15 recipients . See figure 4.

Enable or disable the External Recipients MailTips

We have some embarrassing experiences of sending some internal information to external parties. However company doesn’t want to restrict sending emails to outside domains. With MailTips  at least we can give a alert to the sender before click send button. See figure 5.

Set-OrganizationConfig –MailTipsExternalRecipientsTipsEnabled $True

External Recipients MailTips displays when trying to send to an external domains. See figure 6.

Enable or disable MailTips that rely on mailbox data

Mailbox based MailTips are rely on the mailbox data. There are two Mailbox based Mailtips, The Recipient Out of Office and Mailbox Full MailTips, rely on the mailbox data.

Set-OrganizationConfig -MailTipsMailboxSourcedTipsEnabled $true

The Recipient Out of Office. You can get to know if whether the recipient is out of the office before you send the email. See figure 8.

Mailbox Full. If recipient’s Mailbox is full, you can know that before sending the email. See figure 9.

Configure Group Metrics

MailTIps relies on Group Metrics data to provide information on the the size of distribution groups and dynamic distribution groups. Exchange  server normally query a lot of LDAP requests to the Active Directory to get group membership information for each message.This could affect the the performance experienced by the users. To eliminate these issues Exchange server uses the Group Metric data. Group Metric data can be scheduled to run during office hours. You should use Set-MailboxServer CmdLet to configure Group metric Data. See figure 10.

Set-MailboxServer DAGEK10-01 GroupMetricsGenerationEnabled $true

Used this article as Source for my article.

The Management console is there in to flavors x86 and x64.

The Immidio Flex Profiles Advanced Edition.msi that you need later works both fine on x86 and x64 machines.

Start Immidio FlexProfile Kit


Best Practice is that the ini are placed on a domain controller because If one domain controller fails you have no problems with your flex profile kit.

Import the ini files that you will find in the package
I have al ready some ini files (Word 2007, Outlook 2007, Excel 2007) that i used with a older version of flex profile kit.

Create on a File Server an application install folder. I named it Immidio Flex profiles
Copy the Immidio Flex Profiles Advanced Edition.msi to that folder and the following script.

flexprofilesinstall.cmd

REM Voor Immidio FlexProfiles.
IF EXIST "C:\Program Files\Immidio\Flex Profiles\flexengine.exe" GOTO END
msiexec.exe /i "\\ward-dc01\install\Immidio Flexprofiles\Immidio Flex Profiles Advanced Edition.msi" /qb! LICENSEFILE="\\ward-dc01\Install\Immidio Flexprofiles\wardvissers.lic" /l* c:\InstallFlex.log

:END

Create A New GPO on the computers where you want to install Immidio Flexprofile kit. I named Install Immidio Flexprofiles. Asssign the  flexprofilesinstall.cmd als a startup script. Set the maximum wait time on 3600.
 

Afther that i created a new policy for my domain users witch a named Immidio FlexProfiles Users

Add the Immidio Flex Profiles.adm to the new created GPO Immidio FlexProfiles Users
 
I did some settings where to find the ini files and where to save the settings.

Now you have a working roaming profile based on Immidio Flexprofiles. It’s a great tool a im loving it.

It’s works great when you migrate from XP to Windows 7

Here is a list of the just some of technologies that this book talks about to achieve a Least Privilege Security:

• Program Compatibility Wizard
• Applications Compatibility Wizard
• User Account Control
• Group Policy Software Deployment
• Internet Explorer Add-on Management
• Troubleshooting Remote Users
• Configuring Windows Firewall
• Software Restrictions Policies and AppLocker
• Microsoft Deployment Toolkit
• CD Burning
• ActiveX Controls
• Changing system time and time zones
• Power Management
• Managing networks
• Standard Users Analyzer
• Applications Compatibility Toolkit
• Logon Scripts
• Remote Desktop Services
• App-V
• Med-V

I have read already some chapters. I think it is a great book to have on your collection.
You have always not enough time thinking about security. This book does it for you.

As a special offer Packt Publishing are also letting people download preview chapter of this book by download here Chapter No. 3 – Solving Least privilege Problems with the Application Compatibility Toolkit

1. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.  
2. Right-click the default Web site, point to New, and then click Virtual Directory.
3. In the Virtual Directory Creation wizard, type IISADMPWD in the Alias box, and then click Next.
    
4. In the Directory box, type c:\windows\system32\inetsrv\iisadmpwd or the location where your hard disk is your default hard disk, and then click Next.
   
5. Verify that only the Read and Run script check boxes are selected, such as the ASP check box, click Next, and then click Finish.
    
6. Verify that the IISADMPWD virtual directory has only basic authentication is set
   
7. If you use Windows 2003/IIS 6.0, verify that the application pool is set to MSExchangeOWAAppPool
    
8. Register the IISpwchg.dll file in the Iisadmpwd directory:
   Click Start, and then click Run.
   In the Open box, type the following, and then press ENTER:
   regsvr32 c:\windows\system32\inetsrv\iisadmpwd\iispwchg.dll
9. Configure the PasswordChangeFlags property in the metabase to make sure that the Password Change functionality is enabled:
   Click Start, and then click Run.
   In the Open box, type cmd, and then press ENTER.
   Locate the C:\Inetpub\Adminscripts directory.
   Type the following command, and then press ENTER:
   cscript.exe adsutil.vbs set w3svc/passwordchangeflags 1

   0: This is the default value. This value indicates that you must use a Secure Sockets Layer (SSL) connection when you change the password.
   1: This value permits password changes on non-secure ports. This value is useful if SSL is not enabled.
   2: This value disables the Password Change functionality.
   4: This value disables the advance notification of password expiration.

10. Do not forget to enable Active Server Pages.
     
    Source http://support.microsoft.com/kb/297121

Installation and Deployment

• VMware ESX. VMware vSphere 4.1 and its subsequent update and patch releases are the last releases to include both ESX and ESXi hypervisor architectures. Future major releases of VMware vSphere will include only the VMware ESXi architecture.
  • VMware recommends that customers start transitioning to the ESXi architecture when deploying VMware vSphere 4.1.
  • VMware will continue to provide technical support for VMware ESX according to the VMware vSphere support policy.
  • To learn more about the ESXi architecture and how to migrate from ESX to ESXi, go to the VMware ESX to ESXi Upgrade Center.
• Scripted Install for ESXi. Scripted installation of ESXi to local and remote disks allows rapid deployment of ESXi to many machines. You can start the scripted installation with a CD-ROM drive or over the network by using PXE booting. You cannot use scripted installation to install ESXi to a USB device. See the ESX and vCenter Server Installation Guide, the ESXi Installable and vCenter Server Setup Guide, and the ESXi Embedded and vCenter Server Setup Guide.
• vSphere Client Removal from ESX/ESXi Builds. For ESX and ESXi, the vSphere Client is available for download from the VMware Web site. It is no longer packaged with builds of ESX and ESXi. After installing ESX and ESXi, users are directed to the download page on the VMware Web site to get the compatible vSphere Client for that release. The vSphere Client is still packaged with builds of vCenter Server. See the ESX and vCenter Server Installation Guide, the ESXi Installable and vCenter Server Setup Guide, and the ESXi Embedded and vCenter Server Setup Guide.

Storage

• Boot from SAN. vSphere 4.1 enables ESXi boot from SAN (BFN). iSCSI, FCoE, and Fibre Channel boot are supported. Refer to the Hardware Compatibility Guide for the latest list of NICs and Converged Adapters that are supported with iSCSI boot. See the iSCSI SAN Configuration Guide and the Fibre Channel SAN Configuration Guide.
• Hardware Acceleration with vStorage APIs for Array Integration (VAAI). ESX can offload specific storage operations to compliant storage hardware. With storage hardware assistance, ESX performs these operations faster and consumes less CPU, memory, and storage fabric bandwidth. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Storage Performance Statistics. vSphere 4.1 offers enhanced visibility into storage throughput and latency of hosts and virtual machines, and aids in troubleshooting storage performance issues. NFS statistics are now available in vCenter Server performance charts, as well as esxtop. New VMDK and datastore statistics are included. All statistics are available through the vSphere SDK. See the vSphere Datacenter Administration Guide.
• Storage I/O Control. This feature provides quality-of-service capabilities for storage I/O in the form of I/O shares and limits that are enforced across all virtual machines accessing a datastore, regardless of which host they are running on. Using Storage I/O Control, vSphere administrators can ensure that the most important virtual machines get adequate I/O resources even in times of congestion. See the vSphere Resource Management Guide.
• iSCSI Hardware Offloads. vSphere 4.1 enables 10Gb iSCSI hardware offloads (Broadcom 57711) and 1Gb iSCSI hardware offloads (Broadcom 5709). See the ESX Configuration Guide, the ESXi Configuration Guide, and the iSCSI SAN Configuration Guide.
• NFS Performance Enhancements. Networking performance for NFS has been optimized to improve throughput and reduce CPU usage. See the ESX Configuration Guide and the ESXi Configuration Guide.

Network

• Network I/O Control. Traffic-management controls allow flexible partitioning of physical NIC bandwidth between different traffic types, including virtual machine, vMotion, FT, and IP storage traffic (vNetwork Distributed Switch only). See the ESX Configuration Guide and the ESXi Configuration Guide.
• IPv6 Enhancements. IPv6 in ESX supports Internet Protocol Security (IPsec) with manual keying. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Load-Based Teaming. vSphere 4.1 allows dynamic adjustment of the teaming algorithm so that the load is always balanced across a team of physical adapters on a vNetwork Distributed Switch. See the ESX Configuration Guide and the ESXi Configuration Guide.
• E1000 vNIC Enhancements. E1000 vNIC supports jumbo frames in vSphere 4.1. See the ESX Configuration Guide and the ESXi Configuration Guide.

Availability

• Windows Failover Clustering with VMware HA. Clustered Virtual Machines that utilize Windows Failover Clustering/Microsoft Cluster Service are now fully supported in conjunction with VMware HA. See Setup for Failover Clustering and Microsoft Cluster Service.
• VMware HA Scalability Improvements. VMware HA has the same limits for virtual machines per host, hosts per cluster, and virtual machines per cluster as vSphere. See Configuration Maximums for VMware vSphere 4.1 for details about the limitations for this release.
• VMware HA Healthcheck and Operational Status. The VMware HA dashboard in the vSphere Client provides a new detailed window called Cluster Operational Status. This window displays more information about the current VMware HA operational status, including the specific status and errors for each host in the VMware HA cluster. See the vSphere Availability Guide.
• VMware Fault Tolerance (FT) Enhancements. vSphere 4.1 introduces an FT-specific versioning-control mechanism that allows the Primary and Secondary VMs to run on FT-compatible hosts at different but compatible patch levels. vSphere 4.1 differentiates between events that are logged for a Primary VM and those that are logged for its Secondary VM, and reports why a host might not support FT. In addition, you can disable VMware HA when FT-enabled virtual machines are deployed in a cluster, allowing for cluster maintenance operations without turning off FT. See the vSphere Availability Guide.
• DRS Interoperability for VMware HA and Fault Tolerance (FT). FT-enabled virtual machines can take advantage of DRS functionality for load balancing and initial placement. In addition, VMware HA and DRS are tightly integrated, which allows VMware HA to restart virtual machines in more situations. See the vSphere Availability Guide.
• Enhanced Network Logging Performance. Fault Tolerance (FT) network logging performance allows improved throughput and reduced CPU usage. In addition, you can use vmxnet3 vNICs in FT-enabled virtual machines. See the vSphere Availability Guide.
• Concurrent VMware Data Recovery Sessions. vSphere 4.1 provides the ability to concurrently manage multiple VMware Data Recovery appliances. See the VMware Data Recovery Administration Guide.
• vStorage APIs for Data Protection (VADP) Enhancements. VADP now offers VSS quiescing support for Windows Server 2008 and Windows Server 2008 R2 servers. This enables application-consistent backup and restore operations for Windows Server 2008 and Windows Server 2008 R2 applications.

Management

• vCLI Enhancements. vCLI adds options for SCSI, VAAI, network, and virtual machine control, including the ability to terminate an unresponsive virtual machine. In addition, vSphere 4.1 provides controls that allow you to log vCLI activity. See the vSphere Command-Line Interface Installation and Scripting Guide and the vSphere Command-Line Interface Reference.
• Lockdown Mode Enhancements. VMware ESXi 4.1 lockdown mode allows the administrator to tightly restrict access to the ESXi Direct Console User Interface (DCUI) and Tech Support Mode (TSM). When lockdown mode is enabled, DCUI access is restricted to the root user, while access to Tech Support Mode is completely disabled for all users. With lockdown mode enabled, access to the host for management or monitoring using CIM is possible only through vCenter Server. Direct access to the host using the vSphere Client is not permitted. See the ESXi Configuration Guide.
• Access Virtual Machine Serial Ports Over the Network. You can redirect virtual machine serial ports over a standard network link in vSphere 4.1. This enables solutions such as third-party virtual serial port concentrators for virtual machine serial console management or monitoring. See the vSphere Virtual Machine Administration Guide.
• vCenter Converter Hyper-V Import. vCenter Converter allows users to point to a Hyper-V machine. Converter displays the virtual machines running on the Hyper-V system, and users can select a powered-off virtual machine to import to a VMware destination. See the vCenter Converter Installation and Administration Guide.
• Enhancements to Host Profiles. You can use Host Profiles to roll out administrator password changes in vSphere 4.1. Enhancements also include improved Cisco Nexus 1000V support and PCI device ordering configuration. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Unattended Authentication in vSphere Management Assistant (vMA). vMA 4.1 offers improved authentication capability, including integration with Active Directory and commands to configure the connection. See VMware vSphere Management Assistant.
• Updated Deployment Environment in vSphere Management Assistant (vMA). The updated deployment environment in vMA 4.1 is fully compatible with vMA 4.0. A significant change is the transition from RHEL to CentOS. See VMware vSphere Management Assistant.
• vCenter Orchestrator 64-bit Support. vCenter Orchestrator 4.1 provides a client and server for 64-bit installations, with an optional 32-bit client. The performance of the Orchestrator server on 64-bit installations is greatly enhanced, as compared to running the server on a 32-bit machine. See the vCenter Orchestrator Installation and Configuration Guide.
• Improved Support for Handling Recalled Patches in vCenter Update Manager. Update Manager 4.1 immediately sends critical notifications about recalled ESX and related patches. In addition, Update Manager prevents you from installing a recalled patch that you might have already downloaded. This feature also helps you identify hosts where recalled patches might already be installed. See the vCenter Update Manager Installation and Administration Guide.
• License Reporting Manager. The License Reporting Manager provides a centralized interface for all license keys for vSphere 4.1 products in a virtual IT infrastructure and their respective usage. You can view and generate reports on license keys and usage for different time periods with the License Reporting Manager. A historical record of the utilization per license key is maintained in the vCenter Server database. See the vSphere Datacenter Administration Guide.
• Power Management Improvements. ESX 4.1 takes advantage of deep sleep states to further reduce power consumption during idle periods. The vSphere Client has a simple user interface that allows you to choose one of four host power management policies. In addition, you can view the history of host power consumption and power cap information on the vSphere Client Performance tab on newer platforms with integrated power meters. See the vSphere Datacenter Administration Guide.

Platform Enhancements

• Performance and Scalability Improvements. vSphere 4.1 includes numerous enhancements that increase performance and scalability.
  • vCenter Server 4.1 can support three times more virtual machines and hosts per system, as well as more concurrent instances of the vSphere Client and a larger number of virtual machines per cluster than vCenter Server 4.0. The scalability limits of Linked Mode, vMotion, and vNetwork Distributed Switch have also increased.
  • New optimizations have been implemented for AMD-V and Intel VT-x architectures, while memory utilization efficiency has been improved still further using Memory Compression. Storage enhancements have led to significant performance improvements in NFS environments. VDI operations, virtual machine provisioning and power operations, and vMotion have enhanced performance as well.

  See Configuration Maximums for VMware vSphere 4.1.

• Reduced Overhead Memory. vSphere 4.1 reduces the amount of overhead memory required, especially when running large virtual machines on systems with CPUs that provide hardware MMU support (AMD RVI or Intel EPT).
• DRS Virtual Machine Host Affinity Rules. DRS provides the ability to set constraints that restrict placement of a virtual machine to a subset of hosts in a cluster. This feature is useful for enforcing host-based ISV licensing models, as well as keeping sets of virtual machines on different racks or blade systems for availability reasons. See the vSphere Resource Management Guide.
• Memory Compression. Compressed memory is a new level of the memory hierarchy, between RAM and disk. Slower than memory, but much faster than disk, compressed memory improves the performance of virtual machines when memory is under contention, because less virtual memory is swapped to disk. See the vSphere Resource Management Guide.
• vMotion Enhancements. In vSphere 4.1, vMotion enhancements significantly reduce the overall time for host evacuations, with support for more simultaneous virtual machine migrations and faster individual virtual machine migrations. The result is a performance improvement of up to 8x for an individual virtual machine migration, and support for four to eight simultaneous vMotion migrations per host, depending on the vMotion network adapter (1GbE or 10GbE respectively). See the vSphere Datacenter Administration Guide.
• ESX/ESXi Active Directory Integration. Integration with Microsoft Active Directory allows seamless user authentication for ESX/ESXi. You can maintain users and groups in Active Directory for centralized user management and you can assign privileges to users or groups on ESX/ESXi hosts. In vSphere 4.1, integration with Active Directory allows you to roll out permission rules to hosts by using Host Profiles. See the ESX Configuration Guide and the ESXi Configuration Guide.
• Configuring USB Device Passthrough from an ESX/ESXi Host to a Virtual Machine. You can configure a virtual machine to use USB devices that are connected to an ESX/ESXi host where the virtual machine is running. The connection is maintained even if you migrate the virtual machine using vMotion. See the vSphere Virtual Machine Administration Guide.
• Improvements in Enhanced vMotion Compatibility. vSphere 4.1 includes an AMD Opteron Gen. 3 (no 3DNow!™) EVC mode that prepares clusters for vMotion compatibility with future AMD processors. EVC also provides numerous usability improvements, including the display of EVC modes for virtual machines, more timely error detection, better error messages, and the reduced need to restart virtual machines. See the vSphere Datacenter Administration Guide.

Partner Ecosystem

• vCenter Update Manager Support for Provisioning, Patching, and Upgrading EMC’s ESX PowerPath Module. vCenter Update Manager can provision, patch, and upgrade third-party modules that you can install on ESX, such as EMC’s PowerPath multipathing software. Using the capability of Update Manager to set policies using the Baseline construct and the comprehensive Compliance Dashboard, you can simplify provisioning, patching, and upgrade of the PowerPath module at scale. See the vCenter Update Manager Installation and Administration Guide.
• User-configurable Number of Virtual CPUs per Virtual Socket. You can configure virtual machines to have multiple virtual CPUs reside in a single virtual socket, with each virtual CPU appearing to the guest operating system as a single core. Previously, virtual machines were restricted to having only one virtual CPU per virtual socket. See the vSphere Virtual Machine Administration Guide.
• Expanded List of Supported Processors. The list of supported processors has been expanded for ESX 4.1. To determine which processors are compatible with this release, use the Hardware Compatibility Guide. Among the supported processors is the Intel Xeon 7500 Series processor, code-named Nehalem-EX (up to 8 sockets).

You can download VMware vSphere 4.1 HERE

Step 1: Download the Office 2010 English version booth will be in x86 & x64

Step 2. Download the Office 2010 (language) Multilanguage iso only available from the Microsoft Volume Licensing site. Both in x86 en x64.

Step 3. Add the Office 2010 English version to MDT 2010 here office-2010-uitrollen-met-mdt-2010

Step 4. Extract the Office 2010 (language) Multilanguage iso with 7zip in the same application folder witch you created in Step 3.

Step 5. When you open MDT 2010 management console and you go to the Office 2010 Application that you added in step 3. You wil see that MDT sees more the one language. In my case it was en-us and nl-nl. The Screenshot is from the older MDT 2010 you MDT sees Office 2010 as Office 2007. MDT 2010 beta 1 supports Office 2010. I found till now no issues deploying Office 2010.

Step 6. Check the languages that you want. Check the Screenshot how i did it.

Step 7. Deploy the a Windows XP or Windows 7 client with Office 2010 Multilanguage versions.

Step 8. You can check with Microsoft Office 2010 Language Preferences or the languages that you configured are installed.

Step 9. Use Group Policy to set the language settings for users

1. Download the Office 2010 policy template files to your computer. You will find them HERE

2. Make a new GPO named Office 2010 languages settings it is a user policy.

3. Under User Configuration in the console tree, right-click Administrative Templates.

4. Click Add/Remove Templates, and then click Add.

5. In the Policy Templates dialog box, click the template that you want to add, and then click Open.

6. After you add the Office 2010 templates, click Close.

7. Open the Group Policy object (GPO) for which you want to set policy.

8. Double-click User Configuration and expand the tree under Administrative Templates.

9. Locate language-related policies in the Microsoft Office 2010 \ Language Settings node.

10. Select the languages that you want to use for each setting.

11. Save the GPO.

12. Go Testing

Windows Server 2008 R2 Support

Exchange Server 2007 SP3 supports all Exchange 2007 roles on the Windows Server 2008 R2 operating system.

Windows 7 Support

Exchange 2007 SP3 supports the installation of the Exchange 2007 management tools on a computer that is running Windows 7. Additionally, Exchange 2007 SP3 provides support for the installation of the Exchange 2007 Management Tools together with the Exchange Server 2010 Management Tools on the same Windows 7-based computer.

Improved Password Reset Functionality

Exchange 2007 SP3 introduces password reset functionality for Internet Information Services (IIS) 7.

To enable the password reset feature

1. Log on to the Exchange server that is running the CAS role by using an account that has local administrator rights.

2. Start Registry Editor, and then locate the following registry subkey:

   HLKM\SYSTEM\CurrentControlSet\Services\MSExchange OWA

3. Create the following DWORD value if it does not already exist:

   Value name: ChangeExpiredPasswordEnabledValue type: REG_DWORDValue data: 1

4. Exit Registry Editor.

 Updated Search Functionality

Exchange 2007 SP3 includes updates to the Exchange Search (MSSearch) component. MSSearch provides support for creating full text indexes for Exchange stores. Exchange 2007 SP3 updates the MSSearch binary files to MSSearch 3.1.

Schema Changes

Exchange 2007 SP3 includes Active Directory schema changes for certain Unified Messaging (UM) mailbox attributes. For more information, see Active Directory Schema Changes (SP3).

Support for Right-to-Left Disclaimer Text

Exchange 2007 SP3 includes support for Right-to-Left text in e-mail message disclaimers in a right-to-left language, such as Arabic. In earlier versions of Exchange, when you use a transport rule to create a disclaimer in a right-to-left language on an Exchange 2007 Hub Transport server, the text appears incorrectly when you view it from Outlook 2007.

Exchange 2007 SP3 adds functionality to the transport rule setting to fully support right-to-left text in disclaimers.

Download here SP3 for Exchange 2007

1) Manage your current server certificates.
2) Enable certificates for Exchange 2007 Services (POP, IMAP, SMTP, IIS, UM).
3) Generate an Exchange 2007 Certificate Signing Request and process the Certificate Authority answer.
4) Generate an Exchange 2007 Self-Signed certificate (not for production use).
5) Easily include additional subject names in a single certificate.
6) Import & Export ability for existing certificates.
To read more about Certificate Use in Exchange 2007 at Microsoft TechNet follow the link:

Certificate Manager for Exchange Server 2007 is currently offered by U-BTech Solutions free of charge

Certificate Manager for Exchange Server 2007 Flash Demonstration

Download – Certificate Manager for Exchange 2007

SOURCE

Features:
- You can set user, password and domain on a group and every server in that group you add they inherit the same settings this is very handy when you have a lot of servers.
- Bulk import servers is possible with txt files.
- Export the settings

You can Download Remote Desktop Connection Manager Here

What’s New in VMware Workstation 7.1

Solution 1:

1. Close Outlook 2007
2. Start Registry Editor
3. In Windows 7, click Start –> RUN
4. type regedit in de box and then click OK
5. Collapse this imageExpand this image
6. HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover
7. Click the Edit menu, point to New, and then click String Value.
8. Type RedirectServers, and then press ENTER
9. Right-click RedirectServers, and then click Modify.
10. In the Value data box, type a semicolon delimited list of the HTTPS servers to which AutoDiscover can be redirected without prompting for confirmation from the user, and then click OK.
For example, you want to allow for the following list of servers:
  – https://wardvissers.nl
  – https://wardvissers.local
11.Type the following in the Value data box: wardvissers.local;wardvissers.nl
12. On the File menu, click Exit to exit Registry Editor

Solution 2:
Setting the registry key with group policy preferences.