Windows Server 2003 R2 Technical Overview

1
Windows Server 2003 R2Technical Overview
Branch Office Deep Dive

• Kurt ROGGEN
• System Architect
• Guidance NV

Blog http//blogontheweb.com/roggenkEmail
roggen_at_guidance.be
2
Agenda

• Windows Server new release cycle and Update
  Release
• Overview the new features of Microsoft Windows
  Server 2003 R2
• Branch Office scenarios (File Print)
• DFS (DFS-N and DFS-R)
• Print Management

3
(No Transcript)
4
An Update Release

• Based on the last major release and latest
  Service Pack
• Delivers new features to the present server OS
  generation
• Incorporates select feature packs previously
  released to the Web
• Gives down-level previews of next major release
  features
• All Windows Server 2003 R2 features roll forward
  to Windows Server Longhorn
• Integrate new R2 features easily into your
  environment
• Do not have to reset OS evaluation and
  certification testing
• Windows Server 2003 R2 has same core bits as
  Windows Server 2003 SP1
• Almost all R2 Components installed optionally
• Same app compatibility, quality, reliability, and
  performance
• Same servicing tree as last major release
• Single set of patches and Service Packs for
  Windows Server 2003 and R2

5
Feature Packs and Other Server Products/Technologi
es
For Enterprise Datacenter Editions Only Gold
colored items also in Windows Server 2003 R2
6
Windows Server 2003 Family
7
Windows SharePoint Services
SP1 x64
.NET Framework 2.0
8
Simplified Branch Server Management

• Customer challenges
• Wide Area Network latency
• Management at branch sites
• Goal
• Extend connectivity and reliability to and from
  the branch office, control the total cost of
  ownership (TCO) of branch IT infrastructure
• Key Benefits
• Centralized backup and management of file and
  print services
• High availability
• Efficient publishing and collaboration
• Remote server management
• Key Enablers
• Distributed File System
• Remote differential compression
• Management console
• Failover with failback
• Print management console
• Web Services (WS) for Management

9
Identity and Access ManagementActive Directory
Federation Services

• Customer Challenges
• Organizations need to extend access for people
  and application outside the firewall - Customers,
  Suppliers, Partners, Virtual Employees
• Goal
• Extend connectivity to people and applications
  beyond the firewall, control initial setup and
  ongoing identity management costs
• Key Benefits
• Extends value of Active Directory infrastructure
  for extranet scenarios (Single-sign-on and
  Identity Federation)
• Promotes IT efficiency, end user productivity,
  and better security
• Tight integration with Windows Server
  technologies
• Key Enablers
• Active Directory Federation Services, Active
  Directory Application Mode, Authorization Manager
• Windows SharePoint Services
• WS- specification support for interoperability
  with third-party security solutions

10
Efficient Storage Management

• Customer challenges
• Storage growth estimates 60-100 per year
• Costs of managing storage can be 10X the cost of
  storage
• Networked storage solutions can be complex
• Goal
• Extend connectivity to UNIX file systems, control
  storage setup, and ongoing storage management
  costs
• Key Benefits
• Simple system area network (SAN) provisioning
• File quota management, file screening, and file
  storage reporting
• UNIX Network File System (NFS) connectivity
• Key Enablers
• Simple SAN management for the it generalist
• File server resource management
• NFS support
• Unified file server role management console

11
UNIX Interoperability

• Customer Challenges
• Customers with heterogeneous systems need to
  share files between platforms, manage separate
  environments, invest in diverse skill sets
• Goal
• Extend connectivity in heterogeneous environments
  and UNIX interoperability, control IT management
  costs
• Key Scenarios
• Seamless UNIX/Windows Interoperability
• UNIX/Windows cross-platform management
• Leverage existing UNIX IT skills
• UNIX to Windows application portability
• Key Enablers
• UNIX interoperability components integrated with
  operating system
• NFS Admin and Utilities, NFS Server/Client
• User Name Mapping
• Password Sync
• Network Information System Server
• Subsystem for UNIX Applications

12
Branch Office Windows Server 2003 R2
13
Branch Office Infrastructure

