Archive for October, 2013

We’ve listened to your feedback for improving the on-premises and hybrid Exchange Server deployment experience, and we’re happy to announce the release of the new, consolidated Deployment Assistant!

The Exchange Server Deployment Assistant now combines all the on-premises and hybrid deployment scenarios from both the Exchange 2013 Deployment Assistant and the Exchange 2010 Deployment Assistant into a single tool. We’ve eliminated the need for the installation of Silverlight and provide guidance for all Exchange Server deployments in a true one-stop shop experience. We’ve also kept the same, convenient question-and-answer format to create a customized, step-by-step checklist with instructions to deploy Exchange 2013 or Exchange 2010.


Read the complete blog at


This is one piece of my presentation discussing about new Store for Exchange 2013, the legacy in previous Exchange version called Information Store.


  • The store service process is a controller of all the other store worker processes.
  • The new Managed Store mounts each database with its own worker process
  • Each mount request spins up a new worker process, so a failure on the part of one process won’t impact the other process or database, should it hang



This topic summarizes the new features and enhancements that are available in System Center 2012 R2 Data Protection Manager (DPM).

View original post 268 more words

I have an issue yesterday about my Exchange, I’m using Exchange Server 2010 SP3 by the way. So the problem is I want to delete an email from Submission Queue. When I right click from the queue viewer console, there is no option to delete it, so it must be from the EMS.

to get rid the email I use this following command :

Get-Message -Filter {FromAddress –eq “”} –Server SVR-HT | Remove-Message

too short writing eh ? I know, I’m still grasping some knowledge with Exchange 2013, I’m watching Channel 9 Smile



Failover Cluster

This topic provides an overview of the Failover Clustering feature in Windows Server 2012 R2 Preview and Windows Server 2012. Failover clusters provide high availability and scalability to many server workloads. These include server applications such as Microsoft Exchange Server, Hyper-V, Microsoft SQL Server, and file servers. The server applications can run on physical servers or virtual machines. This topic describes the Failover Clustering feature and provides links to additional guidance about creating, configuring, and managing failover clusters that can scale to 64 physical nodes and to 8,000 virtual machines.

View original post 993 more words

Blog at
[ Back to top ]