Building the Team As easy as this sounds,

Building the Team As easy as this sounds, building the LCS deployment and planning team is probably the most critical element of any LCS deployment whether it is a proof of concept, pilot, or production roll-out. LCS touches many different components of an enterprise network and requires expertise and network permissions for each respective task. It is best to organize your team early with a core LCS team and representatives or champions from additional teams comprised of network administration personnel and business analysts within an organization. The core team should comprise the following resources: . Deployment project manager: The deployment project manager should be the person responsible for the required tasks and action items related to a LCS deployment. The project manager should provide weekly status reports, maintain a list of issues and action items, and be considered the primary point of contact for the project. In most cases, the project manager should also be the liaison between the LCS deployment team and the business sponsors of an organization. . LCS architect: The LCS architect should be the overall authority of the LCS deployment design. The architect should provide guidance and direction as a subject matter expert (SME) and provide assistance to the project team when needed. In most cases, the SME is not a full-time consultant, but a guide who ensures the technical correctness of a deployment, as well as the person who answers questions related to the technology specifically. Typically, an LCS architect is utilized on many different LCS deployments at one time. . Customer IT or business champion (sponsor for the entire project): The project sponsor, or champion, should serve as a liaison between the business and the technical project team. The sponsor is the person who is ultimately responsible for the success or failure of the deployment. The sponsor should provide assistance to the deployment team in terms of providing facility access, remote desktop access to equipment, badge or security access to a company s deployment environment/infrastructure, as well as provide any company policy training or awareness to the contract deployment team of consultants. . Customer IT architect: In some cases, a customer-sponsored IT architect is provided to ensure that the overall architecture for the LCS deployment fits within the company s technical architecture guidelines. The IT architect ensures that standards or approved methods of deployment are used in all or most cases throughout the life cycle of the project. The extended team should consist of the following resources: . DNS administrators . PKI/Certificate administrators . Active Directory administrators (Enterprise and Domain administrators) . Desktop security administrators . Server security administrators . Client deployment administrators (client software packaging and deployment) . Security baseline administrators (can be both desktop and server) . Group Policy administrators (GPO) 41 Live Communications Server 2005 SP1 in the Enterprise
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Building the Team As easy as this sounds,

. SQL Server database administrators . Telephony administrators (PBX and PSTN) . IT operations and support . Training and communications team Depending on the size or structure of the company, only three or four resources may perform all of these roles; in the rarest of cases, you have the unbelievable opportunity to work with an internal resource that has Enterprise Administrator credentials on the network. In reality, most enterprise organizations have a resource or representative competent in each area listed, and in most cases all reside in separate geographic regions. In any case, it is important to build the team early to avoid any confusion and time delays, and to anticipate concerns and lay out a strategy to mitigate risks throughout the deployment. In the preliminary kick-off meetings, a representative from each area should be present. Critical aspects of the project that warrant discussion include Active Directory, network architecture, security, integration, deployment, and client configuration. Entering the IBM Sametime Domain When selling or deploying Live Communications Server within an enterprise organization, you ll generally be faced with a competitive analysis between LCS and an existing Instant Messaging solution. Over the past several years, enterprise customers have been heavily invested in IBM for enterprise collaboration technologies, beginning with Lotus Notes for e-mail, Sametime for Instant Messaging, and QuickPlace for online portal collaboration. Due to the recent large investment that Microsoft has made in its UC platform, these customers have decided to invest in UC technology in an effort to provide a better integrated solution for their users, leveraging the dominating Office system suite of products. The information provided within this section includes reasons why enterprise companies have decided to migrate from IBM to Microsoft, especially in the area of Instant Messaging technology. At a high level, both IBM Sametime and Microsoft Office Communicator provide Instant Messaging functionality which will become the preferred method of electronic communication within the next five years. Both clients provide users with the capability to view another contact s presence and, if available, instantly send and receive messages. The major difference between Sametime and Communicator, outside of many major telephony feature enhancements available with Communicator, is that Communicator is an integrated solution. Sametime is a stand-alone application, whereas Communicator, which can be run via the Web, the desktop, or a mobile device, is integrated within the Office system, including Microsoft Word, Excel, PowerPoint, and SharePoint. At a high level, the Microsoft Office Communicator client is an enterprise messaging application that provides a unified approach to communications by providing Instant Messaging, voice, presence, video, and telephony integration, using a seamless approach to all of these provided features. The current IBM Sametime client is a stand-alone messaging application that requires its own directory and offers no voice or video communication. In my professional opinion, the IBM Sametime solution is a sunset technology like that of Windows 95. Even with enhancements it could not compete with Communicator and is not, in my opinion, an enterprise-class application. 42 Chapter 2
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Role Required Hardware Certificates Internal Windows Certificate Authority

