Office Servers and Services

"La connaissance ne vaut que si elle est partagée" / "An effective Knowledge is a shared one"

Archive for novembre 2010

Forêt de ressource Exchange Server 2010 – Part 1

Posted by David PEKMEZ sur novembre 29, 2010


Exchange Server peut être installé dans votre domaine Active Directory, configuration souvent employée lors des installations d’Exchange Server.

Je vous recommande la lecture de l’article de Laurent TERUIN sur ce même site présentant les avantages et inconvénients des différentes solutions.

Cet article va vous présenter la mise en place d’une forêt de ressource Exchange Server 2010.

Une forêt de ressource est une forêt différente de la forêt ou se trouvent les comptes utilisateurs, et dans laquelle sont installées toutes les ressources liées à Exchange Server (Extensions de schéma, Serveurs, Banques d’informations, Boîtes aux lettres etc …)

Le schéma ci-dessous décrit cette mise en place


Plusieures étapes vont être nécessaires à la mise en place de ce type de solutions :

  • La mise en place d’une relation d’approbation entre les domaines Active Directory
  • L’installation d’Exchange Server dans la forêt de ressource

     

Il est ensuite possible de créer des boîtes aux lettres pour les utilisateurs du domaine de compte.

Infrastructure de démonstration


Etape1 :

Pour mettre en place une relation d’approbation entre les forêts Active Directory vous devez configurer le service DNS pour que les serveurs puissent communiquer via ce service.

Pour cela, configurez les Forwarders sur les serveurs hébergeant le service DNS.



Ensuite vous pourrez créer la relation d’approbation entre les forêts Active Directory

Loguez-vous sur le contrôleur de domaine de la forêt de comptes et lancez la console « Active Directory Domain and Trusts » puis faite un clic droit sur le nom de domaine et cliquez sur « Propriétés ».

Cliquez sur « New Trust » afin de lancer l’assistant de création de relation d’approbation



Choisir un trust de forêt de type « One-way : outgoing »


Entrez un compte et mot de passe du domaine de compte




La relation d’approbation est maintenant créée dans la forêt de ressource


Et dans la forêt de compte


La base de la configuration est maintenant terminée, nous allons pouvoir installer Exchange Server 2010 dans la forêt de ressource.

La seconde partie de cet article sera consacrée à la configuration d’Exchange Server dans la forêt de ressource ainsi qu’à la gestion des utilisateurs.

Bonne lecture

David Pekmez

Posted in Exchange Server 2010 | 1 Comment »

FPE 2010 Installation Error: Root Element is missing

Posted by Teruin laurent sur novembre 25, 2010


You can encountered a warning when you reinstall FPE2010 on Exchange 2010 SP1: Unhandled exception has occurred in your application… « Root element is missing »
Just delete the old installation directory and it will works!

Si vous réinstallez FPE 2010 sur Exchange 2010 SP1 vous pouvez rencontrer le problème suivant. Pour éviter cela supprimer le précédent répertoire d’installation.
Cordialement

Laurent Teruin

Posted in Installation-2010 | Leave a Comment »

MailAlertor : Installation documentation

Posted by Teruin laurent sur novembre 23, 2010


Vous trouverez ici la documentation d’installation de mailalertor. Bonne lecture et merci de vos retours le cas échéants

Laurent Teruin

  1. Purpose

The goal of this application is to provide to administrators of an Active Directory domain to manage accounts for users connected outside network company.This application is used to inform users of the need to change their password. Passwords can be changed using the Outlook Web Access. Three mails are sent to the user. One 15 days before the expiration date, one 7 days before expiration and one 1 day before expiration.The number of days can be set in the application, depending on the policies of the company.

  1. Description

The application consists of the following three components:

  • MailAlertor Application : Used to configure alerts and miscellaneous parameters.
  • MailAlertor Agent : Used to manage sending emails automatically. This is a windows service. It can be run on Windows 2003, Windows 2008, Windows 7 and Windows XP.
  • MailAlertorDB : SQL database server used to store configuration information and history data
  • The MailAlertor agent and MailALertor application must be installed on the same computer.
  • The MailAlertorDB can be installed on any SQL server. The SQL version must be at least SQL server 2008 or SQL server express edition.
  1. Installation

