Today I was reading the recent post from EighTwOne blog where our Exchange Server MVP Michel de Rooij has written over the importance of installing a hot fix that was released for fixing the .net 4.5 issue with Windows Server 2008 and 2012 in terms of Exchange Server 2013.
.jpg)
Where I found this information that Exchange Server 2013 is Built on top of .net 4.5 platform and this hot fix is recommended to get installed on all Exchange 2013 Mailbox and Multi-Role servers as this hot fix reduces the memory consumption of the new Exchange Store worker processes.
Read the below blog for more details with the Hotfix links
http://eightwone.com/2013/09/05/exchange-2013-mailbox-kb2803754-kb2803755/
Additional Bytes,
If you want to know more on Store Worker process and its significance review this blog post form MSExchange Team blog.
Exchange Server 2013 introduced this new concept of Managed Store where each active and passive database copy will have its own Store Worker process running along with the main Information Store Service and gives you the flexibility of managing one single database via the process responsible for that particular database when a issue arise instead of keeping your hands on the Information Store Service.
Read the full post below:
http://msexchangeteam.in/how-to-identify-which-microsoft-exchange-store-worker-process-is-owned-by-mailbox-database-in-exchange-server-2013/
Where I found this information that Exchange Server 2013 is Built on top of .net 4.5 platform and this hot fix is recommended to get installed on all Exchange 2013 Mailbox and Multi-Role servers as this hot fix reduces the memory consumption of the new Exchange Store worker processes.
Read the below blog for more details with the Hotfix links
http://eightwone.com/2013/09/05/exchange-2013-mailbox-kb2803754-kb2803755/
Additional Bytes,
If you want to know more on Store Worker process and its significance review this blog post form MSExchange Team blog.
Exchange Server 2013 introduced this new concept of Managed Store where each active and passive database copy will have its own Store Worker process running along with the main Information Store Service and gives you the flexibility of managing one single database via the process responsible for that particular database when a issue arise instead of keeping your hands on the Information Store Service.
Read the full post below:
http://msexchangeteam.in/how-to-identify-which-microsoft-exchange-store-worker-process-is-owned-by-mailbox-database-in-exchange-server-2013/
No comments:
Post a Comment