Migrate from Exchange Public Folders to Microsoft Office 365

Exchange public folders are widely used in on-premises Exchange environments. However, Microsoft® Exchange Online does not support customer usage scenarios of public folders. If you or your customers are using Exchange public folders, there are special considerations for migrating to Microsoft Office 365. This document outlines these considerations, discusses the most common public folder scenarios and how they are represented in Office 365 services. It also provides the information you need to decide whether Office 365 is a good match for you based on your current public folder usage.

Download: Migrate from Public Folders to Office 365.docx

DPM Error 30126 DPM could not find find a valid recovery point on disk Or ‘Replica Inconsistent’ showing against System State and Bare Metal Recovery on Protected Server

This error normally occurs due to one of the following two possible causes:

  • Not enough disk space is available on the protected machine to store a backup of the system state files
  • The Windows Server Backup feature is not installed on the protected machine (Windows 2008 or Windows 2008 R2)

Solution:
Simply install the Windows Server Backup feature on to the protected machine from Server Manager. Installation of this feature doesn’t normally require a reboot.

If the protected machine doesn’t have enough disk space to store a backup of the system state files (you’ll need 10-12Gb free on the system drive by default to store these files) you’ll need to create some space on the system drive, or add another disk to the machine and modify the PSDataSourceConfig.xml file to allow DPM to use the new location.

The PSDataSourceConfig.xml file is normally located at %SystemDrive%\Program Files\Microsoft Data Protection Manager\DPM\DataSources. Modify the <FilesToProtect> section of the xml file to point to the new drive added. Maybe that you may need to remove protection for the machine from the DPM 2010 console and then re-enable protection to get DPM to read the new location for backup files from the PSDataSourceConfig.xml file.

Exchange 2007 SP3 Update Rollup 5

Today the Exchange Team released Rollup 5 for Exchange Server 2007 Service Pack 3 (KB2602324). This update raises Exchange 2007 version number to 8.3.213.1.

Here’s the list of changes included in this rollup:

981820 New X-headers of a message item do not appear when the message item is retrieved by IMAP4 or by POP3 in an Exchange Server 2007 SP2 environment

2292150 A deleted hyperlink remains in the HTML source of an email message if you create the email message by using OWA in an Exchange Server 2007 environment

2411423 The Msftefd.exe process constantly consumes up to 100 percent of CPU resources when your mailbox language is set to German on an Exchange Server 2007 server

2450078 The sent time in an email message body is incorrect when you reply or forward the email message by using an EWS application in an Exchange Server 2007 environment

2451415 “There was a problem logging onto your mail server” error message when you use a POP3 client to access a mailbox in an Exchange Server 2007 SP3 environment

2536652 EdgeTransport.exe randomly stops responding on a Hub Transport server after you configure public folder replication in Exchange Server 2007

2536695 “Some items cannot be deleted” error message when you try to delete or modify an email message in a public folder in an Exchange Server 2007 environment

2536697 DBCS characters in a rule name are converted to question marks after you move a mailbox from Exchange Server 2003 to Exchange Server 2007

2537783 The EdgeTransport.exe process crashes occasionally after you install Update Rollup 2 for Exchange Server 2007 SP3

2538958 Extended Protection Warning Displayed in Exchange Management Console and Exchange Management Shell After Installing RU2 for Exchange 2007 SP3

2554575 Items accumulate in the MRM submission folder when managed folder assistant journal items in an Exchange Server 2007 environment

2556751 The EdgeTransport.exe process crashes when processing certain email messages on an Exchange Server 2007 Hub Transport server

2557304 The Store.exe process may consume excessive CPU resources and memory resources intermittently when a user opens a calendar item by using OWA in an Exchange Server 2007 SP3 environment

When running ForeFront Protection for Exchange, make sure you disable ForeFront before installing the rollup and re-enable it afterwards, otherwise the Information Store and Transport services may not start. You can disable ForeFront using fscutility /disable and enable it using the fscutility /enable command.

Note that update rollups are cumulative, i.e. they contain fixes released in earlier update rollups for the same product level (RTM, SPx). This means you don’t need to install previous update rollups during a fresh installation but can start with the latest rollup available right away.

You can download Exchange 2007 SP3 Rollup 5 here.

Free Quest vWorkspace Desktop Optimizer

Quest vWorkspace Desktop Optimizer  is a free tool to optimize the virtual desktop.

Blindly deploying entirely the same Windows desktop image that was used for the physical desktops is not the smartest thing to do. Running Windows in a VDI environment requires a decent amount of optimizing. This optimizing is nothing new. Quest has been optimizing SBC environments for over ten years now and many of things that we learned there (the hard way) apply equally to VDI environments.

Quest created a piece of software that contains our entire ‘optimizing knowledge’ called the Quest vWorkspace Desktop Optimizer and it is Free!

Although optimized for Quest vWorkspace environments, the Quest vWorkspace Desktop Optimizer will work just as well in Citrix XenDesktop or VMware View environments. You can download the Quest vWorkspace Desktop Optimizer HERE. Read HERE important information on how to use the Quest vWorkspace Desktop Optimizer.