To install the MailALertor application, run the « MailAlertor setup.exe » file and follow the instructions. As soon as you have installed the MailAlertor application, you have to configure the MailLAertorDB database on the SQL server. To do this refer to the « How to configure the MailAlertor database » document. It is a pdf file located in the folder named « DataBase » under the installation path of the application. To Install the MailAlertor Agent, run the SetupMailAlertorAgent.msi » file and follow the instructions. The MailAlertor agent must be started manually the first time after installation.

  1. Procedure
  • /!\ You must configure MailAlertorDB database before continuing the procedure (refer to the installation chapter).
  • /!\ the MailAlertor Application doesn’t work outside a Windows domain. This means that if you run the application on a computer not inserted in a domain, the application will stop.
  • /!\ On Windows 7 and the Windows 2008 server the application must be run with the administrator rights.
  1. Configuration
  • The first time you run the application, you have to enter the location of the SQL server on which you installed the MailAlertorDB. See installation chapter
  • Enter the SQL server name and if necessary the instance. For SQL server Express edition, the name of the instance is SQLEXPRESS
  • Click on the Check button. If the application cannot connect to the MailALertorDB database on the SQL server, you will have an error message and the application will stop.
  • If the check of the MailAlertorDB is ok, you will get the main screen of the application. This screen contains some tabs.
  • Select the Server Settings tab
  • Enter the Smtp server name
  • Select Smtp authentication if it’s required by your mail system and enter the user name and password.
  • Check that the Database server name matches the SQL server on which the MaiAlertorDb is installed.
  • /!\ The computer where you installed MailAlertor must be authorized to send email.
  • Click on the save settings button to apply your changes
  • Select the Sender tab
  • Enter the display name. The display name is the name the recipient will see when the mail is delivered in his mailbox.
  • Enter the mail address. You have to enter a valid mail address for your organization. This will allow you to receive a ‘Non Delivery Report’ (NDR) and so to follow the outcome of notification.
  • Change the codage of the mail if necessary.
  • Click on the save settings button to apply your changes
  • Select the Configuration tab
  • Select the time you want to send the messages to the users.
  • Enter the path for the folder where the template messages are stored. By default they are put in the folder named ‘template’ during the installation. At installation, the setup program creates four messages. Three messages for standard alerts and a special message, for users with ‘Password never expires’ option.
  • Select ‘Send special message..’. if you want to activate this option, see the above explanation.
  • Select HeartBeat if you want to receive a message indicating that the service is up and running.
  • If you select the HeartBeat option, enter the mail address of the recipient.
  • Click on the save settings button. A message indicating that you have to restart the MailAlertor agent is displayed. After changing the alert emission time, you must to restart the service to get the new time.
  • Select the Messages tab. In this tab, you can configure the messages used by the application
  • You can select the messages already configured in the drop down list. During installation, the setup program creates 4 messages. You can select a message and click on the View HTML message to see the email. All messages are sent in html format.
  • To create a new message enter a name for the reference message, enter a subject, enter the body message or import a html message with the Import message button and select Save message. The application will create a random number for the message and add the message to the list. All reference messages start by IM_
  • You can attach one file for each message. It will be sent with the email.
  • If you select view Html message, you will see the html message and be able to send a test email to any recipient you enter in the recipient field.

  1. Exploitation
  • Select the dash board tab. In this view you can see all available alerts. Next to each alert you have a green or red led depending on the state of the alert. A green led indicates that the alert is active and a red led indicates that the alert is inactive. You can change the status of the by clicking on the led.
  • The Description column indicates the goal of the alert.
  • The scope refers to the users targeted by the alert. There are three scopes : Domain, Group or Organizational Unit.
  • To modify an existing alert click on the icon. The modify alert screen is the same as the new alert screen. See below

 

 

 

 

 

 

  • To create a new alert button, click on the new alert button in the dash board tab.
  • Select the scope of this alert. When your selection is done the ‘View users ‘ button is enabled. By clicking on this button, you will see all users included in the scope. If you apply some options for the search (see tab User filter), all records corresponding to any of the search criteria will appear in orange in the grid.
  • Enter a description for the alert
  • For each of the three alerts you can select when the time of emission.

 

  • Select ‘View assigned users’ button in the dash board tab to view the users. A window shows you the query criteria. You can modify the criteria via the ‘User Filter’ tab.
  • Click on the Ok button
  • The colors are as follows :

Green for users in the first alert

Yellow for users in the 2nd alert

Red for users in the 3rd alert

Orange for users who are « out of the period ».

 

 

Posted in 1-EXCHANGE 2010, Exchange 2010 Service Pack 1 | Leave a Comment »

LYNC 2010 : Liste des protocoles et des ports Tcp/Udp concernés

Posted by Teruin laurent sur novembre 22, 2010


Microsoft vient de publier des informations concernant la liste des ports utilisés par l’environnement Lync. Les tableaux suivants couvrent l’ensemble des rôles, y compris l’aspect client. Des documents de références sans doute.

Bonne journée
Laurent Teruin

 

Component (server role or client)

Service name

Port

Protocol

Does this port need to be open on the load balancer?

Notes

Front End Servers

Lync Server Front-End service

5060

TCP

Yes

Used by Standard Edition servers and Front End pools for listening to client connections from Microsoft Lync 2010 (TCP).

Front End Servers

Lync Server Front-End service

5061

TCP (TLS)

Yes

Used by Standard Edition servers and Front End pools for all internal SIP communications between servers (MTLS), for SIP communications between Server and Client (TLS) and for SIP communications between Front End Servers and Mediation Servers (MTLS).

Front End Servers

Lync Server Front-End service

444

HTTPS

Yes

Used for communication between the Focus (the Lync Server component that manages conference state) and the individual servers.

Front End Servers

Lync Server Front-End service

135

DCOM and remote procedure call (RPC)

Yes (must be open on the hardware load balancer even if you are using DNS load balancing)

Used for DCOM based operations such as Moving Users, User Replicator Synchronization, and Address Book Synchronization.

Front End Servers

Lync Server IM Conferencing service

5062

TCP

No

Used for incoming SIP requests for instant messaging (IM) conferencing.

Front End Servers

Lync Server Web Conferencing service

8057

TCP (TLS)

No

Used to listen for Persistent Shared Object Model (PSOM) connections from client.

Front End Servers

Lync Server Audio/Video Conferencing service

5063

TCP

No

Used for incoming SIP requests for audio/video (A/V) conferencing.

Front End Servers

Lync Server Audio/Video Conferencing service

57501-65335

TCP/UDP

No

Media port range used for video conferencing.

Front End Servers

Web Compatibility service

80

HTTP

Yes (must be open on the hardware load balancer even if you are using DNS load balancing)

Used for communication from Front End Servers to the Web farm FQDNs (the URLs used by IIS Web components) when HTTPS is not used.

Front End Servers

Lync Server Web Compatibility service

443

HTTPS

Yes (must be open on the hardware load balancer even if you are using DNS load balancing)

Used for communication from Front End Servers to the Web farm FQDNs (the URLs used by IIS Web components).

Front End Servers

Lync Server Web Compatibility service

8080

TCP

Yes (must be open on the hardware load balancer even if you are using DNS load balancing)

Used for IIS Web components for external access.

Front End Servers

Lync Server Conferencing Attendant service (dial-in conferencing)

5064

TCP

No

Used for incoming SIP requests for dial-in conferencing.

Front End Servers

Lync Server Conferencing Attendant service (dial-in conferencing)

5072

TCP

Yes

Used for incoming SIP requests for Microsoft Lync 2010 Attendant (dial in conferencing).

Front End Servers that also run a Collocated Mediation Server

Lync Server Mediation service

5070

TCP

Yes

Used by the Mediation Server for incoming requests from the Front End Server to the Mediation Server.

Front End Servers that also run a Collocated Mediation Server

Lync Server Mediation service

5067

TCP (TLS)

Yes

Used for incoming SIP requests from the PSTN gateway to the Mediation Server.

Front End Servers that also run a Collocated Mediation Server

Lync Server Mediation service

5068

TCP

Yes

Used for incoming SIP requests from the PSTN gateway to the Mediation Server.

Front End Servers

Lync Server Application Sharing service

5065

TCP

No

Used for incoming SIP listening requests for application sharing.

Front End Servers

Lync Server Application Sharing service

49152-65335

TCP

No

Media port range used for application sharing.

Front End Servers

Lync Server Conferencing Announcement service

5073

TCP

Yes

Used for incoming SIP requests for the Lync Server Conferencing Announcement service (that is, for dial-in conferencing).

Front End Servers

Lync Server Call Park service

5075

TCP

Yes

Used for incoming SIP requests for the Call Park application.

Front End Servers

Audio Test service

5076

TCP

Yes

Used for incoming SIP requests for the Audio Test service.

Front End Servers

 

5066

TCP

No

Used for outbound Enhanced 9-1-1 (E9-1-1) gateway.

Front End Servers

Lync Server QoE Monitoring Service

5069

TCP

Yes

