today’s agenda 1. session 4 agenda 3 patching sharepoint office 2010 co- authoring sharepoint...
Post on 21-Dec-2015
217 views
TRANSCRIPT
Today’s Agenda
• 9:00-10:15 - SharePoint 2010 Overview for IT Pro’s• 10:15-10:30 - Break• 10:30-12:15 - Upgrading to SharePoint 2010• 12:15-1:00 - Lunch and Windows Phone 7 demo • 1:00 – 2:30 - Understanding and Deploying Office Web Apps• 2:30 – 2:35 – Short Break • 2:45 – 4:15 - SharePoint 2010 Virtualization and
Maintenance• 4:15 - Raffle
1
Additional Topics of SharePoint 2010
Yung ChouSr. IT Pro EvangelistMicrosoft Corporationhttp://blogs.technet.com/yungchouTwitter @yc8050
Session 4
4
Updating SharePoint
• Version to Version Upgrade− MOSS to SharePoint 2010− Major release
• Build to Build Patching− Beta to RTM− RTM to SP1− Hot fixes
Session 2
Session 4
SharePoint Patching Process
• 2 steps− Update Binaries
− Self-extracting exe with a KB reference− “/extract” switch− Every server in the farm
− Update Database− Run Configuration Wizard− Every server in the farm
7
SharePoint 2010 Improvements of Patching
Then in WSS 3.0 and MOSS Now in SF2010 and SP2010
Separate packages for each Product
SP2010 patches include those for SF2010
Problematic and error prone Straightforward and streamline
Only one instance PSCONFIG in a farm
Binary immediately and database later with “compatibility range” mode
Locks to allow upgrading multiple database simultaneously
Long upgrade time and high touch maintenance
Shorter upgrade time with better user experience
New Patch Management Features
Verifying component installation statusChecking database schema versions
DEMO
11
Agenda
Patching SharePoint
Office 2010 Co-
Authoring
SharePoint Virtualizati
on
Building Test Lab
12
Co-Authoring Conceptual Model
• Multiple contributors editing the same document simultaneously
• Much more than just typing in the same document− Metadata (operations, document), data sync, locks,
compatibility
• Three-Way (File) Merge− Downloaded copy, base copy, and working copy
Three-Way Merge (Take 1)
• Multiple copies of the document cached on the client• Merge when updates are
available• Snapshot for upload
ServerCopy
Downloaded
Copy
BaseCopy
UploadCopy
WorkingCopy
Word
Background Sync
Local Edits
UpdatesAvailable
1
2
3
4
Merge
5
6
Background Sync
Three-Way Merge (Take 2)
Server
AB
ClientABC
AXB
AB
AXBC
AB
Downloaded Base Working Result
AXBC
AXB
AXB
AXBC
AXBC
AXBC
Working copy is now up to date with server document.
Base copy is ancestor of both Working and Server document
15
Office 2010 Co-Authoring
• All contributors must work on the same document stored in a co-authoring aware server− SharePoint 2010− SkyDrive (http://skydrive.live.com)
• Word 2010• PowrerPoint 2010• Excel Web Application• OneNote and OneNote Web Application
Server requirements
Client requirements
Operation requirement
17
Agenda
Patching SharePoint
Office 2010 Co-
Authoring
SharePoint Virtualizati
on
Building Test Lab
18
Support
• Full support coverage when deployed in a Microsoft Hyper-V environment− Includes related or required supporting technologies such
as SQL Server 2005 or SQL Server 2008− 3rd party virtualization technologies must be certified by
Microsoft Server Virtualization Validation Program (SVVP)
19
Operating System (OS) Licensing• Distinct OS environments - Physical vs. Virtual• Windows Server licenses
− Attached to the physical server,− Virtual machines use rights covered in the Windows Server license− http://www.microsoft.com/licensing/about-licensing/virtualization.a
spx
• Virtual processors are considered to have the same number of threads and cores as each physical processor
• Microsoft Hyper-V− No license needed for the virtualization layer (physical install)− Guest OS instances in the VMs need to be licensed
• When in doubt, check with your software vendor
21
Sample Physical & Virtual SharePoint Arch.
Source: Virtualization of Microsoft® SharePoint® Products and Technologies
22
Deploying Single SharePoint 2010 in Hyper-V• HW/SW/Capacity requirements for SharePoint and
SQL• Database Requirement
− SQL Server 2008 Express− SLQ Server 2008 with SP1 and Cumulative Update 2− SQL Server 2005 with SP3 and Cumulative Update 3
• Active Directory Domain− SharePoint 2010 on DC− Some configuration required
For evaluation and testing only, not for prodution
23
Agenda
Patching SharePoint
Office 2010 Co-
Authoring
SharePoint Virtualizati
on
Building Test Lab
24
Building SharePoint Test LabStarter Kit• 64-Bit Laptop with Hardware Assisted Virtualization
− Intel® VT or AMD-V™.
• Device drivers− Ethernet, Wireless, and Video
• Windows Server 2008 R2 Trial• SharePoint 2010 Trial• SharePoint Tech Libraries• Anti-virus software
25
Building SharePoint Test LabHyper-V Manager Essentials• Hyper-V Network Manager
− Network topology− External, Internal, and Private− Internet connectivity, bridging
• Virtual Machine− Create/Export/Import− Snapshots
• Virtual Hard Disk (VHD)− Newly created or existing one− P2v and v2p concept, disk2vhd
26
Building SharePoint Test Lab• Build Windows Server 2008 R2 box
− Enable Virtualization− Harden security, install tools, and add Hyper-V Role− Establish Internet Connectivity− Run Windows Updates
• Build Virtual Network− Add network adapters
• Add Virtual Machines− Windows Server 2008 R2− Windows Active Directory− SharePoint pre-requisites− SharePoint Foundation 2010− Standalone with SQL 2008 Express
28
Call to Action• Build your Hyper-V lab for SharePoint:
− SharePoint Technical Libraries− Windows Server 2008 R2 trial− SharePoint Foundation 2010− SharePoint 2010 trial− Office Web Applications− SQL 2008 R2 trial− Office 2010 trial− Windows 7 trial
• Use Office Web Apps today via SkyDrive• Subscribe the following:
− Your regional IT Pro Evangelist’s blog− http://technetevents.com/Presenters.aspx
− TechNet event announcements− http://technetevents.com
− TechNet Edge− http://edge.technet.com
skydrive.com
29
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date
of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.