RSS Subscription 167 Posts and 2,769 Comments

Office Communications Server 2007 R2 Enterprise Deployment – Part 1

Now that Office Communications Server (OCS) 2007 R2 is RTM, I thought it would be nice to create an article on how to deploy a single Enterprise Edition OCS Server which is connected to an x64 SQL Server 2008 RTM Back-End Server. This article will be based off the OCS 2007 R2 RTM version.  This article series is very similar to My OCS 2007 R1 RTM series here but will be based off the R2 RTM version instead of the R1 RTM version.

This article is to guide you through the entire OCS deployment process from scratch. This article will include the following:

  1. Certificate Services installation
  2. Single Enterprise Front End Server (No more expanded configurations) – with information on what to do to get a second Front End Server installed behind a Hardware Load Balancer
  3. Edge Server (Only Consolidated Edge Servers now) – NIC Configurations
  4. Dual-Homed ISA 2006 Installation to reverse proxy internal services

Part 1

Part 2

Part 3

Part 4

Part 5

Lab Setup

Guest Virtual Machines

One Server 2008 Enterprise (Standard can be used) SP1 x64 Domain Controller which Certificate Services will be installed as the Enterprise Root Certificate Authority. Exchange 2007 SP1 is installed on separate computers. The purpose of Exchange in this lab is for Group Expansion where a Universal Distribution Group can be mail-enabled for it to be expanded within Office Communication 2007.  Alternatively, a Distribution Group can be given an e-mail address in its AD properties which satisfies the requirements of Group Expansion.

Two Server 2008 Enterprise (Standard can be used) x64 (x64 required) Member Servers where OCS 2007 R2 will be installed. One of these servers will be the Consolidated Edge Server which will contain 4 NICs.

One Server 2003 Enterprise (Standard can be used) x86 (x86 required) Member Server where ISA 2006 will be installed as a dual-homed box.

One Server 2008 Enterprise (Standard can be used) x64 (x86 can be used) Member Server where SQL 2008 is installed.

IMPORTANT: OCS 2007 R2 introduces some new AD requirements:

  • All Global Catalogs in the forest must be at least Windows 2003 SP1
  • All Domains which will have OCS 2007 R2 or users enabled for OCS 2007 R2 will need to be at least Windows 2003 Domain Functional Level which is obvious due to the next requirement.  These Domain Controllers must be at least Windows 2003 SP1.
  • The forest in which OCS 2007 R2 will be deployed needs to be at least Server 2003 Functional Level.

Assumptions

  • You have a domain that contains at least one Server 2003 SP2 Domain Controller (DC)
  • You have configured the IP settings accordingly for all servers to be on the same subnet. I have provided the IP scheme of my lab below, but this will vary depending on your needs and Virtualization Software configuration. One exception to this is one NIC on the ISA Server will belong to a different subnet. This NIC would be the NIC that lives in the DMZ in a production environment.
  • Exchange 2007 Hub Transport Server, Client Access Server, and Mailbox Server are already installed in the environment. This article does not go over the installation or configuration of these roles but will go over mail-enabling a Distribution Group(s).
  • You have at least SQL 2005 SP2 server installed. We will be using SQL 2008 installed on Server 2008 Enterprise.  SQL 2005 SP1 is NOT supported for OCS 2007 R2 as it was for OCS 2007 RTM.
  • You have a copy of Office Communicator (OC) 2007 R2. We will be installing our copy of OC 2007 R2 on our Exchange CAS.

Computer Names

OCS Front End Server – SHUD-OCSFE1

OCS Edge Server – SHUD-OCSEDGE1

Domain Controller / Exchange Server / Root Enterprise CA – SHUD-DC2

ISA 2006 Server – SHUD-ISA1

SQL Server – SHUD-SQL1

Configuration of  Domain Controller / Root Enterprise CA

Processor: 4

Memory: 512MB

Network Type External NIC

Virtual Disk Type – System Volume (C:\): 50GB Dynamic