• WAN Challenge - Low Bandwidth and High Latency
• Hinders branch performance ? productivity
• LAN speeds mask inefficient protocols
• Branch Servers
• Workaround WAN limitations/availibility, but
  difficult to manage
• Branch File, Print, AD, DNS, DHCP, SMS, ISA
  caching, Virtual Server for LOB applications
• Hub AD, DNS, DHCP, WINS, MOM
• Updated for R2 DFS and Print Management
  technologies, FSRM

14
Branch Office Infrastructure Solution
(BOIS)Current Guides and Tools using R2

• Comprehensive Planning and Deployment Guide
• Conceptual Information
• Prescriptive Guidance
• Best Practices
• Automation Tools
• Available at http//www.microsoft.com/technet/i
  tsolutions/branch/default.mspx
• A Solution Accelerator released to simplify the
  planning, deployment, and maintenance of Branch
  Offices using R2 technologies.

15
Technologies

• File Server
• Distributed File System (DFS)
• Namespace improvements (DFS-N)
• Replication (File Replication Services 2-FRSv2
  DFS-R)
• via Remote Differential Compression (RDC)
• via Management Console 3.0
• File Server Resource Management
• Print Server
• Print Management Console (PMC)

16
DFS Distributed File SystemSession overview

• Covered in this Session
• Data Namespace
• Data Availability
• Data Replication
• DFS Usage Scenarios
• Not Covered in this session
• File Server Migration/Consolidation from old
  Hardware (FSMT File Server Migration Toolkit)
• Migration from FRS to DFS-R (Webcast)

17
Distributed File System Overview

• Namespaces Virtualises File Servers (resources)
• Replication Fault-Tolerance
• Many Usage Scenarios

18
Unified Distributed File SystemTerminology

• DFS-N(amespace)
• DFS-R(eplication)

19
Why use DFS?

• Presents virtual tree of folders known as
  namespace based on organisational needs
• Independence of server names (transparant)
• Minimal amount of drive mappings
• Redundancy of data (via replication)
• WAN load balancing
• Automatic least cost routing
• Ease of manageability
• WAN efficiency with Replication/RDC

20
Deployment Scenario 1Data Collection

• Goal Consolidate Branch Data for Centralised
  Redundancy and Backup through Replication
• Key Requirements
• Branch data efficiently replicated to the hub
• If branch server unavailable, fail-over to hub
• Easy recovery of branch server data (cache)
• Fail-back to branch server once it recovers

21
DFS Scenario 1 Data Collection
Collection Server In Hub
DFS Replication
DFS Namespace
X
Server inGent Branch
User inGent Branch
22
Deployment Scenario 1 Complementary Products

• General Purpose Backup Open Files
• Microsoft System Center Data Protection Manager
  (DPM 2006)
• Third-party backup applications
• Tight Consistency Collaboration
• Microsoft SharePoint
• Third-party storage partners
• See http//www.microsoft.com/branchoffice

23
Deployment Scenario 2Data Publication

• Goal Distribute data to a number of Branch (and
  Hub) Sites
• Key Requirements
• Branch data can act as cache for centrally
  authored data
• If branch server unavailable, fail-over to hub
• Fail-back to branch once it recovers

24
DFS Scenario 2 Data Publication
Server inGent Branch
User inGent Branch
DFS Replication
Server in Brussels Hub
X
DFS Namespace
User inArlon Branch
Server inArlon Branch
25
Deployment Scenario 3 Documents for Roaming
User

• Goal Enable Users to Access Their Documents from
  Closest Location
• Key Requirements
• Branch data efficiently replicated to other
  branches
• User accesses closest branch location
• Fail-over to hub if branch server unavailable

26
DFS Scenario 3 Roaming User Documents
Server inGent Branch
DFS Replication
Server in Brussels Hub
DFS Namespace
Server inArlon Branch
27
Whats new in DFS with R2?Overview

• DFS Management user interface
• DFS-N(amespace)
• Namespace Failback
• Folder Target Priority
• Namespace Delegation
• DFS-R(eplication)
• RDC (Remote Differential Compression)
• VSS Support

28
DFS Management User Interface

• Based on MMC 3.0 (Actions pane)
• Allows new management operations
• Hierarchical view of namespace(using Folders
  and Folder Target Links)
• New features rename links, drag n drop
• Incorporates functionality that was previously
  only available via CLI (Command Line Interface)

29
DFS Namespace Management Console
30
DFS Management Console
31
DFS-N Namespace Failback

• Allows clients to return to preferred server
  after failover.
• Open files stay open against failover server
• Requires client QFE
• KB 898900 (post-XPSP2)
• Enabled on namespace server
• DFSUtil (SP1)
• DFS Management snap-in (R2)

32
DFS-N Folder Target Priority

• Extended control of referral ordering
• Configured at DFS folder
• Globally first/last
• First/Last in site (equal cost)
• Key scenarios
• Block branch-to-branch failover
• Example in branch site only with hub servers
  global last
• Hot standby server
• Example Hot standby Last in site

33
DFS-N Namespace Delegation

• Delegation of admin rights for Windows Server
  2003 SP1 and later
• Domain-based and Stand-alone Namespaces
• Local Admin permissions still required to create
  a DFS namespace

34
Other Namespace Topics

• Access Based Enumeration
• Requires extra configuration when used with DFS
  namespaces
• KB Q907458
• Namespace Backup/Recovery
• DFSutil.exe command line tool must be used for
  backup
• Namespace Monitoring
• MOM 2005 Management Pack

35
DFS Namespace Feature Summary
36
DFS-R(eplication)

• State-Based synchronisation algorithm
• Uses new Remote Differential Compression (RDC)
  and dictionary compression
• Bandwidth Throttling and Scheduling with 15
  Minute granularity
• Multimaster with conflict resolution
• Allows for large and flexible topology
• Topology re-use of multiple replicated folders in
  a Replication Group
• Self-Healing (Automatic Recovery from USN Journal
  Wraps, Journal Losses and Database corruption)
• Configuration Information can be stored in Active
  Directory

37
Multi Master with Conflict Resolution

• Conflicts
• Different for files and directories
• Last writer wins for files
• Earliest Creator wins for directories
• Types of Conflicts
• Name Conflict
• Update Conflict
• Manifest (xml) to identify origin of looser
• Deletes
• Hide away remote deletes so that they can be used
  by RDC during restore

38
Staging Sizing Considerations

• Initial sync size must be proportional to the
  initial size
• Operational size dependent on
• Average drop size/day
• Largest drop size/day to handle bursts of change
• Number of max simultaneous threads for
  downloading (4) and serving (5)
• Calculator max (avg drop size/day, min
  (9largest files, largest drop size/day))
• Additionally if hub increasing staging is
  beneficial so that RDC can use pre-computed
  hashes for similar files

39
DFS Replication Management Console
40
DFS Management ConsoleDFS-R
41
Remote Differential Compression (RDC)

• Brand new delta-based compression algorithm
• Existing objects Efficiently detects insertions,
  removals, re-arrangements of data
• New objects Efficiently discovers and
  reconstructs using relevant pieces of object on
  receiving machine (cross-file)
• Works on any file type, applicable to any
  client/server
• Only send (minimal) deltas when transferring data
  over a network and use dictionary compression
• Application independent
• Requires no local change tracking (state based)

42
Remote Differential Compression (RDC) Algorithm
Client
Server
Original file
Updated file
Request file
MD421 MD425
use recursion
Fetch new chunks 3, 4
The brown dog was
so lazy that he
43
Remote Differential Compression (RDC)Example

• RDC efficiency examples
• Change title in a 3.5-MB PowerPoint file, resync
  takes just 16 K

44
Remote Differential Compression
45
RDC Reduction Factors
Bandwidth Reduction Factors RDC vs. Full File
Transfer
450
409
400
350
292
300
250
200
150
92
100
41
31
30
50
17
15
13
3
0
.DOC 489 K
.DOC 2.6 M
.MPP 241K
.PPT 594K
.XLS 2.4M
.ZIP 348K
.HTM 425K
.PPT 3.9M
.PST 293M
.VSD 318 K
46
DFS Replication Feature Summary
47
DFS Manageability

