How Microsoft IT Architected and Sent Bound together Interchanges.

Uploaded on:
Communicator Web Access. After (Office Communication Server 2K7) ... inside Microsoft spares approx 68min (3%) every week through utilization of OCS/Communicator ...
Slide 1

Slide 2

How Microsoft IT Architected and Deployed Unified Communications Jonathan R. Lewis Sr. IT Manager, Australia Microsoft Corporation

Slide 3

Microsoft IT Purpose Be Microsoft\'s first and best client Ensure security of Microsoft\'s advanced resources Drive efficiency of our clients, customers, and accomplices Run a world class data innovation (IT) environment

Slide 4

Single Instance SAP (1.5Tb Db) Microsoft IT Data 120,000 email server accounts 300,000+ PCs and gadgets Apps Single Instance SAP 1,371LOB applications Devices 300K PCs 10K server farm servers 10K system gadgets Incident Mgmt 90K help work area calls/month 7K framework Service Requests/month 6K changes/month Dublin Redmond Silicon Valley Monthly Remote Access 45K RAS 49K OWA 18K RPC over http Singapore 92,000 end clients 89 nations MSIT bolsters more than 400 destinations all inclusive; 25% Internet associated just 3M+ email messages for each day inside, 10M remotely; 8M sifted through 99.99% accessibility 7,000,000 remote associations/month

Slide 5

Before (Live Communication Server 2005)...

Slide 6

Central Resource Forest Design

Slide 7

Remote User and Federated Access Enhanced Federation Public IM Connection Remote Access (no VPN) Communicator Web Access

Slide 8

After (Office Communication Server 2K7)...

Slide 10

Regional Pool Topology

Slide 11

MS IT OCS Topology LCS Corp arrangement was a solitary EE Pool for every single worldwide client. Picked Regional model for OCS (Redmond, Dublin, Singapore) Improved execution for provincial clients Especially for Audio and Video Web Components and Conferencing Remote Access Provisioning Still Automated Also establishes framework for worldwide business continuation and catastrophe recuperation technique

Slide 12

Business and IT Benefits Information specialist inside Microsoft spares approx 68min (3%) every week through utilization of OCS/Communicator High accessibility and low working expense with Enterprise Edition pool-based territorially oversaw framework >99.9 3 devoted FTE to bolster Low client/ticket proportion Single Identity administration framework utilizing AD Secure IM Single customer for all IM contacts by means of PIC and Federation Intelligent IM Filter gives straightforward assurance Against malware, joins, connections Insure Intellectual Property stays interior

Slide 13

MS IT Deployment Overview Regional Deployments Exchange UM for voice message EE, CE and SE Topologies Parallel OCS and LCS arrangement Not Just the Corp organization Converting our MMS LCS Customers to OCS New MMS clients will be facilitated on OCS

Slide 14

UC Planning Considerations Regional website PBX prerequisites Local dial arrangement cross examination Gateway necessities User Communication Exchange UM Integration UC Routing (Location Profiles) Network movement arranging Mediation Server position

Slide 15

Site Selection Considerations Deploy to nations where administrative and homologation obstacles are cleared for door and VoIP arrangements. Site has satisfactory transfer speed for included UC clients (Peer to Peer), and Client to Mediation Server. Gadget accessibility (Catalina or Tanjay) PBX has save QSIG T1/E1 ports for door availability Users Basic telephone clients with PSTN telephone number

Slide 16

UC Telephony Scenarios

Slide 17

Gateway + Mediation Servers SIP Gateway Translate SIP/RTP to/from circuit exchanged communication conventions Mediation Server Interfaces with a SIP entryway Intermediates SIP flagging collaborations TLS/SRTP  SIP/RTP Transcoding of codec RT Audio  G.711 Media streams between OCS 2007 system and the SIP passage Deploy Gateway and Mediation Server at a 1:1 proportion Install Reskit/Admin instruments Useful to have Netmon introduced on server for investigating

Slide 18

Mediation Server Deployment Datacenter versus Branch Office Data Center a decent decision when… High transmission capacity w/QoS amongst DC and Branch Office Low Latency amongst DC and Branch office No server equipment support at Branch office Branch Office great decision when… 120 Kbps per call system transfer speed not accessible High number of clients on framework

Slide 19

Helpful UC Tools

Slide 20

Per client estimation Type of use is essential when arranging Consider the entire way end to end

Slide 21

Other Network Considerations Delay Engineer to not exactly a mean of 150 ms Loss up to 10% can be taken care of without critical issues Connectivity The customers can associate through really well all regular systems

Slide 22

Troubleshooting Serverside Post Install Server Validation Wizard OCS MOM Packs for Operations Manager 2005 and 2007 OCS Logging Tool Replacement for Flatfile logging Best Practice Analyzer Perfmon for inclining and snappy wellbeing checks

Slide 23

Troubleshooting Clientside Install Client with Logging empowered where conceivable, particularly amid pilot Very valuable to comprehension customer issues Some Privacy and Compliance concerns

Slide 24

Steps to Isolate Voice Quality Issue: Get a reasonable meaning of the issue. Is it reproducible reliably. Did anything change as of late – new gadgets, new environment "Anything by any stretch of the imagination" Which end is the issue Network parameters to consider – Jitter, Packet misfortune, Delay, Bandwidth Touch focuses for Media Device (Hard telephone/Soft telephone) Computer/Laptop Mediation Server Media Gateway PSTN system/Mobile Operator Install Ethereal or Netmon on Mediation servers Voice Troubleshooting

Slide 25

Lessons Learned Important to drive cooperative energies between all groups (Networking, Telephony, Messaging and UC) early . Absence of phone number institutionalization created delays in empowering clients. Remote can be tricky. Live Meeting without wired force can bring about issues. Utilizing voice from other undertaking areas causes RTP to go over TCP, firewalls commonly just permit 443 or 80 which causes sound to go more than 443 through TCP. Legacy system center points/switches can bring about poor sound. Slower tablet CPU\'s can be tricky with UC sound and RoundTable, particularly when Recording.

Slide 26

Gateway Lessons Learned Choose great accomplices Provide site arrangement arranges early and frequently to Gateway Vendor so that deferrals in homologation don\'t prevent organizations. Raise T1/E1 2 weeks preceding organization Standardize on tie line interfaces between the PBX and UC (i.e. QSIG)

Slide 27

Deployment Challenges Dial Plans are situated in UC, PBX, Gateways and Exchange UM Not all Telco transporters are made equivalent Each nation is distinctive for T1/E1 setup Variable length telephone numbers Outbound Caller ID variations Inconsistent, inbound Caller ID can imitate interior clients in the event that it coordinates the length and scope of an inward augmentation. Clients that require progressed PBX components are affected.

Slide 28

Best Practices Infrastructure Standardize portal equipment Deploy in stages Ensure a fresh and well thoroughly considered enablement process End User Create solid correspondences bundle Standardize client gadgets Introduce clients to the softphone idea End client preparing/arrangement Helpdesk planning

View more...