Note: In a real-world environment, depending on the needs of the business and environment, it is best practice to install your database and logs on separate disks/spindles. We will be installing Active Directory, Certificate Services, and Exchange 2007 SP1 on the same disks/spindles for simplicity sakes for this lab.

Configuration of SQL 2008

Processor: 4

Memory: 512MB

Network Type External NIC

Disk Type – System Volume (C:\): 50GB Dynamic

Configuration of ISA 2006 SP1

Processor: 2

Memory: 384MB

Network Type External NIC

Network Type External NIC

Virtual Disk Type – System Volume (C:\): 25GB Dynamic

Configuration of OCS 2007 R2 Edge

Processor: 4

Memory: 512 MB

Network Type External NIC – used for internal NIC

Network Type External NIC – used for Audio/Video Edge NIC

Network Type External NIC – used for Web Conferencing Edge NIC

Network Type External NIC – used for Access Edge NIC

Virtual Disk Type – System Volume (C:\): 50 GB Dynamic

Note: There are few different ways the NICs could be set up on the Edge Roles. I have included a mini-write up below entitled, “Various Edge Server NIC Setups.”

Configuration of OCS 2007 R2 Front End

Processor: 4

Memory: 512MB

Network Type External NIC

IP Addressing Scheme (Corporate Subnet)

IP Address – 192.168.1.x

Subnet Mask – 255.255.255.0

Default Gateway – 192.168.1.1

DNS Server – 192.168.1.150 (IP Address of the Domain Controller/DNS Server)

IP Addressing Scheme (DMZ Subnet)

IP Address – 10.10.10.x

Default Gateway – 10.10.10.x

Subnet Mask – 255.255.255.0

Preparation of ISA 2006 SP1 Node

Network Interface Card (NIC) Configuration

First thing we will want to do is configure the IP Configuration of both the Public DMZ NIC and Internal Corporate NIC.

We will want to rename our Publc DMZ NIC connection to Public and our Internal Corporate NIC connection to Private. To do so, go to Start > Control Panel. Once in the Control Panel, Double Click on Network Connections.

Now you will be presented with the Network Connections window. This is where you can modify the network properties for each NIC in your server. For your Internal Corporate Connection, rename your Local Area Connection to Internal. Likewise, for your Public DMZ Connection, rename your Local Area Connection to Public. After you have done this, it will look something similar to the following:

Note: Do not forget that part of the assumptions earlier in this article as that you have a properly configured TCP/IP Network where all nodes are properly connected to the TCP/IP Network. Because of this, I will skip the actual TCP/IP Configuration. The IP for the Internal NIC is 192.168.1.170/24. The IP for the Public NIC is 10.10.10.153/24 that would typically have a Public IP NAT’d to this Public IP via Static Network Address Translation (NAT) rule.

Important: In a production environment, you would generally have the Default Gateway on your public NIC. Depending on the communication and configuration of firewalls, you would want to create a static route so your internal communications would go directly to a router on the inside of your network that is more open to communications. This way, you would not have to open ports on your Edge firewall when not necessary. For example, if you were doing LDAPs and your DMZ Edge Firewall blocked port 636. You would need to create a static route so traffic destined to your internal corporate network would go to the internal router that allows 636. You would not need to do this if your DMZ Edge Firewall allowed port 636 and knew how to route to the internal corporate network.

To ensure you reduce the attack surface of your ISA Server, open the Public NIC properties, open the TCP/IP Properties > go into the Advanced NIC configuration settings by clicking the Advanced button. From there, you will navigate to DNS tab and de-select “Register this connection’s addresses in DNS.”

Select the WINS tab and de-select “Enable LMHOSTS lookup” and configure the NetBIOS setting to “Disable NetBIOS over TCP/IP.”

Once you are done configuring the Advanced settings, press OK three times and you will be back at the Network Connections screen. From here, choose Advanced and select Advanced Settings

You will be presented with the Binding Order for your current NICs. Ensure that the Internal NIC is on top by selecting Internal and pressing the green up arrow key on the right-hand side of the dialog. The reason you want Internal on top is because your Corporate communications happen on this NIC and things like DNS are configured on this NIC.