Used by Quality of Experience (QoE) agent on the Front End Server.

Front End Servers

Lync Server Response Group service

5071

TCP

Yes

Used for incoming SIP requests for the Response Group application.

Front End Servers

Lync Server Response Group service

8404

TCP (MTLS)

No

Used for incoming SIP requests for the Response Group application.

Front End Servers

Lync Server Bandwidth Policy Service

5080

TCP

Yes

Used for call admission control by the Bandwidth Policy service for A/V Edge TURN traffic.

Front End Servers

Lync Server Bandwidth Policy Service

448

TCP

Yes

Used for call admission control by the Lync Server Bandwidth Policy Service.

Front End Servers where the Central Management store resides

CMS Replication service

445

TCP

No

Used to push configuration data from the Central Management store to servers running Lync Server.

All internal servers

Various

49152-57500

TCP/UDP

N/A

Media port range used for audio conferencing on all internal servers. Used by all servers that terminate audio: Front End Servers (for Lync Server Conferencing Attendant service, Lync Server Conferencing Announcement service, and Lync Server Audio/Video Conferencing service), and Mediation Server.

Directors

Lync Server Front-End service

5060

TCP

Yes

Used by Standard Edition servers and Front End pools for listening to client connections from Lync 2010(TCP).

Directors

Lync Server Front-End service

5061

TCP

Yes

Used for internal communications between servers and for client connections.

Mediation Servers

Lync Server Mediation service

5070

TCP

Yes

Used by the Mediation Server for incoming requests from the Front End Server.

Mediation Servers

Lync Server Mediation service

5067

TCP (TLS)

Yes

Used for incoming SIP requests from the PSTN gateway.

Mediation Servers

Lync Server Mediation service

5068

TCP

Yes

Used for incoming SIP requests from the PSTN gateway.

Mediation Servers

Lync Server Mediation service

5070

TCP (MTLS)

Yes

Used for SIP requests from the Front End Servers.

Monitoring Servers

Lync Server Monitoring service

135

Message Queuing and remote procedure call (RPC)

N/A

Used for message queuing and RPC operations.

Archiving Servers

Lync Server Archiving service

135

Message Queuing and RPC

N/A

Used for message queuing and RPC operations.

Reverse proxy servers

 

80

TCP

N/A

Used by the reverse proxy to listen on the external interface for incoming requests from external users.

Reverse proxy servers

 

443

TCP

N/A

Used by the reverse proxy to listen on the external interface for incoming requests from external users for Web components information and file downloads, distribution group expansion as well as Address Book information.

Reverse proxy servers

 

8080

TCP

N/A

Used for SIP/TLS communication with the internal network to the Web services cluster. Traffic from port 80 on the external interface is redirected to this port.

Reverse proxy servers

 

4443

TCP

N/A

Used by the reverse proxy to listen on the internal interface. Traffic from port 443 on the external interface is redirected to this port.

Edge Servers

All edge services (external interface)

443

TCP

Yes

Used for SIP/TLS communication for external users accessing internal Web conferences, and STUN/TCP inbound and outbound media communications for accessing internal media and A/V sessions.

Edge Servers

Lync Server Access Edge service (internal and external interface)

5061

TCP

Yes

Used for SIP/MTLS communication for remote user access or federation and public Internet connectivity.

Edge Servers

Lync Server Web Conferencing Edge service (internal interface)

8057

TCP

No

Used to listen for PSOM/MTLS communications from the Web Conferencing Server on the internal interface of the Web Conferencing Edge Server.

Edge Servers

Lync Server Audio/Video Edge Authentication service (internal interface)

5062

TCP

Yes

Used for SIP/MTLS authentication of A/V users. Communications flow outbound through the internal firewall.

Edge Servers

Lync Server Audio/Video Edge service (internal and external interfaces)

3478

UDP

Yes

Used for STUN/UDP inbound and outbound media exchange.

Edge Servers

Lync Server Audio/Video Edge service port range

50,000-59,999

RTP/TCP, RTP/UDP

No

Used for inbound and outbound media transfer through the external firewall. This port range always needs to be opened outbound for TCP. If you federate with an organization running Microsoft Office Communications Server 2007 R2 or Microsoft Office Communications Server 2007, you must open this range both outbound and inbound, and for both TCP and UDP.

Edge Servers

All Edge services (internal interface)

4443

TCP

No

Used to push configuration data from the Central Management store to the Edge Server. This port must be opened on every individual Edge Server, not on the load balancer.

