exchange_sphttp://blogs.technet.com/b/exchange_sp/en-USTelligent Evolution Platform Developer Build (Build: 5.6.50428.7875)Misterioso bucle de correo en el servidor Transporte perimetral: compruebe los límites de tamañohttp://blogs.technet.com/b/exchange_sp/archive/2013/05/09/misterioso-bucle-de-correo-en-el-servidor-transporte-perimetral-compruebe-los-l-237-mites-de-tama-241-o.aspxThu, 09 May 2013 06:34:50 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3571633OfficeLocalization0<HTML><HEAD> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> </HEAD> <BODY> </P> <P>Artículo original publicado el viernes, 29 de marzo de 2013</P> <P>Soy ingeniero de asistencia de <ACRONYM title="Asistencia y atención al cliente">CSS</ACRONYM>. Estaba trabajando con un cliente que había informado de un error de bucle de correo para un dominio específico como <SPAN class=command>contoso.com</SPAN>, donde este error solo se observaba en correos electrónicos grandes.&nbsp;Sí, es muy misterioso hasta que llegas a entender que el bucle de correo viene provocado por la restricción de tamaño del conector de envío.&nbsp;He pensado que este tema era lo bastante curioso como para compartirlo.<STRONG></STRONG></P> <H2>Entender la configuración y la causa principal del problema:</H2> <P>En un primer momento creí que podría ser el resultado de que el servidor perimetral estuviera configurado para utilizar un servidor <ACRONYM title="DNS">DNS</ACRONYM> externo (un servidor DNS que resuelve hosts externos). Normalmente, cuando el servidor Transporte perimetral está configurado para utilizar un DNS externo, resuelve el nombre del dominio como las direcciones IP públicas (suele señalarse a sí mismo, al firewall externo o al proveedor de servicio) en vez de como un servidor Transporte de concentradores en el sitio de Active Directory, de forma que se provoca un bucle de correo.</P> <P>Al reproducir el problema, descubrí que el servidor Transporte perimetral no estaba configurado para utilizar un servidor DNS externo. El entorno que configuré para reproducir el problema tenía el aspecto de este diagrama:</P> <P><A href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/6558.clip_5F00_image002_5F00_3D7AC522.png"><IMG style="BACKGROUND-IMAGE: none; BORDER-RIGHT-WIDTH: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; DISPLAY: inline; BORDER-TOP-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px; PADDING-TOP: 0px" title=clip_image002 border=0 alt=clip_image002 src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/1307.clip_5F00_image002_5F00_thumb_5F00_26BB7D99.png" width=623 height=199></A></P> <P>&nbsp;</P> <P>Esto es lo que pasa en este escenario: cuando el servidor Transporte perimetral recibe un correo electrónico de 20 MB de un remitente de Internet, lo acepta. El servidor Transporte perimetral tiene dos conectores que coinciden con el espacio de dirección, uno para el espacio de dirección <SPAN class="fqdn lightyellow">contoso.com</SPAN> al sitio de Active Directory y otro para el espacio de dirección <SPAN class="fqdn lightyellow">*</SPAN>. Cuando se toma la decisión de enrutamiento basada en todos los conectores disponibles, el de Transporte de concentradores no se tiene en cuenta por la restricción de tamaño (establecida en 10 MB). La mejor opción es el conector "*" del perímetro a Internet (vea el logaritmo de selección de conectores documentado en <A class=bold title="Vea 'Descripción del enrutamiento de mensajes' en la documentación de Exchange 2010" href="http://technet.microsoft.com/en-in/library/aa998825(v=exchg.141).aspx">Descripción del enrutamiento de mensajes</A>), que tiene un límite de tamaño para mensajes de 30 MB.</P> <P><SPAN class=bold>Resultado final:</SPAN> el mensaje se enruta para que vuelva a Internet, lo que provoca el bucle del mensaje entre Internet y el servidor perimetral.</P> <P>En función de si el conector de envío está configurado para utilizar DNS o un host inteligente para entregar correo saliente, recibiremos uno de los siguientes <ACRONYM title="informes de no entrega">NDR</ACRONYM>:</P> <P><STRONG>Si se usa DNS:</STRONG></P> <P class=consoletext>#554 5.4.4 SMTPSEND.DNS.MxLoopback; los registros de DNS para este dominio están configurados en un bucle ##</P> <P><STRONG>Si se usa un host inteligente:</STRONG></P> <P class=consoletext>5.4.6 smtp;554 5.4.6 superada la cuenta de saltos; posible bucle de correo&gt; #SMTP#</P> <H2>La solución</H2> <P>Este comportamiento viene dado por el diseño y se puede rectificar fácilmente modificando el límite de tamaño para mensajes que hay en el conector. Según su requisito, puede seleccionar cualquiera de las siguientes opciones:</P> <UL class=arrowlist> <LI>Establezca el parámetro <SPAN class="parameter lightyellow">MaxMessageSize</SPAN> del <SPAN class=bold>conector de recepción</SPAN> (que recibe correo entrante de Internet) en <SPAN class=bold>10MB</SPAN>, para que los mensajes de Internet se restrinjan a 10 MB. <LI>Establezca el parámetro <SPAN class=parameter>MaxMessageSize</SPAN> del <SPAN class=bold>conector de envío</SPAN> de perímetro a concentrador en <SPAN class=bold>30MB</SPAN>, que le permitirá recibir mensajes de 30 MB de remitentes externos. </LI></UL> <P>Misterio resuelto. Gracias a Arindam Thokder y Scott Landry, que me han ayudado a preparar esta entrada para el blog.</P> <P><SPAN class=author>Suresh Kumar (XCON)</SPAN></P> <DIV style="CLEAR: both"></DIV><IMG src="http://blogs.technet.com/aggbug.aspx?PostID=3561643" width=1 height=1> <P>Esta entrada de blog es una traducción. Puede consultar el artículo original en <A href="http://blogs.technet.com/b/exchange/archive/2013/03/28/mysterious-mail-loop-on-edge-transport-server-check-your-size-limits.aspx">Mysterious mail loop on Edge Transport server: Check your size limits!</A></P><!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Mysterious-2D;mail-2D;loop-2D;on-2D;Edge-2D;Transport-2D;server.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Mysterious mail loop on Edge Transport server: Check your size limits!]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Fri, Mar 29 2013]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[I'm a support enginer in <ACRONYM title="Customer Service &amp; Support">CSS</ACRONYM>. I was working with a customer who reported a mail loop error for a specific domain like <SPAN class=command>contoso.com</SPAN>. This error was only observed in large emails.&nbsp; Yeah that’s really mysterious until you figure out that the mail loop is due to size restriction on the Send connector.&nbsp; I thought this was curious enough to share.<STRONG></STRONG>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Understanding the configuration and root cause of the issue:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[I initially thought that this might have been the outcome of the Edge server being configured to use an external <ACRONYM title="Domain Name System">DNS</ACRONYM> server (a DNS server that resolves external hosts). Usually, when the Edge Tranport server is configured to use an external DNS, it resolves the domain name to the public IP addresses (generally pointing to itself, the exernal firewall, or the service provider) instead of a Hub Transport server in the Active Diectory site, causing a mail loop.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[On reproducing the issue, I found out that the Edge Transport server was not configured to use an external DNS server. The environment I set up to reproduce the issue looked like the diagra below:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/6558.clip_5F00_image002_5F00_3D7AC522.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=clip_image002 border=0 alt=clip_image002 src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/1307.clip_5F00_image002_5F00_thumb_5F00_26BB7D99.png" width=623 height=199></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[&nbsp;]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Here's what happens in this scenario: When the Edge Transport server receives a 20 MB email from an Internet sender, it accepts it. The Edge Transport server has two connectors that match the address space -2D; one for the address space <SPAN class="fqdn lightyellow">contoso.com</SPAN> to the Active Directory site and one for the address space <SPAN class="fqdn lightyellow">*</SPAN>. When making the routing decision based on all available connectors, the one from the Edge to Hub is not considered because of the size restriction (it has 10 MB size limit). The best match is the * connector from Edge to the Internet (Please go over the connector selection algorithm documented in <A class=bold title="See 'Undersanding Message Routing' in Exchange 2010 documentation" href="http://technet.microsoft.com/en-2D;in/library/aa998825(v=exchg.141).aspx">Understanding Message Routing</A>) which has a message size limit of 30 MB.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=bold>End result:</SPAN> The message is routed back to the Internet causing the message loop between the Internet and the Edge Server.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Based on whether the Send connector to the Internet is configured to use DNS or a Smart Host to deliver oubound mail, we will get one of the following <ACRONYM title="Non-2D;Delivery Report">NDR</ACRONYM>s:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<STRONG>If using DNS:</STRONG>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="13" ItemType="13;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[#554 5.4.4 SMTPSEND.DNS.MxLoopback; DNS records for this domain are configured in a loop ##]]></Val>-D;-A; </Str>-D;-A; <Disp Order="13" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="14" ItemType="14;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<STRONG>If using a Smart Host:</STRONG>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="14" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="15" ItemType="15;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[5.4.6 smtp;554 5.4.6 Hop count exceeded -2D; possible mail loop&gt; #SMTP#]]></Val>-D;-A; </Str>-D;-A; <Disp Order="15" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="16" ItemType="16;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The Solution]]></Val>-D;-A; </Str>-D;-A; <Disp Order="16" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="17" ItemType="17;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This behavior is by design and can be easily rectified by modifying the message size limit on the connector. Based on your requirement, you can choose either of the following options:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="17" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="18" ItemType="18;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Set the <SPAN class="parameter lightyellow">MaxMessageSize</SPAN> parameter on the <SPAN class=bold>Receive Connector</SPAN> (which receives inbound mail from the Internet) to <SPAN class=bold>10MB</SPAN>, so messages from the Interent are restricted to 10 MB. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="18" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="19" ItemType="19;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Set the <SPAN class=parameter>MaxMessageSize</SPAN> on the <SPAN class=bold>Send connector</SPAN> from Edge to HUB to <SPAN class=bold>30MB</SPAN>, which will allow you to receive 30 MB messages from external senders. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="19" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="20" ItemType="20;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Mystery solved! Thanks to Arindam Thokder and Scott Landry, who helped me with getting this ready for the blog!]]></Val>-D;-A; </Str>-D;-A; <Disp Order="20" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="21" ItemType="21;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Suresh Kumar (XCON)</SPAN>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="21" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; <Item ItemId="22" ItemType="22;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2013/03/28/mysterious-2D;mail-2D;loop-2D;on-2D;edge-2D;transport-2D;server-2D;check-2D;your-2D;size-2D;limits.aspx">Mysterious mail loop on Edge Transport server: Check your size limits!</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="22" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:05:45.0006549Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--></BODY></HTML><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3571633" width="1" height="1">Presentación del Analizador de conectividad de Microsoft (MCA) 1.0 y del Analizador de conectividad remota de Microsoft (RCA) 2.1http://blogs.technet.com/b/exchange_sp/archive/2013/05/09/presentaci-243-n-del-analizador-de-conectividad-de-microsoft-mca-1-0-y-del-analizador-de-conectividad-remota-de-microsoft-rca-2-1.aspxThu, 09 May 2013 06:34:48 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3571632OfficeLocalization0<HTML><HEAD> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> </HEAD> <BODY> </P> <P>Artículo original publicado el martes, 12 de marzo de 2013</P> <P>En noviembre de 2012, anunciamos nuestro cliente beta de MCA. Hemos estado muy ocupados trabajando en la mejora de las opciones de prueba que están disponibles en el cliente de MCA. Le presentamos lo que hemos creado para la versión 1.0:</P> <P><A href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/6560.image_5F00_117B91ED.png"><IMG style="BACKGROUND-IMAGE: none; BORDER-RIGHT-WIDTH: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; DISPLAY: inline; BORDER-TOP-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px; PADDING-TOP: 0px" title=imagen border=0 alt=imagen src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/3362.image_5F00_thumb_5F00_78138EB2.png" width=84 height=85></A>&nbsp;</P> <H2>Herramienta de Analizador de conectividad de Microsoft 1.0</H2> <P>Nos complace anunciar la versión 1.0 del <A href="https://testconnectivity.microsoft.com/?tabid=client">Analizador de conectividad de Microsoft</A>.&nbsp;Esta herramienta acompaña al sitio web del Analizador de conectividad remota de Microsoft.&nbsp;La herramienta de MCA proporciona a los administradores y clientes finales la capacidad de iniciar soluciones de diagnóstico de conectividad para cinco síntomas de conectividad habituales directamente <I>desde su ordenador local</I>.&nbsp;Los usuarios pueden probar su propia conectividad y guardar los resultados en formato HTML, que los administradores reconocerán por la consulta de resultados en el sitio web de RCA.&nbsp; </P> <P><B>Instale aquí la herramienta de MCA 1.0:</B> <A href="https://testconnectivity.microsoft.com/?tabid=client"><B>https://testconnectivity.microsoft.com/?tabid=client</B></A></P> <P><B>Vea el vídeo introductorio: </B></P><IFRAME height=315 src="http://www.youtube.com/embed/RaXMWdUDyq8" frameBorder=0 width=560 allowfullscreen="allowfullscreen"></IFRAME> <H3>La herramienta de MCA ofrece cinco síntomas de prueba:</H3> <UL> <LI><B>"No puedo iniciar sesión con Office Outlook".</B> Esta prueba equivale a la prueba de RCA de Exchange para "Outlook Anywhere (RPC por HTTP)". Existe una opción para llevar a cabo la prueba de SSO proporcionada en la página de parámetros. <LI><B>"No puedo enviar ni recibir correo electrónico en el dispositivo móvil".</B>&nbsp;Esta prueba equivale a la prueba de RCA de Exchange para Exchange ActiveSync. <LI><B>***Nueva prueba de MCA*** "No puedo iniciar sesión en Lync en mi dispositivo móvil o en la aplicación de la Tienda Lync Windows".</B> Esta prueba verifica los registros del servidor DNS para su dominio local para asegurarse de que estén configurados correctamente para admitir clientes de Mobile Lync. Además, conecta al servicio web de detección automática y se asegura de que el servicio web de autenticación, el certificado, de movilidad esté bien configurado. <LI><B>***Nueva prueba de MCA*** "No puedo enviar ni recibir correo electrónico en Outlook (solo Office 365)"</B>. Esta prueba verifica el flujo de correo electrónico SMTP entrante/saliente y también incluye comprobaciones de validación del servidor DNS para los clientes de Office 365. <LI><B>***Nueva prueba de MCA*** "No puedo ver la información de disponible/ocupado de otro usuario"</B>. Esta prueba verifica que un buzón de Office 365 pueda obtener acceso a la información de disponible/ocupado de un buzón local y viceversa (una dirección por cada prueba realizada). </LI></UL> <P><A href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/2210.clip_5F00_image002_5F00_5EAB8B78.jpg"><IMG style="BACKGROUND-IMAGE: none; BORDER-RIGHT-WIDTH: 0px; MARGIN: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; DISPLAY: inline; BORDER-TOP-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px; PADDING-TOP: 0px" title=clip_image002 border=0 alt=clip_image002 src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/3704.clip_5F00_image002_5F00_thumb_5F00_75D996A7.jpg" width=603 height=469></A></P> <P><B>Herramienta de Analizador de conectividad de Microsoft Lync:&nbsp;</B>también observará la herramienta de Analizador de conectividad de Lync en la página cliente.&nbsp;Estamos trabajando en la combinación de MCA con MLCA en un futuro cercano, pero queríamos poner ambas fantásticas herramientas a disposición de los clientes en este momento para mejorar nuestras opciones de diagnóstico cliente. Para más información sobre MLCA, vaya <A href="http://technet.microsoft.com/library/jj907302.aspx">AQUÍ</A></P> <P><B>Comentarios:</B> envíe todos los comentarios que tenga al alias <A href="mailto:mcafeedback@microsoft.com?subject=MCA1.0%20Feedback">MCA Feedback</A>.&nbsp;Denos su opinión sobre la herramienta y si le resultará útil para solucionar problemas en escenarios de conectividad. Además, no dude en proporcionarnos comentarios sobre pruebas adicionales que quiera que se agreguen en el futuro.</P> <P><A href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/4606.image_5F00_1C3B79F3.png"><IMG style="BACKGROUND-IMAGE: none; BORDER-RIGHT-WIDTH: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; DISPLAY: inline; BORDER-TOP-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px; PADDING-TOP: 0px" title=imagen border=0 alt=imagen src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/0083.image_5F00_thumb_5F00_62B869FB.png" width=685 height=61></A></P> <H2>Analizador de conectividad remota de Microsoft 2.1</H2> <P>Nos emociona anunciar la versión 2.1 del sitio web de Analizador de conectividad remota de Microsoft.&nbsp;La herramienta proporciona a los administradores y usuarios finales la capacidad de aplicar soluciones de diagnóstico de la conectividad para nuestros servidores para poder hacer pruebas de los problemas habituales de Exchange, Lync y Office 365.&nbsp;Hemos agregado nuevas pruebas de DNS de Office 365, hemos mejorado pruebas existentes y hemos mejorado la experiencia general del sitio. </P> <P><B>Eche un vistazo a las novedades del sitio web aquí:</B> <A href="https://testconnectivity.microsoft.com"><B>https://testconnectivity.microsoft.com</B></A><B> </B></P> <H3>Aquí tiene los puntos fuertes de la versión 2.1 de RCA:</H3> <P><B>Versión 2.1 (marzo de 2013)</B></P> <UL> <LI>Compatibilidad agregada para admitir traducciones en 60 idiomas <LI>Versión actualizada de la herramienta de Analizador de conectividad de Microsoft v1.0 descargable para solucionar problemas de conectividad desde el ordenador local <LI>Se ha agregado la herramienta descargable de Analizador de conectividad de Microsoft Lync para solucionar problemas de Lync desde el ordenador local <LI>Se ha agregado la sección de pruebas generales de Office 365 <LI>Se ha agregado la prueba de conectividad del servidor DNS de Office 365 Exchange </LI></UL> <P><A href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/3731.clip_5F00_image001_5F00_6C142F2F.png"><IMG style="BACKGROUND-IMAGE: none; BORDER-RIGHT-WIDTH: 0px; PADDING-LEFT: 0px; PADDING-RIGHT: 0px; DISPLAY: inline; BORDER-TOP-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; BORDER-LEFT-WIDTH: 0px; PADDING-TOP: 0px" title=clip_image001 border=0 alt=clip_image001 src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/8446.clip_5F00_image001_5F00_thumb_5F00_607E71F0.png" width=582 height=289></A></P> <P>Esperamos que lo disfrute.</P> <P>Gracias,<B></B></P> <P><SPAN class=author>Brian Feck</SPAN> en nombre de todo el <B>equipo de MCA/RCA<BR>.</B><B>Siga al equipo en Twitter: </B><A href="https://twitter.com/ExRCA"><B>@ExRCA</B></A></P> <DIV style="CLEAR: both"></DIV><IMG src="http://blogs.technet.com/aggbug.aspx?PostID=3557865" width=1 height=1> <P>Esta entrada de blog es una traducción. Puede consultar el artículo original en <A href="http://blogs.technet.com/b/exchange/archive/2013/03/11/announcing-microsoft-connectivity-analyzer-mca-1-0-and-microsoft-remote-connectivity-analyzer-rca-2-1.aspx">Announcing Microsoft Connectivity Analyzer (MCA) 1.0 and Microsoft Remote Connectivity Analyzer (RCA) 2.1</A></P><!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Announcing-2D;Microsoft-2D;Connectivity-2D;Analyzer-2D;MC.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Announcing Microsoft Connectivity Analyzer (MCA) 1.0 and Microsoft Remote Connectivity Analyzer (RCA) 2.1]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Tue, Mar 12 2013]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Back in November 2012, we announced our MCA Beta client. We have been very busy working to improve the testing options that are available from the MCA client. Here’s what we’ve built for the 1.0 release:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/6560.image_5F00_117B91ED.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/3362.image_5F00_thumb_5F00_78138EB2.png" width=84 height=85></A>&nbsp;]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Microsoft Connectivity Analyzer Tool 1.0]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[We are excited to announce the 1.0 release of the <A href="https://testconnectivity.microsoft.com/?tabid=client">Microsoft Connectivity Analyzer</A>.&nbsp; This tool is a companion to the Microsoft Remote Connectivity Analyzer web site.&nbsp; The MCA tool provides administrators and end users with the ability to run connectivity diagnostics for five common connectivity symptoms directly <I>from their local computer</I>.&nbsp; Users can test their own connectivity, and save results in an HTML format that administrators will recognize from viewing results on the RCA website.&nbsp; ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Install the MCA 1.0 tool here:</B> <A href="https://testconnectivity.microsoft.com/?tabid=client"><B>https://testconnectivity.microsoft.com/?tabid=client</B></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Watch the Introduction Video: </B>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The MCA tool offers five test symptoms:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>“I can’t log on with Office Outlook”</B> – This test is equivalent to the Exchange RCA test for “Outlook Anywhere (RPC over HTTP)”. There is an option to run the SSO test provided on the parameters page. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>“I can’t send or receive email on my mobile device”.</B>&nbsp;&nbsp; – This test is equivalent to the Exchange RCA test for Exchange ActiveSync. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>***New MCA Test*** “I can’t log on to Lync on my mobile device or the Lync Windows Store App”</B> – This test checks for the Domain Name Server (DNS) records for your on-2D;premise domain to ensure they are configured correctly for supporting Mobile Lync clients. Also it connects to the Autodiscover web service and makes sure that the authentication, certificate, web service for Mobility is correctly set up ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="13" ItemType="13;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>***New MCA Test*** “I can’t send or receive email from Outlook (Office 365 only)”</B> – This test checks Inbound/Outbound SMTP mail flow and also includes Domain Name Server validation checks for O365 customers. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="13" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="14" ItemType="14;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>***New MCA Test*** “I can’t view free/busy information of another user”</B> – This test verifies that an Office 365 mailbox can access the free/busy information of an on-2D;premises mailbox, and vice versa (one direction per test run). ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="14" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="15" ItemType="15;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/2210.clip_5F00_image002_5F00_5EAB8B78.jpg"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; MARGIN: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=clip_image002 border=0 alt=clip_image002 src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/3704.clip_5F00_image002_5F00_thumb_5F00_75D996A7.jpg" width=603 height=469></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="15" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="16" ItemType="16;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Microsoft Lync Connectivity Analyzer Tool:&nbsp; </B>You will also notice the Lync Connectivity Analyzer Tool on the client page.&nbsp; We are working on combining MCA with MLCA in the near future but wanted to make both these great tools available to customers now to improve our client diagnostics options. To learn more about MLCA – go <A href="http://technet.microsoft.com/library/jj907302.aspx">HERE</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="16" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="17" ItemType="17;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Feedback:</B> Send all feedback to the <A href="mailto:mcafeedback@microsoft.com?subject=MCA1.0%20Feedback">MCA Feedback</A> alias.&nbsp; Please let us know what you think of the tool and whether this will be helpful in troubleshooting connectivity scenarios. Also feel free to provide feedback on additional tests you would like to see added in the future.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="17" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="18" ItemType="18;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/4606.image_5F00_1C3B79F3.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/0083.image_5F00_thumb_5F00_62B869FB.png" width=685 height=61></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="18" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="19" ItemType="19;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Microsoft Remote Connectivity Analyzer 2.1]]></Val>-D;-A; </Str>-D;-A; <Disp Order="19" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="20" ItemType="20;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[We are excited to announce the 2.1 release of the Microsoft Remote Connectivity Analyzer web site.&nbsp; The tool provides administrators and end users with the ability to run connectivity diagnostics for our servers to test common issues with Exchange, Lync and Office 365.&nbsp; We have added new Office 365 Domain Name Server tests, enhanced existing tests, and improved the overall site experience. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="20" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="21" ItemType="21;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Check out the updates to the website here:</B> <A href="https://testconnectivity.microsoft.com"><B>https://testconnectivity.microsoft.com</B></A><B> </B>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="21" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="22" ItemType="22;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Here are the highlights of the 2.1 RCA release:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="22" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="23" ItemType="23;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Version 2.1 (March 2013)</B>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="23" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="24" ItemType="24;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Added support for localized language support for 60 languages ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="24" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="25" ItemType="25;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Updated version of the downloadable Microsoft Connectivity Analyzer v1.0 Tool for troubleshooting connectivity from the local machine ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="25" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="26" ItemType="26;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Added Microsoft Lync Connectivity Analyzer downloadable tool for troubleshooting Lync issues from the local machine ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="26" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="27" ItemType="27;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Added Office 365 General Tests section ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="27" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="28" ItemType="28;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Added Office 365 Exchange Domain Name Server (DNS) Connectivity Test ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="28" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="29" ItemType="29;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/3731.clip_5F00_image001_5F00_6C142F2F.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=clip_image001 border=0 alt=clip_image001 src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/8446.clip_5F00_image001_5F00_thumb_5F00_607E71F0.png" width=582 height=289></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="29" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="30" ItemType="30;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Enjoy!]]></Val>-D;-A; </Str>-D;-A; <Disp Order="30" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="31" ItemType="31;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Thanks.<B></B>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="31" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="32" ItemType="32;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Brian Feck</SPAN> on behalf of the entire<B> MCA/RCA team. <BR></B><B>Follow the team on Twitter -2D; </B><A href="https://twitter.com/ExRCA"><B>@ExRCA</B></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="32" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; <Item ItemId="33" ItemType="33;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2013/03/11/announcing-2D;microsoft-2D;connectivity-2D;analyzer-2D;mca-2D;1-2D;0-2D;and-2D;microsoft-2D;remote-2D;connectivity-2D;analyzer-2D;rca-2D;2-2D;1.aspx">Announcing Microsoft Connectivity Analyzer (MCA) 1.0 and Microsoft Remote Connectivity Analyzer (RCA) 2.1</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="33" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:27:34.0001549Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--></BODY></HTML><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3571632" width="1" height="1">Guía de hospedaje y de arquitectura multiempresa para Exchange Server 2013 ya disponiblehttp://blogs.technet.com/b/exchange_sp/archive/2013/05/09/gu-237-a-de-hospedaje-y-de-arquitectura-multiempresa-para-exchange-server-2013-ya-disponible.aspxThu, 09 May 2013 06:34:47 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3571631OfficeLocalization0<HTML><HEAD> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"/> </HEAD> <BODY> </P> <P>Artículo original publicado el jueves, 21 de febrero de 2013</P> <P>Nos complace anunciar el documento <B>Guía de hospedaje y de arquitectura multiempresa</B> <B>para Exchange Server 2013</B>, muchas veces solicitado. Se puede descargar <A href="http://technet.microsoft.com/en-us/exchange/jj720331">aquí</A>.</P> <P>Como el agudo lector habrá observado, es muy parecida a la guía para Exchange Server 2010. No se debe a que lo único que hemos hecho sea buscar, copiar y sustituir, sino a que la estrategia que elegimos para Exchange 2010 sigue vigente para Exchange 2013. Es decir, use la compilación únicamente en las herramientas, los cmdlets y las interfaces para configurar la solución que haya elegido y no manipule directamente, bajo ninguna circunstancia, objetos en AD para que cumplan la configuración que quiere. </P> <P>Lo que también sigue vigente es la idea de que no todas las características funcionarán como usted quiere en una configuración del tipo arquitectura multiempresa. Por ejemplo, la característica Sugerencias de correo electrónico funcionará exactamente igual que en un despliegue de tipo local. Normalmente, esto puede dar lugar a la revelación de datos no deseados entre inquilinos. En el documento se resaltan las características que puede que no funcionen como se espera al configurar Exchange para arquitectura multiempresa, y se realizan recomendaciones para la configuración o para inhabilitar cuando sea necesario.</P> <P>Una parte esencial del importante elemento de segmentación del directorio de su solución es la característica Directivas de la libreta de direcciones. Con el <A href="http://blogs.technet.com/b/exchange/archive/2013/02/14/address-book-policies-jamba-jokes-and-secret-agents.aspx">reciente anuncio</A> de un agente de transporte, creado para aprovechar las Directivas de la libreta de direcciones, esperamos que la solución 2013 le resulte aún más fácil de crear y de mantener. </P> <P>Tenga en cuenta que hay algunos cambios importantes para 2013 y, por ello, le sugerimos que lea la guía <B>detenidamente</B> antes de planificar y crear la solución. Asimismo, vuelva a consultarla según sea necesario si tiene cualquier problema.</P> <P>Igual que con Exchange 2010, tenemos soluciones de asociados que se crean siguiendo las directrices del documento. Además, las soluciones que hemos validado en este momento se enumeran en el <A href="http://technet.microsoft.com/en-us/exchange/jj720331">sitio</A>. Dicha enumeración irá creciendo, así que vuelva a consultarla si la solución que quiere usar no se encuentra en la enumeración en este momento, o bien póngase en contacto con el proveedor y pregúntele sus planes de validación. </P> <P>Tenemos planeado publicar una versión actualizada de la Guía de escalas para Exchange 2013 configurada para arquitectura multiempresa u hospedaje. Cuando esté disponible este documento, actualizaremos el sitio de soluciones. </P> <P>Esperamos que el documento le resulte útil y estamos deseando recibir sus comentarios.</P> <P><SPAN class=author>Greg Taylor</SPAN><BR>Director líder de administración de programas<BR>Experiencia del usuario de Exchange</P> <DIV style="CLEAR: both"></DIV><IMG src="http://blogs.technet.com/aggbug.aspx?PostID=3553932" width=1 height=1> <P>Esta entrada de blog es una traducción. Puede consultar el artículo original en <A href="http://blogs.technet.com/b/exchange/archive/2013/02/20/hosting-and-multi-tenancy-guidance-for-exchange-server-2013-now-available.aspx">Hosting and Multi-Tenancy Guidance for Exchange Server 2013 Now Available</A></P><!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Hosting-2D;and-2D;MultiTenancy-2D;Guidance-2D;for-2D;Exchang.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Hosting and Multi-2D;Tenancy Guidance for Exchange Server 2013 Now Available]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Thu, Feb 21 2013]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[We are pleased to be able to announce the oft-2D;requested <B>Hosting and Multi-2D;Tenancy Guidance</B> <B>for Exchange Server 2013</B> document. It is available for download <A href="http://technet.microsoft.com/en-2D;us/exchange/jj720331">here</A>.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[As the keen eyed reader will observe, it is very similar to the guidance for Exchange Server 2010. That’s not because all we did was a find, copy and replace, but because the strategy we decided upon for Exchange 2010 holds true for Exchange 2013. That is, you should only use the built in tools, cmdlets and interfaces for configuring your solution, and you should not under any circumstances directly manipulate objects in AD to meet your desired configuration. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[What also holds true is the notion that not all features are going to work as you might want them to in a multi-2D;tenant like configuration. For example, MailTips will work exactly the same as they do in a standard on-2D;premises type deployment – and typically that may result in unwanted data between tenants being exposed. The document highlights features that might not work as hoped when you configure Exchange for multi-2D;tenancy, and makes recommendations for configuration, or for disabling where necessary.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Core to the important directory segmentation element of your solution is the Address Book Policy feature. With the <A href="http://blogs.technet.com/b/exchange/archive/2013/02/14/address-2D;book-2D;policies-2D;jamba-2D;jokes-2D;and-2D;secret-2D;agents.aspx">recent announcement</A> of a transport agent, created to take advantage of Address Book Policies, we hope you will find your 2013 solution even easier to build and maintain. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Please note there are some important changes for 2013, and so we encourage you to read the guidance <B>thoroughly</B> before you plan and build your solution, and refer back to it as needed if you have any problems.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Just as with Exchange 2010, we have partner solutions that are built following the guidelines in the document, and the solutions we have currently validated are also listed on the <A href="http://technet.microsoft.com/en-2D;us/exchange/jj720331">site</A>. That list will grow so do check back if the solution you want to use isn’t currently on that list, or contact the vendor and ask about their plans for validation. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[We do plan on releasing updated Scale Guidance for Exchange 2013 configured for multi-2D;tenancy or hosting, and will update the solutions site when that document is available. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[We hope you find the document useful and look forward to hearing your feedback.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Greg Taylor</SPAN> <BR>Principal Program Manager Lead <BR>Exchange Customer Experience]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2013/02/20/hosting-2D;and-2D;multi-2D;tenancy-2D;guidance-2D;for-2D;exchange-2D;server-2D;2013-2D;now-2D;available.aspx">Hosting and Multi-2D;Tenancy Guidance for Exchange Server 2013 Now Available</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2013-2D;04-2D;25T03:28:44.0005303Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--></BODY></HTML><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3571631" width="1" height="1">Aumento del límite de la tasa de destinatarios hasta 10.000 para Office 365 y Exchange Onlinehttp://blogs.technet.com/b/exchange_sp/archive/2013/01/31/aumento-del-l-237-mite-de-la-tasa-de-destinatarios-hasta-10-000-para-office-365-y-exchange-online.aspxThu, 31 Jan 2013 15:41:17 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3549604OfficeLocalization0<p>Art&iacute;culo original publicado el jueves, 27 de diciembre de 2012</p> <p>En respuesta a los comentarios de nuestros clientes, hemos aumentado el l&iacute;mite de la tasa de destinatarios en los planes de Office 365 para empresas (E1, E2, E3, E4, K1 y K2), para profesionales y peque&ntilde;as empresas (P1) y para gobiernos (G1, G2, G3 y G4) con el fin de que los usuarios puedan enviar correo electr&oacute;nico a un m&aacute;ximo de <span class="lightyellow bold">10.000 destinatarios al d&iacute;a</span>. Estos nuevos l&iacute;mites tambi&eacute;n se aplican a los planes independientes de Exchange Online (Quiosco, plan 1 y plan 2). Anteriormente, el l&iacute;mite de la tasa de destinatarios para estos planes estaba establecido en 1.500 destinatarios al d&iacute;a como m&aacute;ximo.</p> <p>Los l&iacute;mites de la tasa de destinatarios existen para impedir que los usuarios env&iacute;en grandes vol&uacute;menes de correo electr&oacute;nico comercial no solicitado, lo que com&uacute;nmente se conoce como correo no deseado. Estos l&iacute;mites evitan que nuestro servicio en l&iacute;nea se convierta en un origen de correo no deseado y, como resultado de estas protecciones, mantienen el flujo de mensajes de correo electr&oacute;nico de nuestros clientes. Las mejoras de los centros de datos nos han permitido aumentar este l&iacute;mite y, al mismo tiempo, mantener el mismo nivel de protecci&oacute;n.</p> <p>Estos l&iacute;mites se aplican tanto a los mensajes de correo electr&oacute;nico que se env&iacute;an dentro de una organizaci&oacute;n como a los que se env&iacute;an a organizaciones externas. La mejor manera de evitar que se exceda el l&iacute;mite de la tasa de destinatarios es usar grupos de distribuci&oacute;n a la hora de enviar mensajes a un gran n&uacute;mero de destinatarios. Los grupos de distribuci&oacute;n almacenados en la libreta de direcciones compartida cuenta como un &uacute;nico destinatario para el l&iacute;mite de la tasa de destinatarios. Para obtener m&aacute;s informaci&oacute;n, consulte <a class="bold" title=" 'Strategies to Support Bulk Email' in Bulk E-Mail and Daily Recipient Rate Limits" href="http://help.outlook.com/en-us/140/ff381292.aspx#bulkemailstrategies">Estrategias para utilizar correo electr&oacute;nico masivo</a>. Los clientes de Office 365 que necesiten enviar correo electr&oacute;nico masivo leg&iacute;timo (como boletines de clientes), deben continuar usando proveedores de terceros especializados en estos servicios.</p> <p>Si desea obtener m&aacute;s informaci&oacute;n sobre los l&iacute;mites de la tasa de destinatarios, consulte <a class="bold" title="'Bulk E-Mail and Daily Recipient Rate Limits' in Exchange Online documentation" href="http://help.outlook.com/en-us/140/Ff381292.aspx">L&iacute;mites de tasa de correo electr&oacute;nico masivo y de destinatarios al d&iacute;a</a>. Sus comentarios han promovido este cambio. Gracias por compartir su opini&oacute;n con nosotros; siga haci&eacute;ndolo.</p> <p><span class="author">Steve Chew</span></p> <p><img src="http://blogs.technet.com/aggbug.aspx?PostID=3542675" alt="" width="1" height="1" /></p> <p>Esta entrada de blog es una traducci&oacute;n. Puede encontrar el art&iacute;culo original en <a href="http://blogs.technet.com/b/exchange/archive/2012/12/26/recipient-rate-limit-increase-to-10k-for-office-365-and-exchange-online.aspx">Recipient Rate Limit Increase to 10K for Office 365 and Exchange Online</a></p> <!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Recipient-2D;Rate-2D;Limit-2D;Increase-2D;to-2D;10K-2D;for-2D;Offi.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Recipient Rate Limit Increase to 10K for Office 365 and Exchange Online]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:02.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Thu, Dec 27 2012]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:02.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[In response to feedback from our customers, we have increased the recipient rate limit within Office 365 Enterprise (E1, E2, E3, E4, K1, and K2), Professionals and Small Businesses (P1), and Government plans (G1, G2, G3, and G4) to allow users to send email to up to <SPAN class="lightyellow bold">10,000 recipients per day</SPAN>. These new limits also apply to standalone Exchange Online plans (Kiosk, Plan 1, and Plan 2). Previously, the recipient rate limit for users of these plans had been set at a maximum of 1,500 recipients per day.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:02.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Recipient rate limits exist to discourage users from sending large volumes of unsolicited commercial email, commonly referred to as spam. These limits protect our online service from becoming a source of spam and, as a result of these protections, keep our customers’ email messages flowing. Datacenter enhancements have allowed us to increase this limit while maintaining the same level of protection.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:02.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[These limits apply both to email messages sent within an organization and those delivered to external organizations. The best way to avoid exceeding the recipient rate limit is to use distribution groups when sending messages to large numbers of recipients. Distribution groups stored in the shared address book are counted as a single recipient toward the recipient rate limit. For more information, see <A class=bold title="See 'Strategies to Support Bulk Email' in Bulk E-2D;Mail and Daily Recipient Rate Limits" href="http://help.outlook.com/en-2D;us/140/ff381292.aspx#bulkemailstrategies">Strategies to Support Bulk Email</A>. Office 365 customers who need to send legitimate bulk commercial email — such as customer newsletters – should continue to use third-2D;party providers that specialize in these services.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:02.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[If you would like more information on recipient rate limits, see <A class=bold title="See 'Bulk E-2D;Mail and Daily Recipient Rate Limits' in Exchange Online documentation" href="http://help.outlook.com/en-2D;us/140/Ff381292.aspx">Bulk Email and Daily Recipient Rate Limits</A>. We made this change because of your feedback. Thank you for sharing your thoughts with us, and please keep it up!]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:02.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Steve Chew</SPAN>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:02.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2012/12/26/recipient-2D;rate-2D;limit-2D;increase-2D;to-2D;10k-2D;for-2D;office-2D;365-2D;and-2D;exchange-2D;online.aspx">Recipient Rate Limit Increase to 10K for Office 365 and Exchange Online</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:02.0001282Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3549604" width="1" height="1">¿Cuáles son las novedades del Analizador de conectividad remota de Microsoft? Muchas.http://blogs.technet.com/b/exchange_sp/archive/2013/01/31/191-cu-225-les-son-las-novedades-del-analizador-de-conectividad-remota-de-microsoft-muchas.aspxThu, 31 Jan 2013 15:40:00 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3549603OfficeLocalization0<p>Art&iacute;culo original publicado el martes, 20 de noviembre de 2012</p> <p>&iquest;Ha recibido alguna vez una llamada de alguien que conoce y cuyo cliente de Outlook tiene problemas para conectar con su servidor de correo electr&oacute;nico? &iquest;No le gustar&iacute;a tener una herramienta que poder enviarle para guiar sus pasos por una prueba de conectividad y que ofrezca una manera sencilla de recibir los resultados de vuelta?</p> <p>O quiz&aacute;s como administrador ha usado el <a href="https://www.testexchangeconnectivity.com/?tabid=client">Analizador de conectividad remota</a> durante a&ntilde;os para comprobar la configuraci&oacute;n del correo electr&oacute;nico, pero le gustar&iacute;a tener una manera de realizar las mismas pruebas desde su organizaci&oacute;n y que le proporcionara la misma informaci&oacute;n de diagn&oacute;stico detallada que el sitio web del Analizador de conectividad remota.</p> <p>Hemos atendido estas peticiones y nuestro equipo ha creado una herramienta justo para estos escenarios. Nos complace presentar el <strong>Analizador de conectividad de Microsoft (beta)</strong>, una versi&oacute;n port&aacute;til del sitio web Analizador de conectividad remota. Este es un breve v&iacute;deo de presentaci&oacute;n del Analizador de conectividad de Microsoft, de 49 segundos.</p> <p><iframe src="http://www.youtube.com/embed/-Y1VSvPH5eE?rel=0" frameborder="0" width="560" height="315"></iframe></p> <p>Esta herramienta contiene las mismas pruebas que el sitio web, con una interfaz de usuario algo m&aacute;s sencilla; una herramienta que puede compartir con usuarios, familiares o con su vecino.</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/6523.image_5F00_3E424DCD.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/6523.image_5F00_thumb_5F00_0F7C952B.png" alt="imagen" width="624" height="288" border="0" /></a></p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/4150.image_5F00_1C0A4247.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/1732.image_5F00_thumb_5F00_7463C61C.png" alt="imagen" width="497" height="373" border="0" /></a></p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/7367.image_5F00_6CD856AF.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/8764.image_5F00_thumb_5F00_59B72A03.png" alt="imagen" width="495" height="372" border="0" /></a></p> <p>Adem&aacute;s, hemos dividido los resultados en dos vistas: una vista simplificada que solo muestra los resultados que cualquiera podr&iacute;a comprender, y unos resultados detallados que solo un administrador podr&iacute;a querer (s&iacute;, ese es usted).</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/6786.image_5F00_00190D4F.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/8764.image_5F00_thumb_5F00_58729124.png" alt="imagen" width="495" height="371" border="0" /></a></p> <p>Y los detalles adicionales para los administradores se muestran en &ldquo;Revisar todas las pruebas ejecutadas&rdquo;:</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/8345.image_5F00_77B537F7.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/8764.image_5F00_thumb_5F00_092598D0.png" alt="imagen" width="566" height="126" border="0" /></a></p> <p>O pida al usuario que guarde los resultados detallados y se los env&iacute;e. Los resultados detallados se guardan como un archivo HTML y pueden verse en un explorador.</p> <p><strong>Requisitos previos del Analizador de conectividad de Microsoft</strong></p> <ol> <li>La herramienta admite los siguientes sistemas operativos: Windows 7 de 64 bits, Windows 7, Windows Server 2008+</li> <li>Se necesita <a href="http://www.microsoft.com/en-us/download/details.aspx?id=30653">Microsoft .NET Framework 4.5</a>.</li> <li>Requisitos de explorador:</li> </ol> <blockquote> <p>La instalaci&oacute;n funcionar&aacute; en todos los exploradores modernos. Sin embargo&hellip;</p> <ul> <li>Si usa Google Chrome, tendr&aacute; que instalar <a href="https://chrome.google.com/webstore/detail/clickonce-for-google-chro/eeifaoomkminpbeebjdmdojbhmagnncl#detail/clickonce-for-google-chro/eeifaoomkminpbeebjdmdojbhmagnncl">ClickOnce para Google Chrome</a></li> <li>Si usa FireFox, tendr&aacute; que instalar el <a href="https://addons.mozilla.org/en-US/firefox/addon/microsoft-net-framework-assist/">Asistente de Microsoft .Net Framework para FireFox.</a></li> </ul> </blockquote> <p>Encontrar&aacute; las notas completas de la versi&oacute;n <a href="https://www.testexchangeconnectivity.com/Pages/ChangeList.htm">aqu&iacute;</a>.</p> <p><strong>A&uacute;n no hemos terminado. Tenemos planeado agregar m&aacute;s pruebas.</strong><strong></strong></p> <p>Igual que cuando lanzamos el sitio web por primera vez, esta primera versi&oacute;n del Analizador de conectividad de Microsoft es un trabajo en curso.</p> <p>Disponer de una herramienta en el centro del usuario final nos permite ampliar las pruebas para incluir los problemas comunes de todo tipo de conectividad. Esta primera versi&oacute;n de la herramienta es tan solo el comienzo.</p> <p><strong>Y eso no es todo.</strong></p> <p>Adem&aacute;s de proporcionar una nueva herramienta, nos hemos aliado con el Analizador de conectividad remota de Lync y hemos unido las dos herramientas. Ver&aacute; que hemos quitado &ldquo;Exchange&rdquo; del nombre y que hay una nueva manera de acceder al sitio web: <a href="http://testconnectivity.microsoft.com">http://testconnectivity.microsoft.com</a>. Efectivamente, las magn&iacute;ficas pruebas de Lync y Exchange disponibles en el mismo sitio web.</p> <p>Las pruebas incluyen:</p> <ul> <li>La <strong>prueba de conectividad remota del servicio web Microsoft Lync Mobile Auto-Discover </strong>probar&aacute; la conectividad remota con el servidor del servicio web Microsoft Lync Mobile Auto-Discover</li> <li>La <strong>prueba de Microsoft Office Communications Server</strong> probar&aacute; la conectividad remota con Microsoft Office Communications Server, detectar&aacute; autom&aacute;ticamente el servidor perimetral de acceso y el puerto para conectarse, o le permitir&aacute; especificar un servidor perimetral de acceso.<strong></strong></li> <li>La <strong>prueba de conectividad remota de Microsoft Lync Server</strong> probar&aacute; la conectividad remota con Microsoft Lync Server, detectar&aacute; autom&aacute;ticamente el servidor perimetral de acceso y el puerto para conectarse, o le permitir&aacute; especificar un servidor perimetral de acceso.</li> </ul> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/0830.image_5F00_0F6C6F5E.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/4643.image_5F00_thumb_5F00_1BFA1C7A.png" alt="imagen" width="591" height="348" border="0" /></a></p> <p><strong>Espere, &iexcl;hay m&aacute;s!</strong></p> <p>&iquest;Hemos mencionado ya lo ocupados que hemos estado este a&ntilde;o? En la pesta&ntilde;a Office 365, ver&aacute; dos nuevas pruebas: la prueba <strong>Office 365 Lync DNS</strong> y la prueba <strong>Disponibilidad</strong>.</p> <p>La <strong>prueba Office 365 Lync DNS</strong> comprobar&aacute; la configuraci&oacute;n del nombre de dominio externo para su usuario de dominio personalizado en Office 365.</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/0334.image_5F00_3B3CC34D.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/8838.image_5F00_thumb_5F00_2C921768.png" alt="imagen" width="592" height="613" border="0" /></a></p> <p>Gracias al equipo de Servicios de implementaci&oacute;n de Office 365, el sitio web del Analizador de conectividad remota ahora incluye la prueba <strong>Disponibilidad de Office 365</strong>. Esta prueba comprueba si un buz&oacute;n de Office 365 puede acceder a la informaci&oacute;n de disponibilidad de un buz&oacute;n local y viceversa. Esto incluye:</p> <ul> <li>una comprobaci&oacute;n para confirmar que el tiempo del sistema del servidor h&iacute;brido no se desv&iacute;a m&aacute;s de cinco minutos, lo que causar&iacute;a errores al solicitar tokens de delegaci&oacute;n a Microsoft Federated Gateway.</li> <li>una comprobaci&oacute;n para confirmar que la conectividad de entrada al servidor h&iacute;brido no requiere autenticaci&oacute;n previa del firewall; es decir, que el firewall admite la autenticaci&oacute;n de paso a trav&eacute;s.</li> <li>una comprobaci&oacute;n para confirmar que el servidor h&iacute;brido cumple los requisitos de versi&oacute;n m&iacute;nima de Exchange Server (Exchange Server 2010 SP1).</li> <li>una consulta b&aacute;sica de disponibilidad con el servicio de disponibilidad de destino.</li> <li>V&iacute;nculos a informaci&oacute;n sobre el Asistente para la configuraci&oacute;n h&iacute;brida, un origen com&uacute;n de problemas de configuraci&oacute;n de implementaciones h&iacute;bridas</li> </ul> <p>Gracias por llegar hasta aqu&iacute;. Esperamos que haya disfrutado de las nuevas actualizaciones y estamos deseando recibir noticias suyas,</p> <p><span class="author">Nicole Allen</span> <br />En nombre del equipo del Analizador de conectividad remota</p> <p><img src="http://blogs.technet.com/aggbug.aspx?PostID=3533347" alt="" width="1" height="1" /></p> <p>Esta entrada de blog es una traducci&oacute;n. Encontrar&aacute; el art&iacute;culo original en <a href="http://blogs.technet.com/b/exchange/archive/2012/11/19/what-s-new-with-microsoft-remote-connectivity-analyzer-a-lot.aspx">What&rsquo;s new with Microsoft Remote Connectivity Analyzer? A lot!</a></p> <!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Whats-2D;new-2D;with-2D;Microsoft-2D;Remote-2D;Connectivity-2D;.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[What’s new with Microsoft Remote Connectivity Analyzer? A lot!]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Tue, Nov 20 2012]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Have you ever gotten a call from someone you know whose Outlook client is having trouble connecting to their email server? Don’t you just wish you had a tool that you could send to them that would walk them through a connectivity test and provide a simple way for them to send the results back to you?]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Or perhaps you’re an administrator that has been using the <A href="https://www.testexchangeconnectivity.com/?tabid=client">Remote Connectivity Analyzer</A> for years to verify email configuration, but wish you had a way to verify the same tests from within your organization, that provided the same diagnostic details as the RCA website?]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[We’ve heard requests like these, and our team has built a tool for just these scenarios. I’d like to introduce you to the <B>Microsoft Connectivity Analyzer (beta)</B>, a portable version of the Remote Connectivity Analyzer website. Here is a short 49 second video that introduces the Microsoft Connectivity Analyzer. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This tool contains the same tests as the website, in a slightly simpler UI – something you can share with your users, family, or your neighbor down the street. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/6523.image_5F00_3E424DCD.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/6523.image_5F00_thumb_5F00_0F7C952B.png" width=624 height=288></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/4150.image_5F00_1C0A4247.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/1732.image_5F00_thumb_5F00_7463C61C.png" width=497 height=373></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/7367.image_5F00_6CD856AF.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/8764.image_5F00_thumb_5F00_59B72A03.png" width=495 height=372></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[In addition, we’ve split the results into two views – a simplified view which only shows results that your mom could understand, and the full detailed results that only an administrator would love (yes, that’s you).]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/6786.image_5F00_00190D4F.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/8764.image_5F00_thumb_5F00_58729124.png" width=495 height=371></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[And the additional details for administrators is shown under “Review all the tests we ran”:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="13" ItemType="13;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/8345.image_5F00_77B537F7.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/8764.image_5F00_thumb_5F00_092598D0.png" width=566 height=126></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="13" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="14" ItemType="14;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Or ask your user to save the detailed results and send them to you! The detailed results are saved as an HTML file and can be viewed in your browser.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="14" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="15" ItemType="15;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Microsoft Connectivity Analyzer Pre-2D;Requisites</B>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="15" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="16" ItemType="16;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The tool supports the following operating systems: 64bit Windows 7, Windows 7, Windows Server 2008+ ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="16" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="17" ItemType="17;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://www.microsoft.com/en-2D;us/download/details.aspx?id=30653">Microsoft .NET Framework 4.5</A> is required. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="17" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="18" ItemType="18;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Browsers requirements: ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="18" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="19" ItemType="19;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The installation will work on all modern browsers. However…]]></Val>-D;-A; </Str>-D;-A; <Disp Order="19" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="20" ItemType="20;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[If you are using Google Chrome, you will need to install <A href="https://chrome.google.com/webstore/detail/clickonce-2D;for-2D;google-2D;chro/eeifaoomkminpbeebjdmdojbhmagnncl#detail/clickonce-2D;for-2D;google-2D;chro/eeifaoomkminpbeebjdmdojbhmagnncl">ClickOnce for Google Chrome</A> ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="20" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="21" ItemType="21;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[If you are using FireFox, you will need to install <A href="https://addons.mozilla.org/en-2D;US/firefox/addon/microsoft-2D;net-2D;framework-2D;assist/">Microsoft .Net Framework Assistant for FireFox.</A> ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="21" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="22" ItemType="22;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[You can find the full release notes <A href="https://www.testexchangeconnectivity.com/Pages/ChangeList.htm">here</A>.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="22" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="23" ItemType="23;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>We're not finished yet. We have plans to add additional tests.</B><B></B>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="23" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="24" ItemType="24;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Just like when we first released the website, this first version of the Microsoft Connectivity Analyzer is a work in progress. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="24" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="25" ItemType="25;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Having a tool on site with the end user, we’re in a unique position to extend the testing to include common problems with all types of connectivity. This early version of the tool is just the beginning.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="25" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="26" ItemType="26;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>And that’s not all!</B>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="26" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="27" ItemType="27;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[In addition to providing a new tool, we’ve joined forces with the Lync Remote Connectivity Analyzer, and brought the two tools together. You’ll notice we’ve dropped the “Exchange” from the name, and we have a new way to access the website: <A href="http://testconnectivity.microsoft.com">http://testconnectivity.microsoft.com</A>. That’s right – all the same great tests for Lync and Exchange available on the same website.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="27" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="28" ItemType="28;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Tests include:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="28" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="29" ItemType="29;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Microsoft Lync Mobile Auto-2D;Discover Web Service Remote Connectivity Test</B> will test your remote connectivity to the Microsoft Lync Mobile Auto-2D;Discover Web Service Server ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="29" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="30" ItemType="30;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Microsoft Office Communications Server Test </B>will test your remote connectivity to the Microsoft Office Communications Server, it will auto-2D;discover the Access Edge and port to connect to, OR allow you to specific an Access Edge server.<B></B> ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="30" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="31" ItemType="31;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>Microsoft Lync Server Remote Connectivity Test </B>will test your remote connectivity to the Microsoft Lync Server, it will auto-2D;discover the Access Edge and port to connect to, OR allow you to specific an Access Edge server. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="31" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="32" ItemType="32;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/0830.image_5F00_0F6C6F5E.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/4643.image_5F00_thumb_5F00_1BFA1C7A.png" width=591 height=348></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="32" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="33" ItemType="33;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<B>But wait, there’s more…</B>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="33" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="34" ItemType="34;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Did we mention we’ve been busy this year? On the Office 365 tab, you’ll notice two new tests – the <B>Office 365 Lync DNS</B> test, and the <B>Free/Busy</B> test.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="34" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="35" ItemType="35;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The<B> Office 365 Lync DNS Test </B>will check the external domain name settings for your custom domain user in Office365.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="35" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="36" ItemType="36;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/0334.image_5F00_3B3CC34D.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/8838.image_5F00_thumb_5F00_2C921768.png" width=592 height=613></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="36" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="37" ItemType="37;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Thanks to the Office 365 Deployment Services team, the RCA website now hosts the<B> Office 365 Free/Busy</B> test. This test verifies an Office 365 mailbox can access the free/busy information of an on-2D;premises mailbox and vice versa.&nbsp; This includes:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="37" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="38" ItemType="38;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[a check to confirm the system time of the hybrid server is not offset by more than five minutes, which causes failures when requesting delegation tokens from the Microsoft Federated Gateway. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="38" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="39" ItemType="39;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[a check to verify inbound connectivity to the hybrid server does not require firewall pre-2D;authentication; that is, the firewall allows pass-2D;through authentication. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="39" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="40" ItemType="40;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[a check to verify the hybrid server meets the minimum Exchange Server version requirement (Exchange Server 2010 SP1). ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="40" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="41" ItemType="41;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[a basic free/busy query against the target Availability Service. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="41" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="42" ItemType="42;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Links to guidance on the Hybrid Configuration Wizard, a common source of hybrid deployment misconfiguration ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="42" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="43" ItemType="43;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Phew! Thanks for reading this far. We hope you enjoy the new updates, and we look forward to hearing from you,]]></Val>-D;-A; </Str>-D;-A; <Disp Order="43" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="44" ItemType="44;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Nicole Allen</SPAN> <BR>On behalf of the RCA team]]></Val>-D;-A; </Str>-D;-A; <Disp Order="44" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="45" ItemType="45;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2012/11/19/what-2D;s-2D;new-2D;with-2D;microsoft-2D;remote-2D;connectivity-2D;analyzer-2D;a-2D;lot.aspx">What’s new with Microsoft Remote Connectivity Analyzer? A lot!</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="45" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:59.0001282Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3549603" width="1" height="1">Windows Management Framework 3.0 en Exchange 2007 y Exchange 2010http://blogs.technet.com/b/exchange_sp/archive/2013/01/31/windows-management-framework-3-0-en-exchange-2007-y-exchange-2010.aspxThu, 31 Jan 2013 15:39:58 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3549602OfficeLocalization0<p>Art&iacute;culo original publicado el s&aacute;bado, 15 de diciembre de 2012</p> <p>Recientemente, Windows Update comenz&oacute; a ofrecer <span class="bold">Windows Management Framework 3.0</span> como una actualizaci&oacute;n opcional. Esto incluye todas las formas de distribuci&oacute;n de actualizaciones, como Microsoft Update, <acronym title="Windows Server Update Service">WSUS</acronym>, System Center Configuration Manager y otros medios. La clave aqu&iacute; es que Windows Management Framework 3.0 incluye PowerShell 3.0.</p> <p>Windows Management Framework 3.0 se distribuye como <a class="bold" href="http://support.microsoft.com/kb/2506146">KB2506146</a> y <a class="bold" href="http://support.microsoft.com/kb/2506143">KB2506143</a> (cu&aacute;l se ofrezca depender&aacute; de la versi&oacute;n de servidor que est&eacute; ejecutando: Windows Server 2008 SP2 o Windows Server 2008 R2 SP1).</p> <h3>&iquest;Qu&eacute; significa esto?</h3> <p>Windows Management Framework 3.0 (concretamente PowerShell 3.0) <span class="bold">no se admite</span> en ninguna versi&oacute;n de Exchange <em>excepto</em> en Exchange Server 2013, que lo necesita. Si instala Windows Management Framework 3.0 en un servidor que ejecuta Exchange 2007 o Exchange 2010, tendr&aacute; problemas, por ejemplo, los paquetes acumulativos de actualizaciones de Exchange no se instalan o puede que el Shell de administraci&oacute;n de Exchange no se ejecute correctamente.</p> <p>Hemos visto que los paquetes acumulativos de actualizaciones de Exchange no se instalan y presentan los siguientes s&iacute;ntomas:</p> <ul class="arrowlist"> <li>Si se instala un paquete acumulativo mediante Microsoft Update, se podr&iacute;a producir un error de actualizaci&oacute;n con el c&oacute;digo de error <a class="command lightyellow">80070643</a></li> <li>Si se instala un paquete acumulativo mediante una descarga, el error que se muestra es <span class="command">La instalaci&oacute;n finaliz&oacute; antes de tiempo debido a un error</span>.</li> <li>En ambos casos, el id. de evento 1024 puede registrarse en el registro de eventos de aplicaci&oacute;n con el c&oacute;digo de error &ldquo;1603&rdquo;. Por ejemplo, si intenta instalar el paquete acumulativo de actualizaciones 5 para Exchange 2010 SP2, quiz&aacute;s vea la siguiente descripci&oacute;n en el id. de evento 1024: <blockquote><span class="command">Producto: Microsoft Exchange Server - la actualizaci&oacute;n "Paquete acumulativo de actualizaciones 5-v2 para Exchange Server 2010 Service Pack 2 (KB2785908) 14.2.328.10" no se pudo instalar. C&oacute;digo de error 1603. Windows Installer puede crear registros para ayudar a solucionar problemas de instalaci&oacute;n de paquetes de software. Use el v&iacute;nculo siguiente para obtener instrucciones sobre la activaci&oacute;n de la compatibilidad de registro: http://go.microsoft.com/fwlink/?LinkId=23127</span></blockquote> </li> </ul> <p>En estos momentos, nuestro consejo es no implementar Windows Management Framework 3.0 en servidores que ejecuten Exchange 2007 o Exchange 2010, ni en estaciones de trabajo con las herramientas de administraci&oacute;n de Exchange de cualquiera de las versiones instaladas. Si ya ha implementado esta actualizaci&oacute;n, debe quitarla. Una vez quitada la actualizaci&oacute;n, deber&iacute;a restaurarse la funcionalidad.</p> <p><span class="author">Ben Winzenz</span></p> <div class="note"> <ul> <li>17/12/2012: informaci&oacute;n agregada sobre el id. de evento 1024.</li> </ul> </div> <p><img src="http://blogs.technet.com/aggbug.aspx?PostID=3540947" alt="" width="1" height="1" /></p> <p>Esta entrada de blog es una traducci&oacute;n. Puede encontrar el art&iacute;culo original en <a href="http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-management-framework-3-0-on-exchange-2007-and-exchange-2010.aspx">Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010</a></p> <!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Windows-2D;Management-2D;Framework-2D;30-2D;on-2D;Exchange-2D;2.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Sat, Dec 15 2012]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Recently, Windows Update began offering the <SPAN class=bold>Windows Management Framework 3.0</SPAN> as an Optional update. This includes all forms of update distribution, such as Microsoft Update, <ACRONYM title="Windows Server Update Service">WSUS</ACRONYM>, System Center Configuration Manager and other mechanisms. The key bit here is that the Windows Management Framework 3.0 includes PowerShell 3.0.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Windows Management Framework 3.0 is being distributed as <A class=bold href="http://support.microsoft.com/kb/2506146">KB2506146</A> and <A class=bold href="http://support.microsoft.com/kb/2506143">KB2506143</A> (which one is offered depends on which server version you are running -2D; Windows Server 2008 SP2 or Windows Server 2008 R2 SP1).]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[What does that mean to you?]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Windows Management Framework 3.0 (specifically PowerShell 3.0) <SPAN class=bold>is not yet supported</SPAN> on any version of Exchange <EM>except</EM> Exchange Server 2013, which requires it. If you install Windows Management Framework 3.0 on a server running Exchange 2007 or Exchange 2010, you will encounter problems, such as Exchange update rollups that will not install, or the Exchange Management Shell may not run properly.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[We have seen Exchange update rollups not installing with the following symptoms:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[If rollup is installed through Microsoft Update, the installation might error with error code <A class="command lightyellow">80070643</A> ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[If rollup is installed from a download, the error displayed is <SPAN class=command>Setup ended prematurely because of an error</SPAN>. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[In both cases, Event ID 1024 may be logged in the Application event log with the error error code “1603”. For example, if you try to install update roll 5 for Exchange 2010 SP2, you may see the following description in event ID 1024: ]D;]A;<BLOCKQUOTE><SPAN class=command>Product: Microsoft Exchange Server -2D; Update 'Update Rollup 5-2D;v2 for Exchange Server 2010 Service Pack 2 (KB2785908) 14.2.328.10' could not be installed. Error code 1603. Windows Installer can create logs to help troubleshoot issues with installing software packages. Use the following link for instructions on turning on logging support: http://go.microsoft.com/fwlink/?LinkId=23127</SPAN></BLOCKQUOTE>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Our guidance at this time is that Windows Management Framework 3.0 should not be deployed on servers running Exchange 2007 or Exchange 2010, or on workstations with the Exchange Management Tools for either version installed. If you have already deployed this update, it should be removed. Once you remove the update, functionality should be restored.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Ben Winzenz</SPAN>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="13" ItemType="13;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[12/17/2012: Added details about Event ID 1024. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="13" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="14" ItemType="14;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2012/12/14/windows-2D;management-2D;framework-2D;3-2D;0-2D;on-2D;exchange-2D;2007-2D;and-2D;exchange-2D;2010.aspx">Windows Management Framework 3.0 on Exchange 2007 and Exchange 2010</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="14" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:03.0001282Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3549602" width="1" height="1">Exchange Server 2013 alcanza una disponibilidad generalhttp://blogs.technet.com/b/exchange_sp/archive/2013/01/31/exchange-server-2013-alcanza-una-disponibilidad-general.aspxThu, 31 Jan 2013 15:39:00 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3549601OfficeLocalization0<p>Art&iacute;culo original publicado el martes, 4 de diciembre de 2012</p> <p>En <a href="http://blogs.technet.com/b/exchange/archive/2012/10/11/the-new-exchange-reaches-rtm.aspx">octubre</a> anunciamos que la versi&oacute;n RTM de Exchange Server 2013 estaba terminada. Desde entonces, hemos centrado nuestros esfuerzos en el lanzamiento de la siguiente versi&oacute;n de Exchange a trav&eacute;s de varios canales de distribuci&oacute;n hasta nuestros clientes empresariales.</p> <p>Hoy hemos alcanzado otro hito importante: el equipo de Exchange se complace en anunciar la disponibilidad general de Exchange Server 2013. Puede descargarlo de <a href="http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx">TechNet</a> hoy mismo y evaluar el producto durante 180 d&iacute;as. Tambi&eacute;n puede registrarse en Office 365 <a href="https://portal.microsoftonline.com/Signup/MainSignup15.aspx?OfferId=D214930B-46C2-4FD2-B7F9-EC134993F34A&amp;dl=ENTERPRISEPACK_B_PILOT&amp;pc=O365-Preview-2012&amp;ali=1">Preview</a> para disfrutar de la experiencia de Exchange m&aacute;s actualizada de la nube en tan solo unos minutos.</p> <p>Aquellos que quieran implementar Exchange Server 2013 en un entorno virgen, o en laboratorios y entornos de pruebas para evaluar las nuevas caracter&iacute;sticas y realizar pruebas con aplicaciones de l&iacute;nea de negocio, pueden hacerlo directamente. Si est&aacute; ejecutando un entorno de Exchange 2010 o 2007, necesitar&aacute; el paquete acumulativo de actualizaciones de <a href="http://blogs.technet.com/b/exchange/archive/2012/09/25/announcing-exchange-2010-service-pack-3.aspx">Exchange Server 2010 SP3</a> o 2007 para poder realizar la actualizaci&oacute;n. Sabemos que est&aacute; deseando cambiar a la nueva versi&oacute;n y por eso nos estamos esforzando en dar los &uacute;ltimos retoques a Exchange 2010 SP3 y al paquete acumulativo de actualizaciones, que estar&aacute; listo para su lanzamiento en el primer trimestre de 2013.</p> <p>Si a&uacute;n no lo ha hecho, le animamos a conocer m&aacute;s acerca de Exchange Server 2013 leyendo la documentaci&oacute;n de <a href="http://technet.microsoft.com/en-us/exchange/fp179701">TechNet</a> o asistiendo a una sesi&oacute;n de aprendizaje de <a href="http://www.officeignite.com/">Ignite</a>. En este punto es aconsejable evaluar los requisitos previos y los requisitos del sistema, as&iacute; como familiarizarse con la arquitectura simplificada de los bloques de creaci&oacute;n de Exchange para partir con ventaja a la hora de dimensionar, planear y comprar el <a href="http://technet.microsoft.com/library/aa996719(EXCHG.150)">hardware</a>.</p> <p>El equipo de EHLO ha incorporado m&aacute;s contenido t&eacute;cnico al nuevo Exchange desde el anuncio de la versi&oacute;n RTM:</p> <ul> <li><a href="http://blogs.technet.com/b/exchange_sp/archive/2012/12/05/oab-en-exchange-server-2013.aspx">Libreta de direcciones sin conexi&oacute;n en Exchange Server 2013</a>&nbsp;&ndash; Bhalchandra Atre</li> <li><a href="http://blogs.technet.com/b/exchange_sp/archive/2012/12/05/administrar-el-uso-compartido-federado-con-el-eac.aspx">Administrar recursos compartidos federados con EAC</a>&nbsp;&ndash; Elber Ren y Robert Mazzoli</li> <li><a href="http://blogs.technet.com/b/exchange_sp/archive/2012/12/05/acceso-sin-conexi-243-n-en-outlook-web-app-2013.aspx">Acceso sin conexi&oacute;n en Outlook Web App para el nuevo Exchange</a>&nbsp;&ndash; Sara Manning</li> <li><a href="http://blogs.technet.com/b/exchange/archive/2012/11/08/public-folders-in-the-new-office.aspx">Carpetas p&uacute;blicas en el nuevo Office</a>&nbsp;&ndash; Alfons Staerk y Nikhil Aggarwal</li> <li><a href="http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-exchange-server-2013-using-tmg.aspx">Publicar en Exchange Server 2013 mediante TMG</a>&nbsp;&ndash; Greg Taylor</li> <li><a href="http://blogs.technet.com/b/exchange_sp/archive/2012/12/05/lecciones-del-centro-de-datos-disponibilidad-administrada.aspx">Lecciones del centro de datos: disponibilidad administrada</a> &ndash; Ross Smith IV y Greg Thiel</li> </ul> <p>&hellip;y continuaremos publicando nuevos art&iacute;culos sobre Exchange en EHLO en los pr&oacute;ximos meses. No olvide comprobarlo. Gracias de nuevo por su apoyo continuo y no deje de enviar sus comentarios.</p> <p><span class="author">Equipo de Exchange</span></p> <p><img src="http://blogs.technet.com/aggbug.aspx?PostID=3536160" alt="" width="1" height="1" /></p> <p>Esta entrada de blog es una traducci&oacute;n. Puede consultar el art&iacute;culo original en <a href="http://blogs.technet.com/b/exchange/archive/2012/12/03/exchange-server-2013-reaches-general-availability.aspx">Exchange Server 2013 Reaches General Availability</a></p> <!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Exchange-2D;Server-2D;2013-2D;Reaches-2D;General-2D;Availabi.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Exchange Server 2013 Reaches General Availability]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Tue, Dec 04 2012]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Back in <A href="http://blogs.technet.com/b/exchange/archive/2012/10/11/the-2D;new-2D;exchange-2D;reaches-2D;rtm.aspx">October</A>, we announced that the Release to Manufacturing (RTM) build of Exchange Server 2013 was signed off. Since that time, we’ve been focusing our efforts on releasing the next version of Exchange through multiple distribution channels to our business customers.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Today, we’ve reached another important milestone – The Exchange team is excited to announce the general availability of Exchange Server 2013. You can download the bits from <A href="http://technet.microsoft.com/en-2D;us/evalcenter/hh973395.aspx">TechNet</A> today and evaluate the product for 180 days. You can also sign up for the Office 365 <A href="https://portal.microsoftonline.com/Signup/MainSignup15.aspx?OfferId=D214930B-2D;46C2-2D;4FD2-2D;B7F9-2D;EC134993F34A&amp;dl=ENTERPRISEPACK_B_PILOT&amp;pc=O365-2D;Preview-2D;2012&amp;ali=1">Preview</A> to get the most current Exchange experience in the cloud in just a few minutes.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[For those of you who wish to roll out Exchange Server 2013 in greenfield environments, or in labs and test environments to evaluate new features and test with LOB applications, you can start right away. If you are running an Exchange 2010 or 2007 environment, you’ll need <A href="http://blogs.technet.com/b/exchange/archive/2012/09/25/announcing-2D;exchange-2D;2010-2D;service-2D;pack-2D;3.aspx">Exchange Server 2010 SP3</A> or 2007 roll up in order to upgrade. We know you are eager to get moving to the new version, so we are hard at work putting the finishing touches on Exchange 2010 SP3 and the roll up, which are on track for release in Q1 of calendar year 2013.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[If you haven’t already, we encourage you to learn more about Exchange Server 2013 by reviewing <A href="http://technet.microsoft.com/en-2D;us/exchange/fp179701">TechNet</A> documentation or attending an <A href="http://www.officeignite.com/">Ignite</A> training session. It’s a good idea to evaluate prerequisites and system requirements at this time, as well as become familiar with Exchange’s simplified building block architecture, so that you can get a head start on <A href="http://technet.microsoft.com/library/aa996719(EXCHG.150)">hardware</A> sizing, planning and purchasing.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The EHLO team has been adding more technical content on the new Exchange since the RTM announcement:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-2D;in-2D;exchange-2D;server-2D;2013.aspx">Offline Address Book in Exchange Server 2013</A> – Bhalchandra Atre ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/b/exchange/archive/2012/10/30/managing-2D;federated-2D;sharing-2D;with-2D;the-2D;eac.aspx">Managing Federated Sharing with the EAC</A> – Elber Ren and Robert Mazzoli ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/b/exchange/archive/2012/11/06/offline-2D;access-2D;in-2D;outlook-2D;web-2D;app-2D;2013.aspx">Offline Access in Outlook Web App for the New Exchange</A> – Sara Manning ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/b/exchange/archive/2012/11/08/public-2D;folders-2D;in-2D;the-2D;new-2D;office.aspx">Public Folders in the New&nbsp;Office</A> – Alfons Staerk and Nikhil Aggarwal ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/b/exchange/archive/2012/11/21/publishing-2D;exchange-2D;server-2D;2013-2D;using-2D;tmg.aspx">Publishing Exchange Server 2013 using TMG</A> – Greg Taylor ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="13" ItemType="13;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/b/exchange/archive/2012/09/21/lessons-2D;from-2D;the-2D;datacenter-2D;managed-2D;availability.aspx">Lessons from the Datacenter: Managed Availability</A> – Ross Smith IV and Greg Thiel ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="13" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="14" ItemType="14;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[…and we will continue to publish new Exchange articles to EHLO in the coming months, so keep checking back! Thanks again for your continued support, and please keep the feedback coming.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="14" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="15" ItemType="15;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Exchange Team</SPAN>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="15" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="16" ItemType="16;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2012/12/03/exchange-2D;server-2D;2013-2D;reaches-2D;general-2D;availability.aspx">Exchange Server 2013 Reaches General Availability</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="16" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:07:12.0001282Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3549601" width="1" height="1">Solucionador de problemas de replicación de carpetas públicashttp://blogs.technet.com/b/exchange_sp/archive/2013/01/31/solucionador-de-problemas-de-replicaci-243-n-de-carpetas-p-250-blicas.aspxThu, 31 Jan 2013 15:38:06 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3549599OfficeLocalization0<p>Art&iacute;culo original publicado el martes, 13 de noviembre de 2012</p> <p>Recientemente hemos publicado un tutorial guiado para solucionar problemas de replicaci&oacute;n de carpetas p&uacute;blicas en Microsoft Exchange 2003. Hay varias maneras de acceder al solucionador de problemas. Puede usar <a href="http://support.microsoft.com/common/survey.aspx?scid=sw;en;3221&amp;showpage=1">este</a> v&iacute;nculo para acceder directamente a &eacute;l. Tambi&eacute;n se incluir&aacute; en varios art&iacute;culos relativos a la replicaci&oacute;n de carpetas p&uacute;blicas como el siguiente: <a href="http://support.microsoft.com/KB/842273">http://support.microsoft.com/KB/842273</a>.</p> <p>Ahora, s&eacute; que se estar&aacute;n preguntando porqu&eacute; proporcionamos un solucionador de problemas para Exchange 2003 si ya no se ofrece soporte para el mismo. Hay varios motivos para esta decisi&oacute;n. En primer lugar, a&uacute;n hay numerosos clientes de Exchange que est&aacute;n realizando la transici&oacute;n desde esta versi&oacute;n y queremos ayudar en lo posible en su cambio a versiones del producto m&aacute;s recientes con soporte. Esta es la mejor manera de guiar a estos clientes porque ya no disponemos de la opci&oacute;n de soporte telef&oacute;nico. En segundo lugar, ya se han identificado casi todos los problemas de carpetas p&uacute;blicas de Exchange server 2003, por lo que crear un solucionador de problemas que incluya este material no supondr&aacute; un gran cambio. Por &uacute;ltimo, dado que el mecanismo de replicaci&oacute;n de carpetas p&uacute;blicas no ha cambiado sustancialmente durante un tiempo (<a href="http://blogs.technet.com/b/exchange/archive/2012/11/08/public-folders-in-the-new-office.aspx">hasta Exchange 2013</a>), ten&iacute;a sentido comenzar con Exchange 2003 porque esto nos permit&iacute;a realizar actualizaciones para versiones posteriores con relativa facilidad.</p> <p>La organizaci&oacute;n de soporte trabajar&aacute; para ampliar este solucionador de problemas con el fin de incluir las versiones 2007/2010 en el futuro.</p> <p>Este tutorial realmente es una gu&iacute;a para la soluci&oacute;n de problemas de replicaci&oacute;n, desarrollada en una serie de entradas de blog por Bill Long, <a href="http://blogs.technet.com/b/exchange/archive/2006/01/17/public-folder-replication-troubleshooting-part-1-troubleshooting-the-replication-of-new-changes.aspx">aqu&iacute;</a>, <a href="http://blogs.technet.com/b/exchange/archive/2006/01/19/public-folder-replication-troubleshooting-part-2-troubleshooting-the-replication-of-existing-data.aspx">aqu&iacute;</a> y <a href="http://blogs.technet.com/b/exchange/archive/2006/01/23/417974.aspx">aqu&iacute;</a>. Su objetivo no es reemplazar toda la informaci&oacute;n que ayuda a comprender el proceso de replicaci&oacute;n de carpetas p&uacute;blicas, sino proporcionar los pasos necesarios para ayudar a detectar el problema en caso de que haya problemas con la replicaci&oacute;n.</p> <p>Quiero agradecer a las personas que han hecho esto posible. Estas son las partes implicadas (que yo conozca):</p> <p>Soporte de Exchange:</p> <ul> <li>Nick Basile</li> <li>Rob Whaley</li> <li>Bill Long</li> <li>Charlotte Raymundo</li> <li>Will Duff</li> <li>Nino Bilic</li> </ul> <p>Equipos de documentaci&oacute;n y creaci&oacute;n de contenido:</p> <ul> <li>Bobbie DeFault</li> <li>Geoffrey Crisp (Entirenet)</li> <li>Jerry Sitser (Entiernet)</li> <li>Jarrett Renshaw</li> <li>Star Li (Wicresoft)</li> <li>Chen Jiang</li> <li>Victor Zhang (Wicresoft)</li> </ul> <p>Atentamente,</p> <p><span class="author">Charlotte Raymundo <br /></span>Messaging Knowledge Engineer</p> <p><img src="http://blogs.technet.com/aggbug.aspx?PostID=3532064" alt="" width="1" height="1" /></p> <p>Esta entrada de blog es una traducci&oacute;n. Puede consultar el art&iacute;culo original en <a href="http://blogs.technet.com/b/exchange/archive/2012/11/12/public-folder-replication-troubleshooter.aspx">Public Folder replication troubleshooter</a></p> <!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Public-2D;Folder-2D;replication-2D;troubleshooter.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Public Folder replication troubleshooter]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Tue, Nov 13 2012]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Recently, we have released a Guided Walk Through (GWT) for troubleshooting public Folder replication issues in Microsoft Exchange 2003.&nbsp; There are a couple of ways to access the troubleshooter.&nbsp; You can use the link <A href="http://support.microsoft.com/common/survey.aspx?scid=sw;en;3221&amp;showpage=1">here</A> to access it directly.&nbsp; As well, it will be embedded in various related public folder replication articles such as the following:&nbsp; <A href="http://support.microsoft.com/KB/842273">http://support.microsoft.com/KB/842273</A>.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Now, I know you are wondering why we came out with a troubleshooter for Exchange 2003 since it’s no longer in mainstream support?&nbsp; We made this decision for a number of reasons.&nbsp; First, there is a good amount of our Exchange customers who are still transitioning off Exchange 2003 and we want to help those customers as much as possible to move to our newer supported versions of the product.&nbsp; This is the best way to help guide those customers since we no longer have a phone support option for them.&nbsp; Secondly, for the most part, all of our Exchange server 2003 Public Folders issues have already been identified, so creating a troubleshooter covering this material means it will not change drastically. Finally, due to the fact that the public folder replication mechanism has not significantly changed for a while (<A href="http://blogs.technet.com/b/exchange/archive/2012/11/08/public-2D;folders-2D;in-2D;the-2D;new-2D;office.aspx">until Exchange 2013</A>), it made sense to start with Exchange 2003 as it gave us the framework that we can update for later versions relatively easily.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The support organization will be putting efforts into expanding this troubleshooter to include 2007/2010 in the future. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This walk through is really a guide through the replication troubleshooting, as laid out in a series of blog posts by Bill Long, <A href="http://blogs.technet.com/b/exchange/archive/2006/01/17/public-2D;folder-2D;replication-2D;troubleshooting-2D;part-2D;1-2D;troubleshooting-2D;the-2D;replication-2D;of-2D;new-2D;changes.aspx">here</A>, <A href="http://blogs.technet.com/b/exchange/archive/2006/01/19/public-2D;folder-2D;replication-2D;troubleshooting-2D;part-2D;2-2D;troubleshooting-2D;the-2D;replication-2D;of-2D;existing-2D;data.aspx">here</A> and <A href="http://blogs.technet.com/b/exchange/archive/2006/01/23/417974.aspx">here</A>. It is not meant to replace all of the data that helps you understand the public folder replication process, but rather quickly give you the steps you need to help find the problem if there are problems with replication.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[I wanted to thank the people who helped make this a reality. Here are the parties involved (that I am aware of):]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Exchange support:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Nick Basile ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Rob Whaley ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Bill Long ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Charlotte Raymundo ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="13" ItemType="13;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Will Duff ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="13" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="14" ItemType="14;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Nino Bilic ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="14" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="15" ItemType="15;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Documentation / content creation teams:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="15" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="16" ItemType="16;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Bobbie DeFault ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="16" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="17" ItemType="17;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Geoffrey Crisp (Entirenet) ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="17" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="18" ItemType="18;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Jerry Sitser (Entiernet) ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="18" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="19" ItemType="19;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Jarrett Renshaw ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="19" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="20" ItemType="20;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Star Li (Wicresoft) ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="20" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="21" ItemType="21;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Chen Jiang ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="21" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="22" ItemType="22;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Victor Zhang (Wicresoft) ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="22" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="23" ItemType="23;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Regards,]]></Val>-D;-A; </Str>-D;-A; <Disp Order="23" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="24" ItemType="24;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Charlotte Raymundo <BR></SPAN>Messaging Knowledge Engineer]]></Val>-D;-A; </Str>-D;-A; <Disp Order="24" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="25" ItemType="25;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2012/11/12/public-2D;folder-2D;replication-2D;troubleshooter.aspx">Public Folder replication troubleshooter</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="25" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:08:01.0001282Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3549599" width="1" height="1">Administrar la libreta de direcciones sin conexión en Exchange Server 2013http://blogs.technet.com/b/exchange_sp/archive/2013/01/31/administrar-la-libreta-de-direcciones-sin-conexi-243-n-en-exchange-server-2013.aspxThu, 31 Jan 2013 15:38:00 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3549600OfficeLocalization0<p>Art&iacute;culo original publicado el martes 15 de enero de 2013</p> <p>El art&iacute;culo del blog del equipo de Exchange <a class="bold" href="http://blogs.technet.com/b/exchange_sp/archive/2012/12/05/oab-en-exchange-server-2013.aspx">Libreta de direcciones sin conexi&oacute;n en Exchange Server 2013</a> presentaba la nueva generaci&oacute;n de libretas de direcciones sin conexi&oacute;n (OAB) y arquitectura de distribuci&oacute;n de Exchange Server 2013. Dedique unos momentos a leer el art&iacute;culo si a&uacute;n no lo ha hecho o vuelva a leerlo para refrescar la memoria.</p> <p>La administraci&oacute;n de <acronym title="Offline Address Book">libretas de direcciones sin conexi&oacute;n</acronym> es diferente en Exchange 2013 debido a los cambios de arquitectura. Adem&aacute;s, el nuevo <a class="bold" title="Ver la publicaci&oacute;n anterior: Administrar el nuevo Exchange" href="http://blogs.technet.com/b/exchange_sp/archive/2012/09/21/administraci-243-n-del-nuevo-exchange.aspx">Centro de administraci&oacute;n de Exchange</a> no dispone actualmente de opciones para administrar libretas de direcciones sin conexi&oacute;n. Esto significa que, en estos momentos, tendr&aacute; que usar el Shell de administraci&oacute;n de Exchange para las tareas relativas a las libretas de direcciones sin conexi&oacute;n.</p> <p>Este art&iacute;culo muestra las tareas que se realizan con m&aacute;s frecuencia en la administraci&oacute;n de <acronym title="Offline Address Book">libretas de direcciones sin conexi&oacute;n</acronym> e incluye un par de escenarios reales que ayudar&aacute;n a comprender mejor las tareas.</p> <p class="note">Nota: Si se encuentra en un entorno de dominio de Active Directory de bosques m&uacute;ltiples, aseg&uacute;rese de que la sesi&oacute;n del Shell tiene habilitado <span class="parameter lightyellow">ViewEntireForest</span>; de lo contrario, algunos de los comandos del art&iacute;culo no producir&aacute;n ning&uacute;n resultado.</p> <p>Comando para habilitar ViewEntireForest:</p> <p class="code">Set-ADServerSettings -ViewEntireForest $true</p> <h2>Creaci&oacute;n de una nueva libreta de direcciones sin conexi&oacute;n</h2> <p>Para crear una nueva libreta de direcciones sin conexi&oacute;n en Exchange 2013 ya no se usa el par&aacute;metro -Server; &uacute;nicamente se deben especificar las listas de direcciones que se necesitar&aacute;n.</p> <p>En el ejemplo siguiente se crea una libreta de direcciones sin conexi&oacute;n para la lista de direcciones denominada &ldquo;Global Address List FAB&rdquo;</p> <p class="code">New-OfflineAddressBook -Name OAB-FAB -AddressLists "Global Address List FAB"</p> <h2>Identificar los servidores de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n</h2> <p>En Exchange Server 2013, a los buzones de arbitraje se les asigna cierta &ldquo;funcionalidad persistente&rdquo; que define el prop&oacute;sito o funci&oacute;n del buz&oacute;n de arbitraje.</p> <p>Un buz&oacute;n de arbitraje con la funcionalidad persistente &ldquo;OrganizationCapabilityOABGen&rdquo; es responsable de la generaci&oacute;n de libretas de direcciones sin conexi&oacute;n. Haremos referencia a este buz&oacute;n como &ldquo;Buz&oacute;n de la organizaci&oacute;n&rdquo; durante todo el art&iacute;culo.</p> <p>El servidor de buzones de Exchange Server 2013 que hospeda el buz&oacute;n de la organizaci&oacute;n generar&aacute; todas las libretas de direcciones sin conexi&oacute;n definidas en el entorno.</p> <p>En entorno que no sea DAG, use el comando siguiente para identificar los servidores de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n:</p> <p class="code">Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like "*oab*"} | ft name,servername</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/6746.image_5F00_1F282B38.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/3010.image_5F00_thumb_5F00_179CBBCB.png" alt="imagen" width="624" height="55" border="0" /></a></p> <p>En un entorno DAG, la identificaci&oacute;n de los servidores de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n se realiza en dos pasos.</p> <p>Paso 1: Identificar el buz&oacute;n de la organizaci&oacute;n que hospeda la base de datos de buzones con capacidad para generar libretas de direcciones sin conexi&oacute;n.</p> <p>Use el comando siguiente para enumerar los buzones de arbitraje con funcionalidad persistente OABGen y la base de datos donde se hospeda este buz&oacute;n:</p> <p class="code">Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like "*oab*"} | ft name,database</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/1854.image_5F00_5E19ABD3.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/8132.image_5F00_thumb_5F00_24969BDC.png" alt="imagen" width="624" height="55" border="0" /></a></p> <p>Paso 2: Identificar el servidor de buzones donde est&aacute; montada la base de datos que hospeda el buz&oacute;n de la organizaci&oacute;n</p> <p>Use el comando siguiente para identificar la copia activa de la base de datos de buzones:</p> <p class="code">Get-MailboxDatabaseCopyStatus db1</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/3010.image_5F00_0F38E674.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/3426.image_5F00_thumb_5F00_0ECCB37F.png" alt="imagen" width="624" height="62" border="0" /></a></p> <p>El servidor donde el estado de la base de datos es "montada" es el servidor actual de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n.</p> <h2>Cambiar el servidor de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n</h2> <p>Hay dos maneras de cambiar el servidor de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n.</p> <h3>Mover el buz&oacute;n</h3> <p>Mueva el buz&oacute;n de la organizaci&oacute;n a una base de datos de buzones en un servidor destinado a ser designado como servidor de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n.</p> <p>Ejemplo:</p> <p>DB1 es una base de datos de una sola copia presente en el servidor Exch1 que hospeda el buz&oacute;n de la organizaci&oacute;n. DB2 es la base de datos de buzones presente en Exch2.</p> <p>El comando siguiente se puede usar para mover el buz&oacute;n de la organizaci&oacute;n a DB2 y convertir a Exch2 en el servidor de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n.</p> <p class="code">Get-Mailbox -Arbitration -database db1| where {$_.PersistedCapabilities &ndash;like &ldquo;*oab*&rdquo;} | New-MoveRequest -TargetDatabase db2</p> <p>Este m&eacute;todo es m&aacute;s apropiado para entornos que tienen una &uacute;nica copia de la base de datos de buzones que hospeda el buz&oacute;n de la organizaci&oacute;n.</p> <h3>Activar la base de datos de buzones en otro servidor</h3> <p>Este m&eacute;todo est&aacute; indicado para entornos que tienen varias copias de la base de datos de buzones que hospeda el buz&oacute;n de la organizaci&oacute;n.</p> <p>Ejemplo:</p> <p>DB1 hospeda el buz&oacute;n de la organizaci&oacute;n y tiene copias en los servidores Exch1 y Exch2. DB1 est&aacute; actualmente activo en Exch1.</p> <p>El comando siguiente se puede usar para activar DB1 en Exch2 y, por lo tanto, convertirlo en el servidor de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n:</p> <p class="code">Move-ActiveMailboxDatabase DB1 -ActivateOnServer Exch2</p> <p class="note">Nota: Revise las directrices indicadas en la secci&oacute;n &ldquo;Ubicaci&oacute;n del buz&oacute;n de la organizaci&oacute;n&rdquo; m&aacute;s adelante antes de cambiar el servidor de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n.</p> <h2>Creaci&oacute;n de un nuevo buz&oacute;n de la organizaci&oacute;n</h2> <p>Los administradores pueden crear buzones de la organizaci&oacute;n adicionales para tolerancia a errores o para dar servicio a usuarios en una implementaci&oacute;n de Exchange geogr&aacute;ficamente dispersos.</p> <p>La creaci&oacute;n de un nuevo buz&oacute;n de la organizaci&oacute;n se realiza en dos pasos:</p> <p>Paso 1: Crear un nuevo buz&oacute;n de arbitraje</p> <p class="code">New-Mailbox -Arbitration -Name "OAB Seattle" -Database DB2Seattle -UserPrincipalName <a href="mailto:oabs@contoso.com">oabs@contoso.com</a> &ndash;DisplayName &ldquo;OAB Mailbox for Seattle&rdquo;</p> <p>Paso 2: Habilitar la funcionalidad OABGen</p> <p class="code">Set-Mailbox -Arbitration oabs -OABGen $true</p> <p class="note">Nota: Consulte las directrices indicadas en la secci&oacute;n &ldquo;Ubicaci&oacute;n del buz&oacute;n de la organizaci&oacute;n&rdquo; m&aacute;s adelante antes de crear buzones de la organizaci&oacute;n adicionales.</p> <h2>Cambio de la programaci&oacute;n de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n</h2> <p>Hasta Exchange Server 2010, la generaci&oacute;n de libretas de direcciones sin conexi&oacute;n se basaba en una programaci&oacute;n establecida en las propiedades de la libreta de direcciones sin conexi&oacute;n. Puede ver una programaci&oacute;n definida cuando consulte las propiedades de una libreta de direcciones sin conexi&oacute;n de Exchange 2013, pero la generaci&oacute;n de libretas de direcciones sin conexi&oacute;n de Exchange Server 2013 <strong><em>no</em></strong> se realiza seg&uacute;n la programaci&oacute;n definida en las propiedades de la libreta de direcciones sin conexi&oacute;n:</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/5670.image_5F00_235202FD.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/6153.image_5F00_thumb_5F00_22E5D008.png" alt="imagen" width="624" height="58" border="0" /></a></p> <p>En cambio, la generaci&oacute;n de libretas de direcciones sin conexi&oacute;n de Exchange Server 2013 tiene lugar seg&uacute;n las propiedades OABGeneratorWorkCycle y OABGeneratorWorkCycleCheckpoint configuradas en el servidor de buzones.</p> <p>Ejemplo:</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/0218.image_5F00_22799D13.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/2450.image_5F00_thumb_5F00_4D520125.png" alt="imagen" width="443" height="75" border="0" /></a></p> <p>Los valores de la captura de pantalla anterior significan que la libreta de direcciones sin conexi&oacute;n se genera una vez al d&iacute;a.</p> <h2>&iquest;Qu&eacute; servidor de buzones proces&oacute; la solicitud de descarga de la libreta de direcciones sin conexi&oacute;n?</h2> <p>El rol CAS de Exchange Server 2013 env&iacute;a mediante proxy la solicitud de descarga de la libreta de direcciones sin conexi&oacute;n a un servidor de roles de buz&oacute;n apropiado. El rol CAS mantiene un registro de cada solicitud que administra en los archivos de registro, presentes en la carpeta %ExchangeInstallPath%\Logging\HttpProxy\OAB\</p> <p>Estos archivos de registro son una excelente herramienta para identificar qu&eacute; servidor de buz&oacute;n eligi&oacute; el rol CAS para atender la solicitud.</p> <p>Informaci&oacute;n de algunos campos importantes del archivo de registro:</p> <table class="posttable"> <tbody> <tr><th>Campo</th><th>Descripci&oacute;n</th></tr> <tr> <td>UrlStem</td> <td>Resulta &uacute;til para identificar la libreta de direcciones sin conexi&oacute;n que se va a descargar, adem&aacute;s de si esta es una descarga completa o una descarga incremental</td> </tr> <tr> <td>AuthenticatedUser</td> <td>Nombre del usuario que solicita la libreta de direcciones sin conexi&oacute;n</td> </tr> <tr> <td>AnchorMailbox</td> <td>Nombre de dominio del buz&oacute;n de la organizaci&oacute;n identificado como el m&aacute;s pr&oacute;ximo para atender la solicitud de libreta de direcciones sin conexi&oacute;n</td> </tr> <tr> <td>ServerHostName</td> <td>Nombre del servidor CAS que administra la solicitud</td> </tr> <tr> <td>HttpStatus</td> <td>C&oacute;digo de estado de la acci&oacute;n del proxy</td> </tr> <tr> <td>ProxyAction</td> <td>Acci&oacute;n que realiz&oacute; el servidor CAS para la solicitud; normalmente ser&aacute; &ldquo;Proxy&rdquo; para las libretas de direcciones sin conexi&oacute;n de Exchange 2013</td> </tr> <tr> <td>TargetServer</td> <td>Nombre del servidor de roles de buz&oacute;n al que se envi&oacute; la solicitud mediante proxy</td> </tr> </tbody> </table> <p>Para leer mejor el archivo de registro, se puede importar a Excel.</p> <p>Ejemplo:</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/3513.image_5F00_3B093A63.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/8625.image_5F00_thumb_5F00_3A9D076E.png" alt="imagen" width="624" height="77" border="0" /></a></p> <h2>Forzar la generaci&oacute;n de libretas de direcciones sin conexi&oacute;n</h2> <p>Se pueden usar dos m&eacute;todos para forzar el inicio inmediato de la generaci&oacute;n de libretas de direcciones sin conexi&oacute;n de Exchange Server 2013.</p> <h3>M&eacute;todo 1: Update-OfflineAddresBook</h3> <p>El comando siguiente forzar&aacute; la generaci&oacute;n de una libreta de direcciones sin conexi&oacute;n denominada "Default Offline Address Book" en todos los buzones de la organizaci&oacute;n.</p> <p class="code">Update-OfflineAddressBook "default offline address book"</p> <p class="note">Nota: Este comando inicia una solicitud RPC para cada servidor de buzones que hospeda un buz&oacute;n de la organizaci&oacute;n activo.</p> <h3>M&eacute;todo 2: reiniciar el servicio Asistente de buzones.</h3> <p>El servicio Asistente de buzones de Microsoft Exchange en el rol de buz&oacute;n es responsable de generar las libretas de direcciones sin conexi&oacute;n. Al reiniciar el servicio se generan todas las libretas de direcciones sin conexi&oacute;n definidas en el entorno de un servidor de buzones espec&iacute;fico, si hospeda un buz&oacute;n de la organizaci&oacute;n activo.</p> <h2>Ubicaci&oacute;n del buz&oacute;n de la organizaci&oacute;n</h2> <p>El rol CAS de Exchange Server 2013 env&iacute;a mediante proxy la solicitud de descarga de la libreta de direcciones sin conexi&oacute;n al servidor de buzones "m&aacute;s pr&oacute;ximo" que hospede un buz&oacute;n de la organizaci&oacute;n activo. Puede realizar el env&iacute;o mediante proxy de la solicitud del tipo round robin si encuentra m&aacute;s de un buz&oacute;n de la organizaci&oacute;n activo en el mismo sitio de AD. Esto podr&iacute;a provocar descargas completas frecuentes de la libreta de direcciones sin conexi&oacute;n.</p> <p>Por este motivo, actualmente se aconseja planear la ubicaci&oacute;n del buz&oacute;n de la organizaci&oacute;n de manera que tenga un buz&oacute;n de la organizaci&oacute;n activo en un sitio de AD. Esto es aplicable a la creaci&oacute;n de un nuevo buz&oacute;n de la organizaci&oacute;n as&iacute; como a la creaci&oacute;n de copias de la base de datos de buzones que hospeda un buz&oacute;n de la organizaci&oacute;n.</p> <h2>Escenarios</h2> <p>Los escenarios siguientes tratan una situaci&oacute;n real para explicar con m&aacute;s detalle los nuevos m&eacute;todos de administraci&oacute;n de libretas de direcciones sin conexi&oacute;n.</p> <h3>Escenario 1: Crear un nuevo buz&oacute;n de la organizaci&oacute;n</h3> <p>Contoso tiene implementados servidores de buzones y de roles CAS de Exchange Server 2013 en los sitios de Dallas y Seattle. John, el administrador de Exchange para Contoso, analiza los archivos de registro de los servidores proxy http en los servidores CAS y descubre que las solicitudes de descarga de libretas de direcciones sin conexi&oacute;n de los usuarios de Seattle van a los servidores de Dallas. Tras una posterior investigaci&oacute;n, John descubre que solo tiene un buz&oacute;n de la organizaci&oacute;n en Dallas, por lo que las solicitudes de descarga de libretas de direcciones sin conexi&oacute;n de todos los usuarios van al servidor de Dallas.</p> <p>Decide crear un nuevo buz&oacute;n de la organizaci&oacute;n en el sitio de Seattle con los siguientes comandos:</p> <p>Paso 1: Crear un nuevo buz&oacute;n de arbitraje</p> <p class="code">New-Mailbox -Arbitration -Name "OAB Seattle" -Database DB2Seattle -UserPrincipalName <a href="mailto:oabs@contoso.com">oabs@contoso.com</a> &ndash;DisplayName &ldquo;OAB Mailbox for Seattle&rdquo;</p> <p>Paso 2: Habilitar el buz&oacute;n de arbitraje con la funcionalidad OABGen</p> <p class="code">Set-Mailbox -Arbitration oabs -OABGen $true</p> <h3>Escenario 2: Personalizar la programaci&oacute;n de generaci&oacute;n de libretas de direcciones sin conexi&oacute;n</h3> <p>Ben es el administrador de la implementaci&oacute;n de Exchange 2013 en Tail Spin Toys. La programaci&oacute;n predeterminada para la generaci&oacute;n de libretas de direcciones sin conexi&oacute;n no es adecuada para ellos y quieren generar las libretas de direcciones sin conexi&oacute;n aproximadamente cada cuatro horas.</p> <p>Ben usar&aacute; el siguiente comando para cambiar las propiedades de los servidores de buzones que hospedar&aacute;n el buz&oacute;n de la organizaci&oacute;n.</p> <p class="code">Set-MailboxServer Exch1 -OABGeneratorWorkCycle 01.00:00:00 -OABGeneratorWorkCycleCheckpoint 04:00:00</p> <p>Despu&eacute;s de un par de d&iacute;as, John analiza el id. de evento 17002 en un registro de la aplicaci&oacute;n, y se asegura de que la libreta de direcciones sin conexi&oacute;n se genera cada cuatro horas.</p> <p><a href="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/7635.image_5F00_3A30D479.png"><img style="background-image: none; padding-left: 0px; padding-right: 0px; display: inline; padding-top: 0px; border-width: 0px;" title="imagen" src="http://blogs.technet.com/cfs-file.ashx/__key/communityserver-blogs-components-weblogfiles/00-00-00-31-06-metablogapi/4174.image_5F00_thumb_5F00_6BBC420E.png" alt="imagen" width="624" height="139" border="0" /></a></p> <p>Esperamos que esta publicaci&oacute;n les haya resultado &uacute;til. Env&iacute;enos sus comentarios.</p> <p><span class="author">Bhalchandra Atre</span></p> <p><img src="http://blogs.technet.com/aggbug.aspx?PostID=3545777" alt="" width="1" height="1" /></p> <p>Esta entrada de blog es una traducci&oacute;n. Puede consultar el art&iacute;culo original en <a href="http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx">Managing OAB in Exchange Server 2013</a></p> <!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="Managing-2D;OAB-2D;in-2D;Exchange-2D;Server-2D;2013.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Managing OAB in Exchange Server 2013]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Tue, Jan 15 2013]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The Exchange team blog article <A class=bold href="http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-2D;in-2D;exchange-2D;server-2D;2013.aspx">OAB in Exchange Server 2013</A> introduced the new Offline Address Book (OAB) generation and distribution architecture in Exchange Server 2013. Take a few moments to visit the article if you haven’t seen it yet or re-2D;visit it for a quick refresher.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The <ACRONYM title="Offline Address Book">OAB</ACRONYM> management and administration is different in Exchange 2013 because of architecture changes. Additionally, the new <A class=bold title="See previous post: Managing The New Exchange" href="http://blogs.technet.com/b/exchange/archive/2012/08/09/managing-2D;the-2D;new-2D;exchange.aspx">Exchange Admin Center</A> does not currently have options for managing OABs. This means that, at this time, you will need to use Exchange Management Shell for OAB-2D;related tasks.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This article takes you through commonly performed tasks in <ACRONYM title="Offline Address Book">OAB</ACRONYM> administration and has a couple of real life scenarios to help understand the tasks better.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Note: If you are in multi-2D;forest Active Directory domain environment, make sure the Shell session has <SPAN class="parameter lightyellow">ViewEntireForest</SPAN> is enabled, else some of the commands in the article won’t return any output.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Command to enable ViewEntireForest:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Set-2D;ADServerSettings -2D;ViewEntireForest $true]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Creating a new OAB]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Creating a new OAB in Exchange 2013 no longer uses the -2D;Server parameter. In order to create a new OAB, you should only specify the address lists to be required.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The following example creates OAB for address list named “Global Address List FAB”]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[New-2D;OfflineAddressBook -2D;Name OAB-2D;FAB -2D;AddressLists "Global Address List FAB"]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="13" ItemType="13;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Identify the OAB generation server(s)]]></Val>-D;-A; </Str>-D;-A; <Disp Order="13" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="14" ItemType="14;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The arbitration mailboxes in Exchange Server 2013 are assigned certain “Persisted capability” that defines the purpose/function of the arbitration mailbox.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="14" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="15" ItemType="15;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[An arbitration mailbox with Persisted Capability “OrganizationCapabilityOABGen” is responsible for OAB generation. We will refer this mailbox as “Organization Mailbox” throughout the article.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="15" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="16" ItemType="16;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Exchange Server 2013 mailbox server hosting the Organization Mailbox will generate all OAB’s defined in the environment.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="16" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="17" ItemType="17;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[For a non-2D;DAG environment, use following command to identify the OAB Generation servers:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="17" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="18" ItemType="18;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Get-2D;Mailbox -2D;Arbitration | where {$_.PersistedCapabilities -2D;like "*oab*"} | ft name,servername]]></Val>-D;-A; </Str>-D;-A; <Disp Order="18" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="19" ItemType="19;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/6746.image_5F00_1F282B38.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/3010.image_5F00_thumb_5F00_179CBBCB.png" width=624 height=55></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="19" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="20" ItemType="20;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[For a DAG environment, identifying OAB generation server(s) is a two-2D;step process.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="20" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="21" ItemType="21;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Step1: Identify the mailbox database hosting organization mailbox with OAB Gen capability.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="21" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="22" ItemType="22;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Use the following command to list the arbitration mailboxes with persisted capability of OABGen and database on which this mailbox is hosted:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="22" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="23" ItemType="23;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Get-2D;Mailbox -2D;Arbitration | where {$_.PersistedCapabilities -2D;like "*oab*"} | ft name,database]]></Val>-D;-A; </Str>-D;-A; <Disp Order="23" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="24" ItemType="24;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/1854.image_5F00_5E19ABD3.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/8132.image_5F00_thumb_5F00_24969BDC.png" width=624 height=55></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="24" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="25" ItemType="25;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Step2: Identify the mailbox server where the database hosting organization mailbox is mounted]]></Val>-D;-A; </Str>-D;-A; <Disp Order="25" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="26" ItemType="26;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Use following command to identify active copy of mailbox database:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="26" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="27" ItemType="27;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Get-2D;MailboxDatabaseCopyStatus db1]]></Val>-D;-A; </Str>-D;-A; <Disp Order="27" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="28" ItemType="28;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/3010.image_5F00_0F38E674.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/3426.image_5F00_thumb_5F00_0ECCB37F.png" width=624 height=62></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="28" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="29" ItemType="29;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The server where database status is “mounted” is the current OAB generation server.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="29" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="30" ItemType="30;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Change the OAB generation server]]></Val>-D;-A; </Str>-D;-A; <Disp Order="30" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="31" ItemType="31;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[There are two methods of changing the OAB generation server.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="31" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="32" ItemType="32;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Move mailbox]]></Val>-D;-A; </Str>-D;-A; <Disp Order="32" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="33" ItemType="33;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Move the organization mailbox to a mailbox database on a server intended to be designated as OAB Generation server.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="33" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="34" ItemType="34;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Example:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="34" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="35" ItemType="35;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[DB1 is a single copy database present on the server Exch1 and hosts the organization mailbox. DB2 is mailbox database present on Exch2.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="35" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="36" ItemType="36;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The following command can be used to move the organization mailbox to DB2 and make Exch2 the OAB generation server.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="36" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="37" ItemType="37;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Get-2D;Mailbox -2D;Arbitration -2D;database db1| where {$_.PersistedCapabilities –like “*oab*”} | New-2D;MoveRequest -2D;TargetDatabase db2]]></Val>-D;-A; </Str>-D;-A; <Disp Order="37" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="38" ItemType="38;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This method is more suited for environments that have single copy of mailbox database hosting the Organization Mailbox.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="38" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="39" ItemType="39;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Activate the mailbox database on another server]]></Val>-D;-A; </Str>-D;-A; <Disp Order="39" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="40" ItemType="40;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This method is suited for environments that have multiple copies of the mailbox database hosting Organization Mailbox.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="40" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="41" ItemType="41;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Example:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="41" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="42" ItemType="42;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[DB1 hosts the Organization Mailbox and has copies on servers Exch1 and Exch2. DB1 is currently active on Exch1.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="42" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="43" ItemType="43;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The following command can be used to activate DB1 on Exch2 and therefore make it the OAB generation server:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="43" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="44" ItemType="44;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Move-2D;ActiveMailboxDatabase DB1 -2D;ActivateOnServer Exch2]]></Val>-D;-A; </Str>-D;-A; <Disp Order="44" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="45" ItemType="45;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Note: Review guidelines mentioned in “Placement of Organization Mailbox” below before changing the OAB Generation server.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="45" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="46" ItemType="46;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Creating a new Organization Mailbox]]></Val>-D;-A; </Str>-D;-A; <Disp Order="46" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="47" ItemType="47;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Administrators can create additional Organization Mailboxes for fault tolerance or for serving users in a geographically disbursed Exchange deployment.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="47" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="48" ItemType="48;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Creating a new Organization Mailbox is a two step process:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="48" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="49" ItemType="49;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Step1: Create a new arbitration mailbox]]></Val>-D;-A; </Str>-D;-A; <Disp Order="49" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="50" ItemType="50;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[New-2D;Mailbox -2D;Arbitration -2D;Name "OAB Seattle" -2D;Database DB2Seattle -2D;UserPrincipalName <A href="mailto:oabs@contoso.com">oabs@contoso.com</A> –DisplayName “OAB Mailbox for Seattle”]]></Val>-D;-A; </Str>-D;-A; <Disp Order="50" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="51" ItemType="51;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Step2: Enable OABGen capability]]></Val>-D;-A; </Str>-D;-A; <Disp Order="51" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="52" ItemType="52;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Set-2D;Mailbox -2D;Arbitration oabs -2D;OABGen $true]]></Val>-D;-A; </Str>-D;-A; <Disp Order="52" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="53" ItemType="53;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Note: Review guidelines mentioned in “Placement of Organization Mailbox” below before creating additional organization mailboxes.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="53" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="54" ItemType="54;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Changing the OAB Generation Schedule]]></Val>-D;-A; </Str>-D;-A; <Disp Order="54" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="55" ItemType="55;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The OAB Generation till Exchange Server 2010 was based on a “Schedule” set on OAB properties. You might see a “Schedule” defined when viewing properties of Exchange 2013 OAB. But, the Exchange Server 2013 OAB generation <STRONG><EM>does not</EM></STRONG> take place according to the “Schedule” defined on OAB properties:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="55" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="56" ItemType="56;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/5670.image_5F00_235202FD.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/6153.image_5F00_thumb_5F00_22E5D008.png" width=624 height=58></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="56" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="57" ItemType="57;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Instead, Exchange Server 2013 OAB Generation takes place according to OABGeneratorWorkCycle and OABGeneratorWorkCycleCheckpoint properties configured at the Mailbox Server.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="57" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="58" ItemType="58;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Example:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="58" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="59" ItemType="59;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/0218.image_5F00_22799D13.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/2450.image_5F00_thumb_5F00_4D520125.png" width=443 height=75></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="59" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="60" ItemType="60;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The values in the above screenshot mean OAB is generated once every day.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="60" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="61" ItemType="61;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Which Mailbox Server processed the OAB download request?]]></Val>-D;-A; </Str>-D;-A; <Disp Order="61" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="62" ItemType="62;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The Exchange Server 2013 CAS role proxies the OAB download request to an appropriate Mailbox role server. The CAS role maintains log of each request it handles in the log files, present in folder %ExchangeInstallPath%\Logging\HttpProxy\OAB\]]></Val>-D;-A; </Str>-D;-A; <Disp Order="62" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="63" ItemType="63;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[These log files are an excellent tool to identify which mailbox server the CAS chose to serve the request.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="63" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="64" ItemType="64;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Information of some important fields from the log file:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="64" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="65" ItemType="65;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The log file can be imported in Excel for better readability.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="65" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="66" ItemType="66;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Example:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="66" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="67" ItemType="67;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/3513.image_5F00_3B093A63.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/8625.image_5F00_thumb_5F00_3A9D076E.png" width=624 height=77></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="67" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="68" ItemType="68;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Forcing the OAB Generation]]></Val>-D;-A; </Str>-D;-A; <Disp Order="68" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="69" ItemType="69;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The Exchange Server 2013 OAB generation can be forced to start immediately by two methods.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="69" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="70" ItemType="70;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Method 1: Update-2D;OfflineAddresBook]]></Val>-D;-A; </Str>-D;-A; <Disp Order="70" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="71" ItemType="71;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Below command will force OAB generation of an OAB named "Default Offline Address Book" across all organization mailboxes.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="71" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="72" ItemType="72;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Update-2D;OfflineAddressBook "default offline address book"]]></Val>-D;-A; </Str>-D;-A; <Disp Order="72" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="73" ItemType="73;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Note: This command initiates an RPC request to each mailbox server hosting an active organization mailbox.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="73" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="74" ItemType="74;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Method 2: Restart the Mailbox Assistant service.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="74" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="75" ItemType="75;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The Microsoft Exchange Mailbox Assistant service on Mailbox Role is responsible for generating OAB. Restarting this service generates all OAB’s defined in the environment on a specific mailbox server, if it’s hosting an active organization mailbox.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="75" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="76" ItemType="76;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Placement of Organization Mailbox]]></Val>-D;-A; </Str>-D;-A; <Disp Order="76" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="77" ItemType="77;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Exchange Server 2013 CAS role proxies the OAB download request to a “nearest” mailbox server hosting an active Organization Mailbox. It can proxy the request in round robin fashion if it finds more than one organization mailbox active in same AD site. This might result in frequent full OAB download.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="77" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="78" ItemType="78;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Hence, current guidance is to plan organization mailbox placement such that you will have one organization mailbox active in an AD site. This applies to creating a new organization mailbox as well as to creating copies of mailbox database that hosts an organization mailbox.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="78" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="79" ItemType="79;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Scenarios]]></Val>-D;-A; </Str>-D;-A; <Disp Order="79" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="80" ItemType="80;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[The following scenarios discuss a real life situation to further explain the new OAB management methods.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="80" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="81" ItemType="81;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Scenario 1: Create a new Organization Mailbox]]></Val>-D;-A; </Str>-D;-A; <Disp Order="81" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="82" ItemType="82;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Contoso has Exchange Server 2013 Mailbox &amp; CAS role servers deployed at Dallas and Seattle sites. John, the Exchange Admin for Contoso, analyzes the http proxy log files on CAS servers and finds the OAB download request for Seattle users is going to Dallas servers. On further investigation, John finds he has just one Organization Mailbox present in Dallas, hence OAB download requests of all the users are going to Dallas server.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="82" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="83" ItemType="83;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[He decides to create a new Organization Mailbox at Seattle site with following commands:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="83" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="84" ItemType="84;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Step1: Create a new Arbitration Mailbox]]></Val>-D;-A; </Str>-D;-A; <Disp Order="84" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="85" ItemType="85;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[New-2D;Mailbox -2D;Arbitration -2D;Name "OAB Seattle" -2D;Database DB2Seattle -2D;UserPrincipalName <A href="mailto:oabs@contoso.com">oabs@contoso.com</A> –DisplayName “OAB Mailbox for Seattle”]]></Val>-D;-A; </Str>-D;-A; <Disp Order="85" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="86" ItemType="86;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Step2: Enable the Arbitration Mailbox with OABGen capability]]></Val>-D;-A; </Str>-D;-A; <Disp Order="86" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="87" ItemType="87;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Set-2D;Mailbox -2D;Arbitration oabs -2D;OABGen $true]]></Val>-D;-A; </Str>-D;-A; <Disp Order="87" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="88" ItemType="88;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Scenario 2: Customize OAB Generation Schedule]]></Val>-D;-A; </Str>-D;-A; <Disp Order="88" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="89" ItemType="89;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Ben is an administrator of Exchange 2013 deployment at Tail Spin Toys. The default OAB generation schedule does not suit them and they want to generate OAB approximately every fourth hour of the day.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="89" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="90" ItemType="90;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Ben will use following command to change properties of the mailbox servers that will be hosting the Organization Mailbox.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="90" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="91" ItemType="91;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Set-2D;MailboxServer Exch1 -2D;OABGeneratorWorkCycle 01.00:00:00 -2D;OABGeneratorWorkCycleCheckpoint 04:00:00]]></Val>-D;-A; </Str>-D;-A; <Disp Order="91" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="92" ItemType="92;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[After a couple of days, John analyzes Event ID 17002 in application log and makes sure the OAB is generated every four hours.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="92" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="93" ItemType="93;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<A href="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/7635.image_5F00_3A30D479.png"><IMG style="BACKGROUND-2D;IMAGE: none; BORDER-2D;RIGHT-2D;WIDTH: 0px; PADDING-2D;LEFT: 0px; PADDING-2D;RIGHT: 0px; DISPLAY: inline; BORDER-2D;TOP-2D;WIDTH: 0px; BORDER-2D;BOTTOM-2D;WIDTH: 0px; BORDER-2D;LEFT-2D;WIDTH: 0px; PADDING-2D;TOP: 0px" title=image border=0 alt=image src="http://blogs.technet.com/cfs-2D;file.ashx/__key/communityserver-2D;blogs-2D;components-2D;weblogfiles/00-2D;00-2D;00-2D;31-2D;06-2D;metablogapi/4174.image_5F00_thumb_5F00_6BBC420E.png" width=624 height=139></A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="93" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="94" ItemType="94;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Hopefully, you find this post useful! Let us know your feedback below!]]></Val>-D;-A; </Str>-D;-A; <Disp Order="94" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="95" ItemType="95;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author>Bhalchandra Atre</SPAN>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="95" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; <Item ItemId="96" ItemType="96;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-2D;oab-2D;in-2D;exchange-2D;server-2D;2013.aspx">Managing OAB in Exchange Server 2013</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="96" />-D;-A; <Modified By="system" DateTime="2013-2D;01-2D;23T06:06:56.0001282Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3549600" width="1" height="1">Los dispositivos iOS6 pasan a ser los propietarios de las reuniones por errorhttp://blogs.technet.com/b/exchange_sp/archive/2012/12/05/los-dispositivos-ios6-pasan-a-ser-los-propietarios-de-las-reuniones-por-error.aspxWed, 05 Dec 2012 10:03:03 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3538802OfficeLocalization0<p>Art&iacute;culo original publicado el mi&eacute;rcoles, 24 de octubre de 2012</p> <p>Una de las mejores ventajas de usar una de las implementaciones de Exchange m&aacute;s grandes del mundo es que los que trabajamos en Microsoft conocemos todas las situaciones a las que se enfrentan nuestros clientes en el d&iacute;a a d&iacute;a. Tras el reciente lanzamiento de iOS6, observamos un incremento acentuado de llamadas al departamento de soporte t&eacute;cnico porque el propietario de las reuniones cambia (lo que a veces se denomina &ldquo;secuestro de reuniones&rdquo;). En la mayor&iacute;a de los casos que se han notificado hasta la fecha, los usuarios ten&iacute;an delegados que primero abr&iacute;an una convocatoria de reuni&oacute;n en Outlook y luego actuaban en esa misma reuni&oacute;n en iOS.</p> <p>Los problemas relacionados con las reuniones constituyen una gran parte de los desaf&iacute;os a los que algunas organizaciones deben hacer frente al trabajar con dispositivos de otros fabricantes(<a title="Vea " href="http://support.microsoft.com/kb/2563324">esta</a> es nuestra lista). Por desgracia, la &uacute;ltima actualizaci&oacute;n de iOS ha empeorado uno de estos problemas. Quer&iacute;amos informarle del problema y comunicarle que ya hemos tratado este tema con Apple. Tambi&eacute;n estamos explorando diversas formas de reforzar la infraestructura de Exchange para proteger nuestros servidores y el servicio frente a los clientes de bajo rendimiento.</p> <p>Mientras tanto, le ofrecemos algunas opciones de mitigaci&oacute;n:</p> <ul class="arrowlist"> <li> <p><span class="bold">Decir a los usuarios que no hagan acciones en los calendarios en iOS</span>: este problema no se produce si los usuarios no realizan acciones en los elementos de calendario (como aceptar, eliminar o cambiar reuniones).</p> </li> <li> <p><span class="bold">Cambiar a los usuarios de iOS a <acronym title="Protocolo de oficina de correos v.3">POP3</acronym>/<acronym title="Protocolo de acceso a mensajes de Internet v.4">IMAP4</acronym></span>: otra opci&oacute;n es cambiar a los usuarios a conexiones POP/IMAP. As&iacute; se quitan las funciones del calendario y los contactos, pero los usuarios pueden seguir usando el correo (aunque es posible que este cambie de insertar a extraer al usar estos protocolos).</p> </li> <li> <p><span class="bold">Clientes de otros fabricantes/OWA</span>: mover a los usuarios a otro cliente de correo con el que no surja este problema puede ser una soluci&oacute;n temporal. Existen varias opciones de clientes (una de las cuales es OWA). Hay muchos clientes disponibles en las tiendas de aplicaciones m&oacute;viles. No recomendamos ninguno en particular.</p> </li> <li> <p><span class="bold">Bloquear a los delegados</span>: muchos de los problemas que estamos viendo est&aacute;n relacionados con los delegados. Un administrador puede usar la <a class="bold" title="Vea &ldquo;Controlar el acceso de los dispositivos a Exchange ActiveSync con la lista Permitir/Bloquear/En cuarentena&rdquo;" href="http://blogs.technet.com/b/exchange/archive/2010/11/15/3411539.aspx">lista Permitir/Bloquear/En cuarentena</a> para bloquear solo a los usuarios que sean delegados o a aquellos que tengan un delegado para minimizar el efecto del problema, lo cual es una medida menos dr&aacute;stica.</p> </li> <li> <p><span class="bold">Bloquear los dispositivos iOS 6</span>: el servidor Exchange viene con la <a class="bold" title="Vea " href="http://blogs.technet.com/b/exchange/archive/2010/11/15/3411539.aspx">funci&oacute;n Permitir/Bloquear/En cuarentena</a>, que permite a los administradores bloquear cualquier dispositivo o usuario.</p> </li> <li> <p><span class="bold">Decir a los usuarios que no actualicen a iOS 6 o que vuelvan a versiones anteriores</span>: esta soluci&oacute;n puede funcionar temporalmente hasta que Apple proporcione una revisi&oacute;n, pero es posible que muchos usuarios ya hayan decidido actualizar.</p> </li> <li> <p><span class="bold">Esperar</span>: no sabemos cu&aacute;ndo estar&aacute; lista la revisi&oacute;n de Apple, pero si es dentro de poco, puede que esta sea la mejor opci&oacute;n. P&oacute;ngase en contacto con Apple para informarse sobre posibles revisiones y su disponibilidad, y pedir que se la env&iacute;en.</p> </li> <li> <p>El equipo de soporte t&eacute;cnico tambi&eacute;n ha publicado un art&iacute;culo de Knowledge Base sobre este problema que puede leer <a title="Vea KB 2768774: La reuni&oacute;n le pierde la pista al organizador de la reuni&oacute;n en el calendario del asistente" href="http://support.microsoft.com/kb/2768774">aqu&iacute;</a>. Actualizaremos esta publicaci&oacute;n cuando la revisi&oacute;n est&eacute; disponible o cuando dispongamos de m&aacute;s informaci&oacute;n.</p> <p><span class="author"><a href="http://twitter.com/MobileGlick">Adam Glick</a></span><br />Administrador principal de productos t&eacute;cnicos</p> <img src="http://blogs.technet.com/aggbug.aspx?PostID=3528217" alt="" width="1" height="1" /> <p>Esta publicaci&oacute;n del blog es una traducci&oacute;n. Puede leer el art&iacute;culo original en <a href="http://blogs.technet.com/b/exchange/archive/2012/10/23/ios6-devices-erroneously-take-ownership-of-meetings.aspx">iOS6 devices erroneously take ownership of meetings</a></p> </li> </ul> <!--<?xml version="1.0" encoding="utf-2D;8"?>-D;-A;<LCX SchemaVersion="6.0" Name="iOS6-2D;devices-2D;erroneously-2D;take-2D;ownership-2D;of-2D;me.html" PsrId="22" SrcCul="en-2D;US" TgtCul="en-2D;US" xmlns="http://schemas.microsoft.com/locstudio/2006/6/lcx">-D;-A; <Item ItemId=";string" ItemType=";string" PsrId="22" Leaf="false">-D;-A; <Disp Icon="Str" Expand="true" LocTbl="false" />-D;-A; <Item ItemId="1" ItemType="1;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[iOS6 devices erroneously take ownership of meetings]]></Val>-D;-A; </Str>-D;-A; <Disp Order="1" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="2" ItemType="2;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Original article published on Wed, Oct 24 2012]]></Val>-D;-A; </Str>-D;-A; <Disp Order="2" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="3" ItemType="3;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[One of the great benefits to running one of the world’s largest Exchange deployments is that we at Microsoft get to see all the things that our customers face on a daily basis. With the recent release of iOS6, we have noticed a marked increase in support calls due to meetings having the owner of the meeting changed (sometimes called “meeting hijacking”). Most instances reported to us to date involve users with delegates who first open a meeting request in Outlook and then act on that same meeting in iOS. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="3" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="4" ItemType="4;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Meeting issues are a large part of the challenges that we know some organizations see with 3<SUP>rd</SUP> party devices (<A title="See 'Current issues with Microsoft Exchange ActiveSync and third-2D;party devices'" href="http://support.microsoft.com/kb/2563324">here</A> is our list). Unfortunately the recent iOS update has exacerbated one of these issues. We wanted to let you know about this issue as well as let you know that we have discussed this issue with Apple. We are also looking at ways that we can continue to harden the Exchange infrastructure to protect our servers and service from poorly performing clients.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="4" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="5" ItemType="5;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[In the meantime we wanted to offer a few mitigation options:]]></Val>-D;-A; </Str>-D;-A; <Disp Order="5" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="6" ItemType="6;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<P><SPAN class=bold>Tell users not to take action on calendars on iOS</SPAN> We're not seeing this particular issue if users don't take action on their calendar items (for example, accept, delete or change meetings).</P>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="6" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="7" ItemType="7;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=bold>Tell users not to take action on calendars on iOS</SPAN> We're not seeing this particular issue if users don't take action on their calendar items (for example, accept, delete or change meetings).]]></Val>-D;-A; </Str>-D;-A; <Disp Order="7" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="8" ItemType="8;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<P><SPAN class=bold>Switch iOS users to <ACRONYM title="Post Office Protocol -2D; Version 3">POP3</ACRONYM>/<ACRONYM title="Internet Message Access Protocol version 4">IMAP4</ACRONYM></SPAN> Another option is to switch users over to POP/IMAP connections. This will remove calendar and contacts functionality while allowing users to still use email (though the email may shift to pull from push while using these protocols). </P>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="8" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="9" ItemType="9;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=bold>Switch iOS users to <ACRONYM title="Post Office Protocol -2D; Version 3">POP3</ACRONYM>/<ACRONYM title="Internet Message Access Protocol version 4">IMAP4</ACRONYM></SPAN> Another option is to switch users over to POP/IMAP connections. This will remove calendar and contacts functionality while allowing users to still use email (though the email may shift to pull from push while using these protocols). ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="9" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="10" ItemType="10;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<P><SPAN class=bold>3<SUP>rd</SUP> party clients/OWA </SPAN>Moving impacted users over to another email client that is not causing these issue for your organization may help alleviate the pain here. There are a number of other client options (OWA being one of them of course). Numerous clients are available in mobile application stores. We don’t recommend any particular client.</P>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="10" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="11" ItemType="11;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=bold>3<SUP>rd</SUP> party clients/OWA </SPAN>Moving impacted users over to another email client that is not causing these issue for your organization may help alleviate the pain here. There are a number of other client options (OWA being one of them of course). Numerous clients are available in mobile application stores. We don’t recommend any particular client.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="11" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="12" ItemType="12;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<P><SPAN class=bold>Block delegates</SPAN> Many of the issues we are seeing involve delegates. An admin can take the less drastic step of using the <A class=bold title="See 'Controlling Exchange ActiveSync device access using the Allow/Block/Quarantine list'" href="http://blogs.technet.com/b/exchange/archive/2010/11/15/3411539.aspx">Allow/Block/Quarantine list</A> to block only users who are delegates, or have a delegate, to minimize the impact here.</P>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="12" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="13" ItemType="13;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=bold>Block delegates</SPAN> Many of the issues we are seeing involve delegates. An admin can take the less drastic step of using the <A class=bold title="See 'Controlling Exchange ActiveSync device access using the Allow/Block/Quarantine list'" href="http://blogs.technet.com/b/exchange/archive/2010/11/15/3411539.aspx">Allow/Block/Quarantine list</A> to block only users who are delegates, or have a delegate, to minimize the impact here.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="13" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="14" ItemType="14;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<P><SPAN class=bold>Block iOS 6 devices</SPAN> Exchange server comes with the <A class=bold title="See 'Controlling Exchange ActiveSync device access using the Allow/Block/Quarantine list'" href="http://blogs.technet.com/b/exchange/archive/2010/11/15/3411539.aspx">Allow/Block/Quarantine functionality</A> that enables admins to block any device or user. </P>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="14" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="15" ItemType="15;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=bold>Block iOS 6 devices</SPAN> Exchange server comes with the <A class=bold title="See 'Controlling Exchange ActiveSync device access using the Allow/Block/Quarantine list'" href="http://blogs.technet.com/b/exchange/archive/2010/11/15/3411539.aspx">Allow/Block/Quarantine functionality</A> that enables admins to block any device or user. ]]></Val>-D;-A; </Str>-D;-A; <Disp Order="15" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="16" ItemType="16;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<P><SPAN class=bold>Tell users not to upgrade to iOS 6 or to downgrade their devices – </SPAN>This solution may work as a temporary fix until Apple provides a fix but many users may have already made the decision to update.</P>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="16" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="17" ItemType="17;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=bold>Tell users not to upgrade to iOS 6 or to downgrade their devices – </SPAN>This solution may work as a temporary fix until Apple provides a fix but many users may have already made the decision to update.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="17" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="18" ItemType="18;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<P><SPAN class=bold>Wait</SPAN> We do not have any information on the timeline of a fix from Apple but if this timeline is short, this may be the easiest course of action. Please contact Apple about any potential fix or timeline for its delivery.</P>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="18" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="19" ItemType="19;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=bold>Wait</SPAN> We do not have any information on the timeline of a fix from Apple but if this timeline is short, this may be the easiest course of action. Please contact Apple about any potential fix or timeline for its delivery.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="19" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="20" ItemType="20;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<P>Our support team has also published a KB article on this issue that you can read <A title="See KB 2768774: &#13;&#10;Meeting in Attendee’s Calendar Loses Track of the Meeting Organizer" href="http://support.microsoft.com/kb/2768774">here</A>. And we will update this post when a fix is available or we have additional information.</P>]D;]A;<P><SPAN class=author><A href="http://twitter.com/MobileGlick">Adam Glick</A></SPAN><BR>Sr. Technical Product Manager</P>]D;]A;<DIV style="CLEAR: both"></DIV><IMG src="http://blogs.technet.com/aggbug.aspx?PostID=3528217" width=1 height=1>]D;]A;<P>This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2012/10/23/ios6-2D;devices-2D;erroneously-2D;take-2D;ownership-2D;of-2D;meetings.aspx">iOS6 devices erroneously take ownership of meetings</A></P>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="20" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="21" ItemType="21;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[Our support team has also published a KB article on this issue that you can read <A title="See KB 2768774: &#13;&#10;Meeting in Attendee’s Calendar Loses Track of the Meeting Organizer" href="http://support.microsoft.com/kb/2768774">here</A>. And we will update this post when a fix is available or we have additional information.]]></Val>-D;-A; </Str>-D;-A; <Disp Order="21" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="22" ItemType="22;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[<SPAN class=author><A href="http://twitter.com/MobileGlick">Adam Glick</A></SPAN><BR>Sr. Technical Product Manager]]></Val>-D;-A; </Str>-D;-A; <Disp Order="22" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; <Item ItemId="23" ItemType="23;html" PsrId="22" Leaf="true">-D;-A; <Str Cat="AppData">-D;-A; <Val><![CDATA[This is a localized blog post. Please find the original article at <A href="http://blogs.technet.com/b/exchange/archive/2012/10/23/ios6-2D;devices-2D;erroneously-2D;take-2D;ownership-2D;of-2D;meetings.aspx">iOS6 devices erroneously take ownership of meetings</A>]]></Val>-D;-A; </Str>-D;-A; <Disp Order="23" />-D;-A; <Modified By="system" DateTime="2012-2D;11-2D;08T09:25:43.0005917Z" />-D;-A; </Item>-D;-A; </Item>-D;-A;</LCX>--><div style="clear:both;"></div><img src="http://blogs.technet.com/aggbug.aspx?PostID=3538802" width="1" height="1">