RSS

Category Archives: LYNC & OCS

office LiveMeeting client and add-on download from MS

download page

http://office.microsoft.com/en-au/downloads/CD010254990.aspx

direct download
Microsoft Office Live Meeting 2007 Client       Released: 27/07/2010
Conferencing Add-in for Microsoft Office Outlook     Released: 27/07/2010
Advertisements
 
Leave a comment

Posted by on October 28, 2010 in LYNC & OCS

 

Tags:

Lync with OCS resource kit

Lync Server 2010 RC currently has no Resource Kit. So you may try to use OCS 2007 R2 Resource Kit. But when you try to install it on Lync server, you will failed with error that

Microsoft office communications server 2007 r2, resource kit tools installation or uninstallation requires that VC++ 2008 redistrbutable is already installed. either use setup.exe for installation or run vcredist_x86.exe included with the product to install the redistributable.

So let’s take another way to do that. Exactly, we do not need to install the full Resource Kit but the tool called snooper.exe inside it. How about to extract this msi packet without install? (you may able to remove such detection in the msi packet with orac tool)

OCS 2007 R2 Resource Kit is a MSI packet, so you can not use winzip to extract but msiexec.

msiexec /a PathToMSIFile /qb TARGETDIR=DirectoryToExtractTo

So run

msiexec /a OCSResKit.msi /qb TARGETDIR=C:\OCSResKit

after the extraction process finished, you can copy the snooper.exe in “C:\OCSResKit” to “C:\Program Files\Common Files\Microsoft Lync Server 2010\Tracing”, and now you can trace with Lync Server 2010.

 
Leave a comment

Posted by on October 27, 2010 in LYNC & OCS

 

Tags:

LYNC documents download from MS

Microsoft Lync Server 2010 (Release Candidate) Lab Deployment Guide

A step-by-step, how-to document you can use to install a Microsoft Lync Server 2010 (Release Candidate) Standard Edition server, along with an Edge Server. This document is suited to lab and product evaluation deployments.

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=709d1609-a62a-47bd-baa4-6221dfd3c34c

Microsoft Lync Server 2010 (Release Candidate) Getting Started

Descriptions of new features in Microsoft Lync Server 2010 (Release Candidate). Both server features and client features are included.

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=e33765bc-9c5d-49b2-bb4f-ec8d42ccc1c7

Microsoft Lync Server 2010 (Release Candidate) System Requirements

A short document that outlines the hardware, operating system, and database requirements for Microsoft Lync Server 2010 (Release Candidate) and its related clients

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=634a3616-4199-4d51-88ee-618e72d91b7c

Microsoft Lync Server 2010 (Release Candidate) Planning Documents

Documents you can use when planning your deployment of Microsoft Lync Server 2010 (Release Candidate). Includes planning documents for IM and Conferencing, Enterprise Voice, Edge Servers, Monitoring Server, Archiving Server, virtualization and DNS load balancing, along with guidelines for planning your network infrastructure.

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=2da9fa26-e032-4dcf-b487-da916ddc508f

 
Leave a comment

Posted by on October 26, 2010 in LYNC & OCS

 

OCS 2007 R2 prerequisites on Windows Server 2008 R2

Run in powershell:

Import-Module ServerManager

then install OS prerequisites for the OCS server role :
Archiving Server:
Add-WindowsFeature AS-NET-Framework,Desktop-Experience,NET-Framework-Core,MSMQ-Server,MSMQ-Directory,RSAT-ADDS

Communicator Web Access Server:
Add-WindowsFeature AS-NET-Framework,Desktop-Experience,NET-Framework-Core,MSMQ-Server,MSMQ-Directory,RSAT-ADDS,WAS-Process-Model,WAS-Config-APIs,Web-Basic-Auth,Web-Common-HTTP,Web-Digest-Auth,Web-HTTP-Logging,Web-HTTP-Redirect,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-HTTP-Logging,Web-Mgmt-Compat,Web-Mgmt-Console,Web-Request-Monitor,Web-Windows-Auth

Edge Server:
Add-WindowsFeature AS-NET-Framework,Desktop-Experience,NET-Framework-Core

Front-End (Standard Edition) Server:
Add-WindowsFeature AS-NET-Framework,Desktop-Experience,FS-FileServer,NET-Framework-Core,MSMQ-Server,MSMQ-Directory,RSAT-ADDS,WAS-Process-Model,WAS-Config-APIs,Web-HTTP-Logging,Web-Mgmt-Compat,Web-Mgmt-Console,Web-Static-Content,Web-Windows-Auth

Front-End (Enterprise Edition) Server:
Add-WindowsFeature AS-NET-Framework,Desktop-Experience,NET-Framework-Core,MSMQ-Server,MSMQ-Directory,RSAT-ADDS,WAS-Process-Model,WAS-Config-APIs,Web-HTTP-Logging,Web-Mgmt-Compat,Web-Mgmt-Console,Web-Static-Content,Web-Windows-Auth

Mediation Server:
Add-WindowsFeature AS-NET-Framework,Desktop-Experience,NET-Framework-Core,MSMQ-Server,MSMQ-Directory,RSAT-ADDS