Clients

 

67/68

DHCP

N/A

Used by  Lync 2010 to find the Registrar FQDN (if DNS SRV fails and manual settings are not configured).

Clients

 

6891-6901

TCP

N/A

Used for file transfer between Lync 2010 clients and previous clients (clients of Office Communicator 2007 R2, Office Communications Server 2007, and Live Communications Server 2005).

Clients

 

1024-65535

TCP/UDP

N/A

Used by clients for audio port range (minimum of 20 ports required).

Clients

 

1024-65535

TCP/UDP

N/A

Used by clients for video port range (minimum of 20 ports required).

Clients

 

1024-65535

TCP

N/A

Used by clients for peer-to-peer file transfer (for conferencing file transfer, clients use PSOM).

Clients

 

1024-65535

TCP

N/A

Used by clients for application sharing.

Microsoft Lync 2010 Phone Edition for Aastra 6721ip common area phone

Microsoft Lync 2010 Phone Edition for Aastra 6725ip desk phone

Microsoft Lync 2010 Phone Edition for Polycom CX500 common area phone

Microsoft Lync 2010 Phone Edition for Polycom CX600 desk phone

 

67/68

DHCP

N/A

Used by the devices listed to find the  Lync Server 2010 certificate, provisioning FQDN, and Registrar FQDN.

 

IPsec Exceptions

For enterprise networks where Internet Protocol security (IPsec) (see IETF RFC 4301-4309) has been deployed, IPsec must be disabled over the range of ports used for the delivery of audio, video, and panorama video. The recommendation is motivated by the need to avoid any delay in the allocation of media ports due to IPsec negotiation.

The following table explains the recommended IPsec exception settings.

Recommended IPsec Exceptions

Rule name

Source IP

Destination IP

Protocol

Source port

Destination port

Filter action

A/V Edge Server Internal Inbound

Any

A/V Edge Server Internal

UDP and TCP

Any

Any

Permit

A/V Edge Server External Inbound

Any

A/V Edge Server External

UDP and TCP

Any

Any

Permit

A/V Edge Server Internal Outbound

A/V Edge Server Internal

Any

UDP & TCP

Any

Any

Permit

A/V Edge Server External Outbound

A/V Edge Server External

Any

UDP and TCP

Any

Any

Permit

Mediation Server Inbound

Any

Mediation

Server(s)

UDP and TCP

Any

Any

Permit

Mediation Server Outbound

Mediation

Server(s)

Any

UDP and TCP

Any

Any

Permit

Conferencing Attendant Inbound

Any

Any

UDP and TCP

Any

Any

Permit

Conferencing Attendant Outbound

Any

Any

UDP and TCP

Any

Any

Permit

A/V Conferencing Inbound

Any

A/V Conferencing Servers

UDP and TCP

Any

Any

Permit

A/V Conferencing Server Outbound

A/V Conferencing Servers

Any

UDP and TCP

Any

Any

Permit

Exchange Inbound

Any

Exchange Unified Messaging

UDP and TCP

Any

Any

Permit

Application Sharing Servers Inbound

Any

Application Sharing Servers

TCP

Any

Any

Permit

Application Sharing Server Outbound

Application Sharing Servers

Any

TCP

Any

Any

Permit

Exchange Outbound

Exchange Unified Messaging

Any

UDP and TCP

Any

Any

Permit

Clients

Any

Any

UDP

Specified media port range

Any

Permit


 

Posted in Lync 2010 | Leave a Comment »

Lync 2010 : Comment un client Lync interagit avec son serveur

Posted by Teruin laurent sur novembre 19, 2010


Vous désirez savoir comment un client Lync interagit avec les services LYNC 2010. Lisez ce document vous en saurez certainement plus après !!
http://cid-1eca1834ce9fca8e.office.live.com/self.aspx/.Documents/Lync2010/Docs/[MS-OCSPROT][1].pdf

A lire tranquillement

Bonne soirée
Laurent

Posted in Lync 2010 | 3 Comments »

Lync 2010 : Poster des protocoles en jeu

Posted by Teruin laurent sur novembre 19, 2010


Après Microsoft Exchange 2010, Microsoft vient de mettre à disposition un poster de Lync présentant l’architecture générale. A récupérer sur le lien suivant

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ad8ff3fb-014e-4fd7-8003-436d896ab0c6

Cordialement
Laurent Teruin

Posted in Lync 2010 | Leave a Comment »

MailAlertor : How to warn automatically your mail users that their AD password will expire

