<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Exchange 2010 on Zachary Loeber's Blog</title><link>https://blog.zacharyloeber.com/categories/exchange-2010/</link><description>Recent content in Exchange 2010 on Zachary Loeber's Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 25 Sep 2015 01:41:25 +0000</lastBuildDate><atom:link href="https://blog.zacharyloeber.com/categories/exchange-2010/index.xml" rel="self" type="application/rss+xml"/><item><title>Exchange: Stop Email Exfiltration</title><link>https://blog.zacharyloeber.com/blog/2015/09/24/excxhange-stop-email-exfiltration/</link><pubDate>Fri, 25 Sep 2015 01:41:25 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/09/24/excxhange-stop-email-exfiltration/</guid><description>&lt;p>When your users leave or get removed from the organization they may still be getting company confidential information. Here is how you can find out and stop this from happening.&lt;/p></description></item><item><title>Exchange: Stop Email Exfiltration</title><link>https://blog.zacharyloeber.com/blog/2015/09/24/excxhange-stop-email-exfiltration/</link><pubDate>Fri, 25 Sep 2015 01:41:25 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/09/24/excxhange-stop-email-exfiltration/</guid><description>&lt;p>When your users leave or get removed from the organization they may still be getting company confidential information. Here is how you can find out and stop this from happening.&lt;/p></description></item><item><title>Exchange: Database Leveling Redux</title><link>https://blog.zacharyloeber.com/blog/2015/04/06/exchange-database-leveling-redux/</link><pubDate>Tue, 07 Apr 2015 00:12:33 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2015/04/06/exchange-database-leveling-redux/</guid><description>&lt;p>Some time ago I &lt;a href="https://blog.zacharyloeber.com/2014/01/07/exchange-20102013-database-leveling-script/">tackled the challenge&lt;/a> of constructing a variant of the bin packing algorithm for leveling out Exchange databases’ size with the least amount of mailbox migrations necessary. Since then, I’ve been approached by a few people in dreadfully large environments looking for help with errors and compatibility issues around the script I released. I’ve finally rounded back to this script to do it some justice.&lt;/p></description></item><item><title>Exchange Mailbox Auditing with Powershell</title><link>https://blog.zacharyloeber.com/blog/2014/11/24/exchange-mailbox-auditing-with-powershell/</link><pubDate>Tue, 25 Nov 2014 05:55:01 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/11/24/exchange-mailbox-auditing-with-powershell/</guid><description>&lt;p>Some time ago I wrote a script and GUI for performing security audits of Exchange mailbox and calendar rights in an environment. This script was far more popular than I anticipated and, I’m ashamed to say, was rather poorly written by my current Powershell standards. There is an obvious need to simplify the extraction of mailbox permissions or my old script would not still be so popular. So I’ve started to revisit my old code for this project in hopes of remaking it with my PowerShell reporting engine. The first step in this process is to pull out the several bits of code that do the actual rights/permissions extraction. I think I’ve finally got this part done and see no reason not to release this mini-library of functions first.&lt;/p></description></item><item><title>Lync and UM Correlation with Powershell</title><link>https://blog.zacharyloeber.com/blog/2014/11/13/lync-and-um-correlation-with-powershell/</link><pubDate>Fri, 14 Nov 2014 03:31:13 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/11/13/lync-and-um-correlation-with-powershell/</guid><description>&lt;p>I’ve been working on an Exchange/Lync voice deployment lately and have found a new level of frustration for the lack of connectivity between the several voice components involved in turning up such a solution. That being said it is not very difficult to validate your deployment with a bit of Powershell.&lt;/p>
&lt;p>There are a few necessary results to gather where I believe it can be easy to ‘miss’ configuration steps when turning up or disabling users:&lt;/p></description></item><item><title>Exchange: Handling Old Log and Other Files</title><link>https://blog.zacharyloeber.com/blog/2014/09/26/exchange-handling-old-log-and-other-files/</link><pubDate>Fri, 26 Sep 2014 19:41:59 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/09/26/exchange-handling-old-log-and-other-files/</guid><description>&lt;p>In Exchange old logs can really build up fast. Not database transaction logs but rather temporary transport, client access, IIS, and other debug related crap that typically default to locations either on your system drive or Exchange install path. Of course, Powershell scripting can provide a decent solution for this problem.&lt;/p>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>More than any other version, Exchange 2013 seems to like logging information to disk. By default, much of what gets logged will not auto-rotate (or if it does, it happens infrequently) either so you end up with this slow ticking time-bomb in your environment.&lt;/p></description></item><item><title>Exchange: Handling Old Log and Other Files</title><link>https://blog.zacharyloeber.com/blog/2014/09/26/exchange-handling-old-log-and-other-files/</link><pubDate>Fri, 26 Sep 2014 19:41:59 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/09/26/exchange-handling-old-log-and-other-files/</guid><description>&lt;p>In Exchange old logs can really build up fast. Not database transaction logs but rather temporary transport, client access, IIS, and other debug related crap that typically default to locations either on your system drive or Exchange install path. Of course, Powershell scripting can provide a decent solution for this problem.&lt;/p>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>More than any other version, Exchange 2013 seems to like logging information to disk. By default, much of what gets logged will not auto-rotate (or if it does, it happens infrequently) either so you end up with this slow ticking time-bomb in your environment.&lt;/p></description></item><item><title>Update: Get-CalendarPermission</title><link>https://blog.zacharyloeber.com/blog/2014/09/24/update-get-calendarpermission/</link><pubDate>Wed, 24 Sep 2014 17:43:07 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/09/24/update-get-calendarpermission/</guid><description>&lt;p>Going through older code is a bit like looking through an old yearbook or photo album. If the pictures within are old enough you usually end up laughing at how little you recognize yourself and maybe even marvel a bit at how far you have come. This old function I wrote isn’t the worst of my code but I was still able to update it for measurable improvements.&lt;/p></description></item><item><title>Exchange: Receive Connector Tango! – Part 2</title><link>https://blog.zacharyloeber.com/blog/2014/08/23/exchange-receive-connector-tango-part-2/</link><pubDate>Sat, 23 Aug 2014 21:20:31 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/08/23/exchange-receive-connector-tango-part-2/</guid><description>&lt;p>&lt;a href="https://blog.zacharyloeber.com/2014/07/06/exchange-receive-connector-tango-part-1/">In part 1 of this series&lt;/a> I discussed some basic knowledge requirements to get a better grip on receive connectors in Exchange. I continue that conversation with some examples of improperly configured connectors and the issues they may cause. I finish up the discussion with a script you can use to scan your environment for such configurations.&lt;/p></description></item><item><title>Exchange: Auto Batching 2013 Migrations</title><link>https://blog.zacharyloeber.com/blog/2014/07/28/exchange-auto-batching-2013-migrations/</link><pubDate>Mon, 28 Jul 2014 16:48:24 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/07/28/exchange-auto-batching-2013-migrations/</guid><description>&lt;p>Here is a quick script I put together for automatically creating Exchange 2013 mailbox migration batches. This is useful for the final stages of an Exchange 2013 upgrade among other things.&lt;/p></description></item><item><title>Exchange: Auto Batching 2013 Migrations</title><link>https://blog.zacharyloeber.com/blog/2014/07/28/exchange-auto-batching-2013-migrations/</link><pubDate>Mon, 28 Jul 2014 16:48:24 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/07/28/exchange-auto-batching-2013-migrations/</guid><description>&lt;p>Here is a quick script I put together for automatically creating Exchange 2013 mailbox migration batches. This is useful for the final stages of an Exchange 2013 upgrade among other things.&lt;/p></description></item><item><title>Exchange Log Level GUI Script</title><link>https://blog.zacharyloeber.com/blog/2014/07/06/exchange-log-level-gui-script/</link><pubDate>Mon, 07 Jul 2014 03:30:20 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/07/06/exchange-log-level-gui-script/</guid><description>&lt;p>I ran into a situation recently where I was forced to amp up the Exchange logging levels to further troubleshoot an issue with some pretty specific Exchange components. I found myself wanting a quick GUI to view and set the levels but found none. So I used this as an opportunity to learn a bit about xaml based GUIs and powershell. The result is this simple, but useful, Exchange log level GUI script which was written for Exchange 2013 but should also run on 2010.&lt;/p></description></item><item><title>Exchange: Receive Connector Tango! – Part 1</title><link>https://blog.zacharyloeber.com/blog/2014/07/06/exchange-receive-connector-tango-part-1/</link><pubDate>Mon, 07 Jul 2014 03:25:13 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/07/06/exchange-receive-connector-tango-part-1/</guid><description>&lt;p>Exchange receive connectors are often configured incorrectly or worse, insecurely. This is the first of a two part series about Exchange receive connectors and what to look out for when setting them up.&lt;/p></description></item><item><title>Exchange: Update Distribution Group Managers Script</title><link>https://blog.zacharyloeber.com/blog/2014/04/23/exchange-update-distribution-group-managers-script/</link><pubDate>Thu, 24 Apr 2014 00:26:37 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/04/23/exchange-update-distribution-group-managers-script/</guid><description>&lt;p>A small script to automatically update distribution group owners based on an AD security group.&lt;/p></description></item><item><title>AD Audit Report with Powershell: Part 3</title><link>https://blog.zacharyloeber.com/blog/2014/01/10/ad-audit-report-with-powershell-part-3/</link><pubDate>Sat, 11 Jan 2014 04:16:29 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/01/10/ad-audit-report-with-powershell-part-3/</guid><description>&lt;p>This is my third and final major update to my AD auditing script. This includes a handful of new useful sections such as domain published printers, NPS servers, DHCP servers, as well as SCCM sites and DPs. Other improvements include easier to use script parameters and bug fixes.&lt;/p></description></item><item><title>Exchange 2010/2013: Database Leveling Script</title><link>https://blog.zacharyloeber.com/blog/2014/01/07/exchange-20102013-database-leveling-script/</link><pubDate>Tue, 07 Jan 2014 22:08:16 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2014/01/07/exchange-20102013-database-leveling-script/</guid><description>&lt;p>It is common to randomly choose mailbox databases when creating or migrating user mailboxes in Exchange. I actually recommend this practice unless you are setting up a tiered user/storage environment. Unfortunately this may result in an unequal distribution of data which, in turn, can result in an environment where mailbox databases are wildly different in size. In this post I will discuss an approach to leveling the databases so they are equal in size by moving mailboxes between them.&lt;/p></description></item><item><title>AD Audit Report With Powershell: Part 2</title><link>https://blog.zacharyloeber.com/blog/2013/11/02/ad-audit-report-with-powershell-part-2/</link><pubDate>Sat, 02 Nov 2013 17:41:25 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2013/11/02/ad-audit-report-with-powershell-part-2/</guid><description>&lt;p>I’ve updated my AD auditing report. The forest level report now includes AD integrated zones, GPOs, and fixed code to conform to strict v2 Powershell. I’ve also included a new domain level report! This report provides some user/group stats, all privileged group membership, and more.&lt;/p></description></item><item><title>Active Directory Audit Report With Powershell</title><link>https://blog.zacharyloeber.com/blog/2013/10/18/active-directory-audit-report-with-powershell/</link><pubDate>Fri, 18 Oct 2013 15:13:11 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2013/10/18/active-directory-audit-report-with-powershell/</guid><description>&lt;p>Not too long ago I wrote a quick post on how easy it is to gather information from AD. As a case in point example I provided a script to gather all the disabled user accounts which are still assigned Lync IDs. In this script I take it one step further and provide a full blown Active Directory reporting script which can be produced with any non-privileged domain user account.&lt;/p></description></item><item><title>Exchange 2010 Mailbox Audit Report GUI</title><link>https://blog.zacharyloeber.com/blog/2013/06/28/exchange-2010-mailbox-audit-report-gui/</link><pubDate>Fri, 28 Jun 2013 20:17:29 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2013/06/28/exchange-2010-mailbox-audit-report-gui/</guid><description>&lt;p>I’ve updated the original &lt;a href="https://blog.zacharyloeber.com/2013/05/09/exchange-2010-mailbox-audit-report-script/">Exchange Mailbox Audit Report Script&lt;/a> with some new features and bug fixes. These updates have also set the stage for the entire script to be wrapped with a GUI! Here is the initial release of the Mailbox Audit Report GUI for your auditing needs.&lt;/p></description></item><item><title>Exchange 2010 Mailbox Audit Report Script</title><link>https://blog.zacharyloeber.com/blog/2013/05/09/exchange-2010-mailbox-audit-report-script/</link><pubDate>Fri, 10 May 2013 02:33:54 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2013/05/09/exchange-2010-mailbox-audit-report-script/</guid><description>&lt;h1 id="exchange-2010-mailbox-audit-report-script">Exchange 2010 Mailbox Audit Report Script&lt;/h1>
&lt;p>Recently I’ve released a number of scripts such as the &lt;a href="http://gallery.technet.microsoft.com/Colorize-HTML-Table-Cells-2ea63acd">HTML Table Colorizer&lt;/a>, &lt;a href="http://gallery.technet.microsoft.com/Get-Exchange-Calendar-5bb4f527">Exchange Mailbox Calendar Permission Function&lt;/a>, and the &lt;a href="http://gallery.technet.microsoft.com/Exchange-Mailbox-GUI-5b204590">Exchange Mailbox GUI&lt;/a>. These were all actually created specifically as support scripts for a report generation powershell tool I’ve been working on, the Exchange Mailbox Auditing Tool.&lt;/p></description></item><item><title>Exchange: Get Calendar Permissions (multilingual edition)</title><link>https://blog.zacharyloeber.com/blog/2013/04/28/exchange-get-calendar-permissions-multilingual-edition/</link><pubDate>Sun, 28 Apr 2013 17:35:54 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2013/04/28/exchange-get-calendar-permissions-multilingual-edition/</guid><description>&lt;p>Some time ago I released &lt;a href="http://gallery.technet.microsoft.com/Exchange-2010-Calendar-21695fde" title="Exchange 2010 Calendar Permission GUI">a rather simplistic GUI for viewing Exchange 2010 mailbox calendar permissions&lt;/a>. Because of a semi-related script I’m working on currently I rounded back and recreated that GUI script to be a powershell function instead. This is the result.&lt;/p></description></item><item><title>Exchange: Mailbox GUI</title><link>https://blog.zacharyloeber.com/blog/2013/04/07/exchange-mailbox-gui/</link><pubDate>Mon, 08 Apr 2013 01:10:21 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2013/04/07/exchange-mailbox-gui/</guid><description>&lt;h1 id="exchange-2010-mailbox-gui">Exchange 2010 Mailbox GUI&lt;/h1>
&lt;p>A powershell GUI for selecting and performing actions against multiple Exchange mailboxes.&lt;/p></description></item><item><title>Exchange: Co-existence Client Access Preparation Report</title><link>https://blog.zacharyloeber.com/blog/2013/01/15/exchange-co-existence-client-access-preparation-report/</link><pubDate>Wed, 16 Jan 2013 03:36:50 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2013/01/15/exchange-co-existence-client-access-preparation-report/</guid><description>&lt;p>If you upgrade Exchange in a co-existence scenario (you want to keep the same client access namespace) there is one crucial moment of truth which must be overcome. This is the phase of the migration I’ve come to call the “dns flip-over” or the “client access part”. Without preparation this part of the migration can be a real headache as issues are directly experienced by your end users.  This is a simple report card you can use to prepare you for this moment.&lt;/p></description></item><item><title>Exchange – The State Of External Client Access</title><link>https://blog.zacharyloeber.com/blog/2012/11/22/exchange-the-state-of-external-client-access/</link><pubDate>Thu, 22 Nov 2012 19:58:04 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/11/22/exchange-the-state-of-external-client-access/</guid><description>&lt;h1 id="introduction">Introduction&lt;/h1>
&lt;p>Most within the messaging and collaboration industry are hyped up about the next wave of Microsoft collaboration and messaging products which are soon to be released. Among these products is Exchange 2013 RTM. This type of release typically precedes yet another wave of architecture upgrades across the corporate landscape. Some of these (beta testers) will be will undoubtedly upgrade to Exchange 2013.&lt;/p>
&lt;p>Other corporations will start to feel the burn to upgrade as well. These will be organizations which realize that their Exchange 2003/2007 infrastructure is nearing a decade old existence and cannot meet the demands of their ever growing mobile workforce. Realizing they are behind the curve, they may feel hastened to upgrade as well, possibly just to Exchange 2010. Regardless the reason in choosing to upgrade their messaging infrastructure, there are critical design decisions which need to be made in how clients access this infrastructure both internally and externally. This article focuses solely on the external access aspect of the infrastructure.&lt;/p></description></item><item><title>Exchange: Automatically Generating Configuration Scripts</title><link>https://blog.zacharyloeber.com/blog/2012/09/29/exchange-automatically-generating-configuration-scripts/</link><pubDate>Sat, 29 Sep 2012 17:33:20 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/09/29/exchange-automatically-generating-configuration-scripts/</guid><description>&lt;p>I’ve started a side project which is born from personally having to redo many aspects of an Exchange migration over and over again. Most of this, I believe, can be automated. Some aspects of this process include exchange server role prerequisite procedures, co-existence configuration, DAG/CAS configuration, and other general reminders and processes.&lt;/p></description></item><item><title>Exchange 2010: Poor Mans Monitoring 1.5</title><link>https://blog.zacharyloeber.com/blog/2012/08/27/exchange-2010-poor-mans-monitoring-1-5/</link><pubDate>Tue, 28 Aug 2012 02:40:20 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/08/27/exchange-2010-poor-mans-monitoring-1-5/</guid><description>&lt;p>Just a quick upgrade to the script I posted earlier. This script is for monitoring and/or maintaining your Exchange 2010 mailboxes. It is meant to help an admin be proactive in their exchange environment. I updated the script to be a bit more customizable and fixed some obvious issues. The primary changes are removing the requirement for the MS chart controls as well as introducing an area of code just for custom scripts. There is always room for improvement but this version is a good start. &lt;del>Download &lt;a href="https://blog.zacharyloeber.com/wp-content/uploads/2012/08/Troubleshoot-MailboxServer.ps1">Troubleshoot-MailboxServer&lt;/a>or. Or&lt;/del> Grab the recent updates at the &lt;a href="http://gallery.technet.microsoft.com/scriptcenter/Troubleshoot-Exchange-2010-aecdc23f">MS script repository&lt;/a> (Edit: Just to to the script repository as any newest version will be dropped there first. I already have a 1.6 version available there).&lt;/p></description></item><item><title>Exchange 2010: Automated Firewall Rule Generation 1.5</title><link>https://blog.zacharyloeber.com/blog/2012/08/11/exchange-2010-automated-firewall-rule-generation-1-5/</link><pubDate>Sat, 11 Aug 2012 10:17:15 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/08/11/exchange-2010-automated-firewall-rule-generation-1-5/</guid><description>&lt;p>Just some aesthetic changes for upload to the Microsoft scripting repository. Biggest addition is the ability to run the script without parameters (just upgrade the included environment csv to your liking and run the script). Other big addition is the help section.&lt;/p>
&lt;p>&lt;a href="https://blog.zacharyloeber.com/wp-content/uploads/2012/08/GenerateExchangeFirewallRequirements_1-5.zip">GenerateExchangeFirewallRequirements_1-5&lt;/a>&lt;/p>
&lt;p>or&lt;/p>
&lt;p>&lt;a href="http://gallery.technet.microsoft.com/scriptcenter/Generate-Exchange-2010-5fa2344d">At the Microsoft Script Repository&lt;/a>&lt;/p></description></item><item><title>Exchange 2010: Poor Man’s Monitoring</title><link>https://blog.zacharyloeber.com/blog/2012/07/22/exchange-2010-poor-mans-monitoring/</link><pubDate>Sun, 22 Jul 2012 20:11:16 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/07/22/exchange-2010-poor-mans-monitoring/</guid><description>&lt;p>I quietly released a new script into the wild the other day, Troubleshoot-MailboxServer.ps1. This script is meant for monitoring, fixing, and reporting on Exchange 2010 database servers. It pretty much just wraps around and reports on troubleshooting scripts found in %ExchangeInstallPath%Scripts. I also set it so you can have an email sent including warning/error color coded report upon completion.&lt;/p></description></item><item><title>Exchange 2010: Even More Migration Tips</title><link>https://blog.zacharyloeber.com/blog/2012/07/10/exchange-2010-even-more-migration-tips/</link><pubDate>Wed, 11 Jul 2012 00:34:32 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/07/10/exchange-2010-even-more-migration-tips/</guid><description>&lt;p>It has been a while since I passed on some personal experiences when performing Exchange 2010 migrations. I thought it was about time to update my list to include some more of the lesser known aspects of an Exchange 2010 migration.&lt;/p></description></item><item><title>Active Directory: Best Practices Workbook</title><link>https://blog.zacharyloeber.com/blog/2012/05/28/active-directory-best-practices-workbook/</link><pubDate>Mon, 28 May 2012 21:57:58 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/05/28/active-directory-best-practices-workbook/</guid><description>&lt;p>This is a checklist for technicians performing Active Directory assessments. It is broken down by category and best practice. Some items listed are not really a best practice, but rather something which you may find in an environment which should be rectified (as part of an audit perhaps).&lt;/p></description></item><item><title>Assessing Like A Microsoft Technician</title><link>https://blog.zacharyloeber.com/blog/2012/03/09/assessing-like-a-microsoft-technician/</link><pubDate>Sat, 10 Mar 2012 03:08:26 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/03/09/assessing-like-a-microsoft-technician/</guid><description>&lt;h1 id="troubleshooting-like-a-microsoft-technician">Troubleshooting Like A Microsoft Technician&lt;/h1>
&lt;p>I have been doing more and more site assessments for Active Directory, Exchange, Lync, and VMware. As such, I’ve been slowly refining the toolset that I use to gather data and troubleshoot existing environment issues. Here is a list of site assessment tools I’m finding that I regularly return to for rapid analysis or information gathering at a site. All of these tools are free.&lt;/p></description></item><item><title>Exchange 2010: Changing an invalid DNS suffixed server</title><link>https://blog.zacharyloeber.com/blog/2012/02/29/exchange-2010-changing-an-invalid-dns-suffixed-server/</link><pubDate>Thu, 01 Mar 2012 05:30:13 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/02/29/exchange-2010-changing-an-invalid-dns-suffixed-server/</guid><description>&lt;p>I ran into an interesting Exchange 2010/2007 co-existence issue today. After a new Exchange 2010 (all-in-one) server was introduced into the environment traffic would only flow from the 2010 server to the 2007 hub/cas server and not the other way around. The mail queues stated the last error to be&lt;/p>
&lt;pre>“Initial error: 451 4.4.0 dns query failed. The error was: SMTPsend.dns.nonexistentdomain; nonexistent”&lt;/pre></description></item><item><title>Exchange 2010: Client Access Role Configuration Report</title><link>https://blog.zacharyloeber.com/blog/2012/02/04/exchange-2010-client-access-role-configuration-report/</link><pubDate>Sat, 04 Feb 2012 14:03:29 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2012/02/04/exchange-2010-client-access-role-configuration-report/</guid><description>&lt;p>Ok, so I woke up and was wide awake at 4am this morning. I took it as a sign to lose my mind for a while and get to hacking another script. The result is a client access setting report script which includes all internal and external paths along with their authentication settings. It needs some prettying up and a bit of love but it does exactly what I’ve wanted in Exchange 2010, gives me an overall view of all client access settings (specifically related to IIS). Enjoy.&lt;/p></description></item><item><title>Exchange 2010 One-liner: Get All Network Interface Information</title><link>https://blog.zacharyloeber.com/blog/2011/08/19/exchange-2010-one-liner-get-all-network-interface-information/</link><pubDate>Fri, 19 Aug 2011 16:57:15 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2011/08/19/exchange-2010-one-liner-get-all-network-interface-information/</guid><description>&lt;p>Here are a few quick powershell one-liners to get all the network interface information in your exchange environment:&lt;/p>
&lt;pre>$ExchServers=(Get-ExchangeServer); @(foreach ($Srv in $ExchServers) {Get-WmiObject -Class Win32_NetworkAdapterConfiguration -Filter IPEnabled=TRUE -ComputerName $Srv.Name | select @{Name="Server";Expression={$Srv.Name}},@{Name="DNS Host Name";Expression={$_.DNSHostName}},@{Name="Server Role";Expression={$Srv.ServerRole}},Description,@{Name="IP Address";Expression={$_.IPAddress}},@{Name="IP Subnet";Expression={$_.IPSubnet}},@{Name="Default Gateway";Expression={$_.DefaultIPGateway}},@{Name="Mac Address";Expression={$_.MacAddress}},@{Name="DNS Suffix Search Order";Expression={$_.DNSDomainSuffixSearchOrder}},@{Name="DNS Server Search Order";Expression={$_.DNSServerSearchOrder}},FullDNSRegistrationEnabled}) |Export-Csv -NoTypeInformation "C:\Temp\Exchange-network.csv"&lt;/pre>
&lt;p>If you just want interface information for Exchange 2010 servers:&lt;/p>
&lt;pre>$ExchServers=(Get-ExchangeServer | where {$_.ServerRole -ne "None"}); @(foreach ($Srv in $ExchServers) {Get-WmiObject -Class Win32_NetworkAdapterConfiguration -Filter IPEnabled=TRUE -ComputerName $Srv.Name | select @{Name="Server";Expression={$Srv.Name}},@{Name="DNS Host Name";Expression={$_.DNSHostName}},@{Name="Server Role";Expression={$Srv.ServerRole}},Description,@{Name="IP Address";Expression={$_.IPAddress}},@{Name="IP Subnet";Expression={$_.IPSubnet}},@{Name="Default Gateway";Expression={$_.DefaultIPGateway}},@{Name="Mac Address";Expression={$_.MacAddress}},@{Name="DNS Suffix Search Order";Expression={$_.DNSDomainSuffixSearchOrder}},@{Name="DNS Server Search Order";Expression={$_.DNSServerSearchOrder}},FullDNSRegistrationEnabled}) |Export-Csv -NoTypeInformation "C:\Temp\Exchange2010-network.csv"&lt;/pre>
&lt;p> &lt;/p></description></item><item><title>Exchange 2010: A Few More Migration Tips</title><link>https://blog.zacharyloeber.com/blog/2011/08/13/exchange-2010-a-few-more-migration-tips/</link><pubDate>Sat, 13 Aug 2011 23:43:04 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2011/08/13/exchange-2010-a-few-more-migration-tips/</guid><description>&lt;p>Here are a few more notes from the field to consider when you are planning your Exchange 2010 deployment and migration. Some of these items are good to know even after you have completed your migration and may help with overall system stability.&lt;/p>
&lt;h2>&lt;/h2></description></item><item><title>Exchange 2010: Network Communication Table</title><link>https://blog.zacharyloeber.com/blog/2011/07/30/exchange-2010-network-communication-table/</link><pubDate>Sat, 30 Jul 2011 17:06:36 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2011/07/30/exchange-2010-network-communication-table/</guid><description>&lt;p>I figured I’d post the massive table of firewall rules I compiled for my Exchange 2010 firewall generation script. It has both the source and destination roles for many aspects of an Exchange environment. Where there are ???’s is where I’m simply not certain (mainly around encryption between certain roles). If anyone spots any mistakes or omissions please let me know and I’ll update the accordingly.&lt;/p>
&lt;p>&lt;a title="Exchange 2010 Network Communication Table By Role" href="https://blog.zacharyloeber.com/wp-content/uploads/2011/07/FirewallRules.html" target="_blank">Exchange 2010 Network Communication Table By Role&lt;/a>&lt;/p></description></item><item><title>Exchange 2010: Automated Firewall Rule Generation 1.4</title><link>https://blog.zacharyloeber.com/blog/2011/07/29/exchange-2010-automated-firewall-rule-generation-1-4/</link><pubDate>Fri, 29 Jul 2011 15:28:07 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2011/07/29/exchange-2010-automated-firewall-rule-generation-1-4/</guid><description>&lt;p>I made some updates to the automated firewall rule generation script. This includes some updates to the firewall rule spreadsheet to give information on setting setic ports and port ranges for RPC based services. This csv file may be a good general reference even without the script.&lt;/p></description></item><item><title>Exchange 2010: Automated Firewall Rule Generation 1.2</title><link>https://blog.zacharyloeber.com/blog/2011/07/20/exchange-2010-automated-firewall-rule-generation-1-2/</link><pubDate>Wed, 20 Jul 2011 16:35:08 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2011/07/20/exchange-2010-automated-firewall-rule-generation-1-2/</guid><description>&lt;p>I made a few changes to this script to make it more modular and to allow for more exceptions in regards to DAGs and sites. Enjoy!&lt;/p>
&lt;p>&lt;a href="https://blog.zacharyloeber.com/wp-content/uploads/2011/07/ExchangeFirewallRequestGenerator1_2.zip" title="Exchange 2010: Automated Firewall Rule Generation">Exchange 2010 Firewall Rule Generation Script&lt;/a>&lt;/p></description></item><item><title>Exchange 2010: Protect VIP Mailboxes with Exclusive Scopes</title><link>https://blog.zacharyloeber.com/blog/2011/05/04/exchange-2010-protect-vip-mailboxes-with-exclusive-scopes/</link><pubDate>Wed, 04 May 2011 21:26:37 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2011/05/04/exchange-2010-protect-vip-mailboxes-with-exclusive-scopes/</guid><description>&lt;p> &lt;/p>
&lt;p>Prior to starting my new job I wanted to ensure that my previous employer was able to protect VIP mailboxes in their Exchange 2010 SP1 organization. I had to do this with exclusive scopes and these are the steps I had to follow. A general knowledge of role based security is assumed in this post.&lt;/p></description></item><item><title>Exchange – Notify Forwarded Accounts Script</title><link>https://blog.zacharyloeber.com/blog/2011/01/10/exchange-notify-forwarded-accounts-script/</link><pubDate>Mon, 10 Jan 2011 20:00:19 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2011/01/10/exchange-notify-forwarded-accounts-script/</guid><description>&lt;p>In cleaning up a large number of disabled user accounts in AD I wanted a way to notify a large number of users specifically that they were being forwarded e-mail from another account. This was part of an effort to clean up AD a bit before moving everyone over to Exchange 2010 but it can be used independently of any one project as part of a general AD maintenance plan.&lt;/p></description></item><item><title>Exchange 2010 (SP1): Pre-Deployment Tips</title><link>https://blog.zacharyloeber.com/blog/2010/12/17/exchange-2010-sp1-pre-deployment-tips/</link><pubDate>Fri, 17 Dec 2010 18:55:00 +0000</pubDate><guid>https://blog.zacharyloeber.com/blog/2010/12/17/exchange-2010-sp1-pre-deployment-tips/</guid><description>&lt;p>I recently had the opportunity to experience all of the blood, sweat, and tears of migrating a minimally maintained Exchange 2003 infrastructure to Exchange 2010 (and mid-way through, an upgrade to 2010 SP1). All of the docs out on the web for migrations make it seem soooo easy. But if you are going to do anything other than a single server install and are doing things like, oh say; hardware load balancing, Exchange 2003 co-existence, or working in an old multi-domain forest then you are in for some punishment. I think I ran into every possible issue that you can have with an Exchange 2010 migration. One guide that helped me in this endeavor was the &lt;a title="Rapid Exchange 2003 to 2010 Transition Guide" href="http://msexchangegeek.com/2010/01/30/rapid-transition-guide-from-exchange-2003-to-exchange-2010/" target="_blank">rapid transition guide from Exchange 2003 to Exchange 2010&lt;/a>. This guide didn’t cover every aspect for me though, here are a few things that may save you a little bit of hassle. I’ve been meaning to publish this for a while and I have a whole lot more notes from this experience but this is a start.&lt;/p>
&lt;h2>&lt;/h2></description></item></channel></rss>