Getting Started with Azure Government



Requerimientos de procesador y memoria RAM para Exchange Server 2007


Los requerimientos de procesador y memoria para un servidor Exchange Sever 2007, dependen en su mayoría de la cantidad de usuarios y de la cantidad de correos que envían y reciben diarios.

A continuación se muestran los requerimientos de procesador por tipo de rol de Exchange Server 2007:

  • Edge Transport
    • Minimo: Procesador de 1 core
    • Recomendado: Procesador de 2 cores
    • Máximo recomendado: Procesador de 4 cores
  • Hub Transport
    • Minimo: Procesador de 1 core
    • Recomendado: Procesador de 4 cores
    • Máximo recomendado: Procesador de 8 cores
  • Client Access
    • Minimo: Procesador de 1 core
    • Recomendado: Procesador de 4 cores
    • Máximo recomendado: Procesador de 4 cores
  • Unfied Messaging
    • Minimo: Procesador de 1 core
    • Recomendado: Procesador de 4 cores
    • Máximo recomendado: Procesador de 4 cores
  • Mailboxes
    • Minimo: Procesador de 1 core
    • Recomendado: Procesador de 4 cores
    • Máximo recomendado: Procesador de 8 cores
  • Multi-rol (Hub Transport, Client Access, Unified Messaging, Mailbox) 
    • Minimo: Procesador de 1 core
    • Recomendado: Procesador de 4 cores
    • Máximo recomendado: Procesador de 4 cores

Los procesadores soportados son:"

  • Procesadores de arquitectura x64 Intel que soportan Tecnología Intel Extended Memory 64 (EMT64)
  • Procesadores AMD que soportan la plataforma AMD64

NOTA: Los procesadores de la familia Itanium IA64 no son soportados.

 

A continuación se muestran los requerimientos de memoria RAM por tipo de rol de Exchange Server 2007:

  • Edge Transport
    • Minimo: 2GB/Servidor
    • Recomendado: 1GB/Core (2GB mínimo)
    • Máximo recomendado: 16GB/Servidor
  • Hub Transport
    • Minimo: 2GB/Servidor
    • Recomendado: 1GB/Core (2GB mínimo)
    • Máximo recomendado: 16GB/Servidor
  • Client Access
    • Minimo: 2GB/Servidor
    • Recomendado: 1GB/Core (2GB mínimo)
    • Máximo recomendado: 8GB/Servidor
  • Unfied Messaging
    • Minimo: 2GB/Servidor
    • Recomendado: 1GB/Core (2GB mínimo)
    • Máximo recomendado: 4GB/Servidor
  • Mailbox
    • Minimo: 2GB/Servidor
    • Recomendado: 2GB + 2MB a 5MB - Variable por perfíl de usuario*
    • Máximo recomendado: 32GB/Servidor

Perfil de Envío/Recepción diario Recomendación de

usuario (~50kb tamaño mensaje)             Memoria para el Mailbox

Liviano 5 enviados/20 recibidos 2GB + 2MB/buzón

Promedio 10 enviados/40 recibidos 2GB + 3.5MB/buzón

Pesado 20 enviados/80 recibidos 2GB + 5MB/buzón

 

  • Multi-rol (Hub Transport, Client Access, Unified Messaging, Mailbox) 
    • Minimo: 2GB/Servidor - Variable dependiendo de la cantidad de Grupos de Almacenamiento (Storage Groups)**
    • Recomendado: 4GB + 2MB a 5MB - Variable por perfíl de usuario*
    • Máximo recomendado: 8GB/Servidor

**Cantidad de Memoria Física

Storage Groups Mínima Requerida

1-4 2GB

5-8 4GB

9-12 6GB

13-16 8GB

17-20 10GB

21-24 12GB

25-28 14GB

29-32 16GB

33-36 18GB

37-40 20GB

41-44 22GB

45-48 24GB

49-50 26GB

 

Ejemplos para memoria:

Un servidor de Mailbox con 4000 usuarios de perfil pesado llegaría a 22GB de memoria RAM (2048MB + (4000*5MB))


SMART Room System Bandwidth Consumption


 