Role Required Hardware LCS Access LCS 2005 SP1, Standard Edition Proxy Server Windows Server 2003, Standard Edition with Service Pack 1 Windows Script Host Version 5.6 CPU: Dual Pentium Xeon 3.2 GHz w/HT Disk Configuration: 2 18GB (RAID 1) 15K rpm SCSI 1MB cache Memory: 2GB Network: GBit NIC Examples: DELL PowerEdge 2850 (2U) HP DL380 G4 (2U) LCS Address Address Book Service will run on LCS Pool Servers or Standard Edition Servers Book Server IIS 6.0 Virtual Directory pointing to physical shared folder for ABS files Windows Server 2003, Standard Edition with Service Pack 1 Windows Script Host version 5.6 CPU: Dual Pentium Xeon 3.2 GHz w/HT Disk configuration: 2 18 GB (RAID 1) 15K rpm SCSI 1MB cache Memory: 2GB Network: GBit NIC Examples: DELL PowerEdge 2850 (2U) HP DL380 G4 (2U) Client Microsoft Office Communicator 2005 Machines CPU: Pentium 1.2 GHz or higher processor Memory: 128MB RAM Disk: 1.5GB free space Monitor: SVGA with 800 600 resolution minimum Video Camera (optional): USB 1.1, 640 480 resolution (e.g., Logitech QuickCam Pro 4000 ) Microphone (optional) Bandwidth: 10 MB/s recommended Special Notes: Minimum requirement for the LCS back-end database is Microsoft SQL Server 2000 with Service Pack 3a. If virtual servers are to be used in place of physical equipment, the same virtual hardware (memory, CPU, disk space) recommended in previous sections should be allocated to each instance of LCS. 40 Chapter 2
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Role Required Hardware Certificates Internal Windows Certificate Authority

Role Required Hardware LCS Back-end Windows Server 2003, Enterprise Edition with SP1 SQL Servers SQL Server 2000, Standard Edition (Enterprise Edition if clustering) with Service Pack 4 Database installed on default instance CPU: Quad Pentium Xeon 3.0 GHz w/HT Disks: 2 18GB internal drives 4 36GB (RAID 1+0) External Ultra320 SCSI Array (HP StorageWorks MSA500 G2) Disk configuration: OS loaded on C: Data Log Files = D:UCSQLDATA Transaction Log Files = D:UCSQLDATA Memory: 8GB Network: GBit NIC Examples: DELL PowerEdge 6850 (4U) HP DL580 G2 (4U) LCS Archiving LCS 2005 SP1, IM Archiving Service Servers Will run IM Archiving database on an additional or same LCS Back-End Server Windows Server 2003, Standard Edition with SP1 Microsoft SQL Server 2005 SP1 CPU: Dual Pentium Xeon 3.2 GHz w/HT Disk configuration: 2 18GB (RAID 1) 2 36GB (RAID 1) 15K rpm SCSI 1MB cache Memory: 4GB Network: GBit NIC Examples: DELL PowerEdge 2850 (2U) HP DL380 G4 (2U) Table continued on following page 39 Live Communications Server 2005 SP1 in the Enterprise
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Role Required Hardware Certificates Internal Windows Certificate Authority

Role Required Hardware Certificates Internal Windows Certificate Authority Server Authentication EKU certificates for LCS servers (minimum 128-bit encryption) LCS certificate friendly names/common names must match name of pool (LCS Enterprise Edition) or server (LCS Standard Edition) Client machines must have trusted root CA configured for each desktop LCS Pool Servers Pool Server CN = POOL.COMPANY.COM LCS Standard Edition Server: Pool Server CN = SERVER.COMPANY.COM DNS records DNS A Host Record for SIP.COMPANY.COM DNS SRV Records: _sipinternaltls._tcp.Company.com _sipinternal._tcp.Company.com _sip._tls.Company.com _sip._tcp.Company.com LCS Enterprise LCS 2005 SP1, Enterprise Edition Edition Windows Server 2003, Enterprise Edition with SP1 Pool Servers MSMQ (if archiving is enabled) Windows Script Host version 5.6 Flat File Logging Level 3 Remote registry service running CPU: Dual Pentium Xeon 3.2 GHz w/HT Disks: 2 18GB (RAID 1) 2 36GB (RAID 1) 15K rpm SCSI 1MB cache Memory: 4GB Network: GBit NIC Examples: DELL PowerEdge 2850 (2U) HP DL380 G4 (2U) 38 Chapter 2
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Timeline Consulting Tasks Details Estimate Hours Applying DNS