Rename Computer and Join to Active Directory Domain

Make sure you name your ISA box to a name that complies with your naming convention and then join your ISA box to the domain. For purposes of this lab, we will be naming this box, SHUD-ISA1. A lot of Administrators believe that joining the ISA box to the domain is a security threat, but that is not so. Please refer to this article explaining why.

Preparation of Edge Node

Follow through the same exact steps you did for the ISA 2006 node except for a few things. Instead of 2 NICs, add 4 instead. Also, do not join it to the domain.

A summary of the steps involved consist of:

  • Create 4 NICs
  • Rename the NIC that is wired to the Internal Corporate Network to Internal
  • Rename the NICs that are wired to the DMZ appropriate to their function. Our Access Edge NIC will be named AccessEdge. Our Web Conferencing Edge NIC will be named WebConfEdge. Our Audio/Video Conferencing Edge NIC will be named AudioVideoConfEdge.
  • Assign the appropriate IP Addresses to each NIC. In OCS R2, when you have a single Edge Server, you no longer need to have a Public IP directly on the NIC.  When load balancing Edge Servers, the Audio/Video server also has a private IP but the VIP of the load balancer will need to have a Public IP for the A/V Role. This will be discussed more in detail below.
  • Create Static Routes if necessary
  • Disable the Public NICs from registering in DNS
  • Disable the Public NICs NetBIOS settings
  • Modify the Binding Order so the Internal NIC is on the top of the list.
  • Rename the Computer
  • Do NOT join it to the domain

Certificate Authority Configuration

IMPORTANT: Just as a note, the instructions below are for setting up a Certificate Authority in Server 2003 and is from my previous article series on setting up a OCS 2007 RTM.  My lab has the certificate authority set up on my Server 2008 Domain Controller and has already been deployed prior to this article series.  The process for setting up the Certificate Authority is virtually identical.  Because of this, I am not going to set it up all over again just to have the updated pictures via a Server 2008 GUI.  the only difference is that in my existing lab environment where the CA lives on Server 2008, the Root CA will be simply named CA.

So as for how to set up a CA on Windows Server 2003 SP2, we will want to make sure that we have the SP2 binaries and our CD1 for our Windows Server 2003 Enterprise installation. It will be required when we install Certificate Services.

To begin the CA installation, go to Start > Control Panel. Once in the Control Panel, Double Click on Add or Remove Programs.

Click Add/Remove Windows Components.

Place a checkmark in the checkbox next to Certificate Services. You will automatically be prompted with a prompt warning you to not modify the computer name. Ensure your computer name is set correctly before continuing. Once you have your computer name set. Click Yes and then Next to Continue.

Because we will be choosing an Enterprise Root CA, leave the defaults selected. Click Next to Continue.

Note: Choosing an Enterprise Root CA can be considered a security risk to many. Make sure a proper design for a PKI infrastructure is done for both functionality, security, etc. before deploying an internal PKI solution for your organization. I am using an Enterprise Root CA because I am doing this in a test environment and it reduces the amount of resources needed for the lab.

We will name our Root CA OCS-CAROOT. Keep in mind, this is not our machine name. This is what the root certificate’s name will be. As stated earlier, this is the CA name we specified in the OCS 2007 RTM article series.  If you want to follow along more closely and have the naming convention the same as the rest of the OCS 2007 R2 article series, name the Common Name CA. Click Next to Continue.

Specify where you want to store your Certificate Database and Logs. For purposes of this lab, we will install it on our System Partition (C:\). Click Next to Continue to begin installation. As stated earlier, make sure you have the SP2 binaries and CD1 of your Server 2003 Installation CD.

If you’re like me and always forget to install Internet Information Services (IIS) prior to installing Certificate Services, you will get the following prompt. Don’t worry, we’ll fix this after our Certificate Services installation completes. If you did get this prompt, Click OK to Continue.