The SMART Room System for Microsoft Lync is SMART's solution for Microsoft's Lync Room System (https://blogs.technet.com/b/lync/archive/2013/02/19/the-lync-room-system-lrs.aspx). As any other Lync 2013 client, it consumes bandwidth that can be controlled, managed and administered by the Lync 2013 infrastructure.

Lync Room System is very similar to the regular Lync 2013 desktop client, except for the following caveats:

  • Audio Codec: G.722 stereo
  • Lync P2P video calls to/from LRS start in full screen mode on LRS screen (UI suppression), which kicks 720p or 1080p (default) from the very start of the meeting
  • Dual screen LRS might go for even higher resolutions since video tiles are distributed on both screens (gallery view). LRS could be receiving a real estate of 240p per Lync 2013 client being displayed.

Keeping in mind the guidance of Lync Media Traffic (https://technet.microsoft.com/en-us/library/jj688118.aspx) and Lync 2013 Networking Guide (https://blogs.technet.com/b/nexthop/archive/2013/06/04/lync-server-2013-networking-guide-network-planning-monitoring-and-troubleshooting-with-microsoft-lync-server.aspx) , we can estimate the approximate bandwidth usage of the SRS:

Media

Scenario

Codec

Typical bandwidth + RTCP

Audio

P2P, Conferencing

G.722 Stereo

73.1 kbps + 5 kbps

Video

1920x1080 (16:9)

H.264

3,200 kbps + 10 kbps

Now this is only taking into account audio and video feeds, but we also need to add content sharing or application sharing if it's being used (https://technet.microsoft.com/en-us/library/gg425781%28v=ocs.14%29.aspx):

Media

Typical

Application sharing using Remote Desktop Protocol (RDP)

434 kbps sent per sharer

Application Sharing Capacity Planning for Persistent Shared Object Model (PSOM) Applications

Sent per sharer: 713.57 kbps

Received per viewer: 552.92 kbps

Sample Typical Scenario of SRS presenting Whiteboard

Important note:

This is a sample scenario and depicts these specific assumptions:

  • All are Lync 2013 clients
  • 5 Lync 2013 clients in meeting, plus the SRS
  • All Lync 2013 desktop clients are sending typical H.264 1080p video (3,200 kbps) and G.722 (46.1 kbps) to the server
  • We won't take into account the bandwidth consumption upload and download of the Whiteboard at the beginning of the meeting, but only when the meeting has already started and participants are fully engaged.

image

These are sample values, your own scenarios will vary depending on how your Lync conferencing policies and Call Admission Control is set up, therefore you should consider the following to have a great meeting room experience:

  • Microsoft uses Quality of Experience for all Lync video/audio/web calls, therefore the bandwidth consumption in all calls is dynamic. (https://www.microsoft.com/en-us/download/details.aspx?id=6412). That means that a call that started consuming x kbps may consume less or more (adjusting dynamically) during the meeting without the end users knowing it's being adjusted. Lync client doesn't go below the minimum and doesn't go beyond the maximum thresholds depicted in the Networking Guide and Media Traffic guide (https://technet.microsoft.com/en-us/library/jj688118.aspx)
  • The only way to "control the dynamism" of Lync QoE is to establish conferencing policies and CAC (Call Admission Control) in Lync Server to audio and video, which would enable you to "cap" the max used for audio and video. Lync conferencing policies can be applied to any Lync client, including the LRS client. Note that Lync Conferencing Policies in Lync Server can be complemented with QoS policies as well.

Guidance and resources on how to do this can be found here:


Soporte para Exchange 2003 en Virtualización


Microsoft soporta solamente la virtualización de Exchange Server 2003 en Virtual Server 2005 RC2 o versiones posteriores solo si las siguientes condiciones se cumplen:

  • La versión de Exchange Server que está siendo ejecutada en la máquina virtual es Microsoft Exchange Server Service Pack 2 o posterior.
  • Los "Virtual Machine Additions" de Virtual Server 2005 RC2 se encuentran instalados en el sistema operativo virtualizado.
  • Exchange Server 2003 está configurado como un servidor "Stand-Alone", y no como parte de un cluster de Windows.
  • El driver SCSI que se encuentra instalado en el sistema operativo virtualizado es el Microsoft Virtual Machine PCI SCSI Controller.
  • La funcionalidad de "Virtual Hard Disk Undo" no se encuentra habilitada.

Para más información, se pueden conectar a ver el siguiente artículo:

320220 Support policy for Exchange Server 2003 running on hardware virtualization software
https://support.microsoft.com/default.aspx?scid=kb;EN-US;320220


TMG's moving out, I need a Reverse Proxy, what do I do?


Why do we need a Reverse Proxy for Lync? TechNet (https://technet.microsoft.com/en-us/library/gg398069.aspx) specifically mentions that the following features require external access through a reverse proxy:

  • Enabling external users to download meeting content for your meetings.
  • Enabling external users to expand distribution groups.
  • Enabling remote users to download files from the Address Book service.
  • Accessing the Lync Web App client.
  • Accessing the Dial-in Conferencing Settings webpage.
  • Accessing the Location Information service.
  • Enabling external devices to connect to Device Update web service and obtain updates.
  • Enabling mobile applications to automatically discover and use the mobility (Mcx) URLs from the Internet.
  • Enabling the Lync 2013 client, Lync Windows Store app and Lync 2013 Mobile client to locate the Lync Discover (autodiscover) URLs and use Unified Communications Web API (UCWA).

 

On Sept. 12, 2012, Microsoft announced changes to the roadmaps of several Forefront products, including the discontinuation of Forefront Threat Management Gateway (TMG) 2010.  Microsoft will continue to provide maintenance and support for Forefront Threat Management Gateway (TMG) 2010 through Dec.31, 2015. This announcement of course, has spanned off 3rd parties to step in, even Microsoft with a plain Windows 2008 R2 SP1 box to address the gap.

With this announcement, there are several changes that have been taken into consideration:

  • A "Reverse Proxy" section in the Infrastructure qualified for Microsoft Lync has been included. The following solutions are listed:
    • Internet Information Services Application Request Routing  (IIS ARR), more info here.
    • Even though becoming a dead end, Forefront Threat Management Gateway (TMG) 2010, more info here.
  • F5 has posted a solution, more info here.
  • Kemp has a solution, great article here.

To Wi-Fi or not to Wi-Fi


Recently I was with a coworker, helping him deliver a Lync 2013 workshop, and one of the major topics that comes around is whether Lync is ready for Wi-Fi use or not.

There are many considerations that come around if Wi-Fi should be used for real-time communications. I've always been very skeptical and haven't had a "seamless" experience unless I'm the only one using the access point.

Microsoft has taken the time to drill-down into extending customers certain guidelines such as deployment considerations, what issues affect Wi-Fi, among other subjects that can be addressed. The whitepaper can be downloaded from here, and you can find a summary of what it's about in the NextHop blog.

Also, Aruba has been recently certified for delivering a Wi-Fi solution for Microsoft UC. You can find more information here.


Vistazo General de Exchange 2010


He creado una presentación sobre los beneficios más directos que se obtienen de Exchange 2010. Beneificios como:

  • Protección
  • Archivación de correo
  • Acceso desde cualquier lado
  • Nuevo voice mail
  • Sobrecarga en el buzón
  • Disponibilidad

la cual pueden bajar desde Scribd, haciendo clic en la imagen siguiente:

 

image

 

Información acerca de proyectos de migración, me pueden contactar por el blog.

Para finalizar los invito a que visiten el sitio de la empresa para la cual laboro, Integration Technologies Corp., Voice Partner de Microsoft, haciendo clic en:

IntechEsCU


Activation Without .svc files – Config Based Activation (CBA)


.Svc files were perceived as a management overhead. In Net Framework 4.0, WCF  services hosted in WAS/IIS do not require .svc file anymore.

We can activates service through the  config Based Activation feature.

This feature allows for registration of services in web.config file. Here is a sample registration for two services in a single web.config file.

 <system.serviceModel>  
 <serviceHostingEnvironment>  
  <serviceActivations>  <add relativeAddress="CreditCheckService.svc" service="Microsoft.ServiceModel.Samples.CreditCheckService" />  <add relativeAddress="Payment/Service.svc" service="Microsoft.ServiceModel.Samples.PaymentCheckService" />  
 </serviceActivations>  
 </serviceHostingEnvironment>  
</system.serviceModel>  
  

 

 

Some details to remember about  config Based Activation feature

  1. serviceHostingEnvironment is an application level configuration. Please place the web.config containng the configuration under the root of the virtual Application.
  2. CBA supports activation over both http and non-http protocol
  3. CBA feature requires extensions in the relatativeAddress i.e. .svc, .xoml or .xamlx. You can map your own extensions to the know buildProviders which will then enable you to activate service over any extension.
  4. Upon confict, CBA overrides .svc registrations.
  5. serviceHostingEnvironment is a machinetoApplication inheritable section. If you register a single service in the root of the machine then every service in the application will inherit this service.