Deployment Schedule Summary The following table summarizes the required configuration of the scenario described in this section, accompanied by the total project timeline and total estimated number of consulting hours to complete the entire deployment: Total Timeline Total Consulting Required LCS Components Estimate Hours 10 Live Communications Servers: 1,260 hours 830 hours 5 LCS 2005 SP1, Enterprise Edition Pool Servers Load Balanced (Hardware Load Balancer) IM Archiving Service 1 LCS 2005 SP1, Access Proxy Server 1 LCS 2005 SP1, Enterprise Edition Director Server 2 Back-End LCS SQL Servers (clustered) 1 Microsoft Operations Manager Server w/ LCS Pack Configured for secure, remote access PIC (Public IM Connectivity) integration Documentation Equipment and certificate requests The following table outlines the required software and hardware configuration related to the deployment scenario described within this section: Role Required Hardware Active Domain Controller and Global Catalog running on Windows Server 2003 with Directory Service Pack 1 Active Directory native mode Active Directory GC/DC located on same subnet LCS will be deployed within the default AD site LCS service accounts will be named with default configuration nomenclature Permissions Administrators granted Enterprise Administrator permissions within Active Directory with Schema Admin rights Administrators granted SQL DBO permissions for Back-End SQL Server access Service accounts will be granted with default privileges or Enterprise Admin rights to simplify configuration Table continued on following page 37 Live Communications Server 2005 SP1 in the Enterprise
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Timeline Consulting Tasks Details Estimate Hours Applying DNS

Timeline Consulting Tasks Details Estimate Hours Applying DNS Request and implementation of required 40 hours 40 hours records DNS records to support LCS service Required DNS entries: DNS host record(s) to support LCS service running within the customer s forest/ domain DNS Service Records (SRVs) to support client connectivity to the LCS environment by resolving TCP and TLS SIP addresses VIP (Virtual Internet Protocol) address for hardware load balancer Active Directory Running LCS Active Directory 80 hours 80 hours preparation Preparation steps: Schema prep Forest prep Domain prep DomainAdd Enabling users Hardware load Configuration of the hardware load 40 hours 40 hours balancer setup balancer to meet Microsoft requirements SQLServer SQL Server application installation and 40 hours 40 hours preparation configuration for LCS Enterprise Edition Pool Servers, Director Server, and IM Archiving Service LCS application Installation of Live Communications 40 hours 40 hours install Server Access Proxy, Enterprise Edition Pool servers, IM Archiving Service and Director servers LCS application Configuring LCS servers: 80 hours 80 hours configuration LCS Access Proxy configuration LCS Enterprise Edition Pool and Pool Servers configuration LCS Director Server configuration LCS IM Archiving Service configuration LCS Microsoft Operations Manager c onfiguration Connection Entry Ports Forest settings Server settings Configuring certificates Table continued on following page 35 Live Communications Server 2005 SP1 in the Enterprise
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Timeline Consulting Tasks Details Estimate Hours Applying DNS