• New Management Console
• Administrative Delegation
• Command Line for Scripting (Dfsutil, Dfsradmin)
• WMI Provider for Configuration and Monitoring
• In-the-box Reporting of Health and Efficiency
• MOM 2005 Management Pack with State View

48
DFS Reporting

• HTML Report
• Generated on Demand

49
DFS Reporting
50
DFS MOM Management Packs

• DFS (Namespace) Management Pack Available Now
• DFS Replication Management Pack to be released

51
DFS Management Feature Summary
52
Questions from the Beta Program (1)

• Q Does DFSR replicate files that are open by
  another application?
• A If a file is locked exclusively, it cannot be
  replicated. Replication is triggered on file
  close.
• Q Can RDC communicate with the standard FRS?
• A All the members in DFS replication should run
  RDC. It does not communicate with FRS-1.
• Q Can I place the staging folder on different
  volumes?
• A Staging folders could be put on different
  volumes
• Q Is DFS smart enough to tell if the differences
  in a file are bigger than the new file?
• A The overhead of the RDC algorithm is minimal.
  This also provides support for checkpointing.
• Q Is the DFS information encrypted before
  transmission, or is a VPN required/recommended?
• A DFSR uses RPC with encryption.
• Q Is RDC true block level replication?
• A RDC is a general purpose protocol for
  compressing file transfer over the wire. DFSR
  happens to use RDC on the file level (not at the
  disk block level).
• Q Do the servers participating in replication
  HAVE to be in the same domain?

53
Questions from the Beta Program (2)

• Q Does cross-file RDC requires R2 Entreprise
  edition
• A Yes, at least (or just) 1 member in the
  replication group should be running R2 Enterprise
  edition
• Q Can I upgrade my Windows Server 2003 Standard
  edition to Windows Server 2003 Enterprise
• A Yes, you can it is fully supported (Q810613 )
• Q How do I migrate from FRS to DFS-R
• A Have a look at the following webcast
• Q Does DFS-R support EFS
• A No, DFS-R does not support EFS encryption, but
  is supported in the LH timeframe.
• Q Does DFS support ABE (Access Based
  Enumeration)
• A Yes, but follow the guidelines in Q907458
  (How to implement ABE on DFS)

54
DFS and Hotfixes

• Q898900 DFS Namespaces Client failback
• Q903651 Multiple roots on Windows Server 2003,
  Standard Edition
• Q908521 - Outlook DFS-R
• Q222328/Q839647 - Outlook PST unlock DFS-R

55
Print Management Console (PMC)

• Consolidated Print Server Management
• 1 to Many (Print Servers) Console
• MMC Based
• Filters
• Columns
• Conditional Grouping
• Optimised for WAN Bandwidth
• Publishing of Printers via Group Policy
• Per User
• Per Machine
• Ships in R2, but can be used to administer
  earlier Windows Print Servers (2000/2003)

56
Printer Management Console
57
Print Management Console
58
The Branch VisionAchieving the Vision Roadmap
Making Key Server Roles Branch-Friendly

• WAN-Friendly File Replication
• Differential Compression Library
• Scalable Monitoring
• Centralised Printer Management

• DFS Replication for SYSVOL
• On Demand DFS Replication
• PC-to-PC Sync (My Documents)
• AD Improvements (RO DC,SRV)
• Improvements in Printer and Networking
• Improved Offline files Folders
• Cluster support
• EFS Support

2006
2007
59
R2 and Branch Offices Summary

• Windows Optimising for Branches and WANs
• Extensive Documentation Today
• R2 Provides Branch-Friendly Features
• File and Print roles are focus
• DFS and RDC are key enabling technologies
• PMC provides print server management
• Major Updates to DFS
• Longhorn broadens the Branch Vision to more
  server roles

60
DFS and Branch Office Solutions

• DFS Home Page
• http//www.microsoft.com/dfs
• Branch Office Home Page
• http//www.microsoft.com/branchoffice

61
Complete list of R2 features

• Windows Server 2003 R2
• Technical Reviewers Guide
• Feature Matrix
• White Papers
• DFS, PMC, FSRM, ADFS, AD/AM, WS-Mgmt, SAN Mgmt,
  etc
• http//www.microsoft.com/windowsserver2003/R2

62
(No Transcript)