Andrés Lozada

The Last Post!

2010-12-15T13:56:00.000-03:00

This blog is no longer available and only kept alive to remember a lot of work and commitment with all of you.

Thanks

Andrés Lozada

andres.lozada@geeks.ms

Installing Exchange Server 2010 SP1

2010-09-20T20:24:00.000-03:00

Hi fellows, we find a lot of issues around the installation process of Exchange Server 2010 SP1

Before install the Exchange Server 2010 SP1, check this KB and Hot Fixes

Microsoft Office 2010 Filter Packs

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=5cd4dcd7-d3e6-4970-875e-aba93459fbee&displaylang=en

KB 977020-v2 - request
KB 977357 - request
KB 979099 - request No public
KB 979744 - request
KB 979917 - request
KB 981314 - request
KB 982867-v2 - request
KB 983440 - request

Regards

BPOS GUIDES

2010-09-15T22:58:00.000-03:00

Hi Fellows, my friend Oscar Maqueda publish this post with all content about PBOS

http://blogs.technet.com/b/oscarmh/

Category 1: Must read and keep on a USB key.

In other words, this is core content that you cannot be without. You will constantly refer back to it and it needs to be refreshed every month.

Service Descriptions and white papers:

The abosolute best resource is the Deployment Site . There will find a link to the holy grail of BPOS-S technical information related to migration: The BPOS Deployment Guide.

Useful detail can be found in a more summary form in the Service Descriptions:

· Exchange Online Standard

· SharePoint Online Standard

· Office Communications Online Standard

· Blackberry and Mobile Details

Category 2: Must read, subscribe and check when updated

· BPOS Team Blog
THE place you will get the latest info on new services, updates and content

· Microsoft Online Service Notifications RSS Feed
If there are problems with the service this is the official notification vehicle.

· Business Productivity Online Suite Onboarding and Discovery Checklist for Partners
Partner only resource that details pre-sales discovery detais.

Category 3: Online Training

Public

· “How do I” videos – quick and useful, but keep an eye on the dates. Services change regularly, webcasts don’t.

· Getting Your Directory and Mail Content Into Microsoft Online Services: An Overview

· Migration to BPOS

· Microsoft Online Services, the choice of businesses – BPOS or Google

· BPOS 101: Exploring Microsoft Online Services

· Using PowerShell with Microsoft Online Services

· Filtering and Archiving with Exchange Online

Partners:

Start here:

· BPOS Administration and Onboarding 1 day online training class:
BPOS end to end: Level 100-200

Then:

· Administering Exchange Online : 3 hours focus on Exchange Online and

· Administrating SharePoint Online: 3 hours focus on SharePoint Online

Then:

· Migration and Onboarding Deep Dive :
The Deployment Guide (above) should be used the most current reference. This deep dive is still solid though and contains detailed content on migration and pre-sales discovery. Level 200-400.

Then: See Depth Guidance references

Category 4: Online References

· FAQ – quick reference for international availability (at bottom) and other useful topics

· Microsoft Online Services TechCenter on Technet

· BPOS Documentation on Technet

· BPOS Online Help

· Securing Microsoft’s Cloud Infrastructure: How we do it. Useful info about what goes on tour data center(s). Includes more than BPOS.

· Security in Business Productivity Online Suite. Details on BPOS data center specifically.

Category 5: Depth Guidance

· Infrastructure Planning Guides – very good for walking through evaluating on-premise to online migrations.

o SharePoint Online

o Exchange Online

· Developers Guides: what you can and can’t do with web services and BPOS.

o Exchange Online

o SharePoint Online

· Partners: See the Partner Migration Toolkit :
This is a key resource that is not as well known as it should be.

Category 6: Tools

· Speed Testing paper
(Guidance for Microsoft Online Services Multinational Customers)

· Network connectivity analysis tool in North America (United States) data center

· Network connectivity analysis tool in Europe (Ireland) data center

· Network connectivity analysis tool in Asia-Pacific (Singapore) data center

· Microsoft Online Services Diagnostic and Logging Support

· Office Communicator for BPOS

· Microsoft Online Sign in Client

· Outlook 2003 Sign in Connector

· Mac Sign in Client

· Migration Tool – 32 bit: Regulalry updated with new powershell capabilities.

· Migration Tool – 64 bit: Regulalry updated with new powershell capabilities.

· Directory Synch

Microsoft Lync RC RELEASED

2010-09-13T18:32:00.000-03:00

Hi Fellows, today was released the new version of communications server , Microsoft Lync Beta is available to download just right now,

Download

http://technet.microsoft.com/en-us/evalcenter/ff808407.aspx

http://www.microsoft.com/en-us/lync/default.aspx

CodeCamp 2010

2010-08-30T11:14:00.000-03:00

Hola, los invito a participar en este evento el proximo sabado 4 de septiembre en la Universidad de Palermo, estaremos hablando de OCS 2010 y BPOS

Agenda

http://www.codecamp.com.ar/1agenda.aspx

Microsoft Exchange Server 2010 Service Pack 1 (SP1)

2010-08-26T00:35:00.001-03:00

Hi fellows, the service pack 1 for Exchange Server 2010 was release, you can download right now

http://www.microsoft.com/downloads/details.aspx?FamilyID=50b32685-4356-49cc-8b37-d9c9d4ea3f5b&displaylang=en

Overview

Microsoft Exchange Server 2010 helps IT Professionals achieve new levels of reliability with greater flexibility, enhanced user experiences, and increased protection for business communications.

Flexible and reliable - Exchange Server 2010 gives you the flexibility to tailor your deployment based on your company's unique needs and a simplified way to keep e-mail continuously available for your users.
Anywhere access - Exchange Server 2010 helps your users get more done by giving them the freedom to securely access all their communications - e-mail, voice mail, instant messaging, and more - from virtually any platform, Web browser, or device.
Protection and compliance - Exchange Server 2010 delivers integrated information loss prevention, and compliance tools aimed at helping you simplify the process of protecting your company's communications and meeting regulatory requirements.

Evento BPOS

2010-08-20T23:47:00.000-03:00

Hola , los invito a participar de este evento

Andrés Lozada y Alejandro Ponicke nos harán conocer la nueva suite de aplicaciones de mensajería y colaboración Online BPOS, descubriendo el potencial de Exchange Online, de SharePoint Online, de Office Live Meeting y de Office Communications Online dentro de su compañía.

El miércoles 25 de agosto a las 18.30 horas

Fen Hoteles - San Martín 920 CABA

Business Productivity Online Standard Suite DEMO

2010-07-19T09:08:00.000-03:00

Hi fellows, see this demo and get a trial version for BPOS

http://www.microsoft.com/online/demo/demo.aspx

Try

https://mocp.microsoftonline.com/site/services/bpos/signup.aspx?offer=suite&culture=en-US&WT.mc_id=TRY-BPOS_business-productivity_en-us

Exchange Server 2007 Service Pack 3 and now we have Windows Server 2008 R2 support!

2010-06-23T14:59:00.000-03:00

Ask and you shall receive - Exchange 2007 SP3 w/support for Windows Server 2008 R2 Now Available

I am very pleased to let you all know that Exchange Server 2007 SP3 is available for download. As we highlighted in Updates to the Exchange Supportability Matrix this past November, this third service pack for Exchange 2007 enables Exchange 2007 to be installed on the Windows Server 2008 R2 version of the operating system. We heard you loud and clear that this is enormously important to our Exchange 2007 customers, so we worked quickly to deliver SP3 in order to meet this requirement.

Download Exchange 2007 SP3 here.

Keep the feedback coming and for those of you evaluating all the good stuff packed into Exchange Server 2010, don't miss the beta of Exchange Server 2010 SP1. You can read about SP1 here.

Kevin Allison
GM- Exchange Customer Experience

http://msexchangeteam.com/archive/2010/06/21/455145.aspx

Maraton Migrando a OCS 2007 R2

2010-06-10T14:30:00.000-03:00

Hola,

Los invito a participar de esta nueva sesion de siete webcast con los pasos y procedimientos para una correcta migracion a OCS 2007 R2

Migrando a OCS 2007 R2 N°1

(Evaluando una migración y Coexistencia Exitosa) –

10 de Junio 4:00PM Bogotá

Registro:https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032452624&Culture=es-AR

Migrando a OCS 2007 R2 N°2

(Preparando la plataforma para una correcta instalaciÓn de OCS R2) –

15 de Junio 4:00PM Bogotá

Registro:https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032452627&Culture=es-AR

Migrando a OCS 2007 R2 N°3

(Instalando OCS R2)

17 de Junio 4:00PM Bogotá

Registro:https://msevents.microsoft.com/CUI/EventDetail.aspx?EventID=1032452629&Culture=es-AR

Migrando a OCS 2007 R2 N°4

Migrando a OCS 2007 R2 4 (Instalando OCS R2 Extendido)

22 de junio de 2010 04:00 p.m. Bogotá

Registro:https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452631&EventCategory=4&culture=es-AR&CountryCode=AR

Migrando a OCS 2007 R2 N°5

(Configurando OCS R2)

24 de junio de 2010 04:00 p.m. Bogotá

Registro:https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452633&EventCategory=4&culture=es-AR&CountryCode=AR

Migrando a OCS 2007 R2 N°6

(Migrando usuarios y depurando LCS/ OCS)

29 de junio de 2010 04:00 p.m. Bogotá

Registro:https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452635&EventCategory=4&culture=es-AR&CountryCode=AR

Migrando a OCS 2007 R2 N°7

(Monitoreando Office Communication Server 2007 R2)

29 de junio de 2010 05:00 p.m. Bogotá

Registro:https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452693&EventCategory=4&culture=es-AR&CountryCode=AR

Microsoft Exchange Server 2010 SP1 Beta

2010-06-05T23:24:00.000-03:00

http://www.microsoft.com/downloads/details.aspx?FamilyID=a0965fc9-2723-4947-ae6b-74bc3808e72a&displaylang=en#Overview

Brief Description

Microsoft Exchange Server 2010 helps you achieve new levels of reliability and performance by delivering features that help to simplify your administration, protect your communications, and delight your customers by meeting their demands for greater business mobility.

Overview

Microsoft Exchange Server 2010 helps IT Professionals achieve new levels of reliability with greater flexibility, enhanced user experiences, and increased protection for business communications.

Flexible and reliable - Exchange Server 2010 gives you the flexibility to tailor your deployment based on your company's unique needs and a simplified way to keep e-mail continuously available for your users.
Anywhere access - Exchange Server 2010 helps your users get more done by giving them the freedom to securely access all their communications - e-mail, voice mail, instant messaging, and more - from virtually any platform, Web browser, or device.
Protection and compliance - Exchange Server 2010 delivers integrated information loss prevention, and compliance tools aimed at helping you simplify the process of protecting your company's communications and meeting regulatory requirements.

This pre-release software is intended for evaluation purposes only. You must accept the license terms before you are authorized to use the software. There is no product support for this trial software. You are welcome to participate in the forums to share your trial experiences with others and to ask for advice.

BYE-BYE Exchange Server 2003 Webcast

2010-05-08T11:57:00.000-03:00

Hola,

Los invito a esta serie de 7 Webcast en español con todos los pasos y procedimientos para una migracion exitosa a Exchange Server 2010

Mayo Jueves 13

Webcast TechNet: BYE BYE Exchange 2003 N°1 (Entendiendo los pasos para una Migración y Coexistencia Exitosa)

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032450220&EventCategory=4&culture=es-AR&CountryCode=AR

Mayo Martes 18

Webcast TechNet: BYE BYE Exchange 2003 N°2 (Preparando Directorio Activo)

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452061&EventCategory=4&culture=es-AR&CountryCode=AR

Mayo Jueves 20

Webcast TechNet: BYE BYE Exchange 2003 N°3 (Instalando Exchange Server 2010 Consolidado)

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452079&EventCategory=4&culture=es-AR&CountryCode=AR

Mayo Martes 25

Webcast TechNet: BYE BYE Exchange 2003 N°4 (Instalando Exchange Server 2010 Extendido)

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452590&EventCategory=4&culture=es-AR&CountryCode=AR

Mayo Jueves 27

Webcast TechNet: BYE BYE Exchange 2003 N°5 (Configurando Exchange Server 2010)

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452605&EventCategory=4&culture=es-AR&CountryCode=AR

Junio Martes 1

Webcast TechNet: BYE BYE Exchange 2003 N°6 (Migrando Buzones)

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452612&EventCategory=4&culture=es-AR&CountryCode=AR

Junio Jueves 3

Webcast TechNet: BYE BYE Exchange 2003 N°7 (Eliminando Exchange 2003)

https://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032452615&EventCategory=4&culture=es-AR&CountryCode=AR

LAB: Deploying and Configuring Microsoft Office Communications Server 2007 R2 Enterprise Edition

2010-04-17T11:44:00.000-03:00

Hi, check this cool lab to deploy OCS R2

Deploying and Configuring Microsoft Office Communications Server 2007 R2 Enterprise Edition

Objectives
After completing this lab, you will be better able to:

Prepare the Microsoft® Active Directory® domain services for Microsoft Office Communications Server (OCS) 2007 R2.
Create necessary Office Communications Server 2007 R2 Domain Name System (DNS) records.
Create and configure an Office Communications Server 2007 R2 Enterprise Edition pool.
Install Office Communications Server 2007 R2 and configure certificates.
Start the Office Communications Server 2007 services.
Install the Office Communications Server 2007 R2 administrative tools.
Enable and configure users and configure Live Meeting policy.

Scenario
You are the administrator for Litware, a small but growing retailer of outdoor clothing. You plan to implement Office Communications Server 2007 R2 to take advantage of its improved security features, its enhanced end-user experience, and its powerful and easier-to-use administration tools. Before you deploy Office Communications Server 2007 R2, you must first prepare the Active Directory. After that, you will install and configure an Enterprise Edition pool, install the Office Communications Server 2007 R2 Front End server and then enable and configure users. The instructions in this guide are specific to a deployment of an Enterprise Edition Server in a single forest with a single domain (LitwareInc.com).

Estimated time to complete: 90 min

Supportability is available for Office Communications Server 2007 R2 member server role on a Windows Server 2008 R2 operating system

2010-04-03T02:29:00.000-03:00

Hi Everyone , We were waiting for this fix for a long time, OCS R2 Supported on Windows Server 2008 R2

http://support.microsoft.com/kb/982021/en-us

Take the following steps to install Office Communications Server 2007 R2 on a server that is running a Windows Server 2008 R2 operating system:

Install.NET Framework 3.5.1 by using Roles wizard from Server Manager. You can do this by selecting the Windows-based application server role to make sure completeness. This is a manual step. You must have .NET Framework 3.5 SP1 on a Windows Server 2008 R2 operating system before you install a version of Office Communications Server 2007 R2 that only includes .NET Framework 3.5.
Install the Desktop Experience Features by using Add Features wizard from Server Manager. This is required for Media format runtime. The name of the media format runtime package depends on the operating system and the Office Communications Server 2007 R2 setup that refers to the Windows Server 2008 or to the Windows Server 2003 Media format runtime installation package.
Install the Hotfix that is described in KB 975858 for Windows Server 2008 R2.
975858 (http://support.microsoft.com/kb/975858/ ) An application or service that calls the InitializeSecurityContext function together with the ISC_REQ_EXTENDED_ERROR flag may encounter a TLS/SSL negotiation failure on a computer that is running Windows Server 2008 R2 or Windows 7 operating system
Install Office Communications Server 2007 R2 Server Roles
For Office Communications Server 2007 R2, Standard Edition, or Enterprise Edition, or Edge Server role, when KB 974571 is installed, Activation of the Office Communications Server 2007 R2 server role fails. To fix this problem, follow these steps:
1. Apply the OCSASNFix.exe file. To download the Ocsasnfix.exe file, visit the following Microsoft Web site:
  Install the OCSASNFix.exe file (http://go.microsoft.com/fwlink/?LinkId=168248)
2. Rerun Office Communications Server 2007 R2 Activation
Note This is not specific to Windows Server 2008 R2 operating system. For more information, visit the following Microsoft Web site:
Learn more about the vulnerabilities in CryptoAPI (http://support.microsoft.com/?kbid=974571)
Install updates for Office Communications Server 2007 R2 that are dated October 2009 (3.5.6907.56), or install later versions. To download the updates for Office Communications Server 2007 R2, visit the following Microsoft Web site:
Microsoft Office Communications Server 2007 R2 Hotfix KB 968802 (http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=b3b02475-150c-41fa-844a-c10a517040f4)

For more information about how to install the Office Communications Server 2007 R2 updates, click the following article number to view the article in the Microsoft Knowledge Base:

968802 (http://support.microsoft.com/kb/968802/ ) Updates for Communications Server 2007 R2
The default security setting on Windows Server 2008 R2 operating system for NTLM SSP requires 128-bit encryption. Depending on the client operating system mix in the enterprise, you may have to reduce this setting on a Windows Server 2008 R2 operating system that is running Office Communications Server 2007 R2 as a down level operating system. The key is set to "No requirement."
1. For any down level operating system, such as Windows XP or for Windows Vista, the default value is set to "No Minimum."
2. For a Windows 7 operating system, the default value is set to "Requires 128-bit encryption."

For more information about the “Changes in NTLM Authentication” as it applies to Windows 2008 R2 and Windows 7 operating systems, please visit the following Microsoft Web site:

Learn more about the changes in NTLM Authentication (http://technet.microsoft.com/pl-pl/library/dd566199(WS.10).aspx)

If you want to change the NTLM setting, follow these steps:

Start secpol.msc on a Windows Server 2008 R2 operating system server.
Click to select Local Policies and then click Security Options node.
Make sure that the following values of the policies are set to "No Minimum."
- Network Security: Minimum session security for NTLM SSP based (including secure RPC)
- Network Security: Minimum session security for NTLM SSP based (including secure RPC) servers

For more information about the operating systems that are currently supported for Office Communications Server 2007 R2, visit the following Microsoft Web site:

Learn more about Internal Office Communications Server Component requirements (http://technet.microsoft.com/en-us/library/dd425098(office.13).aspx)

For more information about Office Communications 2007 R2 running in Windows 2008 R2 Domain and Forest, click the following article number to view the article in the Microsoft Knowledge Base:

982020 (http://support.microsoft.com/kb/982020/ ) Office Communications Server 2007 R2, Office Communications Server 2007 or Live Communications Server 2005 does not work correctly after you upgrade a domain controller to Windows Server 2008 R2 operating system

Webcast Abril

2010-03-18T23:30:00.001-03:00

Hola,

Los invito a participar en estos tres webcast que estare dando durante el mes de abril

Webcast TechNet: Exchange 2010 en dispositivos móviles

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032443809&EventCategory=4&culture=es-AR&CountryCode=AR

Webcast TechNet: Usando Windows Mobile y la nueva productividad

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032443811&EventCategory=4&culture=es-AR&CountryCode=AR

Webcast TechNet: Implementación y configuración de Office Communications Server 2007 R2 Enterprise Edition

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032440993&EventCategory=4&culture=es-AR&CountryCode=AR

Update Rollup 2 for Exchange Server 2010 (KB979611)

2010-02-28T14:30:00.000-03:00

Update Rollup 2 for Exchange Server 2010 (KB979611)

http://www.microsoft.com/downloads/details.aspx?FamilyID=6d3ae3e0-3982-46d6-9e9c-7d7d63fae565&displaylang=en

Description of Update Rollup 2 for Exchange Server 2010

http://support.microsoft.com/kb/979611/en-us

Issues that the update rollup fixes

Update Rollup 2 for Exchange Server 2010 fixes the issues that are described in the following Microsoft Knowledge Base (KB) articles:

977633 (http://support.microsoft.com/kb/977633/ ) Certain third-party IMAP4 clients cannot connect to Exchange Server 2003 mailboxes through an Exchange Server 2010 CAS server

979431 (http://support.microsoft.com/kb/979431/ ) The POP3 service crashes when a user connects to a mailbox through the POP3 protocol and the user is migrated from an Exchange Server 2003 server to an Exchange Server 2010 server

979480 (http://support.microsoft.com/kb/979480/ ) Users cannot receive new messages if they access mailboxes that are moved to another Exchange Server 2010 RU1 server by using IMAP4 clients

979563 (http://support.microsoft.com/kb/979563/ ) Exchange Server 2010 Push Notifications does not work

979566 (http://support.microsoft.com/kb/979566/ ) A 0x85010014 error is generated when linked mailbox users try to synchronize their mailboxes with mobile devices in a CAS-CAS proxying scenario in Exchange Server 2010

980261 (http://support.microsoft.com/kb/980261/ ) This fix introduces the supports for Exchange Server 2010 page patching when a "-1022" disk I/O error is generated

980262 (http://support.microsoft.com/kb/980262/ ) Event ID 2156 is logged on a computer that is running Exchange Server 2010

AudioCodes MediaPack 1xx Video Datasheet

2010-02-25T21:02:00.000-03:00

hi everyone, searching, i found this two videos for AudioCodes MediaPack and Mediant

MediaPack 1xx

MediaPacks are well suited for commercial VoIP deployment because of their mature and field-proven voice and fax technology. Their rich feature set allows integration with a wide range of Carriers and Enterprise network applications. MediaPack gateways are used by Carriers and Service Providers in Access networks for connecting Multi-Tenant Units (MTU), IP Centrex subscribers, payphones and rural users over various wireless and satellite links. Enterprises use MediaPack gateways to connect their legacy PBX systems over an IP infrastructure. In addition, in IP Centrex and central IP-PBX applications, the MediaPack increases the remote
location availability and provides Stand Alone Survivability (SAS) when there is no IP connection between branch locations and the central SIP servers, SIP Proxy or central IP-PBX.

Deliver Feature-rich Solutions
MediaPacks are third generation products that have been designed to meet real market needs. In addition to superior voice technology, the products provide advanced telephony features such as long-haul, metering tones generation, country dependent MWI and CID for true integration
with the existing telephony infrastructure. A variety of management and provisioning tools, such as AudioCodes’ EMS, embedded web server, Telnet and SNMP enable fast deployment and management of large and complex networks. MediaPacks are based on VolPerfect™ architecture, AudioCodes underlying, best-of-breed, core media gateway technology for all of its
products.

Provide Interoperability
MediaPacks are part of AudioCodes’ complete family of stand-alone VoIP Gateways for OEM system integration. Throughout the years, AudioCodes has invested significant effort in complying with the leading and evolving VoIP standards. Support of multiple VoIP control protocols has been tested with leading Softswitch vendors. As a provider for OEMs, System Integrators and Network Equipment Providers, AudioCodes offers short time-to-market
with field-proven products.

Benefit From Extensive Experience
AudioCodes, established in 1993, is one of the world’s leading providers of VoIP technology. AudioCodes’ commitment to innovation yields consistently high-quality voice processing products that are feature-rich and field-proven. AudioCodes has deployed tens of millions of VoP ports
in over 100 countries to date.

MediaPack Series Features

Spans a range of 2 to 24 analog ports
Supports PSTN/PBX analog telephone sets or analog trunk lines (FXS/FXO)
Selectable, multiple LBR coders per channel
T.38 compliant
Rich subscriber Feature Set including: 3-Way conference with local mixing, call pickup, hunt groups, call forwarding, call hold and call transfer
Echo cancellation, Jitter Buffer, VAD and CNG
Complies with MGCP, H.323 (V4) and SIP control protocols
Enhanced capabilities which include MWI, long-haul, Metering Tones, STUN, Security features, Generation, CID and outdoor protection
Stand Alone Survivability (SAS) for SIP based IP Centrex and Central IP-PBX applications
Web Management for easy configuration and installation
EMS for comprehensive management operations (FCAPS)
Automatic provisioning via TFTP/HTTP
Internal Access List firewall for network traffic filtering

Mediant 2000 for Microsoft UC

AudioCodes Products

Mediant 2000 for Microsoft UC

The Mediant 2000 is AudioCodes’ digital enterprise class VoIP media gateway. Intelligently packaged in a stackable 1U chassis, it is designed to interface between legacy PBXs and/or the PSTN, and Microsoft Unified Communications solutions, including Microsoft Exchange Server 2007 and Microsoft Office Communications Server 2007. Incorporating AudioCodes’ innovative Voice over Packet technology, the Mediant 2000 enables high quality, reliable and cost-effective deployment of voice-enabled Unified Communications networks, supporting "Basic Gateway" as well as "Basic Hybrid" gateway configurations.

FOR TECHNICAL RESOURCES AND DOWNLOADS OF MICROSOFT MATERIAL PLEASE CLICK THE DOWNLOADS TAB IN THIS PAGE

AudioCodes has collaborated with Microsoft to provide enterprises with a smooth migration from the world of separated telephony and IT environments, to the world of Unified Communications.

AudioCodes offers the enterprise customer a key component in the unified telephony network – the Media Gateway - which connects the existing legacy telephony PBX with Microsoft Exchange Server 2007 & Microsoft Office Communications Server 2007.

AudioCodes Mediant 2000 Media Gateway is a cost-effective VoIP media gateways utilizing cutting edge technology. Intelligently packaged in a stackable 1U chassis it is designed to interface between Enterprise legacy telephony & IP networks.

Scale Up As Your Business Grows

The AudioCodes Mediant 2000 Media Gateway supports different configurations, enabling the connection of the Microsoft Unified Communications solution to different models of PBXs using E1/T1/J1 interfaces. The compact Mediant 2000 VoIP Gateway scales from 1 to 16 E1/T1/J1 spans in a 1U chassis.

In addition, the AudioCodes Mediant 2000 Media Gateway can be ordered as a “Basic Hybrid Gateway”, supporting an integrated Microsoft Mediation Server, running up to 120 simultaneous RTA channels and up to 480 regular VoIP channels.

Support of Microsoft Exchange Server 2007 & Microsoft Office Communications Server 2007

The Mediant 2000 Media Gateway can support the connection to legacy PBXs and PSTN, both for Exchange Server 2007 Unified Messaging deployments and Office Communications Server 2007 deployments. Enterprises can smoothly migrate from isolated telephony and IT environments, and connect their legacy PBXs to the Microsoft Exchange Server 2007 as well as to the Microsoft Office Communications Server 2007, allowing full implementations of Unified Messaging and Unified Communications in the enterprise.

Ultimately, the organization can migrate to a pure-IP environment, using the Office Communications Server 2007 as the communications platform, connecting to the PSTN via the AudioCodes Mediant 2000 Media Gateway.

3rd Party Application Platform

The Mediant 2000 extends the flexibility of the Media Gateway family with additional deployment options. Using an integrated cPCI slot, the Mediant 2000 offers partners the option to host their own applications (e.g., IP-PBX, call center, conferencing and messaging applications), including a powerful processor and hard disks to provide a complete solution within the Mediant 2000 chassis along with rich SIP gateway features. In the case of the Microsoft "Basic Hybrid Gateway" configuration, the cPCI hosts a powerful Intel-based server, which runs the Microsoft Mediation Server software, supporting up to 120 simultaneous RTA sessions.

Exchange 2010 Mailbox Server Role Requirements Calculator Updated to Version 3.2

2010-01-23T04:28:00.000-03:00

Hi , the Exchange product team release the new update for Exchange 2010 Mailbox Server Role Requirements Calculator

http://msexchangeteam.com/archive/2010/01/22/453859.aspx

For the explanation of different tabs and how the calculator works, go here. Yup, we updated that too!

to get the new calculator - go here.

Update Rollup 2 for Exchange Server 2007 Service Pack 2 (KB972076)

2010-01-22T16:16:00.000-03:00

Overview

Update Rollup 2 for Exchange Server 2007 Service Pack 2 (SP2) resolves issues that were found in Exchange Server 2007 SP2 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP2 customers.
For a list of changes that are included in this update rollup, see KB972076.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM) or Exchange Server 2007 Service Pack 1 (SP1). For a list of update rollups applicable to Exchange Server 2007 RTM or Exchange Server 2007 SP1, refer to the Knowledge Base article KB937052.
This is a cumulative update rollup and replaces the following:

KB971534 Update Rollup 1 for Exchange Server 2007 Service Pack 2 (KB971534)

Download

http://www.microsoft.com/downloads/details.aspx?FamilyID=fa83be11-9d5e-47bc-9a51-a10986f22928&displaylang=en

Description of Update Rollup 2 for Microsoft Exchange Server 2007 Service Pack 2

http://support.microsoft.com/?kbid=972076

Issues that the update rollup fixes
Update Rollup 2 for Exchange Server 2007 SP2 fixes the issues that are described in the following Microsoft Knowledge Base articles:

961525 (http://support.microsoft.com/kb/961525/ ) Exchange Server 2003 may generate duplicate journal reports in a mixed Exchange Server 2003 and Exchange Server 2007 environment

969230 (http://support.microsoft.com/kb/969230/ ) The "age limits" function of a public folder do not work as expected in an Exchange Server 2007 environment

969948 (http://support.microsoft.com/kb/969948/ ) A Computer that is running Microsoft Exchange Server 2007 that has the Client Access Server (CAS) role installed becomes slow when a user tries to open a folder that contains many items

970817 (http://support.microsoft.com/kb/970817/ ) An appointment is displayed incorrectly as an all-day event if you use a mobile device to synchronize the calendar in Exchange Server 2007

971177 (http://support.microsoft.com/kb/971177/ ) The Auto Attendant 'Business Hours' schedule is not updated in Exchange Server 2007 when the DST setting is changed

971349 (http://support.microsoft.com/kb/971349/ ) Exchange Server 2007 users intermittently cannot access an Exchange Server 2003 user's Free/Busy information in Office Outlook 2007

971889 (http://support.microsoft.com/kb/971889/ ) When Unified Messaging-enabled users call Outlook Voice Access on Exchange Server 2007 to play voice mails messages, there is a delay before the voice mail message is played

972705 (http://support.microsoft.com/kb/972705/ ) The Microsoft Exchange Server 2007 log or database experiences abnormal growth

972744 (http://support.microsoft.com/kb/972744/ ) When a user sends e-mail messages to a remote domain, some e-mail messages are queued on an Exchange Server 2007 Hub Transport server or Edge server

973165 (http://support.microsoft.com/kb/973165/ ) A return address is split into two separate and incomplete addresses when a recipient replies to a specific message in Exchange 2007

973486 (http://support.microsoft.com/kb/973486/ ) Some message parts are not readable when Exchange Server 2007 must convert the message part encoding from binary or from 8 bit to 7 bit

973969 (http://support.microsoft.com/kb/973969/ ) Incorrect exceptions are generated for a recurring iCalendar message when an Exchange Server 2007 server processes an SMTP message that contains the iCalendar message part

974155 (http://support.microsoft.com/kb/974155/ ) OWA does not highlight misspelled words in an Exchange Server 2007 CAS proxy environment

974161 (http://support.microsoft.com/kb/974161/ ) Some attendees cannot receive a meeting cancellation notification when the appointment recurrence pattern is changed by using EWS in Exchange Server 2007

974312 (http://support.microsoft.com/kb/974312/ ) Unread messages are marked as "read" when Exchange Server 2007 processes the EXAMINE command

974344 (http://support.microsoft.com/kb/974344/ ) You still receive an error message when you run the Test-OwaConnectivity command after you apply hotfix KB957485 in Exchange Server 2007

974401 (http://support.microsoft.com/kb/974401/ ) Store sessions are not released when you run the Add-PublicFolderClientPermission cmdlet or the Remove-PublicFolderClientPermission cmdlet in public folders on a computer that is running Exchange Server 2007

974450 (http://support.microsoft.com/kb/974450/ ) A new accepted domain that is added does not work in an Exchange Server 2007 organization

974679 (http://support.microsoft.com/kb/974679/ ) Returned folder names include a question mark when you check the folder names of an Exchange Server 2007 mailbox

974775 (http://support.microsoft.com/kb/974775/ ) The EdgeTransport.exe process crashes intermittently on an Exchange Server 2007 server

974843 (http://support.microsoft.com/kb/974843/ ) Exchange Server 2007 performance counter "Messages queued for submission" shows incorrect value

974897 (http://support.microsoft.com/kb/974897/ ) You receive an NDR you try to send messages through your Microsoft Exchange Server 2007 account

974946 (http://support.microsoft.com/kb/974946/ ) Exchange Server 2007 OWA users receive an error message when the users change the display line for the search results on the address books

974999 (http://support.microsoft.com/kb/974999/ ) The "Task Owner" field is not set when you create a task in Outlook Web Access

975050 (http://support.microsoft.com/kb/975050/ ) A call transfer fails by using key mapping in a mixed Exchange Server 2007 UM server and OCS 2007 environment

975165 (http://support.microsoft.com/kb/975165/ ) EWS proxying requests fail after you run Availability Service requests in a CAS to CAS proxying scenario in Exchange Server 2007

975213 (http://support.microsoft.com/kb/975213/ ) You cannot log on to your mailbox and you receive an error in an Exchange server 2003 and Exchange Server 2007 coexist environment

975255 (http://support.microsoft.com/kb/975255/ ) Event 2104 and event 2147 are continuously logged in an Exchange Server 2007 Cluster Continuous Replication (CCR) environment

975404 (http://support.microsoft.com/kb/975404/ ) An attachment of a meeting request cannot be opened when you use a CDO application to accept a meeting request in Exchange Server 2007

975844 (http://support.microsoft.com/kb/975844/ ) The misspelled word of a message loses its custom format when an Exchange Server 2007 user writes the message in OWA

975903 (http://support.microsoft.com/kb/975903/ ) The RemoveDelegate operation of EWS fails, and then a "500 internal server" error response and event ID 4999 are logged in an Exchange Server 2007 server

975916 (http://support.microsoft.com/kb/975916/ ) The custom form of a meeting request is removed in the recipients' calendar in an Exchange Server 2007 environment

975918 (http://support.microsoft.com/kb/975918/ ) When an IMAP4 client sends a FETCH (bodystructure) request to a server that is running the Exchange Server 2007 IMAP4 service, a corrupted response is sent as a reply

975946 (http://support.microsoft.com/kb/975946/ ) An S/MIME message is not verified and is rejected when BizTalk Server 2006 uses the Exchange Server 2007 version of ExSMime.dll to parse MIME messages

975990 (http://support.microsoft.com/kb/975990/ ) Messages that have duplicate message IDs are deleted when they are archived to an Exchange 2007 mailbox

976025 (http://support.microsoft.com/kb/976025/ ) The free/busy information of an Exchange Server 2007 user is not displayed

976106 (http://support.microsoft.com/kb/976106/ ) Microsoft Exchange Transport services crashes with StackOverflowException when Message Journaling is enabled on Exchange Server 2007

976107 (http://support.microsoft.com/kb/976107/ ) You receive the warning "Failed to update recipient" when you run the Update-addresslist cmdlet in Exchange Management Shell on Exchange Server 2007

976137 (http://support.microsoft.com/kb/976137/ ) Exchange Server 2007 Unified Messaging incorrectly plays a nonbusiness hours greeting when someone call during holiday

976195 (http://support.microsoft.com/kb/976195/ ) You cannot edit a transport rule if one or more of the recipient addresses are disabled or removed in an Exchange Server 2007 server

976653 (http://support.microsoft.com/kb/976653/ ) The Cluster Administrator shows that the mount operation fails and error 1003 is logged even though the database is mounted in an Exchange Server 2007 CCR or in a SCC environment

976787 (http://support.microsoft.com/kb/976787/ ) The Calendar Month View displays a numeric date and not an abbreviated month name when you set the Regional Settings to Japanese or to Korean in Outlook Web Access for Exchange Server 2007

976794 (http://support.microsoft.com/kb/976794/ ) When you edit an e-mail message in OWA, the font changes to the default Internet Explorer font

976946 (http://support.microsoft.com/kb/976946/ ) The message delivery time is incorrect when you send e-mail messages by using an IMAP4 client together with the APPEND command in Exchange Server 2007

977085 (http://support.microsoft.com/kb/977085/ ) An incorrect value for DumpsterMessagesDeleted is reported in an Exchange Server 2007 environment

977091 (http://support.microsoft.com/kb/977091/ ) The time for an updated meeting request is incorrectly shown in an exception instance of a recurring meeting request on an Exchange Server 2007 environment

977181 (http://support.microsoft.com/kb/977181/ ) The EXOLEDB component is not initialized successfully when you start Exchange Information Store Service on an Exchange Server 2007 server

977223 (http://support.microsoft.com/kb/977223/ ) A move operation on a folder fails when the "ptagProvisionedFid" attribute is invalid in an Exchange Server 2007 environment

977261 (http://support.microsoft.com/kb/977261/ ) One or more errors occur when you set the Message Access logging level to Expert in an Exchange Server 2007 SP2 server

977355 (http://support.microsoft.com/kb/977355/ ) Non-ASCII characters in a display name of a forwarded message are shown with "?" when the display name of a contact is in East Asia characters in an Exchange Server 2007 environment

977412 (http://support.microsoft.com/kb/977412/ ) Error message when you use the WebDAV protocol to connect to an Exchange Server 2007 server: "Error 1000"

977425 (http://support.microsoft.com/kb/977425/ ) The "Proxy server name" field is incorrectly shown in OWA in an Exchange Server 2007 CAS-to-CAS proxy environment

978593 (http://support.microsoft.com/kb/978593/ ) Windows Server 2008 VSS backup plug-in fails to backup Exchange 2007 Service Pack 2 databases that reside on a volume mount point

Microsoft Security Bulletin MS10-002 - Critical

2010-01-21T20:23:00.000-03:00

http://www.microsoft.com/technet/security/bulletin/ms10-002.mspx

General Information

Executive Summary

This security update resolves seven privately reported vulnerabilities and one publicly disclosed vulnerability in Internet Explorer. The more severe vulnerabilities could allow remote code execution if a user views a specially crafted Web page using Internet Explorer. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights.

This security update is rated Critical for all supported releases of Internet Explorer: Internet Explorer 5.01, Internet Explorer 6, Internet Explorer 6 Service Pack 1, Internet Explorer 7, and Internet Explorer 8 (except Internet Explorer 6 for supported editions of Windows Server 2003). For Internet Explorer 6 for supported editions of Windows Server 2003 as listed, this update is rated Moderate. For more information, see the subsection, Affected and Non-Affected Software, in this section.

The security update addresses these vulnerabilities by modifying the way that Internet Explorer handles objects in memory, validates input parameters, and filters HTML attributes. For more information about the vulnerabilities, see the Frequently Asked Questions (FAQ) subsection under the next section, Vulnerability Information.

This security update also addresses the vulnerability first described in Microsoft Security Advisory 979352.

Recommendation. The majority of customers have automatic updating enabled and will not need to take any action because this security update will be downloaded and installed automatically. Customers who have not enabled automatic updating need to check for updates and install this update manually. For information about specific configuration options in automatic updating, see Microsoft Knowledge Base Article 294871.

For administrators and enterprise installations, or end users who want to install this security update manually, Microsoft recommends that customers apply the update immediately using update management software, or by checking for updates using the Microsoft Update service.

Get a Second Shot

2010-01-12T21:10:00.000-03:00

Second Shot provides a free retake when you fail your first attempt at an IT Pro or Developer Microsoft Certification Exam, reducing concern and fear of not passing your exam.

Buy a Microsoft IT Professional, Developer, or Microsoft Dynamics certification exam and get a Free Retake if you fail your first try.
This promotion is valid from January 13, 2009 – June 30, 2010. Customers must register, obtain a voucher code, schedule, pay, and sit for both the first and (if necessary) second retake exams before June 30, 2010.
Eligible Exams: All 070 and 083 exams. Offer available worldwide.

Click here to get your Second Shot!

Why Certify?
Whether you are currently unemployed, looking for a promotion, or trying to become indispensible in your existing role, Microsoft Certifications can validate your training and knowledge for skills applicable for some of the top IT and Developer jobs in the industry.
To find out more, visit: www.microsoft.com/learning/en/us/offers/Career.aspx

Exchange 2010 Rollup1 - This process can take an extended period of time to complete

2009-12-16T12:15:00.000-03:00

Description of Update Rollup 1 for Exchange Server 2010

http://support.microsoft.com/kb/976573

Download

http://www.microsoft.com/downloads/details.aspx?FamilyID=371add31-d7a0-4c8b-8325-a6fced2d05e6&displaylang=en

This process can take an extended period of time to complete, to fix this issue you have to change the process of Certificate Revocation Check or grant the access to the public CRL of Microsoft, you can do it in three diferents ways

The installation of Rollup 1 performs the process of Certificate Revocation Check, if the server does not have internet access to validate the CRL from Microsoft freezes and down the services in DISABLE mode

Workaround:

1. Enable Internet Access while the installation process

2. Disable Certificate Revocation Check Option

Turn off certificate revocation check in Internet Explorer

In Internet Explorer –> Tools –> Internet Options –> Advanced tab
In the Security section, uncheck or clear the box for two options mentioned below:

Check for publisher’s certificate revocation
Check for server certificate revocation

Turn off certificate revocation check in registry

In registry editor browse to the following key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing

Change Value “State” to 146944 Decimal or 0×00023e00 Hexadecimal

Either way, you should not leave these settings intact after installation of Rollup update. Do not forget to revert the changes. I don’t think you will ask me for steps to revert it if you used IE method. If you changed registry, I have listed details below.

Turn on certificate revocation check in registry

In registry editor browse to the following key: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\WinTrust\Trust Providers\Software Publishing

Change Value “State” to 146432 Decimal or 0×00023c00 Hexadecimal

3. Edit the configuration file on each services

<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>

http://andreslozada.blogspot.com/2009/03/after-you-install-microsoft-exchange.html

Installing Update Rollup 1 for Exchange 2010 on DAG Members

2009-12-10T17:34:00.000-03:00

Hi , My friend Scott Schnoll has published this article with the steps required for the installation of Rollup 1 for Exchange Server 2010 on DAF Members

Installing Update Rollup 1 for Exchange 2010 on DAG Members

http://blogs.technet.com/scottschnoll/archive/2009/12/10/installing-update-rollup-1-for-exchange-2010-on-dag-members.aspx

Install a Update Rollup on a Database Availability Group Member

Suspend activation for the database copies on the server being updated

Run the following command in the Exchange Management Shell:

Get-MailboxDatabaseCopyStatus -Server <Server> | Suspend-MailboxDatabaseCopy -ActivationOnly -Confirm:$False -SuspendComment "Install update rollup for Exchange 2010"

Perform a server switchover on the server being updated

In the console tree, navigate to Server Configuration > Mailbox.
In the result pane, select the Mailbox server you want.
In the Actions pane, select Switchover Server.
In the Switchover server database copies dialog box, do one of the following:

Accept the default setting of Automatically choose a target server (in which case, the system automatically selects the best Mailbox server for each database being switched over), and then click OK.
Use the specified server as the target for switchover, click Browse to select a Mailbox server, and then click OK.

Install the update rollup

Close all Exchange management tools.
Right-click the update rollup file (.MSP file) you downloaded and select Apply.
On the Welcome page, click Next.
On the License Terms page, review the license terms, select I accept the License Terms, and then click Next.
On the Completion page, click Finish.

Resume activation for the databases on the updated server

Run the following command in the Exchange Management Shell:

Get-MailboxDatabaseCopyStatus -Server <Server> | Resume-MailboxDatabaseCopy

Perform database switchovers as needed

In the console tree, navigate to Organization Configuration > Mailbox.
In the result pane, click the Database Management tab, and then right-click the mailbox database whose copy you want to activate.
In the action pane, click Activate a Database Copy.
On the Activate a Database Copy page, click Browse to select the server you updated.
Select the desired setting for the automatic database mount dial setting on the selected server.
Click Move to activate the selected passive copy of the database to the updated server.
On the Completion page, review the following, and then click Finish to close the wizard.

Scott Schnoll´s Blog

http://blogs.technet.com/scottschnoll/default.aspx

BlackBerry Enterprise Server fully supported on Exchange 2010

2009-12-09T17:39:00.000-03:00

http://msexchangeteam.com/archive/2009/12/09/453486.aspx

In order to enable full support, three updates are required:

Roll-Up 1 (RU1) for Exchange Server 2010
MAPI v6.5.8147
BlackBerry Enterprise Server 5.0.1 Maintenance Release 1 (MR1)

All three of these updates are available to customers of Exchange Server 2010 and BlackBerry Enterprise Server v.5.0 with Service Pack 1 at no cost. BlackBerry Enterprise Server v5.0 Service Pack 1 and Maintenance Release 1 can be found here: http://www.blackberry.com/support/downloads

Additional information on the solution requirements, preparing the BlackBerry environment for Microsoft Exchange Server2010, can be found on the BlackBerry site here.

http://na.blackberry.com/eng/services/server/exchange/2010support.jsp

Solution Requirements

BlackBerry Enterprise Server v5.0 with Service Pack 1 and Maintenance Release 1
- Download service packs and maintenance releases for BlackBerry Enterprise Server v5.0

Microsoft Exchange Server 2010 updated with Roll Up 1
- Learn more about Microsoft Exchange Server 2010

Microsoft MAPI/CDO Download Package
- Download v6.5.8146 or higher of the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

Resources to Help You Prepare Your BlackBerry Environment for Microsoft Exchange 2010

View all documentation for BlackBerry Enterprise Server for Microsoft Exchange v5.0.1

Exchange Server 2010 Rollup 1 – Available!

2009-12-09T15:28:00.000-03:00

Description of Update Rollup 1 for Exchange Server 2010

http://support.microsoft.com/kb/976573

Download

http://www.microsoft.com/downloads/details.aspx?FamilyID=371add31-d7a0-4c8b-8325-a6fced2d05e6&displaylang=en

Issues that the update rollup fixes

Update Rollup 1 for Exchange Server 2010 fixes the issues that are described in the following Microsoft Knowledge Base articles:

977439 (http://support.microsoft.com/kb/977439/ ) Exchange Server 2010 users cannot open certain attachments when they access their mailboxes by using Outlook Web App

977551 (http://support.microsoft.com/kb/977551/ ) Meeting requests that are sent to a room mailbox are not processed in Exchange Server 2010

977552 (http://support.microsoft.com/kb/977552/ ) Exchange RPC Client Access service crashes in the Handler.dll that is located on an Exchange 2010 Client Access service server

977553 (http://support.microsoft.com/kb/977553/ ) Exchange RPC Client Access service crashes in Parser.dll on the Exchange Server 2010 CAS server

977554 (http://support.microsoft.com/kb/977554/ ) The subject or body of a message that is hosted in an Exchange Server 2010 mailbox is not set as expected

977555 (http://support.microsoft.com/kb/977555/ ) The message body is inaccessible when the property conversion from PR_BODY_HTML to PR_BODY fails

977556 (http://support.microsoft.com/kb/977556/ ) The body text of an e-mail message is invisible after you create exceptions for a recurring appointment or for a recurring meeting by using a CDO application together with Exchange Server 2010

977557 (http://support.microsoft.com/kb/977557/ ) An E_FAIL error occurs when you create an exception to a meeting request by using a CDO application for a Microsoft Exchange Server 2010 mailbox

977558 (http://support.microsoft.com/kb/977558/ ) A folder name is not changed when you try to move and then rename the folder in an Exchange Server 2010 mailbox by using the CopyFolder method of the IMAPIFolder interface

977559 (http://support.microsoft.com/kb/977559/ ) The location of a meeting or an appointment is not updated on an Exchange Server 2010 mailbox

977560 (http://support.microsoft.com/kb/977560/ ) Update fails when you use a CDO application to update a recurrence task on Exchange Server 2010

977561 (http://support.microsoft.com/kb/977561/ ) VSS backup process stops responding when you try to perform a Volume Shadow Copy Service (VSS) backup for Exchange Server 2010 databases

Step By Step Active Directory Windows Server 2008 R2

2009-12-01T23:07:00.000-03:00

Hi everyone, I going to show how we can install the first Domain Controller in Windows Server 2008 R2

Procedure

1. Set a manual IP address

2. Start > Run > Type DCpromo

3. Select the advanced mode installation

4. Read the Operating System Compatibility advisor

5. Select Create a new domain in a new forest option

6. type the FQDN of the Domain (technet.lab)

7. Verify the NetBIOS name (Technet)

8. Select the Forest Functional Level

9. Select Windows Server 2008 R2 forest functional level

10. Select the DNS Server to install this component

11. Click on YES

12. Select the database and log folder path

13. Type the Directory Services Restore Mode Administrator Password

14. Verify the summary

15. Begging the process

16. Finish the Wizard

17. Restart the server

18. After restart the server you must logon with domain credentials

19. Verify the AD DS tools

So easy, your first domain controller in Windows Server 2008 R2

Install Exchange Server 2010 RTM – Step by Step

2009-11-12T00:40:00.000-03:00

Hi, i write this post with the step by step to install Exchange Server 2010 RTM

Install the Windows Server 2008 R2 operating system prerequisites

http://technet.microsoft.com/en-us/library/bb691354(EXCHG.140).aspx#WS08R2

On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack

http://www.microsoft.com/downloads/details.aspx?FamilyId=60C92A37-719C-4077-B5C6-CAC34F4227CC&displaylang=en

1. On the Start Menu, navigate to All Programs, then Accessories, then Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:

Import-Module ServerManager

2. Use the Add-WindowsFeature cmdlet to install the necessary operating system components:

For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:

Add-WindowsFeature NET-Framework,RSAT-ADDS,Web-Server,Web-Basic-Auth,Web-Windows-Auth,Web-Metabase,Web-Net-Ext,Web-Lgcy-Mgmt-Console,WAS-Process-Model,RSAT-Web-Server,Web-ISAPI-Ext,Web-Digest-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-Over-HTTP-Proxy –Restart

Restart

3. After the system has restarted, log on as an administrator, open an elevated Windows PowerShell console, and configure the Net.Tcp Port Sharing Service for Automatic startup by running the following command:

Set-Service NetTcpPortSharing -StartupType Automatic

Prepare Active Directory

http://technet.microsoft.com/en-us/library/bb125224(EXCHG.140).aspx

Prerequisites

Your domains and the domain controllers must meet the system requirements in the "Network and Directory Servers" section of Exchange 2010 System Requirements.
In each domain in which you will install Exchange 2010, you must have at least one domain controller running Windows Server 2003 Service Pack 1 (SP1).
If you are running the release to manufacturing (RTM) version of Exchange 2010 Setup.com, in each domain (including child domains) where you have the Exchange Enterprise Servers and Exchange Domains Servers security groups and therefore must run Setup /PrepareLegacyExchangePermissions, you must have at least one domain controller running Windows Server 2003 SP1 or a later version.
If you are deploying a new Exchange organization, and you are preparing your Active Directory schema and domains by using a computer running Windows Server 2008, you must first install the Active Directory management tools on the Windows Server 2008 computer prior to preparing the schema or domains. To do this, run the following command.

ServerManagerCmd -i RSAT-ADDS

The computers on which you will install Exchange 2010 must meet the system requirements. For details, see Exchange 2010 System Requirements.

Prepare Active Directory and domains

If you have any computers in your organization running Exchange 2003, open a Command Prompt window, and then run one of the following commands:
- To prepare legacy Exchange permissions in every domain in the forest that contains the Exchange Enterprise Servers and Exchange Domain Servers groups, run the following command.
  setup /PrepareLegacyExchangePermissions.or setup /pl
- To prepare legacy Exchange permissions in a specific domain, run the following command.
  setup /PrepareLegacyExchangePermissions: < FQDN of domain you want to prepare > or setup /pl:<FQDN of domain you want to prepare>

Note:

You can skip this step and prepare the legacy Exchange permissions as part of Step 2 or Step 3. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

Note the following:
- To run this command to prepare every domain in the forest, you must be a member of the Enterprise Admins group. To run this command to prepare a specific domain, or if the forest has only one domain, you must be delegated the Exchange Organization Management role, and you must be a member of the Domain Admins group in the domain that you will prepare.
- If you don't specify a domain, the domain in which you run this command must be able to contact all domains in the forest. If the server can't contact a domain that must have legacy Exchange permissions prepared, it prepares the domains that it can contact, and then returns an error message that it was unable to contact some domains.
- You can run this command from any 64-bit Windows Server 2003 SP1 server in the forest.
- You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency. For information on how to identify the schema master, see Identify the schema master. To change site membership for the schema master:

5. For information on how to transfer

o After you run this command, you must wait for the permissions to replicate across your Exchange organization before continuing to the next step. If the permissions haven't replicated, the Recipient Update Service on your Exchange Server 2003 computers could fail. The amount of time that replication takes depends on your Active Directory site topology.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Microsoft Windows Server 2003 Support Tools Setup. By default, it's located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

For detailed information about the permissions set by this command, see Preparing Legacy Exchange Permissions.

From a Command Prompt window, run the following command.
setup /PrepareSchema or setup /ps

Note:

You can skip this step and prepare the schema as part of Step 3.

Important:

You must not run this command in a forest in which you don't plan to run setup /PrepareAD. If you do, the forest will be configured incorrectly, and you won't be able to read some attributes on user objects.

Note:

It isn't supported to use the LDIF Directory Exchange tool (LDIFDE) to manually import the Exchange 2010 schema changes. You must use Setup to update the schema.

This command performs the following tasks:

o Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with Exchange 2010 specific attributes. The LDIF files are copied to the Temp directory, and then deleted after they are imported into the schema.

o If you haven't completed Step 1, setup /PrepareSchema will automatically perform the PrepareLegacyExchangePermissions step.

Note the following:

o If you want to verify the updates to the schema before the changes are replicated to other servers in the domain, you must disable outbound replication on the computer on which you run the command before you run it, and then enable outbound replication after you have verified that the import completed successfully.

o To run this command, you must be a member of the Schema Admins group and the Enterprise Admins group.

o You must run this command on a 64-bit computer in the same domain and in the same Active Directory site as the schema master.

o If you haven't completed Step 1, setup /PrepareSchema will automatically perform the PrepareLegacyExchangePermissions step. To complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

o If you use the /DomainController parameter with this command, you must specify the domain controller that is the schema master.

o After you run this command, you should wait for the changes to replicate across your Exchange organization before continuing to the next step. The amount of time this takes is dependent upon your Active Directory site topology.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Windows Server 2003 Support Tools Setup. By default, it's located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

For more information, see Exchange Server Changes to the Active Directory Schema.

From a Command Prompt window, run the following command.
setup /PrepareAD [/OrganizationName: <organization name> ] or setup /p [/on:<organization name>]
This command performs the following tasks:

o If the Microsoft Exchange container doesn't exist, this command creates it under CN=Services,CN=Configuration,DC=<root domain>.

o If no Exchange organization container exists under CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain >, you must specify an organization name by using the /OrganizationName parameter. The organization container will be created with the name that you specify.
The Exchange organization name can contain only the following characters:
A through Z
a through z
0 through 9
Space (not leading or trailing)
Hyphen or dash
The organization name can't contain more than 64 characters. The organization name can't be blank. If the organization name contains spaces, you must enclose the name in quotation marks.

o Verifies that the schema has been updated and that the organization is up to date by checking the objectVersion property in Active Directory. The objectVersion property is in the CN=<your organization>, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<domain> container. The objectVersion value for the RTM version of Exchange Server 2007 is 10666.

o If they don't exist, creates the following containers and objects under CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>. These are required for Exchange 2010.
CN=Address Lists Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Addressing,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Administrative Groups,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Client Access,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Connections,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=ELC Folders Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=ELC Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Global Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Mobile Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Recipient Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=System Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=Transport Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM AutoAttendant,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM DialPlan,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM IPGateway Container,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
CN=UM Mailbox Policies,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>

o If it doesn't exist, creates the default Accepted Domains entry, based on the forest root namespace, under CN=Transport Settings,CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>.

o Assigns specific permissions throughout the configuration partition.

o Imports the Rights.ldf file. This adds the extended rights required for Exchange to install into Active Directory.

o Creates the Microsoft Exchange Security Groups organizational unit (OU) in the root domain of the forest and assigns specific permissions on this OU.

o Creates the following universal security groups (USGs) within the Microsoft Exchange Security Groups OU:
Exchange Organization Administrators
Exchange Recipient Administrators
Exchange Servers
Exchange View-Only Administrators
Exchange Public Folder Administrators (New in Exchange Server 2007 Service Pack 1)
ExchangeLegacyInterop

o Adds the new USGs that are within the Microsoft Exchange Security Groups OU to the otherWellKnownObjects attribute stored on the CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain> container.

o Creates the Unified Messaging Voice Originator contact in the Microsoft Exchange System Objects container of the root domain.

o Prepares the local domain for Exchange 2010. For information about what tasks are completed to prepare a domain, see Step 4.

Note the following:

o To run this command, you must be a member of the Enterprise Admins group.

o The computer where you run this command must be able to contact all domains in the forest on port 389.

o You must run this command on a computer in the same domain and in the same Active Directory site as the schema master. Setup will make all configuration changes to the schema master to avoid conflicts because of replication latency.

o If you haven't completed Step 1, setup /PrepareAD will automatically perform the PrepareLegacyExchangePermissions step. To complete the PrepareLegacyExchangePermissions step, the domain in which you run this command must be able to contact all domains in the forest. If you are also a member of the Schema Admins group, and if you haven't completed Step 2, setup /PrepareAD will automatically perform the PrepareSchema step. The advantages of running each step separately are that you can run each step with an account that has the minimum permissions required for that step, and you can verify completion, success, and replication before continuing to the next step.

Note:

To track the progress of Active Directory replication, you can use the Active Directory Replication Monitor tool (replmon.exe), which is installed as part of the Windows Server 2003 Support Tools Setup. By default, it is located at "%programfiles%\support tools\." Add your domain controllers as monitored servers so that you can track the progress of replication throughout the domain.

o To verify that this step completed successfully, make sure that there is a new OU in the root domain called Microsoft Exchange Security Groups. This OU should contain the following new Exchange USGs:
Exchange Organization Administrators
Exchange Recipient Administrators
Exchange View-Only Administrators
Exchange Servers
Exchange Public Folder Administrators (new in Exchange 2007 SP 1)
ExchangeLegacyInterop

From a Command Prompt window, run one of the following commands:

o Run setup /PrepareDomain or setup /pd to prepare the local domain. Note that you don't need to run this in the domain where you ran Step 3. Running setup /PrepareAD prepares the local domain.

o Run setup /PrepareDomain:<FQDN of domain you want to prepare> to prepare a specific domain.

o Run setup /PrepareAllDomains or setup /pad to prepare all domains in your organization.

These commands perform the following tasks:

o Sets permissions on the domain container for the Exchange Servers, Exchange Organization Administrators, Authenticated Users, and Exchange Mailbox Administrators.

o If this is a new organization, creates the Microsoft Exchange System Objects container in the root domain partition in Active Directory and sets permissions on this container for the Exchange Servers, Exchange Organization Administrators, and Authenticated Users. This container is used to store public folder proxy objects and Exchange-related system objects, such as the mailbox database's mailbox.

o Sets the objectVersion property in the Microsoft Exchange System Objects container under DC=<root domain>. This objectVersion property contains the version of domain preparation. The version for Exchange 2007 RTM is 10628.

o Creates a new domain global group in the current domain called Exchange Install Domain Servers. The command places this group in the Microsoft Exchange System Objects container. It also adds the Exchange Install Domain Servers group to the Exchange Servers USG in the root domain.

Note:

The Exchange Install Domain Servers group is used if you install Exchange 2010 in a child domain that is an Active Directory site other than the root domain. The creation of this group allows you to avoid installation errors if group memberships haven't replicated to the child domain.

o Assigns permissions at the domain level for the Exchange Servers USG and the Exchange Recipient Administrators USG.

Note the following:

o For domains that are in an Active Directory site other than the root domain, /PrepareDomain might fail with the following messages:
"PrepareDomain for domain <YourDomain> has partially completed. Because of the Active Directory site configuration, you must wait at least 15 minutes for replication to occur, and run PrepareDomain for <YourDomain> again."
"Active Directory operation failed on <YourServer>. This error is not retriable. Additional information: The specified group type is invalid.
Active Directory response: 00002141: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0
The server cannot handle directory requests."
If you see these messages, wait for or force Active Directory replication between this domain and the root domain, and then run /PrepareDomain again.

o To run setup /PrepareAllDomains, you must be a member of the Enterprise Admins group.

o To run setup /PrepareDomain, if the domain that you are preparing existed before you ran setup /PrepareAD, you must be a member of the Domain Admins group in the domain. If the domain that you are preparing was created after you ran setup /PrepareAD, you must be a member of the Exchange Organization Administrators group, and you must be a member of the Domain Admins group in the domain.

o You must run this command in every domain in which you will install Exchange 2007. You must also run this command in every domain that will contain mail-enabled users, even if the domain doesn't have Exchange 2007 installed.

To verify that this step completed successfully, confirm the following:

o You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers.

Note:

To view the Microsoft Exchange System Objects container in Active Directory Users and Computers, on the View menu, click Advanced Features.

o The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.

o On each domain controller in a domain in which you will install Exchange 2010, the Exchange Servers USG has permissions on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.

Install Exchange Server 2010

Technet Webcast: Unified Communication Introduction

2009-11-10T19:38:00.001-03:00

Hola, los invito a particiar en este webcast el 11 de Noviembre a las 4:00 pm Bogota

Registrarse

Idiomas:
Español.

Productos:
Microsoft Exchange Server 2007,Microsoft Office Communications Server 2007.

Audiencia(s):
Generalista de IT.

Moderador(es):

Andrés Lozada

Duración:
60 Minutos

Fecha de Inicio:

miércoles, 11 de noviembre de 2009 04:00 p.m. Bogotá

Información general del Evento

Integre su plataforma de comunicaciones, audio, voz y video con su sistema de mensajeria con Exchange Server 2007 y Office Communication Server 2007.

Exchange Server 2010 RTM Released!

2009-11-09T20:49:00.001-03:00

Hi folks,

Today was released the RTM BITS of Exchange Server 2010, you can now download from your licensing Website Download Microsoft Exchange Server 2010 TRIAL

http://technet.microsoft.com/en-us/evalcenter/dd185495.aspx

Virtual Experience

Take a simple web-based test drive. Get your free end
user account to preview Exchange Server 2010 and Office
Communications Server 2007 R2 together for 60 days.

Downloads

Free 120-day Software Trial

Try Exchange Server 2010 in your own environment.

Virtual Hard Drive

Try a pre-configured Exchange Server 2010 VHD.

Exchange Online Trial

Get a Free Exchange Online account for 30 days.
Experience the suite of hosted services
provided by Microsoft Online.

Webcast TechNet: Como migrar a Exchange Server 2010

2009-10-29T23:39:00.001-03:00

Hola,

Los invito a participar en este Webcast el proximo lunes 9 de Noviembre, Migracion a Exchange Server 2010

Registrate ya

http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032420899&EventCategory=4&culture=es-AR&CountryCode=AR

Idiomas:
Español.

Productos:
Microsoft Exchange Server 2007.

Audiencia(s):
Generalista de IT.

Moderador(es):

Andrés Lozada

Duración:
60 Minutos

Fecha de Inicio:

lunes, 09 de noviembre de 2009 04:00 p.m. Bogotá

Información general del Evento

Evalúe los requisitos y la forma más sencilla de migrar su plataforma de correo a Microsoft Exchange Server 2010.

Do NOT Apply KB974571 to LCS/OCS Servers

2009-10-15T18:41:00.001-03:00

Hey folks, check this post URGENT, CRITICAL to LCS and OCS

http://blogs.technet.com/dodeitte/archive/2009/10/13/do-not-apply-kb974571-to-lcs-ocs-servers.aspx

Update #1 - Until this issue can be resolved, I am only suggesting that you either hold off on deploying this update, or test very throughly to make sure that this won't cause an outage in your environment. Security updates are VERY important, and once this issue is resolved, you should deploy this update to all of your LCS/OCS servers.

Currently an issue is being observed after applying KB974571 (MS09-056: Vulnerabilities in CryptoAPI could allow spoofing) to LCS/OCS servers, that is causing them to believe that they are running an evaluation version of LCS/OCS and that it has expired.

http://support.microsoft.com/kb/974571/

If you apply the patch, the LCS/OCS services fail to start and you see these errors in the event log:

Event Type:        Error
Event Source:    Live Communications Server
Event Category:                (1000)
Event ID:              12290
Date:                     10/13/2009
Time:                     8:28:57 PM
User:                     N/A
Computer:
Description:
The evaluation period for Microsoft Office Live Communication Server 2005 has expired. Obtain the released version of this product and upgrade to the non-evaluation version by running setup.exe

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:        Error
Event Source:    Live Communications Server
Event Category:                (1000)
Event ID:              16417
Date:                     10/13/2009
Time:                     8:28:57 PM
User:                     N/A
Computer:
Description:
Unable to initialize the protocol stack. The service has to stop.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:        Error
Event Source:    Live Communications Server
Event Category:                (1000)
Event ID:              12299
Date:                     10/13/2009
Time:                     8:28:57 PM
User:                     N/A
Computer:
Description:
The service is shutting down due to an internal error.

Error Code: 0xC3ED0804.
Resolution:
Check the previous event log entries and resolve them. Restart the server. If the problem persists contact product support.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Uninstalling the patch is the only way to currently fix this issue.

The issue is currently being escalated, but until a fix can be found, delaying the install of KB974571 is recommended.

Webcast Introduccion Exchange Server 2010 (Nivel 100)

2009-10-14T01:54:00.000-03:00

Hola,

Los invito a participar de este Webcast

Webcast TechNet: Introducción a Exchange Server 2010

Registrarse

Idiomas:Español.

Productos:Microsoft Exchange Server 2010.

Audiencia(s): Generalista de IT.

Moderador(es): Andrés Lozada

Duración:60 Minutos

Fecha de Inicio:miércoles, 14 de octubre de 2009 04:00 p.m. Bogotá

Información general del Evento

Conozca lo nuevo de Exchange 2010 y evalue los pre requisitos para migrar su plataforma de mensajeria a Exchange 2010

Microsoft Virtual Academy 2

2009-10-08T15:40:00.000-03:00

Hola,

Los invito a participar de la nueva version Microsoft Virtual Academy, pueden encontrar entrenamiento gratuito y la nueva carrera de Exchange Server 2010

http://www.mslatam.com/latam/technet/mva2/Home.aspx

Exchange Server 2010

Evento Virtual Nueva Eficiencia Registrate YA!

2009-09-28T19:03:00.000-03:00

Hola, Los invito a participar en este evento virtual el proximo 7 de Ocutbre, registrate YA!

http://www.microsoft.com/latam/technet/nuevaeficiencia/

Windows 7

· Características, despliegue y seguridad en Windows 7

· De Vista a 7: virtualización de escritorios, migración de redes y fundamentos de administración Optimización de aplicaciones

Windows Server 2008 R2

· Revisión de la nueva tecnología, optimización en el consumo de energía

· Mejoras de virtualización, analizador de mejores prácticas e infraestructura para trabajar en cualquier sitio

Exchange Server 2010

· Revisión general, movilidad y Outlook Web Access

· Alta disponibilidad y almacenamiento

· Herramientas de manejo, transición y descarga

Forefront

· Introducción y la nueva generación de productos Forefront

· Forefront y Office SharePoint Server, mejor juntos!

Information Workers

· Introducción a Office 2010

· Novedades, mejoras y trucos

PreCallDiagnostic Resource Kit Tool

2009-09-21T21:55:00.001-03:00

Brief Description

The PreCallDiagTool is an application that reports expected audio quality as it relates to the network effect.

Download

http://www.microsoft.com/downloads/details.aspx?FamilyID=f16ab4c2-353f-4c9b-b353-22a656c03c9b&displaylang=en

Overview

The PreCallDiagTool is an application that reports expected audio quality as it relates to the network effect. The tool should be installed on any desktop or laptop PC that suffers from inconsistent network connection quality. The PreCallDiagTool can provide a quick check of the current network conditions and also preserve a history of quality data to let users profile their network performance over time or other conditions. The tool is particularly useful for home/mobile users and users using WIFI access points.

Note: This is the 32 bit version of the PreCallDiagTool. The 64 bit version can be found in the Office Communications Server 2007 R2 Resource Kit.

System Requirements

Supported Operating Systems: Windows Server 2003 Service Pack 2; Windows Server 2008; Windows Vista; Windows XP Embedded Service Pack 2
This download works with the following Office program:
- Microsoft Office Communications Server 2007 R2

Install Exchange Server 2010 RC1 Edge Role

2009-09-15T22:11:00.000-03:00

Hi, now i going to show you a few steps to install the Edge Server Role on Windows Server 2008 R2

Before you run the setup add the FQDN DNS suffix over the computer properties

The DNS suffix is not set on the local computer

To set the primary DNS suffix of the local computer

1. Right-click My Computer, and then click Properties. The System Properties dialog box will appear.

2. Click the Computer Name tab.

3. Click Change. The Computer Name Changes dialog box will appear.

4. Click More. The DNS Suffix and NetBIOS Computer Name dialog box will appear.

5. Enter the appropriate DNS suffix for the domain.

6. Select the Change primary DNS suffix when domain membership changes check box.

7. Click OK to save the changes, and then click OK to exit the Computer Name Changes dialog box.

8. Click OK to close the System Properties dialog box, and then restart the computer for the change to take effect.

Then, install the pre-requisites

Windows Server 2008 R2 operating system prerequisites

1. On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For details, see 2007 Office System Converter: Microsoft Filter Pack.
On the Start Menu, navigate to All Programs, then Accessories, then Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:

Import-Module ServerManager

3. For a server that will host the Edge Transport role:

Add-WindowsFeature NET-Framework,RSAT-ADDS,ADLDS -Restart<?xml:namespace prefix = o />

Run the setup wizard Introduction License Agreement Error Reporting Select the installation directorySelect the Edge Role Customer Experience Improvement ProgramInstallation Status

Install Exchange 2010 RC1

2009-09-08T04:49:00.000-03:00

Hi, I post the step by step for Exchange Server 2010 on windows Server 2008 R2 in a consolidate installation

Windows Server 2008 R2 operating system prerequisites

1. On servers that will host the Hub Transport or Mailbox server role, install the Microsoft Filter Pack. For details, see 2007 Office System Converter: Microsoft Filter Pack.

2. On the Start Menu, navigate to All Programs, then Accessories, then Windows PowerShell. Open an elevated Windows PowerShell console, and run the following command:

Copy Code

Import-Module ServerManager

3. Use the Add-WindowsFeature cmdlet to install the necessary operating system components:

a. For a server that will have the typical installation of Client Access, Hub Transport, and the Mailbox role:

Copy Code

Prepare Active Directory

setup /PrepareLegacyExchangePermissions.or setup /pl setup /PrepareSchema or setup /pssetup /PrepareAD [/OrganizationName: setup /PrepareDomain or setup /pd Installation Introduction License Agreement Error Reporting Installation Type Server Role Selection Client Settings Configure Client Access Server External Domain Custumer Experience Improvement Program Readiness Checks Installing OWA

Exchange Server 2010 Management Pack RC

2009-09-01T02:49:00.000-03:00

Hi , Yesterday was released the Management Pack for Exchange Server 2010

Exchange Server 2010 Management Pack (x86) Release Candidate

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a0047276-553c-4054-afc9-ec3b4ececf3c#tm

Exchange Server 2010 Management Pack (x64) Release Candidate

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=a0d4e1f0-e2ba-4391-a118-9da83e827623#tm

Exchange 2007 SP2 Available!

2009-08-24T12:49:00.000-03:00

Overview

Microsoft Exchange Server 2007 Service Pack 2 (SP2) has been designed specifically to help meet the challenges of any business and the needs of all the different groups with a stake in the messaging system. Exchange Server 2007 SP2 is a mission-critical communications tool that enables employees to be more productive and access their information anywhere and anytime while providing a messaging system that enables rich, efficient access to e-mail, calendar items, voice mail, and contacts. For the administrator, Exchange Server 2007 SP2 provides advanced protection options against e-mail security threats, such as spam and viruses, as well as the tools to help manage internal compliance and high availability needs. For an overview of the new features that are available in Exchange Server 2007 SP2, see "What's New in Exchange Server 2007 SP2".

Exchange Server 2007 Service Pack 2 Download

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=4c4bd2a3-5e50-42b0-8bbb-2cc9afe3216a

What's New in Exchange Server 2007 SP2

http://technet.microsoft.com/en-us/library/ee221150.aspx

Uncovering the new Exchange 2007 SP2 Volume Snapshot (VSS) Plug-in (Part 1)

http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/uncovering-new-exchange-2007-sp2-volume-snapshot-vss-plug-in-part1.html

Uncovering the new Exchange 2007 SP2 Volume Snapshot (VSS) Plug-in (Part 2)

http://www.msexchange.org/articles_tutorials/exchange-server-2007/high-availability-recovery/uncovering-new-exchange-2007-sp2-volume-snapshot-vss-plug-in-part2.html

New Features

Microsoft Exchange Server 2007 Service Pack 2 (SP2) introduces many new features for each server role. This topic discusses the new and improved features that are added when you install Exchange 2007 SP1.

To download Exchange 2007 SP2, see Exchange Server 2007 Downloads.

Deploying Exchange Server 2010

You can deploy Exchange Server 2010 in your organization once all of the Client Access servers in your organization have been upgraded to Exchange Server 2007 Service Pack 2 (SP2). In addition, any Exchange 2007 Server, regardless of server role, in the Active Directory site you are transitioning, must be upgraded to Exchange 2007 SP2.

Exchange Backup Functionality

Exchange 2007 Service Pack 2 includes a VSS plug-in for Windows Server Backup to support Exchange backups. Once SP2 is installed, you can use Windows Server Backup to back up and restore your Exchange 2007 SP2 databases. The new plug-in is delivered in the form of a single executable called WSBExchange.exe. This plug-in is automatically installed by SP2 on all Exchange 2007 Mailbox servers. The plug-in enables Windows Server Backup to be able to make Exchange-aware VSS backups. For more information about this feature and how to use it, see Using Windows Server Backup to Back Up and Restore Exchange Data.

Enhanced Auditing

New Exchange auditing events and audit log repository enable Exchange administrators to more easily audit the activities occurring on their Exchange servers. It allows the right balance of granularity, performance, and easy access to audited events via a dedicated audit log repository. This simplifies the auditing process and makes review of audited events easier by segregating audited events in a dedicated location. For more information about the new auditing features available with SP2, see Understanding Mailbox Access Auditing with Exchange Server 2007 Service Pack 2.

Dynamic Active Directory Schema Validation

The dynamic AD schema update and validation feature allows for future schema updates to be dynamic deployed as well as proactively preventing conflicts whenever a new property is added to the AD schema. Once this capability is deployed it will enable easier management of future schema updates and will prevent support issues when adding properties that don’t exist in the AD schema. For more information about Dynamic Active Directory Schema Validation, see Understanding Dynamic Schema Updates and Validation in Exchange 2007 SP2.

Public Folder Quota Management

Exchange 2007 Service Pack 2 provides a more efficient way to manage Public Folder quotas by improving the current cmdlets and removing the dependency on the Public Folder Distributed Authoring and Versioning Administration to perform management tasks. For more information about the new public folder quota management features, see the Set-PublicFolder cmdlet documentation.

Centralized Organizational Settings

There are several new cmdlet parameters that have been added that enable centralized management of many of the Exchange organization settings.

For more information about the new cmdlet parameters, see the following topics:

In addition to the parameters that have been added to the cmdlet topics listed previously, the UseRUSServer parameter has been added to the following topics:

The Active Directory Schema is not up-to-date and Ldifde.exe

2009-08-24T00:39:00.000-03:00

Hi, this error occurs frequently during the prerequisites validation process in the installation wizard in Exchange 2007 and service packs

To install Ldifde.exe on the local computer

Click Start, Run, and in the Open field run 'ServerManagerCmd -i RSAT-ADDS'

2. Restart the Exchange Server

3. Try again

Active Directory Schema Extension Requires That Ldifde.exe be Installed

http://technet.microsoft.com/en-us/library/bb643109.aspx

Microsoft Exchange Server 2010 Release Candidate is now available

2009-08-18T12:24:00.001-03:00

As a participant in the Microsoft Exchange Server 2010 Beta experience, we invite you to download the new Exchange Server 2010 Release Candidate version. Now you can evaluate the release candidate product to simplify your IT environment and give you more control.

Resources delivered right when you need them.
You will have access to resources that will help you optimize your evaluation of Microsoft Exchange Server 2010 RC. Get started now to take advantage of the wealth of resources.

Download Microsoft Exchange Server 2010 RC today.

Microsoft Exchange Server 2010 Release Candidate

http://www.microsoft.com/downloads/details.aspx?FamilyID=c6d27da1-ba2c-4570-a491-c0d7b39ede8b&displaylang=en

Live Event – Windows 7 / Server 2008 R2 / Exchange 2010

2009-08-16T12:34:00.000-03:00

http://www.microsoft.com/business/thenewefficiency/default.aspx

SEE WHAT IT MEANS TO JOIN THE NEW EFFICIENCY

Windows 7

See how Windows 7 can help you reduce management costs and raise productivity as part of the Windows Optimized Desktop
Manage Risks through enhanced security and control
See new deployment tools with enhanced data protection, better control, automation and advanced image management

Windows Server 2008 R2

Dynamically provision and manage virtual workloads with Live Migration and System Center
Reduce energy costs with improved power management and policies for servers and clients
Improve productivity and lower costs for branch office and remote workers together with Windows 7

Exchange Server 2010

Simplify administration and deployment of your messaging platform
Lower IT costs with new archiving capabilities that combine advanced multi-mailbox search, granular retention polices, and more
Extend access to your messaging platform with mobility, voicemail, and the Internet

Office Communications Server 2007 R2 Web Scheduler

2009-08-14T15:26:00.000-03:00

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6d6848ec-e7d6-41f4-82d9-5bed3526fcbd

Brief Description

Office Communications Server 2007 R2 Web Scheduler provides a browser-based conference management experience for Office Communications Server 2007 R2.

Overview

Web Scheduler is a 64-bit tool for Microsoft Office Communications Server 2007 R2. It provides a Web-based alternative to the add-in for the Microsoft Outlook messaging and collaboration client for the purpose of scheduling a meeting using Office Communications Server 2007 R2. It also provides a browser-based conference management experience that includes operations such as:

Scheduling a new Live Meeting conference or conference call.
Viewing and modifying details of an existing conference.
Listing all existing user schedules of a Microsoft Office conference.
Deleting an existing conference.
Sending an e-mail invitation to conference participants by using a configured SMTP mail server.
Joining an existing conference.

Schema Versions

2009-08-12T22:15:00.000-03:00

Hi, thanks to my friend Brian Giannino I post this article that describe the steps to verify the Schema version and check if our platform is ready to deploy

Procedure

To find the current Active Directory Schema Version, you can use one of the following methods:

Note: The internal root domain that we use in this demo is: "domain.local".

1. Using "ADSIEdit.msc " or/and "LDP.exe" tools:Navigate to:
"CN=Schema,CN=Configuration,DC=domain,DC=local"
and review the current "objectVersion" attribute.

2. Using "DSQuery" command line:
"dsquery * cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr objectVersion"

The following information provide a mapping between the "objectVersion" attribute value, to
the Active Directory Schema commutability:

Windows 2000 Server	13
Windows Server 2003 RTM	30
Windows 2003 With Service Pack 1	30
Windows 2003 With Service Pack 2	30
Windows Server 2003 R2	31
Windows Server 2008 RTM	44

To find the current Exchange Schema Version, you can use one
of the following methods:
Note: The internal root domain that we use in this demo is: "domain.local".

1. Using "ADSIEdit.msc " or/and "LDP.exe" tools:
Navigate to:
"CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=domain,DC=local"
and review the current "rangeUpper" attribute.

2. Using "DSQuery" command line:
"dsquery * CN=ms-Exch-Schema-Version-Pt,cn=schema,cn=configuration,dc=domain,dc=local -scope base -attr
rangeUpper"
The following information provide a mapping between the "rangeUpper" attribute value, to

the Exchange Schema commutability:

ms-Exch-Schema-Version-Pt

Exchange Server 2000 RTM	4397
Exchange Server 2000 With Service Pack 3	4406
Exchange Server 2003 RTM	6870
Exchange Server 2003 With Service Pack 3	6936
Exchange Server 2007	10628
Exchange 2007 With Service Pack 1	11116

To verify check the PolicyTest.exe result

ms-RTC-SIP-SchemaVersion

LCS 2005 Sp1	1006
OCS 2007	1007
OCS R2	1008

to verify the state check this tool

lcscmd /domain:[fqdn] /action:CheckDomainPrepState.

Resources

How to find the current Schema Version

http://support.microsoft.com/kb/556086

Microsoft Desktop Energy Savings Calculator

2009-08-07T17:03:00.000-03:00

hi, in this new age of Green IT we talk about consolidation and virtualization options to our infrastructure, with this tool you can calculate and get a executive reports about the energy consume, CO2 emission and saved cost

http://www.microsoft.com/environment/greenit/

Desktop Energy Saving Calculator

OCS Remote Connectivity Analyzer

2009-08-03T14:51:00.000-03:00

Hi, today was unleashed the OCS Remote Connectivity Analyzer

https://www.testocsconnectivity.com/

Office Communication Server Remote Connectivity Test

This test will test your remote connectivity to the OCS Server.

Office Communication Server Remote Connectivity Test with AutoDiscover

This test will test your remote connectivity to the OCS Server, it will auto-discover the Access Edge and port to connect to.

Unified Communication Tutorial

2009-08-03T13:46:00.000-03:00

Hi , enjoy this excellent unified communication tutorial for free :)

http://www.microsoft.com/communicationsserver/enduser/tutorials/

MSExchange ADAccess Event ID: 2114

2009-08-02T20:17:00.000-03:00

Hi,

This error is often introduced at the Microsoft Exchange Server 2007 on Windows Server 2008 when you disable the IPv6 protocol installed by default.
The service MSEXCHANGEADTOPOLOGYSERVICE.EXE can not locate the DC and GC and failed to start , to fix this you must re-enable or disable IPv6 completely

Log Name:      Application

Source:           MSExchange ADAccess

Date:

Event ID:         2114

Task Category: Topology

Level:               Error

Keywords:      Classic

User:               N/A

Computer:      SERVER.DOMINIO.NET

Description:

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=2080). Topology discovery failed, error 0x80040a02 (DSC_E_NO_SUITABLE_CDC). Look up the Lightweight Directory Access Protocol (LDAP) error code specified in the event description. To do this, use Microsoft Knowledge Base article 218185, "Microsoft LDAP Error Codes." Use the information in that article to learn more about the cause and resolution to this error. Use the Ping or PathPing command-line tools to test network connectivity to local domain controllers.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

    <Provider Name="MSExchange ADAccess" />

    <EventID Qualifiers="49156">2114</EventID>

    <Level>2</Level>

    <Task>3</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="DATE-02T22:21:11.000Z" />

    <EventRecordID>16235</EventRecordID>

<Channel>Application</Channel>

    <Computer> SERVER.DOMINIO.NET </Computer>

<Security />

</System>

<EventData>

    <Data>MSEXCHANGEADTOPOLOGYSERVICE.EXE</Data>

    <Data>2080</Data>

    <Data>80040a02</Data>

    <Data>DSC_E_NO_SUITABLE_CDC</Data>

</EventData>

</Event>

to completely disable IPv6

Open Registry with "Regedit"

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters

Create a dword (32-bit) value and name it as "Disabled Components" and then click OK

Double click "Disabled Components" and type 0xffffffff(hexadecimal value) or 4294967295 (Decimal value)
Please note: The above value 0xffffffff(hexadecimal value) or 4294967295 (Decimal value) will disable all IPv6 components, except the IPv6 loopback interface.

IPv6 Support in Exchange 2007 SP1

http://technet.microsoft.com/en-us/library/bb629624.aspx

Security Explorer for Exchange - Quest Software

2009-07-21T01:12:00.000-03:00

hi,
I invite you to learn the new tool from Quest Software “Security Explorer for Exchange” for real-time verification of security and access permissions to objects of exchange

Real-time Management of Access Controls and Security in Exchange

ScriptLogic Security Explorer for Exchange™ is a powerful, graphical solution for real-time management of Exchange permissions that simplifies the burdensome task of managing security on Exchange.

Consolidates the backup and recovery of all Exchange objects for simpler restoration of permissions for an individual object or multiple objects
Searches for permissions on a very granular level
Manages permissions on mailbox folders such as Calendars, Contacts and Inbox folders without having to access the Outlook client
Reports on mailbox and public folder permissions by exporting data to an Excel spreadsheet for easy manipulation
Clones permissions from one account to another to avoid duplication of effort and potential errors
Demonstrates compliance with the ability to enforce security and manage access controls
Manages Exchange and Active Directory permissions from one, easy to use interface

Security Explorer for Exchange™ is part of a family of solutions to manage permissions and security across the entire Windows network. Check out:

Security Explorer for File Servers

Read the Datasheet (PDF)
Features and Benefits

Management Solutions

http://www.quest.com/unified-communications/management.aspx

Helps administrators detect problems in the messaging environment, quickly diagnose exactly where and what the problems are, and resolve the problems from a single, easy-to-use interface.

Reports on all Exchange, OCS, Windows Mobile and BlackBerry activity to enable the trending of system usage for proactive management.

Captures, indexes and stores messaging data transparently to end-users.

Item-level recovery from Exchange and Notes backups. Reduces the cost of e-discovery and provides end users with message-level data recovery services.

Protects organizations from external attacks, prevents intentional or inadvertent leaks of sensitive data, and enables IT to demonstrate compliance concerning the use of real-time communications.

Powerful, graphical solution for real-time management of Exchange permissions; simplifies the burdensome task of managing security on Exchange.

Troubleshooting Exchange 2007 Store Log/Database growth issues

2009-07-20T03:53:00.000-03:00

Hi, Mike Lagase published an excellent solution for logs and database showing an unexpected growth

http://blogs.technet.com/mikelag/archive/2009/07/12/troubleshooting-store-log-database-growth-issues.aspx

One of the common issues we see in support is excessive Database and/or Transaction log growth problems. If you have ever run in to one of these issues, you will find that they are not always easy to troubleshoot as there are many tools that are needed to help understand where the problem might be coming from. Customers have asked why does the Server allow these type of operations to occur in the first place and why is the Exchange Server not resilient to this? That is not always an easy question to answer as there as so many variables as to why this may occur in the first place ranging from faulty Outlook Add-ins, Custom or 3rd party applications, corrupted rules, corrupted messages, online maintenance not running long enough to properly maintain your database, and the list goes on and on.

Once an Outlook client has created a profile to the Exchange server, they pretty much have full reign to do whatever actions they want within that MAPI profile. This of course, will be controlled mostly by your Organizations mailbox and message size limits and some of the Client throttling or backoff features that are new to Exchange 2007.

Since I have dealt with these type problems in great detail, I thought it would be helpful to share some troubleshooting steps with you that may help you collect, detect and mitigate these problems when and if you should see them.

General Troubleshooting

Use Exchange User Monitor (Exmon) server side to determine if a specific user is causing the log growth problems.
- Sort on CPU (%) and look at the top 5 users that are consuming the most amount of CPU inside the Store process. Check the Log Bytes column to verify for this log growth for a potential user.
- If that does not show a possible user, sort on the Log Bytes column to look for any possible users that could be attributing to the log growth
- If it appears that the user in Exmon is a ?, then this is representative of a HUB/Transport related problem generating the logs. Query the message tracking logs using the Message Tracking Log tool in the Exchange Management Consoles Toolbox to check for any large messages that might be running through the system. See step 5.9 for a Powershell script to accomplish the same task.
If suspected user is found via Exmon, then do one of the following:
1. Disable the users AD account temporarily
2. Kill their TCP connection with TCPView
3. Call the client to have them close Outlook in the condition state for immediate relief.
If closing the client down seems to stop the log growth issue, then we need to do the following to see if this is OST or Outlook profile related:
1. Have the user launch Outlook while holding down the control key which will prompt if you would like to run Outlook in safe mode. If launching Outlook in safe mode resolves the log growth issue, then concentrate on what add-ins could be attributing to this problem.
2. If you can gain access to the users machine, then do one of the following:
  1. Launch Outlook to confirm the log file growth issue on the server.
  2. If log growth is confirmed, do one of the following
    1. Check users Outbox for any messages.
      1. If user is running in Cached mode, set the Outlook client to Work Offline. Doing this will help stop the message being sent in the outbox and sometimes causes the message to NDR.
      2. If user is running in Online Mode, then try moving the message to another folder to prevent Outlook or the HUB server from processing the message.
      3. After each one of the steps above, check the Exchange server to see if log growth has ceased
    2. Call Microsoft Product Support to enable debug logging of the Outlook client to determine possible root cause.
  3. Follow the Running Process Explorer instructions in the below article to dump out dlls that are running within the Outlook Process. Name the file username.txt. This helps check for any 3rd party Outlook Add-ins that may be causing the excessive log growth.
    970920 Using Process Explorer to List dlls Running Under the Outlook.exe Process
    http://support.microsoft.com/kb/970920
  4. Check the Sync Issues folder for any errors that might be occurring
3. Let’s attempt to narrow this down further to see if the problem is truly in the OST or something possibly Outlook Profile related:
  1. Run ScanPST against the users OST file to check for possible corruption.
  2. With the Outlook client shut down, rename the users OST file to something else and then launch Outlook to recreate a new OST file. If the problem does not occur, we know the problem is within the OST itself.
  3. If renaming the OST causes the problem to recur again, then recreate the users profile to see if this might be profile related.
Ask Questions:
1. Is the user using any type of mobile device?
2. Question the end user if at all possible to understand what they might have been doing at the time the problem started occurring. It’s possible that a user imported a lot of data from a PST file which could cause log growth server side or there was some other erratic behavior that they were seeing based on a user action.
If Exmon does not provide the data that is necessary to get root cause, then do the following:
1. Check current queues against all HUB Transport Servers for stuck or queued messages
  get-exchangeserver | where {$_.IsHubTransportServer -eq "true"} | Get-Queue | where {$_.Deliverytype –eq “MapiDelivery”} | Select-Object Identity, NextHopDomain, Status, MessageCount | export-csv HubQueues.csv
  Review queues for any that are in retry or have a lot of messages queued.
  Export out message sizes in MB in all Hub Transport queues to see if any large messages are being sent through the queues.
  get-exchangeserver | where {$_.ishubtransportserver -eq "true"} | get-message –resultsize unlimited | Select-Object Identity,Subject,status,LastError,RetryCount,queue,@{Name="Message Size MB";expression={$_.size.toMB()}} | sort-object -property size –descending | export-csv HubMessages.csv
  Export out message sizes in Bytes in all Hub Transport queues.
  get-exchangeserver | where {$_.ishubtransportserver -eq "true"} | get-message –resultsize unlimited | Select-Object Identity,Subject,status,LastError,RetryCount,queue,size | sort-object -property size –descending | export-csv HubMessages.csv
2. Check Users Outbox for any large, looping, or stranded messages that might be affecting overall Log Growth.
  
  get-mailbox -ResultSize Unlimited| Get-MailboxFolderStatistics -folderscope Outbox | Sort-Object Foldersize -Descending | select-object identity,name,foldertype,itemsinfolder,@{Name="FolderSize MB";expression={$_.folderSize.toMB()}} | export-csv OutboxItems.csv
  Note: This does not get information for users that are running in cached mode.
3. Utilize the MSExchangeIS Client\Jet Log Record Bytes/sec and MSExchangeIS Client\RPC Operations/sec Perfmon counters to see if there is a particular client protocol that may be generating excessive logs. If a particular protocol mechanism if found to be higher than other protocols for a sustained period of time, then possibly shut down the service hosting the protocol. For example, if Exchange Outlook Web Access is the protocol generating potential log growth, then stopping the World Wide Web Service (W3SVC) to confirm that log growth stops. If log growth stops, then collecting IIS logs from the CAS/MBX Exchange servers involved will help provide insight in to what action the user was performing that was causing this occur.
4. Run the following command from the Management shell to export out current user operation rates:
  To export to CSV File:
  
  get-logonstatistics |select-object username,Windows2000account,identity,messagingoperationcount,otheroperationcount,progressoperationcount,streamoperationcount,tableoperationcount,totaloperationcount | where {$_.totaloperationcount -gt 1000} | sort-object totaloperationcount -descending| export-csv LogonStats.csv
  To view realtime data:
  get-logonstatistics |select-object username,Windows2000account,identity,messagingoperationcount,otheroperationcount,progressoperationcount,streamoperationcount,tableoperationcount,totaloperationcount | where {$_.totaloperationcount -gt 1000} | sort-object totaloperationcount -descending| ft
  Key things to look for:
  In the below example, the Administrator account was storming the testuser account with email.
  You will notice that there are 2 users that are active here, one is the Administrator submitting all of the messages and then you will notice that the Windows2000Account references a HUB server referencing an Identity of testuser. The HUB server also has *no* UserName either, so that is a giveaway right there. This can give you a better understanding of what parties are involved in these high rates of operations
  UserName : Administrator
  Windows2000Account : DOMAIN\Administrator
  Identity : /o=First Organization/ou=First Administrative Group/cn=Recipients/cn=Administrator
  MessagingOperationCount : 1724
  OtherOperationCount : 384
  ProgressOperationCount : 0
  StreamOperationCount : 0
  TableOperationCount : 576
  TotalOperationCount : 2684
  UserName :
  Windows2000Account : DOMAIN\E12-HUB$
  Identity : /o= First Organization/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=testuser
  MessagingOperationCount : 630
  OtherOperationCount : 361
  ProgressOperationCount : 0
  StreamOperationCount : 0
  TableOperationCount : 0
  TotalOperationCount : 1091
5. Enable Perfmon/Perfwiz logging on the server. Collect data through the problem times and then review for any irregular activities. You can grab some pre-canned Perfmon import files at http://blogs.technet.com/mikelag/archive/2008/05/02/perfwiz-replacement-for-exchange-2007.aspx to make collecting this data easier.
6. Run ExTRA (Exchange Troubleshooting Assistant) via the Toolbox in the Exchange Management Console to look for any possible Functions (via FCL Logging) that may be consuming Excessive times within the store process. This needs to be launched during the problem period. http://blogs.technet.com/mikelag/archive/2008/08/21/using-extra-to-find-long-running-transactions-inside-store.aspx shows how to use FCL logging only, but it would be best to include Perfmon, Exmon, and FCL logging via this tool to capture the most amount of data.
7. Dump the store process during the time of the log growth. (Use this as a last measure once all prior activities have been exhausted and prior to calling Microsoft for assistance. These issues are sometimes intermittent, and the quicker you can obtain any data from the server, the better as this will help provide Microsoft with information on what the underlying cause might be.)
  1. Download the Current Release version of the Windows debuggers from http://www.microsoft.com/whdc/devtools/debugging/install64bit.mspx and select a custom installation and change the directory to install the debuggers to c:\debuggers and finish the installation.
  2. Open the command prompt and change in to the c:\Debuggers directory
  3. Type cscript adplus.vbs –hang –pn store –quiet –o d:\DebugData. Note: -o switch signifies the location in which you want to store the debug data that has sufficient drive space. Important: Once this has launched, a minimized CDB window will open. Please wait for this to complete and do not close this window as this will disappear once the dump has completed.
  4. Wait 2 minutes and perform the same dump operation again.
  5. Open a case with Microsoft Product Support Services to get this data looked at.
8. Collect a portion of Store transaction log files (100 would be good) during the problem period and parse them following the directions in http://blogs.msdn.com/scottos/archive/2007/11/07/remix-using-powershell-to-parse-ese-transaction-logs.aspx to look for possible patterns such as high pattern counts for IPM.Appointment. This will give you a high level overview if something is looping or a high rate of messages being sent. Note: This tool may or may not provide any benefit depending on the data that is stored in the log files, but sometimes will show data that is MIME encoded that will help with your investigation
9. Export out Message tracking log data from affected MBX server
  Method 1
  Download the attached ExLogGrowthCollector.zip file to this post and extract to the MBX server that experienced the issue. Run ExLogGrowthCollector.ps1 from the Exchange Management Shell. Enter in the MBX server name that you would like to trace, the Start and End times and click on the Collect Logs button.
  
  Note: What this script does is to export out all mail traffic to/from the specified mailbox server across all HUB servers between the times specified. This helps provide insight in to any large or looping messages that might have been sent that could have caused the log growth issue.
  Method 2
  Copy/Paste the following data in to notepad, save as msgtrackexport.ps1 and then run this on the affected Mailbox Server. Open in Excel for review. This is similar to the GUI version, but requires manual editing to get it to work.
  
  #Export Tracking Log data from affected server specifying Start/End Times
  Write-host "Script to export out Mailbox Tracking Log Information"
  Write-Host "#####################################################"
  Write-Host
  $server = Read-Host "Enter Mailbox server Name"
  $start = Read-host "Enter start date and time in the format of MM/DD/YYYY hh:mmAM"
  $end = Read-host "Enter send date and time in the format of MM/DD/YYYY hh:mmPM"
  $fqdn = $(get-exchangeserver $server).fqdn
  Write-Host "Writing data out to csv file..... "
  Get-ExchangeServer | where {$_.IsHubTransportServer -eq "True" -or $_.name -eq "$server"} | Get-MessageTrackingLog -ResultSize Unlimited -Start $start -End $end | where {$_.ServerHostname -eq $server -or $_.clienthostname -eq $server -or $_.clienthostname -eq $fqdn} | sort-object totalbytes -Descending | export-csv MsgTrack.csv -NoType
  Write-Host "Completed!! You can now open the MsgTrack.csv file in Excel for review"
  
  Method 3
  You can also use the Process Tracking Log Tool at http://msexchangeteam.com/archive/2008/02/07/448082.aspx to provide some very useful reports.
10. Save off a copy of the application/system logs from the affected server and review them for any events that could attribute to this problem
11. Enable IIS extended logging for CAS and MB server roles to add the sc-bytes and cs-bytes fields to track large messages being sent via IIS protocols and to also track usage patterns.

Proactive monitoring and mitigation efforts

Increase Diagnostics Logging for the following objects depending on what stores are being affected:
- MSExchangeIS\Mailbox\Rules
- MSExchangeIS\PublicFolders\Rules
Enable Client Side monitoring per http://technet.microsoft.com/en-us/library/cc540465.aspx
Create a monitoring plan using MOM/SCOM to alert when the amount of Log Bytes being written hit a specific threshold and then alert the messaging team for further action. There are thresholds that are a part of the Exchange 2007 Management Pack that could help alert to these type situations before the problem gets to a point of taking a database offline. Here are 2 examples of this.
ESE Log Byte Write/sec MOM threshold
Warning Event
http://technet.microsoft.com/en-us/library/bb218522.aspx
Error Event
http://technet.microsoft.com/en-us/library/bb218733.aspx
If an alert is raised, then perform an operation to start collecting data.
Ensure http://support.microsoft.com/kb/958701 is installed at a minimum for each Outlook 2003 client to address known log/database growth issues for users streaming data to the information store that have exceeded message size limits. This fix also addresses a problem where clients could copy a message to their inbox from a PST that during the sync process could exceed mailbox limits, thus causing excessive log growth problems on the server.
These hotfixes make use of the PR_PROHIBIT_SEND_QUOTA and PR_MAX_SUBMIT_MESSAGE_SIZE which is referenced in http://support.microsoft.com/kb/894795

Additional Outlook Log Growth fixes:
http://support.microsoft.com/kb/957142
http://support.microsoft.com/kb/936184
Implement minimum Outlook Client versions that can connect to the Exchange server via the Disable MAPI clients registry key server side. See http://technet.microsoft.com/en-us/library/bb266970.aspx for more information.
To disable clients less than Outlook 2003 SP2, use the following entries on an Exchange 2007 server
"-5.9.9;7.0.0-11.6568.6567"
Setting this to exclude Outlook client versions less than Outlook 2003 SP2 will help protect against stream issues to the store. Reason being is that Outlook 2003 SP2 and later understand the new quota properties that were introduced in to the store in http://support.microsoft.com/kb/894795. Older clients have no idea what these new properties are, so if a user sent a 600MB attachment on a message, it would stream the entire message to the store generating excessive log files and then get NDR’ed once the message size limits were checked. With SP2 installed, the Outlook client will first check to see if the attachment size is over the set quota for the organization and immediately stop the send with a warning message on the client and prevent the stream from being sent to the server.

Allowing any clients older than SP2 to connect to the store is leaving the Exchange servers open for a growth issue.
If Entourage clients are being utilized, then implement the MaxRequestEntityAllowed property in http://support.microsoft.com/kb/935848 to address a known issue where sending a message over the size limit could potentially create log growth for a database.
Check to ensure File Level Antivirus exclusions are set correctly for both files and processes per http://technet.microsoft.com/en-us/library/bb332342.aspx
Enable Content Conversion tracing on all HUB servers per http://technet.microsoft.com/en-us/library/bb397226.aspx . This will help log any failed conversion attempts that may be causing the log growth problem to occur.
If POP3 or IMAP4 clients are connecting to specific servers, then implementing Protocol Logging for each on the servers that may be making use of these protocols will help log data to a log file where these protocols are causing excessive log growth spurts. See http://technet.microsoft.com/en-us/library/aa997690.aspx on how to enable this logging.
Ensure Online maintenance is completing a pass for each database within the past week or two. Query Application event logs for the ESE events series 700 through 704 to clarify. If log growth issues occur during online maintenance periods, this could be normal as Exchange shuffles data around in the database. We just need to ensure that we keep this part in mind during these log growth problems.
Check for any excessive ExCDO warning events related to appointments in the application log on the server. (Examples are 8230 or 8264 events). http://support.microsoft.com/kb/947014 is just one example of this issue. If recurrence meeting events are found, then try to regenerate calendar data server side via a process called POOF. See http://blogs.msdn.com/stephen_griffin/archive/2007/02/21/poof-your-calender-really.aspx for more information on what this is.
Event Type: Warning
Event Source: EXCDO
Event Category: General
Event ID: 8230
Description: An inconsistency was detected in username@domain.com: /Calendar/<calendar item> .EML. The calendar is being repaired. If other errors occur with this calendar, please view the calendar using Microsoft Outlook Web Access. If a problem persists, please recreate the calendar or the containing mailbox.
Event Type: Warning
Event ID : 8264
Category : General
Source : EXCDO
Type : Warning
Message : The recurring appointment expansion in mailbox <someone's address> has taken too long. The free/busy information for this calendar may be inaccurate. This may be the result of many very old recurring appointments. To correct this, please remove them or change their start date to a more recent date.
Important: If 8230 events are consistently seen on an Exchange server, have the user delete/recreate that appointment to remove any corruption
Add additional store logging per http://support.microsoft.com/kb/254606 to add more performance counter data to be collected with Perfmon. This will allow us to utilize counters such as ImportDeleteOpRate and SaveChangesMessageOpRates which allows us to see what these common log growth rates are.
Recommend forcing end dates on recurring meetings. This can be done through the usage of the registry key DisableRecurNoEnd (DWORD).
For Outlook 2003:
http://support.microsoft.com/kb/952144
HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Preferences
For Outlook 2007:
http://support.microsoft.com/kb/955449
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Preferences
Value: 1 to Enable, 0 to Disable
Implement LimitEmbeddingDepth on the Exchange servers as outlined in KB 833607 to prevent log growth due to recursion looping. Note: This article states this if for Exchange 2000-2003, but the key is also still valid in Exchange 2007 per source code

Known Issues

Exchange Server
Release Update 9 fixes

959559 - Transaction log files grow unexpectedly in an Exchange Server 2007 Service Pack 1 mailbox server on a computer that is running Windows Server 2008

925252 - The Store.exe process uses almost 100 percent of CPU resources, and the size of the public folder store increases quickly in Exchange Server 2007

961124 - Some messages are stuck in the Outbox folder or the Drafts folder on a computer that is running Exchange Server 2007 Service Pack 1

970725 - Public folder replication messages stay in the local delivery queue and cause an Exchange Server 2007 Service Pack 1 database to grow quickly

Release Update 8 fixes

960775 - You receive a "Message too large for this recipient" NDR that has the original message attached after you restrict the Maximum Message Send Size value in Exchange Server 2007

Release Update 7 fixes

957124 - You do not receive an NDR message even though your meeting request cannot be sent successfully to a recipient

960775 - You receive a "Message too large for this recipient" NDR that has the original message attached after you restrict the Maximum Message Send Size value in Exchange Server 2007

Release Update 1 fixes

947014 - An Exchange Server 2007 mailbox server randomly generates many transaction logs in an Exchange Server 2007 Service Pack 1 environment
Outlook 2007

970944 – Installing this hotfix package addresses and issue where log files are generated unexpectedly when a user is running Outlook 2007 in the cached Exchange mode and sends an e-mail message to the recipients who have a corrupted e-mail address and/or e-mail address

Outlook 2003

958701 - Description of the Outlook 2003 Post-Service Pack 3 hotfix package (Engmui.msp, Olkintl.msp, Outlook.msp): October 28, 2008

936184 - Description of the Outlook 2003 post-Service Pack 3 hotfix package: December 14, 2007

897247 - Description of the Microsoft Office Outlook 2003 post-Service Pack 1 hotfix package: May 2, 2005

Entourage

935848 - Various performance issues occur when you use Entourage for Mac to send large e-mail messages to an Exchange 2007 server

Update Rollup 9 for Microsoft Exchange Server 2007 SP 1

2009-07-17T16:03:00.000-03:00

hi, few hours ago was released the rollup 9 for Microsoft Exchange Server 2007 Service Pack 1

http://support.microsoft.com/kb/970162

Download

Download the Exchange2007-KB970162-EN package now.

Issues that the update rollup fixes

Update Rollup 9 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

943073 (http://support.microsoft.com/kb/943073/ ) An image attachment appears as a red "X" when you send an RTF e-mail message from an Exchange Server 2007 organization to an external recipient
945877 (http://support.microsoft.com/kb/945877/ ) The "eseutil /k" command takes a long time to verify the checksum of transaction logs in Exchange Server 2007 Service Pack 1
947662 (http://support.microsoft.com/kb/947662/ ) The transport rule "when the Subject field or the body of the message contains text patterns" does not work accurately on an Exchange Server 2007 Service Pack 1-based computer
954739 (http://support.microsoft.com/kb/954739/ ) The Exchange Impersonation feature does not work if a cross-forest topology has only a one-way trust relationship between forests in Exchange Server 2007 Service Pack 1
957137 (http://support.microsoft.com/kb/957137/ ) The reseed process is unsuccessful on the CCR passive node after you restore one full backup and two or more differential backups to the CCR active node in Exchange Server 2007 Service Pack 1
957374 (http://support.microsoft.com/kb/957374/ ) The Microsoft Exchange Replication service on a Standby Continuous Replication (SCR) target server continually crashes when you enable SCR for a storage group on an Exchange Server 2007 Service Pack 1-based computer
959559 (http://support.microsoft.com/kb/959559/ ) Transaction log files grow unexpectedly in an Exchange Server 2007 Service Pack 1 mailbox server on a computer that is running Windows Server 2008
961124 (http://support.microsoft.com/kb/961124/ ) Some messages are stuck in the Outbox folder or the Drafts folder on a computer that is running Exchange Server 2007 Service Pack 1
961544 (http://support.microsoft.com/kb/961544/ ) Mobile users whose location is set to New Zealand cannot synchronize an exceptional occurrence after the daylight saving time (DST) update that is described in KB 951072 is installed on an Exchange 2007 Service Pack 1 Client Access server (CAS)
961551 (http://support.microsoft.com/kb/961551/ ) An error message is returned when you run the Get-Recipient command in the Exchange Management Shell that uses a Windows 7 domain controller
963679 (http://support.microsoft.com/kb/963679/ ) The Update-Recipient command does not update specified domain controller parameters when you use Identity Lifecycle Manager (ILM) 2007 to migrate mail users to mailbox users in Exchange Server 2007 Service Pack 1
967479 (http://support.microsoft.com/kb/967479/ ) Entourage clients cannot synchronize with mailboxes that are located on a computer that is running Exchange 2007 Service Pack 1 and Windows Server 2008
967525 (http://support.microsoft.com/kb/967525/ ) Error 4 is returned when you synchronize a supported list of contact properties by using Exchange ActiveSync in Exchange Server 2007 Service Pack 1
967605 (http://support.microsoft.com/kb/967605/ ) A non-delivery report (NDR) is returned when a user sends an e-mail message to an X.400 address that includes the slash field separator in Exchange Server 2007 Service Pack 1
967676 (http://support.microsoft.com/kb/967676/ ) E-mail address properties of contacts changed through Exchange Web Services (EWS) are not updated in Outlook or Outlook Web Access (OWA) in Exchange Server 2007 Service Pack 1
967739 (http://support.microsoft.com/kb/967739/ ) If a sender requests a delivery receipt in an e-mail message, a delivery status notification (DSN) message is returned that has a blank subject in the body even though the original message contains a subject in Exchange Server 2007 Service Pack 1
968081 (http://support.microsoft.com/kb/968081/ ) Monthly recurring meetings are declined if the "Schedule only during working hours" option is enabled in Exchange Server 2007 Service Pack 1
968106 (http://support.microsoft.com/kb/968106/ ) Outlook clients are directed to global catalogs from the wrong domain if you are using a split session configuration to enable Outlook clients to access their mailboxes through an RPC/HTTP proxy server in Exchange Server 2007 Service Pack 1
968111 (http://support.microsoft.com/kb/968111/ ) Event ID 4999 is logged when an administrator deletes a mailbox store on an Exchange Server 2007 Service Pack 1-based server
968205 (http://support.microsoft.com/kb/968205/ ) The Microsoft Exchange Information Store service crashes every time that a specific database is mounted on a computer that is running Exchange Server 2007 Service Pack 1
968224 (http://support.microsoft.com/kb/968224/ ) You still receive unexpected error messages when you run the Test-OwaConnectivity command or the Test-ActiveSyncConnectivity command after you apply hotfix KB954213 on an Exchange 2007 Service Pack 1-based server
968322 (http://support.microsoft.com/kb/968322/ ) An HTTP 500 error message is returned when you send a message that has a large attachment by using Outlook Web Access (OWA) with S/MIME installed in Exchange Server 2007 Service Pack 1
968350 (http://support.microsoft.com/kb/968350/ ) When you change the location field of a recurring calendar item to empty in Exchange Server 2007 Service Pack 1, the location field is set to the default value of the recurring series if this recurring item is synchronized on a Windows Mobile device
968621 (http://support.microsoft.com/kb/968621/ ) The Microsoft Exchange Information Store service crashes when you use a Data Protection Manager (DPM) 2007 server to perform a snapshot backup for an Exchange Server 2007 Service Pack 1 server
968626 (http://support.microsoft.com/kb/968626/ ) Event ID 1009 is logged when you use an application to access a shared mailbox by using the POP3 protocol in Exchange Server 2007 Service Pack 1
968651 (http://support.microsoft.com/kb/968651/ ) Exchange Server 2007 Service Pack 1 servers continue to contact a domain controller even after you exclude it by using the Set-ExchangeServer command
968715 (http://support.microsoft.com/kb/968715/ ) Both public logons and private logons that connect to a Client Access server (CAS) proxy are processed as private logons on an Exchange Server 2007 Service Pack 1-based server
969054 (http://support.microsoft.com/kb/969054/ ) Error message after an Exchange Server 2007 Service Pack 1 user replies to a message that has more than 300 recipients in Outlook Web Access (OWA): "Microsoft Exchange issued an unexpected response (500)"
969089 (http://support.microsoft.com/kb/969089/ ) Some databases are not mounted on the target server after you use the Move-ClusteredMailboxServer command to transfer a clustered mailbox server (CMS) to an available passive cluster node in Exchange Server 2007 Service Pack 1
969129 (http://support.microsoft.com/kb/969129/ ) HTML e-mail messages that have a charset META tag that differs from the MIME charset tag are garbled when they are processed through disclaimer rules in Exchange Server 2007 Service Pack 1
969324 (http://support.microsoft.com/kb/969324/ ) Outlook crashes when you try to use Outlook to view e-mail messages that are arranged by subject in Exchange Server 2007 Service Pack 1
969436 (http://support.microsoft.com/kb/969436/ ) You cannot log on to a hidden mailbox by using Base64 authentication for IMAP4 or for POP3 in an Exchange Server 2007 Service Pack 1 environment
969838 (http://support.microsoft.com/kb/969838/ ) An error message is returned when a user tries to change a recurring appointment in Office Outlook Web Access that was created in Outlook 2007 in Exchange Server 2007 Service Pack 1
969911 (http://support.microsoft.com/kb/969911/ ) Mailboxes do not follow E-mail Lifecycle (ELC) configuration or storage limitation policies in Exchange Server 2007 Service Pack 1
969943 (http://support.microsoft.com/kb/969943/ ) Memory leaks occur in the Powershell.exe process when you run the Get-MailboxStatistics command and the Get-PublicFolderStatistics command in Exchange Server 2007 Service Pack 1
969969 (http://support.microsoft.com/kb/969969/ ) Error message when an Exchange Server 2007 Service Pack 1 user tries to delete a calendar item in OWA: "Outlook Web Access has encountered a Web browsing error"
970028 (http://support.microsoft.com/kb/970028/ ) The Store.exe process crashes when you use a WebDAV application to connect to Exchange Server 2007 Service Pack 1
970086 (http://support.microsoft.com/kb/970086/ ) Exchange Server 2007 Service Pack 1 crashes when the Extensible Storage Engine (ESE) version store is out of memory on a computer that is running Windows Server 2008
970277 (http://support.microsoft.com/kb/970277/ ) The System Attendant (SA) resource is not brought online or offline during a failover in an Exchange 2007 Service Pack 1 cluster environment
970444 (http://support.microsoft.com/kb/970444/ ) A move operation between an Exchange Server 2003-based server and an Exchange Server 2007 Service Pack 1-based server fails if the SimpleDisplayName attribute of a mailbox in the Exchange Server 2003-based server contains a single quotation mark
970515 (http://support.microsoft.com/kb/970515/ ) You receive an error message when you try to use the "New-Mailbox" command to create more than 1000 users who have the same “mailNickname” attribute (alias) in Exchange Server 2007 Service Pack 1
970526 (http://support.microsoft.com/kb/970526/ ) The EdgeTransport.exe process on a computer that is running Exchange Server 2007 Service Pack 1 crashes when a MIME message that contains iCAL items for a recurring meeting has more than 999 occurrences
970725 (http://support.microsoft.com/kb/970725/ ) Public folder replication messages stay in the local delivery queue and cause an Exchange Server 2007 Service Pack 1 database to grow quickly
970993 (http://support.microsoft.com/kb/970993/ ) Error message when a user tries to perform an address book search by using Outlook Web Access in an Exchange Server 2007 Service Pack 1 environment: “The item that you attempted to access appears to be corrupted and cannot be accessed.”

Infrastructure Planning and Design Guides for Windows Server 2008 R2 — Now Available!Infrastructure Planning and Design Guides for Windows Server 2008 R2 — Now Available!

2009-07-16T18:06:00.000-03:00

Infrastructure Planning and Design Guides for Windows Server 2008 R2 — Now Available!
Updated to reflect new features and capabilities available in Windows Server 2008 R2, these guides outline the critical design elements that are crucial to a successful implementation. Updated guides include Active Directory Domain Services, Internet Information Services 7.5, File Services, and Print Services. Download the guides individually, or the entire IPD Guide Series today and streamline your design processes for Windows Server 2008 R2!

IPD One-click Downloads

IPD Guides for Virtualization

IPD Guides for Windows Server

IPD Guides for System Center

IPD Guides for Other Topics

Webcast / Overcoming Exchange Failures - Insights from an Industry Expert

2009-07-13T10:00:00.000-03:00

PRE-REGISTER FOR WEBCAST:
http://go.techtarget.com/r/8674620/8630994

Date and time:
Tuesday, July 21, 2009 8:00 am
Pacific Daylight Time (GMT -07:00, San Francisco)
Change time zone

Tuesday, July 21, 2009 10:00 am
Central Daylight Time (GMT -05:00, Chicago)

Tuesday, July 21, 2009 11:00 am
Eastern Daylight Time (GMT -04:00, New York)

Tuesday, July 21, 2009 4:00 pm
GMT Daylight Time (GMT +01:00, London)

Duration:
1 hour

Description:
Paul Robichaux, Exchange MVP and author of multiple books on Exchange management, integration, and security, will share his expert insight and provide guidelines for Exchange protection and recovery to address common challenges such as over-running Exchange backup windows and media failures as well as less common but potentially devastating failures such as database corruption and loss of an entire Exchange Server.

Publish Exchange 2007 OWA via ISA with RSA TOKEN

2009-07-12T03:25:00.001-03:00

Few days ago, I perform the configuration for publishing OWA through ISA Server 2006 with a RADIUS authentication to use a RSA Token and use this post from Elan Shudnow to do it.

Procedure:

http://www.shudnow.net/2009/07/01/exchange-2007-owa-via-isa-rsa-authentication-delegation/

When utilizing ISA (in this case, ISA 2006) to publish Outlook Web Access (OWA), there are various options you can choose from in order to authenticate a user. One listener authentication mechanism that is often used is Forms Based Authentication. By default, your ISA form when publishing OWA will look like the following:

As you can see, by default, it asks you for Domain\User name. By going into the listener authentication options, you can specify the default domain that should be specified if the user does not specify a domain. Without specifying this, if the user were to only enter their user name, authentication would fail as it is not passing the domain back to Exchange. By going into the properties of your OWA listener, you will see an Authentication tab.

Because we will be utilizing RSA, we will choose RSA as the method of Authentication utilizing Forms Based. Because Exchange isn’t set to also authenticate to RSA (only ISA), we will need to collect additional information in the form. This allows a user to also enter their AD credentials so after ISA authenticates a user, ISA can still pass back the AD credentials back to Exchange as the Authentication Delegation mechanism using Basic. Selecting to Collect dditional delegation credentials in the form allows you to utilize either Basic, NTLM, or Negotiate as an Authentication Delegation mechanism.

By clicking on Advanced, we can see the section in which we can configure the domain to automatically pass back to Exchange during the Authentication Delegation. Again, a user authenticates from a browser to a web listener and from there, ISA then takes certain information about the user and passes that back to Exchange which is the Authentication Delegation piece.

But, as you can see, the Domain name piece is greyed out. But if you look at the authentication form for ISA when RSA is enabled, you can see it doesn’t ask for the Domain Name.

Now because of this, if a user doesn’t specify to use a different user name which does allow you to enter a domain\username, the authentication delegation piece will fail as the basic authentication mechanism that you will set on Exchange will want a domain\username passed back. So if we can’t set this in ISA, how do we set it? Well, we can actually configure IIS to automatically assume a specific domain to be used if no domain is specified. While IIS6 and IIS7 are very much different, you can actually utilize the Exchange Management Console to set this option which will stamp IIS appropriately (both IIS6 and IIS7.)

The default authentication option for OWA on a CAS is to use Forms Based Authentication and require a user to specify their domain.

If you specify the following option, choose your domain, and click Apply, it will stamp IIS to assume the specified domain name. A user can still specify their domain or not specify it and both will work when authenticating. This should hopefully make you realize that if ISA relays authentication back to IIS on the CAS, that it won’t matter anymore if the domain is specified or not.

But because our ISA Authentication Delegation for our OWA rule will utilize Basic Authentication, we now want to specify Basic Authentication within Exchange for OWA. But don’t worry, even if you change it from the previous setting of Forms Based Authentication with the assumed domain, IIS will still stay stamped properly. So go ahead and choose Basic. You will be prompted to do an IISReset -Noforce. Go ahead and do it after choosing Basic.

So back over to ISA, if we go into our Outlook Rule, we can see the Authentication Delegation set to Basic which it will need to be since that’s what the Authentication option is set to for OWA on our CAS.

So taking everything into account what we did above, what happens is the user authenticates to ISA utilizing a form and specifies their username without the domain, RSA key, and password for their username. When they click Log On to authenticate, ISA will authenticate the user with RSA, and when that passes, ISA will utilize basic authentication due to the authentication delegation being set to basic to pass the username and password they specified (with no domain) back to OWA. Because IIS is stamped to automatically utilize the domain even if it wasn’t specified, authentication will work and the user will be logged into OWA.

Resources:

Outlook Web Access Server Publishing in ISA Server 2004: RADIUS and Forms-based Client Authentication

http://technet.microsoft.com/en-us/library/cc302660.aspx

Enabling RADIUS authentication for the OWA Forms-Based Authentication in ISA Server 2004

http://support.microsoft.com/kb/884560

Webcast / Exchange, OCS , UC

2009-07-03T19:51:00.001-03:00

hello, I invite you to participate in this webcast series

Webcast TechNet: Introducción a Exchange Server 2007 Id. de evento: 1032420897 Registrarse Idiomas: Español. Productos: Microsoft Exchange Server 2007. Audiencia(s): Profesional de IT. Moderador(es): Andrés Lozada Duración: 60 Minutos Fecha de Inicio: miércoles, 14 de octubre de 2009 04:00 p.m. Bogotá

Webcast TechNet: Como migrar a Exchange Server 2007 Id. de evento: 1032420899 Registrarse Idiomas: Español. Productos: Microsoft Exchange Server 2007. Audiencia(s): Profesional de IT. Moderador(es): Andrés Lozada Duración: 60 Minutos Fecha de Inicio: miércoles, 28 de octubre de 2009 04:00 p.m. Bogotá

Webcast TechNet: Introducción a Mensajería Unificada Id. de evento: 1032420901 Registrarse Idiomas: Español. Productos: Microsoft Exchange Server 2007,Microsoft Office Communications Server Audiencia(s): Profesional de IT. Moderador(es): Andrés Lozada Duración: 60 Minutos Fecha de Inicio: miércoles, 11 de noviembre de 2009 04:00 p.m. Bogotá

Webcast TechNet: Descripción general de Exchange 2010 Id. de evento: 1032420904 Registrarse Idiomas: Español. Productos: Microsoft Exchange Server 2010. Audiencia(s): Profesional de IT. Moderador(es): Andrés Lozada Duración: 60 Minutos Fecha de Inicio: miércoles, 25 de noviembre de 2009 04:00 p.m. Bogotá

OCS / Migrating Global Settings Container

2009-06-19T14:47:00.000-03:00

Important:

If you decide to migrate your global settings to the Configuration container and you plan to migrate from a prior version of Office Communications Server to Office Communications Server 2007 R2, you must perform the global settings migration first. Once you upgrade to the Office Communications Server 2007 R2 Active Directory schema, you can no longer use this tool to migrate your global settings.

You can migrate global settings in the following scenarios:

Live Communications Server 2005 with SP1, System container to Configuration container

Important:

For Live Communications Server 2005 with SP1, you can store global settings in the Configuration container only if you apply Windows update provided in the Microsoft Knowledge Base article 911996. For details, see Knowledge Base article 911996, "Description of the update for Live Communications Server 2005: February 10, 2006, rereleased July 11, 2006," at http://go.microsoft.com/fwlink/?LinkId=132177.

Office Communications Server 2007, System container to Configuration container

Migrating global settings involves the following seven steps:

Copying the tree structure to the Configuration container.
Copying the global settings attributes.
Running forest preparation and, for Live Communications Server 2005 with SP1, also running domain preparation to set permissions.
Updating distinguished name (DN) references to the global settings tree.
Updating msRTCSIP-PrimaryHomeServer DN references for user, contact, and inetOrgPerson objects.
Verifying that the migration was successful.
Removing the original global settings tree structure from the System container in the root domain.

1. Migrating the Tree Structure

The MigrateGlobalSettingsTree action of the MigrateOcsGlobalSettings command copies the global settings tree structure from the System container to the Services sub-container in the Configuration container. This step does not copy the global settings attributes because the new hierarchy must fully replicate before the DN references stored in some attributes can succeed.

Membership in the EnterpriseAdmins or DomainAdmins group for the forest root domain is required to perform this step.

This step is complete when the global settings tree structure is successfully copied to the Configuration container and replication is complete.

2. Copying Global Settings Attributes

The MigrateGlobalSettingsProperties action of the MigrateOcsGlobalSettings command copies the Office Communications Server global settings attributes from the original tree structure to the corresponding nodes of the new tree built in the previous step.

For DN references stored in attributes, the DN is changed to point to the Configuration container.

Membership in the EnterpriseAdmins or DomainAdmins group for the forest root domain is required to perform this step.

This step is complete when all attributes are copied to the new global settings tree and replication is complete.

Caution:

It is critical that replication completes before you proceed to step 3.

3. Setting Permissions

Once the tree structure and global settings attributes are successfully copied, the next step is to set up the Access Control Entries (ACEs) that allow the Office Communications Server service to access the new global settings tree.

For both Office Communications Server 2007 and Live Communications Server 2005 with SP1, the ForestPrep action of the Lcscmd.exe command-line tool sets up the permissions. You must run the forest preparation step again to create the ACEs for administrators and for Office Communications Server services and to validate the new global settings tree. You cannot use the Prep Forest wizard for this migration step. For details about forest preparation for Office Communications Server 2007, see the Office Communications Server 2007 Active Directory Guide.

Important:

You must use the Live Communications Server 2005 or the Office Communications Server 2007 version of LcsCmd.exe to perform this step. You must not use the Office Communications Server 2007 R2 version of LcsCmd.exe.

For Live Communications Server 2005 with SP1, you must also run domain preparation. In Live Communications Server 2005 with SP1, domain global groups control domain access. Most global settings permissions are created by either the DomainPrep or the DomainAdd action of the Lcscmd.exe command-line tool. Because global settings are located on every domain controller after deployment, it is not necessary to rerun DomainAdd. Therefore, rerunning DomainPrep for each Live Communications Server 2005 domain is sufficient to create the ACEs for the new global settings tree. For details about the domain preparation step for Live Communications Server 2005, see Live Communications Server 2005 with SP1: All Technical Documents.

Membership in the EnterpriseAdmins or DomainAdmins group for the forest root domain is required to perform this step.

This step is complete when all permissions have been created for the new global settings tree, and the new global settings tree is replicated to forest global catalogs. Depending on the topology and replication configuration, full replication can take anywhere from minutes to days.

4. Updating DN References to the Global Settings Tree

Once the new global settings tree is replicated, all server DN references to the global settings tree must be modified to point to the Configuration container for the following server roles:

Front End Servers
Conferencing Servers
Web Components Servers
Mediation Servers

Membership in the RTCUniversalServerAdmins or RTCUniversalUserAdmins group is required to perform this step.

This step is complete when all DN references for all the server roles mentioned above point to the new global settings tree.

5. Updating msRTCSIP-PrimaryHomeServer DN References

The final migration step is to modify all user DN references to the global settings tree to point to the Configuration container. This step modifies the msRTCSIP-PrimaryHomeServer and msRTCSIP-UserPolicy attributes to point to the objects in the new location.

Membership in the RTCUniversalServerAdmins or RTCUniversalUserAdmins group is required to perform this step.

This step is complete when all user DN references point to the new global settings tree. Depending on the number of enabled users and their geographical location, this step might take the longest time to run (for example, with stable network connectivity, it takes about one hour to migrate 30,000 users).

6. Verifying that Migration Is Successful

After completing the previous five steps, it is recommended that you test the migration by performing some instant messaging and conferencing to verify that the new global settings tree is working properly.

7. Removing Global Settings Tree from the System Container

When you are sure that the migration was successful, remove the original global settings tree from the System container.

Microsoft Office Communications Server 2007 Global Settings Migration Tool http://www.microsoft.com/downloads/details.aspx?FamilyID=23236784-508e-44c9-809d-30ff245928d8&DisplayLang=en

Remove Live Communications Server 2005 with SP1 Enterprise Edition

2009-06-08T19:56:00.000-03:00

For each server in the pool, deactivate and then remove the files.

Important

Before you begin this process, verify that no users are still assigned to the pool.

Use the following procedures to uninstall Live Communications Server 2005 with SP1 Standard Edition. This involves the following tasks:

Deactivating each server in the Enterprise pool.
Removing the files on all but the last server in the pool.
Removing the Enterprise pool.

To deactivate a server in the Enterprise pool

Log on as a member of the DomainAdmins group to a Live Communications Server that is a member of the same domain as the Live Communications Server 2005 with SP1 Enterprise Edition server that you are deactivating. If the domain is a child domain, you must also be logged on as a member of the RTCDomainServerAdmins group. The Standard Edition server can be anywhere in the enterprise, as long as it is joined to a domain and the user has the necessary group memberships. You can also perform this task from a domain member server that has the Live Communications Server 2005 with SP1 administrative snap-in installed.
Open the Live Communications Server 2005 with SP1 snap-in: Click Start, point to All Programs, point to Administrative Tools, and then click Live Communications Server 2005.
In the console tree, expand Live Communications Server 2005 with SP1.
Expand subsequent nodes under the Domains node until you reach the domain in which the server or pool resides.
Expand Live Communications servers and pools.
Right-click the FQDN of the server, and then click Deactivate.

To remove the Live Communications Server files on all but the last server in the pool

Log on to the Live Communications Server 2005 with SP1 server as a member of the Administrators group.
Click Start, point to Control Panel, and then click Add or Remove Programs.
In Add or Remove Programs, click Live Communications Server 2005 with SP1, and then click Change.
In the Setup Wizard, click Next.
On the Program Maintenance page, confirm that the action is set to Remove, and then click Next.

Remove the Enterprise pool only after you have deactivated and removed the files from all but one server in the pool. Do not remove a pool unless you are certain that the pool is no longer used by any servers or users. After you remove this pool, you must delete its configuration from the load balancer.

To remove a pool

Log on as a member of the RTCDomainServerAdmins group to a Live Communications Server that is a member of the same domain as the Enterprise pool that you are removing. The computer can be anywhere in the enterprise, as long as it is joined to a domain and the user account has the necessary group membership.
Click Start, point to All Programs, point to Administrative Tools, and then click Live Communications Server 2005.
In the console tree, expand Live Communications Server 2005 with SP1.
Expand nodes under the Domains node until you reach the domain in which the server or pool resides.
Expand Live Communications servers and pools.
Right-click the pool, and then click Remove pool.
Deactivate and remove Live Communications Server 2005 with SP1 from this server as described earlier in this section.

Update Rollup 8 for Exchange Server 2007 Service Pack 1

2009-05-19T13:04:00.000-03:00

Description of Update Rollup 8 for Exchange Server 2007 Service Pack 1

http://support.microsoft.com/default.aspx/kb/968012

Download the Exchange2007-KB968012-EN package now.

945684 (http://support.microsoft.com/kb/945684/ )

Description of Update Rollup 1 for Exchange Server 2007 Service Pack 1

948016 (http://support.microsoft.com/kb/948016/ )

Description of Update Rollup 2 for Exchange Server 2007 Service Pack 1

949870 (http://support.microsoft.com/kb/949870/ )

Description of Update Rollup 3 for Exchange Server 2007 Service Pack 1

952580 (http://support.microsoft.com/kb/952580/ )

Description of Update Rollup 4 for Exchange Server 2007 Service Pack 1

953467 (http://support.microsoft.com/kb/953467/ )

Description of Update Rollup 5 for Exchange Server 2007 Service Pack 1

959241 (http://support.microsoft.com/kb/959241/ )

Description of Update Rollup 6 for Microsoft Exchange Server 2007 Service Pack 1

960384 (http://support.microsoft.com/kb/960384/ )

Description of Update Rollup 7 for Microsoft Exchange Server 2007 Service Pack 1

Exchange 2010 Webcast

2009-05-18T19:37:00.000-03:00

Henrik Walther inicia la serie de Webcast de Exchange 2010 en Junio

http://www.microsoft.com/events/series/tnexchangeserver.aspx?tab=webcasts&id=liveall

TechNet Webcast: Exchange 2010 High Availability (Level 300)
Monday, June 1, 2009
9:00 A.M.–10:00 A.M. Pacific Time

TechNet Webcast: Exchange 2010 Overview (Level 200)
Wednesday, June 3, 2009
9:00 A.M.–10:00 A.M. Pacific Time

TechNet Webcast: Forefront code name “Stirling” - The next generation of Forefront Security for Exchange Server (Level 200)
Thursday, June 4, 2009
1:00 P.M.–2:00 P.M. Pacific Time

TechNet Webcast: Exchange 2010 Management Tools (Level 300)
Monday, June 8, 2009
1:00 P.M.–2:00 P.M. Pacific Time

TechNet Webcast: Microsoft Exchange Hosted Filtering is now Forefront Online Security for Exchange (Level 200)
Tuesday, June 9, 2009
1:00 P.M.–2:00 P.M. Pacific Time

TechNet Webcast: Exchange 2010 Archiving and Retention (Level 300)
Wednesday, June 10, 2009
9:00 A.M.–10:00 A.M. Pacific Time

TechNet Webcast: Exchange 2010 Outlook Web Access (Level 200)
Monday, June 15, 2009
9:00 A.M.–10:00 A.M. Pacific Time

TechNet Webcast: Exchange 2010 Architecture (Level 300)
Wednesday, June 17, 2009
9:00 A.M.–10:00 A.M. Pacific Time

TechNet Webcast: Federation in Exchange 2010 (Level 300)
Monday, June 22, 2009
9:00 A.M.–10:00 A.M. Pacific Time

TechNet Webcast: Exchange 2010 Voice Mail enabled by Unified Messaging (Level 300)
Wednesday, June 24, 2009
9:00 A.M.–10:00 A.M. Pacific Time

TechNet Webcast: Exchange 2010 Information Protection and Control (Level 300)
Monday, June 29, 2009
9:00 A.M.–10:00 A.M. Pacific Time

TechNet Webcast: Exchange 2010 Transition and Deployment (Level 300)
Wednesday, July 1, 2009
9:00 A.M.–10:00 A.M. Pacific Time

Power Shell Videos

2009-05-18T19:23:00.000-03:00

Hola,

Idera ha publicado estos 5 excelentes videos de Power Shell

http://www.idera.com/Promo/Practical-PowerShell/

Part 1: Getting to Know PowerShell
Part 2: PowerShell for Active Directory
Part 3: PowerShell for Exchange Server 2007
Part 4: PowerShell for SQL Server 2008
Part 5: PowerShell for Windows Servers and Clients

http://powershell.com/cs/

Gracias Andres Lozada