<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>microsoft exchange server</title><link>https://evotec.xyz/de/tags/microsoft-exchange-server/</link><description>Evotec</description><atom:link href="https://evotec.xyz/de/tags/microsoft-exchange-server/index.xml" rel="self" type="application/rss+xml" /><item><title>Microsoft Exchange – OU picker is empty when creating new user</title><link>https://evotec.xyz/de/blog/microsoft-exchange-ou-picker-empty-creating-new-user/</link><description>If the Exchange ECP OU picker is blank when creating a new mailbox, you may have hit the built-in result limit and need to raise the ECP web.config value.</description><pubDate>Tue, 01 Nov 2016 11:24:27 GMT</pubDate><guid>https://evotec.xyz/de/blog/microsoft-exchange-ou-picker-empty-creating-new-user/</guid><category>error</category><category>exchange</category><category>exchange 2013</category><category>microsoft exchange</category><category>microsoft exchange server</category></item><item><title>Microsoft Exchange – Connecting to remote server failed with the following error message</title><link>https://evotec.xyz/de/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message/</link><description>Connecting to Microsoft Exchange via PowerShell is a standard administrative tasks since Exchange 2007 was released. It’s available in all…</description><pubDate>Thu, 26 Nov 2015 17:47:09 GMT</pubDate><guid>https://evotec.xyz/de/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message/</guid><category>error</category><category>exchange</category><category>microsoft exchange</category><category>microsoft exchange 2007</category><category>microsoft exchange 2010</category><category>microsoft exchange 2013</category><category>microsoft exchange 2016</category><category>microsoft exchange server</category><category>powershell</category><category>ssl certificate</category></item><item><title>Exchange 2013 – Exchange Management Shell (EMS) loading very slow</title><link>https://evotec.xyz/de/blog/exchange-exchange-management-shell-loading-very-slow/</link><description>Troubleshoot slow Exchange Management Shell startup on Exchange 2013 by checking DNS, connectivity, and common PowerShell session bottlenecks.</description><pubDate>Thu, 22 Oct 2015 12:06:43 GMT</pubDate><guid>https://evotec.xyz/de/blog/exchange-exchange-management-shell-loading-very-slow/</guid><category>ems</category><category>exchange</category><category>exchange 2010</category><category>exchange 2013</category><category>exchange 2016</category><category>exchange management shell</category><category>microsoft exchange</category><category>microsoft exchange server</category></item><item><title>Exchange 2013 – TooManyMissingItems or TooManyBadItems</title><link>https://evotec.xyz/de/blog/exchange-2013-too-many-missing-items-permanent-exception-or-too-many-bad-items-permanent-exception-solution/</link><description>During Microsoft Exchange 2010 to Exchange 2013 Migration one of the steps is to migrated all mailboxes from old servers to new servers. Unfortunately with large number of mailboxes a lot of possible things can go wrong during New-MoveReque...</description><pubDate>Mon, 21 Sep 2015 21:19:11 GMT</pubDate><guid>https://evotec.xyz/de/blog/exchange-2013-too-many-missing-items-permanent-exception-or-too-many-bad-items-permanent-exception-solution/</guid><category>Exchange</category><category>exchange 2013</category><category>exchange 2016</category><category>exchange error</category><category>exchange mailbox move</category><category>exchange migration</category><category>exchange server</category><category>mailbox move</category><category>microsoft exchange</category><category>microsoft exchange server</category><category>toomanybaditems</category><category>toomanymissingitems</category></item><item><title>Exchange Server 2010 – Service Pack 3 Update Rollup 11 (SP3 RU11) Released</title><link>https://evotec.xyz/de/blog/exchange-server-2010-service-pack-3-update-rollup-11-sp3-ru11-released/</link><description>Exchange 2010 SP3 RU11 was an important release because it became the minimum version required for supported coexistence with Exchange 2016.</description><pubDate>Wed, 16 Sep 2015 07:05:59 GMT</pubDate><guid>https://evotec.xyz/de/blog/exchange-server-2010-service-pack-3-update-rollup-11-sp3-ru11-released/</guid><category>Exchange</category><category>exchange 2010</category><category>exchange 2010 RU11</category><category>exchange 2010 sp3</category><category>exchange 2010 sp3 ru 11</category><category>exchange server 2010</category><category>microsoft exchange</category><category>microsoft exchange server</category><category>sp3 ru11</category></item><item><title>Exchange 2013 SP1 – The fully qualified domain name for node ‘DAG-EX2013’ could not be found.</title><link>https://evotec.xyz/de/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/</link><description>If Exchange DAG operations fail because the fully qualified domain name for a DAG node cannot be found, check the DAG computer object and its dNSHostName attribute in Active Directory.</description><pubDate>Sat, 14 Mar 2015 17:11:28 GMT</pubDate><guid>https://evotec.xyz/de/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/</guid><category>dag</category><category>dag problem</category><category>evotec</category><category>Exchange</category><category>exchange 2013</category><category>exchange 2013 dag</category><category>exchange 2013 sp1</category><category>microsoft</category><category>microsoft exchange server</category></item></channel></rss>