image

Optimizing Windows 7 Images for use in VDI

One of our MCS deployment guys in the UK – Jonathan Bennett (you may know Jonathan as the author of the autoit tools and GImageX) has developed a tool for configuring Windows 7/Windows Vista/Server 2008 images for use in a VDI environment. The tool called VDI Optimizer outputs a VBScript (based on the selections you make in the GUI interface), which can then be used to apply performance and configuration settings to images that will be deployed via VDI platforms – this is particularly useful if you are using MDT 2010 for your image engineering process as the VBScript can bolted into the task sequence using a Run Command Line task.

image

You can make machine based selections for turning off services and functions that may not be required when the operating system is running in a VDI environment such as hibernation, system restore, and background defrag, as well as adjusting some user based settings such as visual effects, font smoothing and off-screen composition for Internet Explorer.

The beta of this tool is available from http://www.autoitscript.com/files/tools/VDIOptimizer.zip but please remember The tool is provided "AS IS" with no warranties, confers no rights, and is not supported by the authors or Microsoft Corporation.

Source: Optimizing Windows 7 images for use in VDI

The Deployment Guys released Deployment Mindmaps

"Why deployment is so hard?", “Where can I find all related information?” What else I need to consider?”

Those or similar questions are normal during my any projects. After getting the same questions again and again, The Deployment Guys decided to create a Mindmap with all common links you need to know if you in the deployment space.

Attachment: MINDMAPS.zip Source:Deployment-Mindmaps

Microsoft Exchange Server 2010 Performance on vSphere 5

A white paper has been published that examines how Microsoft Exchange Server 2010 performs on vSphere 5 in terms of scaling up (adding more virtual CPUs) and scaling out (adding more VMs). Having the choice to scale up or out while maintaining a positive user experience gives IT more flexibility to right-size system deployments and maximize total cost of ownership with respect to licensing and hardware purchases.

Testing shows the effectiveness of vSphere 5 to add compute power by scaling up Exchange Server VMs, in increments, from 2 to 12 virtual CPUs. This allowed the total number of very heavy Exchange users to increase from 2,000 to 12,000 while sendmail latency remained well within the range of acceptable user responsiveness. Processor utilization remained low, at about 15% of the total host processing capacity for 12,000 very heavy Exchange users.

Testing also shows that scaling out to eight Exchange Server VMs supports a workload of up to 16,000 very heavy users, with the load consuming only 32% of the ESXi host processing capacity.

Additional tests were undertaken to show the performance improvements of vMotion and Storage vMotion in vSphere 5. vMotion migration time for a 4-vCPU Exchange mailbox server VM showed a 34% reduction in vSphere 5 over vSphere 4.1. Storage vMotion migration time for a 350GB database VMDK showed an 11% reduction in vSphere 5 over vSphere 4.1.

image

For the full paper, see Microsoft Exchange Server 2010 Performance on vSphere 5.

Microsoft Lync Server 2010 Protocol Workloads Poster

This poster shows each workload in Lync Server 2010, describing relationships, dependencies, the servers that initiate connections, and certificate requirements. Relationships between Microsoft Lync 2010 communications software, Microsoft Lync 2010 Phone Edition, Microsoft Office Live Meeting 2007, Microsoft Lync Web App, and other communications software are also described. SIP and XMPP connection patterns are shown for Yahoo!, MSN, AOL, Gmail, and Jabber

To download: Click on the Picture

image

HP Sizer for Microsoft Exchange Server 2010

At the moment I am busy to design a Exchange 2010 environment.
The customer where I going to implement Exchange 2010 use only HP equipment.

A great tool is the HP sizer for Exchange 2010.

About the HP Sizer tool:
Microsoft® Exchange Server 2010 is a complex application that requires intensive knowledge of deployment strategies, interdependencies, server and storage performance related issues.HP has developed the HP Sizer for Microsoft Exchange Server 2010 to assist customers with proper server and storage sizing for their Exchange Server 2010 deployments. The algorithms developed and implemented in this tool are based upon extensive testing of Exchange Server 2010 server roles and technologies, HP’s deep experience with Microsoft Exchange, and intricate knowledge of server CPU, memory, and I/O subsystems. This tool is free to download and use, and is designed to simplify configuration across a broad range of deployments. This newest Microsoft Exchange Server Sizer provides support for multiple site deployments, varied client types and access methods, all Exchange Server 2010 server roles, Database Availability Group (DAG) high availability options, choice of tower, rack mounted, or HP BladeSystem server platforms, and either direct attached or SAN-based storage solutions. Based on your input, the tool provides a comprehensive bill of materials along with a deployment overview of the Exchange Server 2010 server roles and storage configurations. Once this Sizer is installed, updates can be downloaded automatically to the underlying software engines that are necessary to provide support for HP server and storage product information details.

Please see the ‘What’s new” link on the home page of the Sizer (when installed on your system) for the most recent information.

Download: HP Sizer for Microsoft Exchange Server 2010

Translate »