Monitoring Server:
Add-WindowsFeature AS-NET-Framework,Desktop-Experience,NET-Framework-Core,MSMQ-Server,MSMQ-Directory,RSAT-ADDS
These commands are largely based on the Server 2008 R1 blog entries here and here.

Note: You should uninstall .NET Framework 4.0 before installing. If you install .NET Framework 3.5 and .NET Framework 4.0 before installing OCS, the OCS setup program will complain that .NET Framework 3.5 is missing,

Note: As mentioned on other sites, Web-HTTP-Logging is technically optional, but makes debugging IIS and OCS much easier if available.

 

From http://blog.tiensivu.com/aaron/archives/1943-Server-2008-R2-Add-WindowsFeature-one-liners-for-OCS-2007-R2-prerequisites.html

 
Leave a comment

Posted by on August 1, 2010 in LYNC & OCS

 

OCS 2007 r2 on windows server 2008 r2 supportability document from MS

this is what not support

  • Upgrading the operating system to Windows Server 2008 R2 for an existing installation of Office Communications Server 2007 R2 is not supported.
  • Office Communications Server 2007 R2 administration tools will only install in native 32-bit or native 64-bit mode. Because of an application compatibility issue with Windows Server 2008 R2, installing 32-bit Office Communications Server 2007 R2 administration tools on 64-bit Windows 2008 R2 operating system is not supported.
  • Development with Speech Server (2007) Developer Edition and deployment of the Speech Server 2007 role on Windows Server 2008 R2 are not supported.
  •  

    install steps for OCS 2007 r2 on Windows server 2008 r2:

    1. 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.
    2. 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.
    3. 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

    4. Install Office Communications Server 2007 R2 Server Roles
    5. 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)

    6. 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

    7. Install updates for Office Communications Server 2007 R2, Group Chat Server, Office Communications Server 2007 R2, Group Chat Admin Tool and Office Communications Server 2007 R2, Group Chat Client that are dated May 2010 (3.5.6907.200), or install later versions.
      Note You will experience the issue that is described in Microsoft Knowledge Base article 982129 (http://support.microsoft.com/kb/982129) if you do not apply the the update that is mentioned in the previous step. To download the updates for Office Communications Server 2007 R2, Group Chat Server, visit the following Microsoft website:

      Microsoft Office Communications Server 2007 R2 Group Chat Server Hotfix 980042 (http://support.microsoft.com/kb/980042)

      To download the updates for Office Communications Server 2007 R2 Group Chat Administration Tool, visit the following Microsoft website:

      Microsoft Office Communications Server 2007 R2 Group Chat Administration Tool Hotfix 982128 (http://support.microsoft.com/kb/982128)

      To download the updates for Office Communications Server 2007 R2 Group Chat Client, visit the following Microsoft website:

      Microsoft Office Communications Server 2007 R2 Group Chat Client Hotfix 980043 (http://support.microsoft.com/kb/980043)

    8. 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:

    1. Start secpol.msc on a Windows Server 2008 R2 operating system server.
    2. Click to select Local Policies and then click Security Options node.
    3. 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

     

    From http://support.microsoft.com/kb/982021/

     
    Leave a comment

    Posted by on August 1, 2010 in LYNC & OCS

     

    how to add live messanger contact with non-hotmail address in ocs PIC mode?

    if want to add a live messanger contact with abc@cashcat.com or you have an messanger contact that share the same address as internal email address, you will find that it is easy can not do that. try to use abc(cashcat.com)@msn.com will solve this issue.

     
    Leave a comment

    Posted by on June 7, 2010 in LYNC & OCS

     

    how to setup OCS Public IM connectivity with MSN

    1-an public certificate with required domain name.

    2-submit Microsoft MSN connect request to lcsprovisioningsupport@microsoft.com.

    Get a confirmed Mail. like:

    Dear xxxxxx,
    Agreement Number: xxxxxxxx
    Organization Name: xxxxxx

    Access Edge Service FQDN

    Tracking Number

    sip.xxxxxx.com

    2010xxxxxxxxxxxxxx

    Your provisioning request for Office Communications Server public IM connectivity has been successfully completed. You should now be able to connect to the public IM connectivity providers for IM federation. If you have any questions or concerns about your new public IM connectivity service, or if you wish to stop the service, please contact us at lcsvlops@microsoft.com.
    Note: Your provisioning request was submitted by the Microsoft operation team, on behalf of your Administrator.
    Thank you for using Office Communications Server public IM connectivity service.
    Sincerely,
    Microsoft Corporation
    ================================================
    Microsoft Corporation
    1 Microsoft Way
    Redmond, WA 98052
    USA
    Microsoft Office Communications Server
    http://go.microsoft.com/fwlink/?LinkId=157702
    ================================================

    3-config ocs edge

    change certificate

    enable function

     

    confirm settings.

    4-config ocs pool

    5-config ocs user

    6-change OCS edge to public network. keep in mind that OCS edge server have to connect with MSN server via 5061 port (both side).

    7-test function

     
    Leave a comment

    Posted by on June 4, 2010 in LYNC & OCS

     
     
    %d bloggers like this: