{"id":5712,"date":"2015-07-15T12:00:47","date_gmt":"2015-07-15T11:00:47","guid":{"rendered":"http:\/\/www.markwilson.co.uk\/blog\/?p=5712"},"modified":"2015-07-11T14:00:42","modified_gmt":"2015-07-11T13:00:42","slug":"some-design-principles-for-microsoft-exchange","status":"publish","type":"post","link":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm","title":{"rendered":"Some design principles for Microsoft Exchange"},"content":{"rendered":"

In a previous role, I managed a team that was responsible for Microsoft Exchange design. Working with Microsoft, we established a set of design principles, some template designs and a rule-book for any changes made to those designs. Soon afterwards, Microsoft published their Preferred Architecture for Exchange<\/a> and the similarity was striking (to be honest, I’d have been concerned if it was different)!<\/p>\n

As that Preferred Architecture is publicly available, I think it’s fine to talk about some of the principles we applied. They seem particularly pertinent now as I was recently working with a customer whose Exchange design doesn’t follow these… and they were experiencing a few difficulties that were affecting the stability of their systems…<\/p>\n

Physical, not virtual<\/h3>\n

Virtualisation has many advantages in many circumstances but it is not a “silver bullet”. It also brings complexity and operational challenges into Exchange design, with few (if any) advantages that would not be already provided by Exchange out of the box. Exchange is designed to make full use of the available hardware and Microsoft is able to provide large, low cost mailboxes within Office 365 (Exchange Online), without a requirement to virtualise their Exchange 2013 platform. In addition to the operational and supportability complexities that virtualisation brings, virtualising the Exchange deployment requires more Exchange design effort.<\/p>\n

Deploy multi-role Exchange servers<\/h3>\n

Microsoft\u2019s current recommended practice is to deploy multi-role Exchange 2013 servers (i.e. client access and mailbox roles on the same server) for the following reasons:<\/p>\n

    \n
  1. Reduced hardware. Multi-role servers make best use of processor capacity given the more powerful server specifications which are now available.<\/li>\n
  2. Reduced operational and capital expenditure. Fewer servers to deploy and manage.<\/li>\n
  3. Building block design which is simple to deploy and scale. Automated deployment of standard server builds.<\/li>\n<\/ol>\n

    The mailbox server role must be designed not to exceed the maximum processor capacity guidance for multi-role servers; this provides confidence that the hardware deployed can co-host all roles on a single server. This is where the Exchange 2013 Server Role Requirements Calculator comes in…<\/a><\/p>\n

    Use direct attached storage – not a SAN<\/h3>\n

    Microsoft designed Exchange 2013 to run on commodity hardware and believes this is the most cost effective way to provide storage for the Exchange mailbox databases.\u00a0\u00a0Changes to the Exchange 2013 storage engine have yielded a significant reduction in I\/O over previous versions of Exchange, allowing customers to take advantage of larger, cheaper disks and reduce the overall solution costs. In general, Direct Attached Storage (DAS) should be used\u00a0in a Just a Bunch of Discs (JBoD) configuration although there are some circumstances where a Redundant Array of Inexpensive Devices (RAID) configuration may be used.<\/p>\n

    Microsoft uses a commoditised email platform with DAS and JBoD architecture to provide and support large, low cost mail mailboxes within Office 365. There are many more solution elements to consider with a SAN (Host Bus Adapters (HBAs), fibre channel switches and SAN I\/O modules) as well as additional software for managing the infrastructure and firmware to keep up-to-date. Consequently, there is an increased likelihood of technical integration issues using a SAN and, once installed, a SAN infrastructure has to be carefully monitored and managed with appropriately skilled staff. In stark contrast, the costs of direct-attached JBoD solutions is falling as larger disks become available.<\/p>\n

    Native resilience<\/h3>\n

    Database availability groups (DAGs) were introduced in Exchange Server 2010 to replicate databases between up to 16 servers. A DAG with multiple mailbox database copies, can provide automatic recovery from a variety of server, storage, network and other hardware failures. Auto-reseed functionality in Exchange Server 2013 allows for automatically bringing spare disks on line in the event of failure and creating new database copies.<\/p>\n

    If four highly available copies of each database are deployed, Exchange native resilience can be used without the requirement for third party backup solutions. Only specific requirements (i.e. ability to recover to an offline datacentre; recovery of deleted mailbox outside the deleted mailbox recovery retention time; protection against operational immaturity; protection against security breaches etc.) drive a requirement for adoption of a third party backup solution<\/p>\n

    Exchange Online\u00a0uses the Exchange native resilience to protect against database failures, without resorting to the use of third party backup solutions.<\/p>\n

    Whilst a DAG can support 16 servers, it may be prudent to artificially limit the number of DAG members (e.g. to 12) in order to provide flexibility in upgrade scenarios.<\/p>\n

    Site resilience<\/h3>\n

    DAGs can be extended between sites and copies of databases replicated across sites to provide additional redundancy. Each member of the DAG must have a round trip latency no greater than 500ms to contact the other members, regardless of their physical location. In general, Exchange DAGs should span at least two physical sites and Microsoft also recommends that separate Active Directory sites are used.<\/p>\n

    Mailbox distribution<\/h3>\n

    With multiple sites in use, the next consideration is whether both are active (i.e. providing live service) or whether one is a secondary, passive, datacentre (i.e. invoked for disaster recovery purposes).\u00a0 If all active mailboxes are hosted in a single site, and all passive copies of the mailboxes reside in a secondary site, the user distribution model is referred to as active\/passive. If there are active mailboxes in both primary and secondary datacentres then the user distribution model is known to be active\/active.<\/p>\n

    This should not be confused with the databases within the DAG, where only one copy of each database is active at any time.<\/p>\n

    Exchange 2013 simplified the client access model and with all clients connecting using HTTPS an active\/active architecture is simple and spreads the client load across all Client Access servers, making best use of the deployed hardware.<\/p>\n

    This also facilitates a simplified SMTP namespace and allows automatic site failure (assuming the File Share Witness is located in a tertiary datacentre).<\/p>\n

    Archiving<\/h3>\n

    With today’s storage capabilities, large mailboxes are becoming normal.\u00a0 The use of a native Exchange 2013 archive or a third party archiving solution is only required where there is a defined need for a user experience that warrants the management of email data (the \u2018personal archive\u2019 user experience, e.g. auto archive functionality) or by legal\/policy requirements regarding the retention and discovery of email data (\u2018the regulatory archive\u2019).<\/p>\n

    There is a common misconception that using a third party archive solution will provide a cost effective, single instance storage solution by differentiating \u2018hot\u2019 and \u2018cold\u2019 data and providing the ability to store \u2018colder\u2019 data on cheaper, slower disks. In fact, introducing a secondary system increases costs and complexity (in design and management) as well as reducing the flexibility of the solution.<\/p>\n

    Many organisations are electing to leave behind their archives with browser-only access as they migrate to larger online mailboxes in the cloud, e.g. using Exchange Online.<\/p>\n

    Conclusion<\/h3>\n

    Whilst Exchange is supported in a virtualised environment, with SAN-attached storage, third party backup and making use of email archive solutions, deviating from the Preferred Architecture is a huge risk. The points in this blog post, combined with Microsoft’s advice linked above highlight the reasons to keep your Exchange design as simple as possible. Whilst a more complex design will probably work, identifying issues when it doesn’t will be a much bigger challenge.<\/p>\n

     <\/p>\n","protected":false},"excerpt":{"rendered":"

    In a previous role, I managed a team that was responsible for Microsoft Exchange design. Working with Microsoft, we established a set of design principles, some template designs and a rule-book for any changes made to those designs. Soon afterwards, Microsoft published their Preferred Architecture for Exchange and the similarity was striking (to be honest, … Continue reading Some design principles for Microsoft Exchange<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[218],"tags":[46],"class_list":["post-5712","post","type-post","status-publish","format-standard","hentry","category-technology","tag-exchange"],"yoast_head":"\nSome design principles for Microsoft Exchange - markwilson.it<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm\" \/>\n<meta property=\"og:locale\" content=\"en_GB\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Some design principles for Microsoft Exchange - markwilson.it\" \/>\n<meta property=\"og:description\" content=\"In a previous role, I managed a team that was responsible for Microsoft Exchange design. Working with Microsoft, we established a set of design principles, some template designs and a rule-book for any changes made to those designs. Soon afterwards, Microsoft published their Preferred Architecture for Exchange and the similarity was striking (to be honest, … Continue reading Some design principles for Microsoft Exchange\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm\" \/>\n<meta property=\"og:site_name\" content=\"markwilson.it\" \/>\n<meta property=\"article:published_time\" content=\"2015-07-15T11:00:47+00:00\" \/>\n<meta name=\"author\" content=\"Mark Wilson\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@markwilsonit\" \/>\n<meta name=\"twitter:site\" content=\"@markwilsonit\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Mark Wilson\" \/>\n\t<meta name=\"twitter:label2\" content=\"Estimated reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm\"},\"author\":{\"name\":\"Mark Wilson\",\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/#\\\/schema\\\/person\\\/98f61365e7c39d6be942174b8c4de468\"},\"headline\":\"Some design principles for Microsoft Exchange\",\"datePublished\":\"2015-07-15T11:00:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm\"},\"wordCount\":1205,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/#\\\/schema\\\/person\\\/98f61365e7c39d6be942174b8c4de468\"},\"keywords\":[\"Microsoft Exchange\"],\"articleSection\":[\"Technology\"],\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm\",\"url\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm\",\"name\":\"Some design principles for Microsoft Exchange - markwilson.it\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/#website\"},\"datePublished\":\"2015-07-15T11:00:47+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm#breadcrumb\"},\"inLanguage\":\"en-GB\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/2015\\\/07\\\/some-design-principles-for-microsoft-exchange.htm#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Some design principles for Microsoft Exchange\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/\",\"name\":\"markwilson.it\",\"description\":\"get-info -class technology | write-output > \\\/dev\\\/web\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/#\\\/schema\\\/person\\\/98f61365e7c39d6be942174b8c4de468\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-GB\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/#\\\/schema\\\/person\\\/98f61365e7c39d6be942174b8c4de468\",\"name\":\"Mark Wilson\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-GB\",\"@id\":\"https:\\\/\\\/i0.wp.com\\\/www.markwilson.co.uk\\\/blog\\\/uploads\\\/image-4.png?fit=800%2C800&ssl=1\",\"url\":\"https:\\\/\\\/i0.wp.com\\\/www.markwilson.co.uk\\\/blog\\\/uploads\\\/image-4.png?fit=800%2C800&ssl=1\",\"contentUrl\":\"https:\\\/\\\/i0.wp.com\\\/www.markwilson.co.uk\\\/blog\\\/uploads\\\/image-4.png?fit=800%2C800&ssl=1\",\"width\":800,\"height\":800,\"caption\":\"Mark Wilson\"},\"logo\":{\"@id\":\"https:\\\/\\\/i0.wp.com\\\/www.markwilson.co.uk\\\/blog\\\/uploads\\\/image-4.png?fit=800%2C800&ssl=1\"},\"description\":\"A Chartered IT Professional, with recent experience in technology leadership, IT strategy and practice management roles, Mark Wilson is an Enterprise Architect in the Advisory and Management Group at risual. During a career spanning more than two decades, Mark has gained widespread recognition as an expert in his field including both industry and national press exposure. In addition to certifications from Microsoft, VMware, Red Hat, The Open Group and Axelos, Mark held a Microsoft Most Valuable Professional (MVP) award for three years and is now part of the MVP Reconnect programme. Mark is also well-known on social media and maintains an award-winning blog.\",\"sameAs\":[\"http:\\\/\\\/www.markwilson.co.uk\\\/\",\"https:\\\/\\\/www.instagram.com\\\/markwilsonuk\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/in\\\/markawilson\\\/\",\"https:\\\/\\\/x.com\\\/markwilsonit\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UCWHlZCoHRTocdvtrOJ2IL4A\"],\"url\":\"https:\\\/\\\/www.markwilson.co.uk\\\/blog\\\/author\\\/mark-wilson\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Some design principles for Microsoft Exchange - markwilson.it","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm","og_locale":"en_GB","og_type":"article","og_title":"Some design principles for Microsoft Exchange - markwilson.it","og_description":"In a previous role, I managed a team that was responsible for Microsoft Exchange design. Working with Microsoft, we established a set of design principles, some template designs and a rule-book for any changes made to those designs. Soon afterwards, Microsoft published their Preferred Architecture for Exchange and the similarity was striking (to be honest, … Continue reading Some design principles for Microsoft Exchange","og_url":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm","og_site_name":"markwilson.it","article_published_time":"2015-07-15T11:00:47+00:00","author":"Mark Wilson","twitter_card":"summary_large_image","twitter_creator":"@markwilsonit","twitter_site":"@markwilsonit","twitter_misc":{"Written by":"Mark Wilson","Estimated reading time":"6 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm#article","isPartOf":{"@id":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm"},"author":{"name":"Mark Wilson","@id":"https:\/\/www.markwilson.co.uk\/blog\/#\/schema\/person\/98f61365e7c39d6be942174b8c4de468"},"headline":"Some design principles for Microsoft Exchange","datePublished":"2015-07-15T11:00:47+00:00","mainEntityOfPage":{"@id":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm"},"wordCount":1205,"commentCount":0,"publisher":{"@id":"https:\/\/www.markwilson.co.uk\/blog\/#\/schema\/person\/98f61365e7c39d6be942174b8c4de468"},"keywords":["Microsoft Exchange"],"articleSection":["Technology"],"inLanguage":"en-GB","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm","url":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm","name":"Some design principles for Microsoft Exchange - markwilson.it","isPartOf":{"@id":"https:\/\/www.markwilson.co.uk\/blog\/#website"},"datePublished":"2015-07-15T11:00:47+00:00","breadcrumb":{"@id":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm#breadcrumb"},"inLanguage":"en-GB","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.markwilson.co.uk\/blog\/2015\/07\/some-design-principles-for-microsoft-exchange.htm#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.markwilson.co.uk\/blog"},{"@type":"ListItem","position":2,"name":"Some design principles for Microsoft Exchange"}]},{"@type":"WebSite","@id":"https:\/\/www.markwilson.co.uk\/blog\/#website","url":"https:\/\/www.markwilson.co.uk\/blog\/","name":"markwilson.it","description":"get-info -class technology | write-output > \/dev\/web","publisher":{"@id":"https:\/\/www.markwilson.co.uk\/blog\/#\/schema\/person\/98f61365e7c39d6be942174b8c4de468"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.markwilson.co.uk\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-GB"},{"@type":["Person","Organization"],"@id":"https:\/\/www.markwilson.co.uk\/blog\/#\/schema\/person\/98f61365e7c39d6be942174b8c4de468","name":"Mark Wilson","image":{"@type":"ImageObject","inLanguage":"en-GB","@id":"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/uploads\/image-4.png?fit=800%2C800&ssl=1","url":"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/uploads\/image-4.png?fit=800%2C800&ssl=1","contentUrl":"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/uploads\/image-4.png?fit=800%2C800&ssl=1","width":800,"height":800,"caption":"Mark Wilson"},"logo":{"@id":"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/uploads\/image-4.png?fit=800%2C800&ssl=1"},"description":"A Chartered IT Professional, with recent experience in technology leadership, IT strategy and practice management roles, Mark Wilson is an Enterprise Architect in the Advisory and Management Group at risual. During a career spanning more than two decades, Mark has gained widespread recognition as an expert in his field including both industry and national press exposure. In addition to certifications from Microsoft, VMware, Red Hat, The Open Group and Axelos, Mark held a Microsoft Most Valuable Professional (MVP) award for three years and is now part of the MVP Reconnect programme. Mark is also well-known on social media and maintains an award-winning blog.","sameAs":["http:\/\/www.markwilson.co.uk\/","https:\/\/www.instagram.com\/markwilsonuk\/","https:\/\/www.linkedin.com\/in\/markawilson\/","https:\/\/x.com\/markwilsonit","https:\/\/www.youtube.com\/channel\/UCWHlZCoHRTocdvtrOJ2IL4A"],"url":"https:\/\/www.markwilson.co.uk\/blog\/author\/mark-wilson"}]}},"jetpack_featured_media_url":"","jetpack-related-posts":[{"id":624,"url":"https:\/\/www.markwilson.co.uk\/blog\/2006\/10\/message-hygiene-principles-for.htm","url_meta":{"origin":5712,"position":0},"title":"Message hygiene principles for Microsoft Exchange Server","author":"Mark Wilson","date":"Tuesday 3 October 2006","format":false,"excerpt":"Whilst researching my post on the Microsoft Exchange intelligent message filter a couple of months back, I came across the following message hygiene architectural principles, which Microsoft promotes as best practice: Anti-spam filtering must be performed before anti-virus filtering. Anti-spam filtering should be performed for inbound mail only. Anti-spam filtering\u2026","rel":"","context":"In \"Malware\"","block_context":{"text":"Malware","link":"https:\/\/www.markwilson.co.uk\/blog\/tag\/malware"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":350,"url":"https:\/\/www.markwilson.co.uk\/blog\/2006\/06\/exchange-server-2007-may-well-shake-up.htm","url_meta":{"origin":5712,"position":1},"title":"Exchange Server 2007 may well shake up messaging – and about time too!","author":"Mark Wilson","date":"Friday 30 June 2006","format":false,"excerpt":"A colleague recently alerted me to a Network World article about how Exchange 2007 will shake up messaging. Whilst Exchange Server 2007 (formerly codenamed E12) will bring significant improvements that will require careful consideration and planning, I found the article to be highly misleading and thought I'd probably better set\u2026","rel":"","context":"In \"Microsoft Exchange\"","block_context":{"text":"Microsoft Exchange","link":"https:\/\/www.markwilson.co.uk\/blog\/tag\/exchange"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":6688,"url":"https:\/\/www.markwilson.co.uk\/blog\/2016\/12\/architecture-for-the-microsoft-platform-defining-standards-principles-reference-architecture-and-patterns.htm","url_meta":{"origin":5712,"position":2},"title":"Architecture for the Microsoft platform: defining standards, principles, reference architecture and patterns","author":"Mark Wilson","date":"Thursday 1 December 2016","format":false,"excerpt":"IT architecture is a funny old game... you see, no-one does it the same way. Sure, we have frameworks and there's a lot of discussion about \"how\" to \"architect\" (is that even a verb?) but there is no defined process that I'm aware of and that's broadly adopted. A few\u2026","rel":"","context":"In "Technology"","block_context":{"text":"Technology","link":"https:\/\/www.markwilson.co.uk\/blog\/topic\/technology"},"img":{"alt_text":"Blueprint","src":"https:\/\/i0.wp.com\/c4.staticflickr.com\/3\/2511\/3770016707_bb5aca3a02_m.jpg?resize=350%2C200&ssl=1","width":350,"height":200},"classes":[]},{"id":4983,"url":"https:\/\/www.markwilson.co.uk\/blog\/2013\/07\/exchange-and-outlook-resource-roundup.htm","url_meta":{"origin":5712,"position":3},"title":"Exchange and Outlook resource roundup","author":"Mark Wilson","date":"Friday 19 July 2013","format":false,"excerpt":"I mentioned that I've been attending an Exchange Server 2013 training course, when I wrote earlier in the week\u00a0about creating dynamic distribution groups using custom directory attributes. Our course instructor, Annette Gill, has curated a number of resources and links on her website for Exchange (2007, 2010 and 2013), Windows\u2026","rel":"","context":"In "Technology"","block_context":{"text":"Technology","link":"https:\/\/www.markwilson.co.uk\/blog\/topic\/technology"},"img":{"alt_text":"","src":"http:\/\/ir-uk.amazon-adsystem.com\/e\/ir?t=marsweblo-21&l=as2&o=2&a=B00DXJMZNK","width":350,"height":200},"classes":[]},{"id":684,"url":"https:\/\/www.markwilson.co.uk\/blog\/2007\/02\/retain-or-recycle.htm","url_meta":{"origin":5712,"position":4},"title":"Retain or recycle?","author":"Mark Wilson","date":"Thursday 1 February 2007","format":false,"excerpt":"In a few months time, I'm hoping that we will be able to convert our loft to a new guest room\/my office (den); however that means that I need to do some serious rationalisation of the amount of \"stuff\" we have accumulated. I did sort out a lot when my\u2026","rel":"","context":"In \"Green computing\"","block_context":{"text":"Green computing","link":"https:\/\/www.markwilson.co.uk\/blog\/tag\/green-computing"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":37,"url":"https:\/\/www.markwilson.co.uk\/blog\/2004\/11\/passed-microsoft-certified.htm","url_meta":{"origin":5712,"position":5},"title":"Passed Microsoft Certified Professional exam 70-224","author":"Mark Wilson","date":"Thursday 11 November 2004","format":false,"excerpt":"Today I passed the Microsoft Certified Professional exam 70-224: Installing, configuring and administering Microsoft Exchange 2000 Server. Microsoft's non-disclosure agreement prevents me from saying too much about the exam but much to my relief I scored maximum points in three areas (\"installing and upgrading Exchange 2000 Server\", \"configuring Exchange 2000\u2026","rel":"","context":"In \"Certification\"","block_context":{"text":"Certification","link":"https:\/\/www.markwilson.co.uk\/blog\/tag\/certification"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/posts\/5712","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=5712"}],"version-history":[{"count":2,"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/posts\/5712\/revisions"}],"predecessor-version":[{"id":5722,"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/posts\/5712\/revisions\/5722"}],"wp:attachment":[{"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=5712"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=5712"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.markwilson.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=5712"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}