<feed xmlns="http://www.w3.org/2005/Atom"><title>microsoft exchange server</title><id>https://evotec.xyz/es/tags/microsoft-exchange-server/index.atom.xml</id><updated>2016-11-01T11:24:27.0000000Z</updated><subtitle>Evotec</subtitle><link href="https://evotec.xyz/es/tags/microsoft-exchange-server/" /><link href="https://evotec.xyz/es/tags/microsoft-exchange-server/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>Microsoft Exchange – OU picker is empty when creating new user</title><id>https://evotec.xyz/es/blog/microsoft-exchange-ou-picker-empty-creating-new-user/</id><link href="https://evotec.xyz/es/blog/microsoft-exchange-ou-picker-empty-creating-new-user/" /><updated>2016-11-01T11:24:27.0000000Z</updated><summary>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.</summary><category term="error" /><category term="exchange" /><category term="exchange 2013" /><category term="microsoft exchange" /><category term="microsoft exchange server" /></entry><entry><title>Microsoft Exchange – Connecting to remote server failed with the following error message</title><id>https://evotec.xyz/es/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message/</id><link href="https://evotec.xyz/es/blog/microsoft-exchange-connecting-to-remote-server-failed-with-the-following-error-message/" /><updated>2015-11-26T17:47:09.0000000Z</updated><summary>Connecting to Microsoft Exchange via PowerShell is a standard administrative tasks since Exchange 2007 was released. It’s available in all…</summary><category term="error" /><category term="exchange" /><category term="microsoft exchange" /><category term="microsoft exchange 2007" /><category term="microsoft exchange 2010" /><category term="microsoft exchange 2013" /><category term="microsoft exchange 2016" /><category term="microsoft exchange server" /><category term="powershell" /><category term="ssl certificate" /></entry><entry><title>Exchange 2013 – Exchange Management Shell (EMS) loading very slow</title><id>https://evotec.xyz/es/blog/exchange-exchange-management-shell-loading-very-slow/</id><link href="https://evotec.xyz/es/blog/exchange-exchange-management-shell-loading-very-slow/" /><updated>2015-10-22T12:06:43.0000000Z</updated><summary>Troubleshoot slow Exchange Management Shell startup on Exchange 2013 by checking DNS, connectivity, and common PowerShell session bottlenecks.</summary><category term="ems" /><category term="exchange" /><category term="exchange 2010" /><category term="exchange 2013" /><category term="exchange 2016" /><category term="exchange management shell" /><category term="microsoft exchange" /><category term="microsoft exchange server" /></entry><entry><title>Exchange 2013 – TooManyMissingItems or TooManyBadItems</title><id>https://evotec.xyz/es/blog/exchange-2013-too-many-missing-items-permanent-exception-or-too-many-bad-items-permanent-exception-solution/</id><link href="https://evotec.xyz/es/blog/exchange-2013-too-many-missing-items-permanent-exception-or-too-many-bad-items-permanent-exception-solution/" /><updated>2015-09-21T21:19:11.0000000Z</updated><summary>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...</summary><category term="Exchange" /><category term="exchange 2013" /><category term="exchange 2016" /><category term="exchange error" /><category term="exchange mailbox move" /><category term="exchange migration" /><category term="exchange server" /><category term="mailbox move" /><category term="microsoft exchange" /><category term="microsoft exchange server" /><category term="toomanybaditems" /><category term="toomanymissingitems" /></entry><entry><title>Exchange Server 2010 – Service Pack 3 Update Rollup 11 (SP3 RU11) Released</title><id>https://evotec.xyz/es/blog/exchange-server-2010-service-pack-3-update-rollup-11-sp3-ru11-released/</id><link href="https://evotec.xyz/es/blog/exchange-server-2010-service-pack-3-update-rollup-11-sp3-ru11-released/" /><updated>2015-09-16T07:05:59.0000000Z</updated><summary>Exchange 2010 SP3 RU11 was an important release because it became the minimum version required for supported coexistence with Exchange 2016.</summary><category term="Exchange" /><category term="exchange 2010" /><category term="exchange 2010 RU11" /><category term="exchange 2010 sp3" /><category term="exchange 2010 sp3 ru 11" /><category term="exchange server 2010" /><category term="microsoft exchange" /><category term="microsoft exchange server" /><category term="sp3 ru11" /></entry><entry><title>Exchange 2013 SP1 – The fully qualified domain name for node ‘DAG-EX2013’ could not be found.</title><id>https://evotec.xyz/es/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/</id><link href="https://evotec.xyz/es/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/" /><updated>2015-03-14T17:11:28.0000000Z</updated><summary>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.</summary><category term="dag" /><category term="dag problem" /><category term="evotec" /><category term="Exchange" /><category term="exchange 2013" /><category term="exchange 2013 dag" /><category term="exchange 2013 sp1" /><category term="microsoft" /><category term="microsoft exchange server" /></entry></feed>