Posted by Teruin laurent sur novembre 16, 2010


Un petit outil génial ! Nous avons tous le souci des personnes extérieures qui ne se connectent pas sur le réseau interne et ne sont pas alertés que leurs mots de passe va expirer. Voici un outil qui va résoudre ce souci. Connecté sur l’environnement AD il va scanner les comptes Active directory qui ont une boite aux lettres et les alerter par un message pouvant être accompagné d’une procédure à suivre. Simple et efficace !
Ce service car il s’agit d’un service Windows va se baser sur une base de données SQL qui peut être installé soit sur le serveur lui-même soit sur un serveur tiers. MailAlertor est composé des deux modules qui sont les suivants.

  • Module : Service
    • OS : Windows 2008 Std Entreprise
    • Composant : .NET Framework 2.0
    • Utilise un compte LocalSystem
  • Module programme mailalertor
    • Sert à configurer le service
    • Configurer les envois de messages
    • Configurer la nature du message (format HTML)
    • Configuration des alertes
    • Connexion à l’active Directory pour recherche des utilisateurs. (Fonctionne dans l’environnement de l’utilisateur). Sur 2008 server le compte utilisateur doit être admin de la machine.

     

    Je vous livre ici quelques écrans du produit en question

LA liste des alertes et du scope retenu.


 

La liste des utilisateurs concernés


Création d’une alerte par filtrage d’un scope

Scope de recherche des utilisateurs dans l’AD

  • Par Domaine
  • Par OU
  • Par Groupe
  • Possibilité d’appliquer un filtre de recherche. (User Filter)


Filtrage des utilisateurs


Le message d’alerte que l’utilisateur va recevoir.


Pour l’obtenir. Envoyez un mail a unifiedit@hotmail.fr pour le recevoir

Un grand merci à Philippe S !!
cordialement
Laurent Teruin

Posted in 1-EXCHANGE 2010, EXCHANGE 2007, Outils-2010 | Leave a Comment »

Exchange 2010 SP1: Best Practices in Deploying Microsoft Exchange for BlackBerry

Posted by Teruin laurent sur novembre 15, 2010


Rim lors d’une conférence qui s’est tenue le 29 Avril de cette année à mise en ligne un document ou l’on apprend que les BBY Devices ne consommeraient pas plus qu’un client Outlook si l’on utilise la version BES 5.0.2 en environnement Exchange 2010.


Ceci est vrai à condition de procéder à une optimisation qui joue sur la valeur du Checkpoint Depth Sinon un facteur de 1,85 est à considérer. Cette optimisation est de facto en mode DAG car les prérequis annoncés par RIM porte sur un CPD de 100 M ce qui est la valeur par défaut dans le cas de serveur de boites aux lettres en mode DAG. Pour plus d’info voir : http://technet.microsoft.com/en-us/library/ee832793.aspx


Par contre on apprend que l’impact sur les processeurs est un peu différent. Un BBY aurait un facteur ‘aggravant’ de 1,4 /1,5 par boites aux lettres. Le throttling doit cependant être désactivé pour le compte de service sur l’environnement CAS.


Si vous désirez la version complète du document : un petit mail à unifiedIT@hotmail.fr et l’on vous reverra cela

Bonne journée
Laurent TERUIN

Posted in BlackBerry, Mobilité-2010 | Leave a Comment »

Vidéos du Tech·Ed 2010

Posted by David PEKMEZ sur novembre 13, 2010


Vous n’êtes pas au Tech·Ed ? Regardez les vidéos disponibles sur le site internet de l’évènement !

http://www.msteched.com/2010/Europe

Lien des sessions concernant les communications unifiées

http://www.msteched.com/2010/Europe/Tracks/UnifiedCommunications

Bons Webcasts !

David

Posted in 9 - Evenements | Leave a Comment »

Comparaison des fonctionnalités entre OWA 2010 et Outlook 2010

Posted by David PEKMEZ sur novembre 13, 2010


Je vous recommande vivement la lecture de ce post si la comparaison des fonctionnalités entre OWA 2010 et Outlook 2010 vous intéresse ! Comparaison de Steve Goodman sur son site à l’adresse suivante

http://www.stevieg.org/2010/11/comparison-outlook-2010-owa-2010-outlook-2011-features/

Je vous recommande chaudement la lecture quotidienne de ce site au passage

Bonne lecture !

David


 

Posted in Exchange 2010 Service Pack 1, Owa-2010 | Leave a Comment »