Timeline Consulting Tasks Details Estimate Hours SharePoint Portal Configure SharePoint Portal Server 2003 1 hour 1 hour Server 2003 to enable online presence configuration Microsoft Office 2003 Enable the shared workspace client 1 hour 1 hour configuration feature within Microsoft Office 2003 Office system Configure the Office System to use 1 hour 1 hour configuration Microsoft Office Communicator features** Testing Testing of the LCS environment 80 hours 80 hours Client deployment Packaging and distribution of 80 hours 80 hours applications to client machines: Windows Messenger 5.1 Microsoft Office Communicator 2005 Total estimated hours 1,040 hours 610 hours **Estimate does not include distribution of the Microsoft Office Service Pack 2, which is required for this task Scheduling Additional Deliverables The following table outlines the expected additional deliverables to be completed and distributed to the customer upon project completion, with additional estimated hours: Deliverable Consulting Hours Live Communications Server Design Document 120 hours Live Communications Server Test Plan 80 hours Total estimated hours 200 hours The Live Communications Server Design Document, which is also provided as an example in Appendix B, should include all of the design components that are part of the LCS deployment. These components include an architectural outline drawing of the LCS infrastructure, a listing of records and IP addresses, as well as hardware and software configurations. The purpose of this document is to provide a blueprint of the deployment for review or reference. The Live Communications Server Test Plan, which is provided in Appendix A, is a step-by-step testing document that can be used to test each LCS service after the technology has been deployed. This document is helpful both to certify that your deployment is working correctly and to provide a written proof of success. 36 Chapter 2
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Activity Details Estimated Schedule Overview presentation 100 200 level

Planning Your Schedule Based upon the requirements outlined in the previous section, the following table lists the schedule of tasks with estimated hours required to support the deployment scenario presented earlier in this section. The estimated hours listed in the table are based on the assumption that the customer has Microsoft Active Directory deployed. The estimates also assume that the customer either is either willing to grant Enterprise Administrator credentials to the engagement team or provides project sponsors to facilitate changes to DNS, Active Directory, SQL Server, and general Windows Server builds to enable Live Communications Server service within the environment. Timeline Consulting Tasks Details Estimate Hours Customer approval/ If required, customer signature to approve 40 hours 1 hour sign-off details to kick off the engagement Public IM connectivity Completed registration of the Public IM 40 160 hours 2 hours provisioning Connectivity Provisioning System In addition, a valid purchase order from the large account reseller (LAR) needs to be received by Microsoft Corporation prior to the entry on the provisioning page being successful. Equipment order Ordering of Live Communications Server 120 160 hours 1 hour equipment (depends on vendor) Ordering digital Request of digital certificates to apply to 40 hours 1 hour certificates LCS Access Proxy and Standard Edition Servers Required certificates: LCS Access Proxy External Edge LCS Access Proxy Internal Edge LCS Enterprise Edition Pool Servers LCS Enterprise Edition Director Server Trusted Root Certificate for Clients Configuring Rack and mounting of servers 80 hours 80 hours equipment Operating system load IP address configuration Security baseline (if required) 34 Chapter 2
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services

Activity Details Estimated Schedule Overview presentation 100 200 level

Activity Details Estimated Schedule Overview presentation 100 200 level overview 1 hour Live meeting or on-site meeting LCS features and components Demonstration (client) Pricing (EA licensing discussion) Technical deep dive 300 400 level 2 hours (by request) Break-out sessions Security Architecture PIC (Public IM Connectivity) integration Client Archiving Demonstration Architecture guide LCS architecture guide, including customer 8 hours (optional) name and addressing of required user deployment Consulting services Schedule 8 hours work order Deliverables Rate Disclaimers (legal) Total estimated hours 19 hours Deploying for an Enterprise Customer This section provides an estimated schedule for the deployment of a typical Microsoft Office Live Communications Server 2005 SP1 environment for an enterprise organization. (Live Communications Server is primarily intended for organizations with 250 or more desktops.) The sample Live Communications Server deployment is intended to illustrate the primary steps required to deploy Live Communications Server; it is not exhaustive. Use the information outlined within this section as a guide to estimating deployment schedules. The information captured in this section serves only as a baseline for a hypothetical deployment scenario, with the understanding that each customer environment possesses unique business processes and requirements. Therefore, the hours presented here are necessarily estimates. Also note that these estimates assume that the customer has provided the required network permissions or personnel for the deployment of Live Communications Server. The scenario described in this section is based on an enterprise customer who has decided to deploy Live Communications Server for their entire company. The requirements for this customer include the ability to deploy Live Communications Server 2005 with Service Pack 1 and Communicator 2005 to support up to 150,000 users. The customer also wants the following: secure, remote access to the environment, archiving for reporting and compliance purposes, and Public Instant Messaging Connectivity (PIC) integration. In addition, the solution must be highly scalable. Finally, the customer requires that the environment be monitored by their existing Microsoft Operations Manager service. 32 Chapter 2
Note: If you are looking for good and high quality web space to host and run your jsp application check Lunarwebhost jsp web hosting services