Now our Certificate Services Installation should complete successfully. If you did forget to install IIS before Certificate Services installation began and you received the prompt above, go install IIS by following the instructions here. You will also need your SP2 binaries and CD1 of your Server 2003 Installation CD.

Once IIS is installed, to create the CertSrv subfolder within IIS, type the following command:

Certutil -vroot

Various Edge Server NIC Setups

When going over the NIC configuration of our Edge Servers, it has been noted that we will be using 4 NICs for our Consolidated Edge Server. This would be Method #1 below. As you can see, there are two other ways the NIC Setup could be configured.

Note: The IPs in the above diagram do not represent IPs we will be using in our lab. They are only a representation of what you may see in a production environment.

Method #1

Every Role has its’ own dedicated NIC. This is recommended due to people having issues in the past with communications when roles share IP Addresses on the same NIC.

Method #2

It is also possible to use one NIC for the Audio/Video Edge Server, Web Conferencing Edge Server, as well as the Access Edge Server. Because of this, all 3 Edge Server Roles would have Private IPs meaning they can all be on the same NIC. You would then use a dedicated NIC for the Internal NIC.

Update 1/17/2009 – I used to have a recommendation to use Method #1.  This worked just fine out of the box with Windows 2003 and still does.  Windows 2008 and using Windows 2008 R2 (not yet supported) both use the new Strong Host networking model which introduce some complications when using Method #1.  There are some security differences with the Strong Host model than what the Weak Host model used.  For example, if traffic comes in on one interface, it’s going to leave back out that same interface.  But with Windows 2003 networking, you can only have one default gateway.  So there are some tricks to do with multiple NICs such as assigning multiple Default Gateways and tweaking your Windows routes.  Jeff Schertz, OCS MVP, details this on his blog article here.  Generally, Method #1 will give you greater performance benefits but with how OCS scales and its sizing guidance, 2 NICs are fine.  I’ve generally been using Method #2.

Private IP on Audio/Video

In OCS R1, an Audio/Video Edge Server needed a Public IP directly on the NIC.  In OCS R2, when you are doing a single Edge deployment with no load balancer, you can have a private IP directly on the Audio/Video Edge NIC.  When load balancing, you can also utilize a private IP on the Audio/Vide NIC, but the load balancer IP must be a public IP Address which then NAT’s to the Private IP Address of the Audio/Video Edge NIC.

As you can see, when utilizing Load Balancing on an Edge, you must now use DNAT for incoming connections with a public IP of 192.0.2.1 which then NAT’s to the private IP on the Audio/Video Edge NIC of 10.10.10.1.  The same happens outbound except for SNAT being used instead of DNAT.  The incoming DNAT and outbound SNAT is a requirement.

Summary

Well folks, that is all for Part 1 of this article. For Part 2, I will go over the preparation and installation of a Front End OCS 2007 R2 Server Pool.

Share

