Seminar Windows Server 2012 features


Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Seminar Windows Server 2012 features

  1. 1. Windows Server 2012Darmawan SuandiTechnical Evangelist, Developer and Platform Evangelist GroupMicrosoft
  2. 2. Agenda Server Manager Minimal Shell Power Shell 3.0 Storage Spaces IIS 8.0 – CPU Throttling
  3. 3. Management and InfrastructureWindows Server 2012 User Interface Changes
  4. 4. Server ManagerWhy redesigned? How does it benefit admins?
  5. 5. Why Server Manager Redesigned?
  6. 6. Modern UI Style and the Local ServerExperience• By default, Server Manager starts when logging on to server• Administrative Tools available from the Tools Menu
  7. 7. Server ManagerDEMO
  8. 8. Window Server 2012 UserInterface ChangesWhy should I care?
  9. 9. Why should I care?The challenges… • Lowering the attack footprint of the server to the smallest size possible while keeping it fully patched is a primary responsibility of administrators • Many administrators are uncomfortable with only a minimal command-line interface (Server Core)The Windows Server 2012 solution… multiple interface options • Allows administrators to use the same familiar graphical tools to administer the server without using remote management tools • Removes the overhead of the other operating system elements not needed to perform that task • Does not require a re-installation to modify the level of GUI on a server; modified in the same manner as any other role or feature • Allows for a single server deployment image
  10. 10. User Interface ChangesWindows Server 2012 allows you to have three levels of UserInterface: • Server Core • Traditional server core with command line only interface • Minimal Installation Shell (“MinShell”) • Server Core plus select UI elements such as MMC support and Server Manager • Full Shell • Full Windows desktop, which can also include the Desktop Experience
  11. 11. MinShellDEMO
  12. 12. Windows PowerShellWhat is it?
  13. 13. What is Windows PowerShell?PowerShell is a distributed automation engine with a scripting language andinteractive shell(s). • Focuses on the business • Makes change safe through automation • Bridges the gap between Operators and DevelopersPowerShell 3.0 is available for the followingOperating Systems: • Built-in: • Windows Server 2012 • Windows 8 (built-in) • Downloadable for: • Windows 7 SP1 • Windows Server 2008 SP2 • Windows Server 2008 R2 SP1
  14. 14. Windows PowerShellWhy should I care?
  15. 15. Why should I care?The challenge… • Reduce errors during configuration changes • Reduce the skill set required for authoring automation of complex solutions • Locate and import the numerous PowerShell modules into each session • Reduce the syntax learning curve, especially for people new to PowerShell • Bridge the gap between Operators and DevelopersThe Windows Powershell 3.0 solution…. • Allows for use of tested scripts, reducing the number of errors that impact production environments • Improves efficiency due to the dramatic increase number of built-in cmdlets • Includes new features designed to speed understanding and correct usage of syntax (Show-Command) • Makes excellent progress toward bridging the gap between Operators and Developers
  16. 16. Windows PowerShellTechnical Overview
  17. 17. What’s New for IT Professionalsin PowerShell 3.0?Easier to Automate • ~2,430 built-in cmdlets (compared with ~ 230 in Windows Server 2008/R2) • Skill level required to successfully automate complex solutions is reduced • Language and utility cmdlets are simplified to reduce steps and syntax • Improved authoring tools • PowerShell ISE supports rich Intellisense, snippets, 3rd party extensibility, and a Show-Command windowWindows Workflow Foundation integration • Operators can use any available Workflow designers to create workflowsScheduled Jobs • Seamless integration with Task SchedulerRobust Networking • PowerShell Remoting enabled by default • Disconnected session support
  18. 18. Windows PowerShellDEMO
  19. 19. Storage SpacesOverview
  20. 20. What is Storage Spaces & ThinProvisioning?Storage Spaces • New in Windows Server 2012 • Provides an in-box storage virtualization that can use low-cost commodity storage devices • Aggregates unallocated space on physical disks installed in or connected to servers through a “pooling” model • Can provide a cost-effective platform for business critical storage across a variety of scenariosThin Provisioning • “Just-in-Time” allocations of storage with the ability to reclaim storage (“Trim”) • Integrated with Storage Spaces
  21. 21. Why should I care?The features of Storage Spaces are designed to meet a variety of challenges insupport of highly-available storage Storage pools • Can be mapped to combinations of hard disks as well as solid-state drives (SSDs) • Can be expanded dynamically by simply adding additional drives, thereby seamlessly scaling to cope with unceasing data growth Multitenancy • Administration of storage pools can be controlled through access control lists (ACLs) and delegated on a per-pool basis • Can be fully integrated with Active Directory Domain Services Resilient storage • Storage Spaces support two optional resiliency modes (mirroring and parity) • Per-pool support for disks that are reserved for replacing failed disks (hot spares), background scrubbing, and intelligent error correction allow continuous service availability despite storage component failures
  22. 22. Why should I care? (cont.)Continuous Availability • Failover clustering integration delivers continuously available service deployments • One or more pools can be clustered across multiple nodes within a single cluster. Storage spaces can then be instantiated on individual nodes, and the storage will seamlessly fail over to a different node when necessary (in response to failure conditions or due to load balancing) • Integration with CSVs permits scale-out access to dataOptimal storage use through thin provisioning • To allow businesses to easily share storage capacity among multiple unrelated data sets and thereby maximize capacity use • Trim support permits capacity reclamation when possibleOperational simplicity • Easily managed through the File Services role in Server Manager • Fully remoteable and scriptable management through the Windows Storage Management API, WMI, and Windows PowerShell • Designed to be compatible with existing backup-restore and cloning tools, as well as snapshotting infrastructures
  23. 23. Storage SpacesTechnical Overview
  24. 24. Storage Spaces Requirements• Windows Server 2012 Drive Stand-Alone Clustered File• Serial ATA (SATA) or Serial Attached SCSI (SAS) Type File Servers Servers connected disks (in an optional just-a-bunch-of- SATA Supported disks [JBOD] enclosure) SCSI Supported• Multinode clustered shared-storage deployments iSCSI Supported Supported • Two or more servers running Windows Server SAS Supported Supported 2012 USB Supported • Requirements as specified for failover clustering and Windows CSV • SAS connected JBODs that comply with Windows Certification requirements• The criterion for determining which drives are eligible to be part of a Pool are: • Minimum drive size is 10 GB • Drive is empty, i.e. no partition data exists on the drive • Drive is not assigned to any other pool • The Primordial Pool will consist of Physical Disks that are not assigned to any existing Storage Pool
  25. 25. Storage SpacesDEMO
  26. 26. Web Application Deploymentwith IIS 8.0Why should I care?
  27. 27. Why should I care?The challenges The IIS 8.0 solutionsManaging a large number of dedicated IP addresses for each SNI uses the host name to identify the network endpoint sosecure site multiple dedicated IP addresses are no longer neededTaking full advantage of emerging high-performance NUMA-Aware Scalability can help you take advantage ofhardware systems emerging, high-performance server hardware systems for greater efficiency, scalability and manageabilityManaging resources across application pools IIS CPU Throttling is used to establish the maximum CPU consumption allowed per application poolManagement of SSL certificates is time consuming and SSL certificate management is greatly simplified - nocostly certificates to import to each server; there is now support for a centralized certificate storeImproving the speed of first connections to a web Application Initialization helps to speed up the initializationapplication of websitesProtecting web sites from DoS and brute force attacks IP Address filtering can be dynamically filtered; FTP Logon Attempt Restriction provides protection from brute-force attacksSupporting multiple types of applications on the same Open Web Platform provides for support and managementserver of .NET 3.5, .NET 4.5 and open source applications
  28. 28. Application Initialization • x Example modifications in applicationHost.config Application pool configuration entry: <add name=".NET v4.5" managedRuntimeVersion="v4.0" /> Application configuration entry: <application path="/appinit" applicationPool=".NET v4.5"> Example modifications to application level web.config <applicationInitialization skipManagedModules="true" > <add initializationPage="/default.aspx" /> </applicationInitialization>
  29. 29. IIS CPU Throttling Sandboxing sites and applications
  30. 30. IIS CPU ThrottlingDEMO
  31. 31. 31
  32. 32. Server Core • • • .Net Framework 4.5 Active Directory (AD) Active Directory Lightweight Directory Services (ADLDS) • Active Directory Certificate Services (ADCS)Microsoft promotes Server Core as • DHCP Serverthe primary server deployment • DNS Server • File Servicesoption • BITS Server • BranchCache • Server Core now supports more • Hyper-V roles and services, including .Net • Internet Information Services (IIS) Framework 4.5 and SQL Server • Printing Services • Streaming Media Services 2012 • iSCSI • Firewall-friendly remote • Load Balancing management (WinRM) and • MPIO Windows PowerShell are • qWave • Telnet enabled and installed by default • Unix Migration • Added the ability to easily move • SQL Server 2012 between Server Core and MinShell
  33. 33. MinShellMinimal User Experienceoption • Server Core with GUI tools • Server Manager and cmd.exe launch by default when server is booted •Allows other GUI tools to be loaded • Enabled through Add Roles and Features wizard, or with PowerShell
  34. 34. Enabling/Disabling MinShell Install-WindowsFeature Server-Gui-Mgmt-Infra Install-WindowsFeature Server-Gui-Shell Install-WindowsFeature Desktop-Experience Uninstall-WindowsFeature Server-GUI-Shell Uninstall-WindowsFeature Server-GUI-Shell -remove
  35. 35. Interface Feature Sets Server Core MinServer Server W/GUI Desktop ExperienceCommand Prompt Available Available Available AvailableWindows PowerShell Available Available Available AvailableServer Manager Not Available Available Available AvailableMMC Not Available Available Available AvailableControl Panel Not Available Not Available Available AvailableControl Panel Applets Not Available Some Available Available AvailableWindows Explorer Not Available Not Available Available AvailableTaskbar Not Available Not Available Available AvailableNotification Area Not Available Not Available Available AvailableInternet Explorer Not Available Not Available Available AvailableHelp Not Available Not Available Available AvailableThemes Not Available Not Available Not Available AvailableMetro Start Screen Not Available Not Available Not Available AvailableMetro Apps Not Available Not Available Not Available AvailableMedia Player Not Available Not Available Not Available Available