90 Responses to “Office Communications Server 2007 R2 Enterprise Deployment – Part 1”

  1. […] machines being introduced into the same lab I set up for my OCS R2 Article series which is located here. The same exact lab set up you see in that article series still exist in this lab environment. The […]

  2. on 09 Oct 2009 at 4:18 amManish Malik

    Hi, In my setup I already have Edge with ISA Reverse Proxy and pretty soon I am going to deploy CWA as well. I was just wondering, can I use same ISA server for CWA External which I used for Edge Server.

    If yes, then do I need to assign another public IP to frontend NIC of ISA Server and get that address published on Public DNS for CWA. Is that how it works?

    Please help!

    ~Manish

  3. on 12 Oct 2009 at 11:18 pmElan Shudnow

    Not necessarily. You can use the same listener and configure your rule to bypass pre-auth. That means to configure your rule so the authentication delegation tab allows all clients to authenticate directly and then assigning "All users" to use the rule instead of "Authenticated Users." Or you can use a new public IP and create a new listener.

  4. on 16 Oct 2009 at 4:19 pmMelvin

    We are deploying OCS 2007 R2 Enterprise in single server and empty root domain environment. We have three Windows 2008 AD site domains, the FE OCS server will sit in one of those sites. Is there any special configurations that I need to consider to allow the users from the other two sites to access OCS; for example do I have to run the Domain Prep in each domain?

  5. on 16 Oct 2009 at 8:23 pmElan Shudnow

    You just need to make sure you domain prep any domain that will contain users who will be enabled for OCS.

  6. on 02 Dec 2009 at 1:22 pmNetpros

    Hi Elan,

    Great article, Currently planning to deploy OCS Server and Exchange 2010 for small business client, I think a guide which combines these as full unified communication solution would be very helpful to our community.

    I just created a lab for it to start with it.

    Thanks

    Netpros

  7. on 14 Dec 2009 at 9:11 amLiz

    Hi Elan

    Thanks for all the info, it has been really useful.

    I have a question regarding Edge services. We are a fairly large organisation that shares a secure external WAN with other similar organisations with which we would like to federate. We also need to enable external client access and possible federation with external partners from the Internet. Is it possible to support this configuration i.e. communication via the external WAN where available, otherwise via the Internet? If so, how is this best achieved?

  8. on 22 Dec 2009 at 4:41 amShahid

    Soon I shall have an interview for OCS administration job and I have never learnt it. I am reading the book but
    but want to do practical also.

    Could someone in this world please help me with the questions I have as follow:

    I do not have a 64 bit machine. Is there any possibility of installing,OCS 2007 R2 on Server 2003 x86?
    Can I do it on virtual Machines?
    Can I download OCS 2007(not R2) from anywhere?
    What could be the possible interview questions, any tips?

    Thank you in advance.

  9. on 22 Dec 2009 at 4:58 amElan Shudnow

    Hi Shahid. OCS 2007 was x86 only (no x64 out there) and OCS 2007 R2 is x64 only (no x86 out there).

    You can run them in VMs. OCS 2007 has no virtualization support and OCS 2007 R2 has some virtualization support. You can read the virtualization support policy here: http://communicationsserverteam.com/archive/2009/

    You can download OCS 2007 R2 Evaluation here: http://technet.microsoft.com/en-us/evalcenter/bb6

    More documentation here including a doc specific to OCS Administration: http://www.microsoft.com/downloads/details.aspx?f

    Hope that helps and good luck on the interview.

  10. on 20 Jan 2010 at 7:18 pmShabir

    Hi Elan

    Thanks for the effort for the installation in details. It really helpful.

    But, I do have one problem, which is i have received this “distribution group service could not perform this action” when i’m using ISA Server 2006 as a proxy for my IE. If i removed it(and using Cisco Transparent Proxy), office coomunicator able to retrieved the distribution group.

    Hope U may help on this on how to change the setting at ISA Server to allow distribution group is retrievable.

  11. on 24 Jan 2010 at 10:12 amPå gadeniveau med Google « IHD Blog

    […] implementeringen er Office Communication projektet og i den sammenhæng faldt jeg også idag over et godt link, som gør en i stand til selv at installere sådan en løsning Der kommer mere om vores klient installation etc. […]

  12. on 28 Jan 2010 at 2:04 pmgareth

    This is fantastic – cheers for posting!

  13. on 01 Feb 2010 at 12:56 pmalthaf

    Hi All,

    I am althaf, working for a tech support mnc company.. I would like to install OCS 2007 R2 on Win 2008. tried several times and havent succeeded.

    I want some basic information like… whether can we install OCS 2007 R2 on a Single VM Windows 2008 machine. if its yes. Please suggest the steps which one is to install prior to the levels.

    So far i had tried several times and got struck up at Setup Delegation Wizard… pls find below is the error message it throws all the times
    Failure "[0x8007001F] A device attached to the system is not functioning."

    I would appreciate you guys to suggest or any help in this regard.

    Thanks n Regards,
    Althaf

  14. on 04 Feb 2010 at 6:35 pmElan Shudnow

    althaf,

    For my labwork, I always virtualize. Keep in mind though, that most roles for virtualization are not supported and should not be done in production. This does not mean that you cannot, just that you risk having issues and/or not receiving support from Microsoft.

    Make sure your time is in sync, timezone is set correctly, Also, make sure that you are not using some extensive password with not so typical passwords as I have seen this break an install. Also, you may want to try running the ocsanfix.exe as I have seen that break certain parts of an install process. That exe is located from here: http://support.microsoft.com/kb/974571

    Hope that helps

  15. on 07 Feb 2010 at 12:19 amKings

    Good job,
    Some questions, When I setup OCS test environment in enterprise environment, what is needed when user is outside the network using ISDN connecting through firewall to the company network? Is it possible through Mediation server (Romote access enable), a Remote users from internet can call from office communicator client to office communication client into company network without edge server inplace?

  16. on 23 Mar 2010 at 1:34 pmElan Shudnow

    No, a Mediation Server does not allow any Remote Access. An Edge Server is needed. In fact, when deploying a Mediation Server for PSTN Voice, you still specify the A/V Edge so OCS users can relay PSTN Audio through the A/V Edge to the Mediation Server which will then send that audio out to the PSTN which will eventually get transcoded to G.711. So, you'll always need an Edge.

  17. on 21 Mar 2010 at 11:49 amKwadwo

    Hello Elan,

    Can please tell me how many servers i need to be able to implement all the roles on my network, also which of the roles can run parallel on one server(so i can consolidate some of the roles and cut cost).

    Thanks,

    Kwadwo

  18. on 28 Mar 2010 at 7:13 amabidg

    hi elan,

    congrats for nice work and helping others by quick reply, i want to install im feature just for few users, we have exchange 2007 production with ISA 2006 for publishing OWA etc, i have two virtual servers 64bit with 4 gb RAM and sql i can use the existing one, i want to know from where i should start, already i have downloaded the OCS r2 and once i feel ok then i will update the license

  19. on 30 Mar 2010 at 2:40 amElan Shudnow

    Just deploy a Front End Server. You can use the Standard Edition which will install SQL Express 2005 or you can use OCS Enterprise which will allow you to use your existing SQL Server. You can use a second box as an Edge Server. Then use ISA to publish the Web Components role that lives in the Front End to give you access to distribution group expansion, address book, etc…

  20. on 12 May 2010 at 9:12 amDean

    Hi Elan,

    am about to deploy OCS 2007 R2 here at work. Do you think your guide will help someone to install it from scratch, step by step? Obviously you wrote it with IT people in mind, but say, do you think a basic IT person can follow it?

    thanks

    Dean

  21. on 09 Jun 2010 at 7:23 pmJoey Freyre

    Hi Elan!

    First off I'd like to echo everyone’s sentiments on this forum and offer a hearty thank you! This is an extremely helpful piece of work. The time you dedicated out of what I’m sure is a very busy schedule is certainly appreciated!

    I have one question. I currently have TMG 2010 in my environment acting as both a firewall (VPN tunnel endpoint) and Exchange Edge server. The later role requires that the TMG NOT be a domain member. For purposes of OCS you mention that you "SHOULD" join the reverse proxy to the domain. I’m wondering if this is a hard requirement. What if any functionality will be lost if the reverse proxy is not joined? Will it still "work"? Your help is very truly appreciated! Thank you sir! Hope to hear from you soon.

    Regards,

    Joey Freyre

  22. on 29 Jun 2010 at 4:42 pmeshudnow

    I don't think I've ever said that you "should." I would say it would depend on the environment. There are Pros/Cons to each method but I typically push for the Domain-Joined model if possible. The following articles will talk about pros/cons: http://blogs.isaserver.org/shinder/2006/06/04/to-

  23. on 06 Aug 2010 at 12:00 amkc571

    I've been going crazy with this one. I used your guide and other resources. I can make calls from PSTN GW > MED > OCS > MOC. But, when I call from MOC > OCS > MED > PSTN GW, the call fails. I've isolated that the issue is specific to the 5061 closing upon the initial TLS negotiaion. Firewall is off. I think the certs are ok. I've made the changes to the local security policy. I have three VMs running WS2008R2 (1 with AD/DNS/CA, 1 with OCS, and 1 with Mediation). I appreciate any feedback.

  24. on 10 Aug 2010 at 1:21 pmkc571

    I figured it out. Never mind.

  25. on 30 Aug 2010 at 10:19 ambw201

    Can you help with this one.
    I need to define the process of how Communicator 2007R2 locates the pool in their specific region. There are two pools one in New York (pool0.nyc.mydomain.com) and one in London (pool1.LON.mydomain.com). How does Communicator knows which pool to attach to. Does anyone have a step by step process of how this happens. Would this be the same step for existing Communicator 2005 as well. One other questions do we make any changes to Communicator 2005 settings when we move users from their current pool to the new OCS 2007 R2 pool. FYI all clients workstation is has static IP's.

  26. on 30 Aug 2010 at 10:36 amElan Shudnow

    You’re in luck since I wrote an article on this:
    http://www.shudnow.net/2008/09/04/automatic-logons-directors-and-client-redirections/

  27. on 17 Sep 2010 at 3:17 pmPhilo

    should the DNS server for name resolution be on the internal (talking to internal DNS) or external (talking to public DNS) interface on the edge server?

  28. on 20 Sep 2010 at 11:38 amElan Shudnow

    I always let the internal DNS Servers handle recursion for DNS. Keep in mind, if you want NAT for AV Edge (requires that you not be load balancing), the Edge Server will need to the public IP for this FQDN. You can do that in the hosts file or in internal dns.

  29. on 03 Nov 2010 at 3:18 amMadushka

    Dear Sir,

    We have done OCS 2007R2 POC in Sri lanka(UTC + 5.30) here its working fine in this domain, But we have try to connected client in Nederalnd ,Spain and few places .but show like a error its Time Zone Problem.
    the different time zones client's not connected.

    Please explain me how this correct.

    regards

    Madushka

  30. on 18 Nov 2010 at 9:53 amElan Shudnow

    It may not be a time zone problem, but the time may be skewed somewhere. If the time on a client or server (this case probably client) is more than 5 minutes (by default in Group Policy) off from DCs, connectivity issues will ensue.

  31. on 02 Mar 2011 at 10:05 amtunji

    hi Elan, please i need you to end me link to your exchange server 2007

  32. on 04 Apr 2011 at 4:55 pmJohn Jennings

    Hey Elan,

    I was just wondering if you can point me in the right direction to remove a 2007 R2 Edge server from a depoyment? The client still wants to use OCS internally, but wants to remove the ability to access outside the network, federate, etc.

    Any tips?

  33. on 17 Apr 2011 at 4:23 pmElan Shudnow

    http://technet.microsoft.com/en-us/library/dd5728

  34. on 20 May 2011 at 6:03 amSalim Jamadar

    Hi Elan,

    Just we installed exchange 2007 in our organization now the issue Iam facing that we are using CRM software and Iam unable to send mail from CRM to the customers (outside) internally working fine Error is the server one or more recipient addresses. the server response was 550 5.7.1 unable to relay

  35. on 01 Feb 2012 at 6:02 amнастройка

    настройка…

    […]Office Communications Server 2007 R2 Enterprise Deployment – Part 1 | Elan Shudnow's Blog[…]…

  36. on 14 Mar 2013 at 4:31 amfitness tips and motivation

    Your payments will not only get to you faster but it will provide you with a history of your
    earnings for your records. We know because they have done so for millions of other people.
    Stretching will help you prevent injuries and it will help you loosen up your muscles.

    Feel free to visit my weblog – fitness tips and motivation

  37. on 12 May 2013 at 4:40 amHTTP://www.gather.com/viewArticle.action?articleId=281474981777511

    Thank you for the good writeup. It in fact was a amusement account it.

    Look advanced to more added agreeable from you! By the way, how could we communicate?

Trackback this post | Feed on Comments to this post

Leave a Reply