Presentation is loading. Please wait.

Presentation is loading. Please wait.

4/16/ :00 PM © 2005 Microsoft Corporation. All rights reserved.

Similar presentations


Presentation on theme: "4/16/ :00 PM © 2005 Microsoft Corporation. All rights reserved."— Presentation transcript:

1 4/16/2017 10:00 PM © 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

2 Embedded Server Technical Overview
Tres Hill Microsoft Corporation

3 Microsoft Server Workloads
MGX 2006 二○一七年四月十六日 Microsoft Server Workloads Embedded Server Products Server Functions Network Infrastructure Embedded Solutions Embedded Application Platform Information Worker Infrastructure Workloads Storage (file, portal) Print Collaboration Embedded Application Database Imaging Telco Industrial Any specialized server Remote Access Security Identity Management For Embedded Systems Speaker Notes: In today’s complex network architectures, servers perform many functions, among them those listed on this slide. Within each of these server functions are a series of server workloads. Depending on the size and complexity of the network, server workloads can be grouped onto a single server, such as Small Business Server, or a single server workload running on dedicated server. In some cases, the single server workload becomes an ideal candidate for a “server appliance” or “fixed function” server, particularly where the server hardware platform has been architected to efficiently address a particualr workload. For such solutions, Microsoft offers a variety of Embedded Server Products. For Embedded Systems Runtime For Embedded Systems © 2006 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.

4 Embedded Systems + Embedded Applications = Specialized Servers
Key Definitions Embedded Server Defined “Embedded Systems” means COMPANY’S computing system or device with an Image that (i) is designed for and distributed with an Embedded Application, and (ii) is not marketed or usable as a general purpose personal computing device (such as a personal computer) or a multi-function server or a commercially viable substitute for one of these systems. Embedded Application Defined “Embedded Application” means industry- or task-specific software programs and/or functionality with the following attributes: (a) It provides the primary functionality of the Embedded System (b) It is designed to meet the functionality requirements of the specific industry into which the Embedded System is marketed (c) It offers significant functionality in addition to the Licensed Product Software Embedded Systems + Embedded Applications = Specialized Servers

5 Embedded Server Product Benefits
Time to market, the OS is ready It is Windows Server, full binary equivalent Ease of deployment and management Network Interoperability Comprehensive set of hardware device drivers Extensive number of ISVs Certified solution programs Broad availability of services and support Foundation Support Speaker Notes: Read the slide

6 Embedded Channel Key Benefits The right server @ the right price.
Embedded licensing provisions tailored to embedded system OEM/SI business models for enhanced customer and partner satisfaction Agreements for use of Third Party Installer and Third Party Integrator are available for partners who outsource manufacturing and/or software engineering respectively Software license migration (downgrade rights) available to ease the pain of transitioning to a newer version of software 15 year product lifecycles provide longer availability and consistency of solutions required for long term OEM/SI customer contracts System Lock Preinstallation (SLP) available for qualifying partners eliminating the need for OS activation Software license cost savings for restricted/dedicated functionality OEM Volume Royalty Program available for qualifying partners provides additional software license cost savings

7 OEM Logistics Typical development cycle = 6 mos.
Download and evaluate Windows Embedded Server Product software. Prepare prototype and test proof of concept. Contact your Microsoft Authorized Embedded Distributor to determine which product SKU to use and request Customer License Agreement (CLA) and associated additional licensing provisions (ALPs) for review. Sign the CLA, return to distributor and request appropriate Windows Embedded Server Product OPK. Design, develop and test server prototype and install the selected Windows Embedded Server Product and embedded application (if applicable) Lock down the operating system for fixed function use (if applicable) Prep and clone final image for manufacture QA & Test systems Activate the OS via Windows Product Activation (WPA) method or System Lock Pre-installation (SLP) if/when OEM is eligible for SLP by shipping 100 units or more in the previous twelve (12) months Ship systems with required EULA and Certificate of Authentication (COA) affixed to the outside of the server enclosure. Speaker Notes: This list represents the typical steps and OEM will go through from product concept to shipping. Read the Slide

8 Server vs. Embedded Server Comparison
SPEC/Licensing Provisions Windows Server 2003 R2 Standard Edition Windows Server 2003 R2 for Embedded Systems, Standard Edition Windows Storage Server 2003 R2, Standard Edition Windows Server 2003 R2, Standard Edition for Embedded Systems and ISA 2006 Microsoft Windows Branch Office Appliance R2, Standard Edition Windows Server 2003, Standard Edition for Embedded Systems with SAS 3.0 Operating System Code Base R2 R1 SP1 Storage Capacity FS maximum RAM OS maximum Licensable Physical Processors 1-4 1-2 Preinstalled OS Optional Mandatory Line of Business Applications No Embedded Application ISA 2006 Remote Management Interface MMC Web UI Keyboard, Video & Mouse Firewall, VPN, Web Cache Cache Only Messaging or Enterprise Mail Yes POP3 mail only File service over Network Authentication Services Network Infrastructure Services Microsoft Net Load Balancing Clustering Print CALs Required Speaker Notes: This slide provides the key differences between our general purpose server operating system and our Embedded Server Products. The highlighted areas represent the difference between the licensing restrictions of the embedded server SKU compared to Windows Server For the purpose of simplifying the comparison, the Standard Edition within each product family is represented. Starting with Windows Server 2003 for Embedded Systems, notice the three key differences, the OS must be preinstalled, it cannot run line of business applications and it must have an embedded application. The same holds true for all the Windows Server 2003 with the Server Appliance Software 3.0 family. For Windows Storage Server 2003, Microsoft already provides the embedded application which is file and print. Similarly, for the ISA 2006 family, Microsoft provides the embedded application. More specific information on each SKU family follows later in the presentation. Highlighted areas indicate key licensing differences

9 For Embedded Systems

10 Windows Server 2003 R2 Software Architecture for Dedicated Servers
Anti-virus, Backup agents, etc… Embedded Application Windows Server 2003 R2 for Embedded Systems Contains complete operating system OEM Microsoft 3rd Party Speaker Notes: This software architecture slide depicts the different modules that represent the overall software platform. The green block is Windows Server 2003, the blue block identifies the OEMs embedded application and the red block represents additional utilities or services the OEM may wish add from third parties for additional functionality permitted within the solution. Please note as of April 1, 2005, the enterprise version of Windows Server 2003 for embedded systems is now available through Microsoft’s Embedded Distributor Channel.

11 Windows Server 2003 R2 Key Features
Based on Windows Server 2003 SP1 Microsoft Management Console 3.0 (MMC) .NET 2.0 framework included Enhanced DFS Remote differential compression (RDIF) Failover with failback Active Directory Federated Services (ADFS) Active Directory Application Mode (ADAM) SharePoint Services Storage Management Simple SAN Management Storage resources (quota, file screening, storage reporting) Unix Interoperability NFS server/client, NIS server (authentication, user name mapping, password sync) Subsystem for UNIX applications 32bit and 64bit versions Same CALs, upgrades not required

12 For Embedded Systems with Server Appliance Software 3.0

13 Server Appliance Software Version 3
Server Appliance Software Version 3.0 Software Architecture for Server Appliances Server Appliance Software Web UI framework for server management OEM Differentiators Includes all enhancements to UI OEM Proprietary Software Embedded Application 3rd Party Applications Anti-virus, SNMP agents, etc… Windows Server 2003 for Embedded Systems Contains complete operating system OEM Microsoft 3rd Party Key takeaway: OEMs building headless servers managed over a web UI Speaker Notes: As with the previous slide, the green block represents software Microsoft provides, the blue block represents the OEMs embedded application and any customizations they may wish to make to the Web browser user interface provided by Microsoft in the Server Appliance Software module and the red block represents additional utilities or services the OEM may wish add from third parties for additional functionality permitted within the solution. You will notice the key difference with this software architecture compared to the previous slide is the inclusion of the Server Appliance Software module which contains the Web UI for managing the server without the need for a connected keyboard, monitor or mouse.

14 Windows Server Appliance Software SKUs
SPEC/Licensing Provisions Microsoft® Windows Server™ 2003 for Telecommunications Systems with the Server Appliance Software 3.0 (1-4 CPU) Microsoft® Windows Server™ Server 2003, Standard Edition for Embedded Systems with the Server Appliance Software Version 3.0 (1-4 CPU Version) Microsoft® Windows Server™ 2003, 32-bit Enterprise Edition for Embedded Systems with the Server Appliance Software Version 3.0 (1-8 CPU Version) Operating System Code Base R1 SP1 RAM OS maximum Processors 1-4 1-8 Embedded Application Mandatory Remote Management Interface Web UI or MMC Messaging or Enterprise Mail POP3 mail and voice messaging application POP3 mail CompactPCI hot swap driver redistribution Yes No DHCP, DNS Services Yes, limited to embedded application Web or File service over Network Directory/Authentication Services Microsoft Network Load Balancing (NLB) Clustering Print Speaker Notes: Windows Server 2003 with Server Appliance Software comes in three different SKUs, all of which appear in the table shown here. For more information on the licensing restrictions for each SKU, please refer to a courtesy copy of the Additional Licensing Provisions. Highlighted areas indicate key licensing differences

15

16 Windows Storage Server 2003 Software Architecture for File Server Appliances
Storage Server Specific MMC Remote Desktop Management interface OEM Differentiators and Implementations Includes all enhancements to drivers and MMC 3rd Party Applications Anti-Virius, HA, DR, SRM Windows Server 2003 R2 for Embedded Systems Contains complete operating system OEM Microsoft 3rd Party Key takeaway: For building file servers or network attached storage or storage area network gateways. Speaker Notes: Windows Storage Server 2003 contains many of the same architectural blocks as the previous ones but you will notice the addition of file server optimizations and additional file protocols to the base Windows Server 2003 platform along with an optional third party software package called Storage Manager offered by Microsoft. Also, Microsoft has already modified the Web UI in order to manage the underlying software platform as a file server.

17 Windows Storage Server 2003 R2 SKUs
SPEC/Licensing Provisions Microsoft® Windows® Storage Server 2003 R2, Express (1 CPU Version) Microsoft® Windows® Storage Server 2003 R2, Workgroup Microsoft® Windows® Storage Server 2003 R2, Standard (1-4 CPU Version) Microsoft® Windows® Storage Server 2003 R2, Enterprise (1-8 CPU Version) Operating System Code Base R2 Storage Capacity (Max) FS maximum RAM OS maximum Licensable Physical Processors 1 1-4 1-8 NIC Ports 2 Unlimited Embedded Application No Remote Management Interface MMC Disk Drives 1-2 Any RAID Software Software or Hardware HDD Interface ATA, SATA F/C, SCSI, iSCSI, ATA iSCSI Target Software Optional Microsoft NLB Clustering Yes Transportable Snapshots Print Yes, 5 Printers Speaker Notes: The first two SKUs are Windows Storage Server 2003 Workgroup for systems having 4 disk drives or less, two network interfaces or less and a single processor. The Workgroup with print SKU allows the use of up to 5 printers which is ideal for remote office, branch office deployments. The Standard and Enterprise SKUs lift restrictions on maximum number of disks and NICs and are used in larger non-clustered and clustered systems respectively. Highlighted areas indicate key licensing differences

18 Universal Distributed Storage
Industry-standard hardware Advanced Functionality DAS, NAS, SAN, WAN, Internet Distributed Ubiquitous and always accessible Datacenter, departments and branch offices DAS, NAS, and SAN Talking Points Organizations are looking for new solutions that offer universal distributed storage. Universal By universal we mean advanced storage solutions that are built with industry standard hardware, that is less expensive, well understood, and easy to buy and replace… We also mean support for all physical methods of connecting to heterogeneous storage (DAS, NAS, SAN, LAN, WAN, Internet). Distributed By distributed we mean storage solutions that are ubiquitous – always available, and always accessible regardless of platform (server, desktop, laptop, cell phone) or location (datacenter, departments, branch offices, mobile). The two concepts will help to drive a new generation of storage solutions that are highly cost effective, scalable, available, and robust.

19 Windows SharePoint Services
Surveys Documents Tasks Contacts Members Calendar Team Discussions End-User Scenarios Collaborate on documents Share Information Manage virtual teams Key Features Presence integration Versioning, Check-in/Check Out Shared calendars, discussions… Office Integration Talking Points As we said earlier, Windows Storage Server 2003 R2 is the only NAS appliance with collaboration built in. End-User Scenarios Windows SharePoint Services will allow users to collaborate on documents, share information through an easy-to-use browser interface, and manage virtual teams. Key Features Key features included in Windows SharePoint Services include presence integration for instant messaging, document control versioning, as well as check-in and check-out, shared calendars, and integration with Office. Windows Storage Server 2003 R2 is the only NAS appliance with collaboration built in

20 Storage Options Explained
Hard drives installed into computers Difficult to Manage Difficult to Audit Difficult to Scale Direct Attached Storage Dedicated file server appliance Good performance Easy to deploy Network Attached Storage Fast, highly available Expensive Complex Storage Area Network Talking Points Before we discuss what iSCSI is and how iSCSI Target integrates with Windows Storage Server 2003 R2, let’s review the three general types of storage, Direct Attached Storage, Network Attached Storage, and Storage Area Networks. Direct Attached Storage Direct Attached Storage is the most straightforward type of storage. These are hard drives directly attached to a server’s bus. A great deal of management must be done locally, requiring a technician onsite. As an organization deploys more servers, particularly into remote offices, it becomes more and more difficult to optimize storage resources. Most likely, each location will require a separate backup and recovery solution, which is costly and time consuming. It is also troublesome to keep track of what servers have additional capacity and where you need to deploy more disks. Expansion requires adding another drive, which will require downtime. Network Attached Storage One solution is Network Attached Storage, or NAS. Dedicated File Servers, such as Windows Storage Server 2003 R2 Appliances, allow organizations to use the advanced storage features like those Windows Server 2003 R2. NAS solutions can provide high performance file services, however SAN solutions have some advantages in some situations. Storage Area Network Unlike NAS solutions, a Storage Area Network (SAN) require considerably more planning to deploy, and their management is more complex. SAN solutions are ideal for database and on-line processing applications requiring rapid data access. SAN storage devices serve block-level data rather than files, and thus require either a Fibre Channel network to transport the SCSI (Small Computer System Interface) commands or a Gigabit Ethernet infrastructure to do so via iSCSI (Internet SCSI). Fibre Channel equipment is highly specialized and can be costly. In addition, setup and management is potentially complex. A generalist IT administrator will require additional expertise to configure a Fibre Channel network. Smaller businesses often look at Fibre Channel and find the deployment cost prohibitive. NAS devices can also be attached to SANs. In this configuration, the NAS components necessary for filing are physically separated from the components necessary for storing: a NAS “head” or “gateway” (containing the filing functionality) attaches to the LAN network, and behind that lies the storage component—a “backend” SAN consisting of either the Fibre Channel network (wiring and switches) or the Gigabit Ethernet infrasctructure for iSCSI and the storage disks

21 Windows Storage Server
iSCSI SAN Solutions Exchange Server File Services Windows Storage Server iSCSI Initiator iSCSI Target SQL Server Talking Points A SAN separates the storage from the server, allowing for consolidation and easy expandability of the storage infrastructure. One SAN can offer storage services to multiple servers: In place of a server that provided exclusively file services, an iSCSI SAN can provide traditional file services as well as consolidate Exchange servers and SQL servers. This provides some obvious management and optimization advantages. Consolidation reduces the cost of supporting a system. The storage investment can go farther when split among multiple servers. iSCSI is SAN alternative iSCSI uses the familiar TCP/IP protocol over Ethernet. It can share the infrastructure an your existing network. The network team does not need to support unfamiliar hardware. It can deploy familiar, proven security features, such as IPSec. iSCSI also makes new applications possible: with security implementations in place, and distance limitations removed, Branch offices can be served by iSCSI, further consolidating resources and personnel. iSCSI success stories have led IDC, a global market research firm for IT industries, to predict that iSCSI disk array sales in 2004 will be about $45 million, a threefold increase from sales in 2003 (the year the iSCSI protocol was ratified). By 2007, revenue is predicted to be over $1 billion. (Market Analysis (2003): Worldwide Disk Storage Systems Forecast and Analysis,  , indicating a substantial increase in new iSCSI storage array adoption. Even more significantly, by 2007, the number of systems (host initiators) using iSCSI to connect to in-place storage—FC SANs—is forecast to be 6.5 million. Microsoft iSCSI Initiator To enable any server as an iSCSI Initiator, you need only install the free add-on Microsoft iSCSI Initiator on to the host server. Microsoft iSCSI Initiator is compatible with IPSec security, CHAP authentication, and MPIO multipathing to provide security, performance, and reliability between your iSCSI initiators and targets. The iSCSI Initiator will be built into Windows Vista, providing a simple deployment if iSCSI as a file server solution. Configurable Software Target The target in an iSCSI SAN is the physical location of your disks. Most likely, you will want a storage-focused server with highly reliable, high performance drives to serve as your iSCSI target. With a focus on storage capabilities, Windows Storage Server 2003 R2 is an ideal operating system for your iSCSI target. It is easily managed, integrates with your existing environment, and will provide reliable, high performance data services to your servers and services. You can enable a Windows Storage Server 2003 R2 server as an iSCSI target by installing Microsoft iSCSI Target, a software target service. By coupling Microsoft iSCSI Target and Windows Storage Server 2003 R2, You can select the proper hardware for your needs and configure it based on your requirements.

22 Scenario – Diskless Boot
Diskless Blade Servers Talking Points The benefits of migrating to SAN storage applies to boot volumes as well as to storage volumes. Managers of large server farms are finding that consolidating the OS simplifies management and upgrades as well. As a result, blade servers are the fastest growing segment of the server market. The Microsoft iSCSI initiator supports the ability to boot servers from remote iSCSI targets/disks.

23 Runtime For Embedded Systems

24 Windows Server 2003 R2 with ISA 2006 Software Architecture for Security Appliances
Internet Security and Acceleration Server 2004 VPN, Firewall and Web caching & MMC interface OEM Differentiators and Implementations Includes all enhancements to drivers, and utilities 3rd Party Applications Anti-virus, SNMP agents, etc… Windows Server 2003 R2 for Embedded Systems Contains complete operating system OEM Microsoft 3rd Party Key takeaway: These SKUs are used for building firewall, VPN and caching servers. Speaker Notes: The ISA 2006 block sits atop Windows Server 2003 and are represented in green. As before, the blue block is for OEM enhancements to drivers and utilities and the red block is for any additional third party software the OEM may wish to ship with the unit for additional functionality not prohibited in the Additional Licensing Provisions for ISA 2006.

25 Windows Server 2003 with ISA 2006
SPEC/Licensing Provisions Microsoft® Windows Server™ 2003 R2, Workgroup Edition for Embedded Systems and Microsoft® Internet and Acceleration Server 2004 Standard Edition (1 CPU Version) Microsoft® Windows Server™ 2003 R2, Standard Edition for Embedded Systems and Microsoft® Internet and Acceleration Server 2004 Standard Edition (1 CPU Version) Microsoft® Windows Server™ 2003 R2, Standard Edition for Embedded Systems and Microsoft® Internet and Acceleration Server 2004 Standard Edition (1 CPU Version) Microsoft® Windows Server™ 2003 R2, Standard Edition for Embedded Systems and Microsoft® Internet and Acceleration Server 2004 Enterprise Edition Operating System Code Base R2 Storage Capacity (Max) FS maximum 1 Disk, 40GB RAM 1GB OS maximum Licensable Physical Processors 1 1-2 1-4 NIC Ports 6 Unlimited Embedded Application No Remote Management Interface MMC Firewall Yes Concurrent VPN Connections 100 1000 1,000 4,000 Web Caching Messaging or Enterprise Mail Web or File service over Network Directory/Authentication Services Microsoft NLB Cluster Yes, unlimited CALs Required Speaker Notes: The key differences here are that the SKUs in the first and last column use identical software and offer Firewall and Web caching but there is a limitation on the number of concurrent VPN connections allowed, 100 vs The two SKUs in the middle are for either building a dedicated Web caching appliance or a Firewall/VPN appliance. All are priced according to the functionality offered. Highlighted areas indicate key licensing differences

26 What’s New in ISA 2006? ISA 2006 ISA 2004 Publishing/Protection
Automatic Link Translation Exchange/SharePoint wizards Web Publishing Load Balancing Publishing/Protection Manual Link Translation Authentication Single Sign On Multi-Factor Authentication (SSL Certs) LDAP / RADIUS OTP Back-End KCD/NTLM/Negotiate Delegation Customizable Form Authenticationb Authentication Active Directory / RADIUS Back-End HTTP Basic Delegation only OWA Form only Caching/Bandwidth FW Storage deployed at branches Caching/Bandwidth Windows Update (BITS) cache HTTP Compression Flooding Resiliency FW Storage support on slow links

27 Secure Application Publishing with ISA Server 2006
Integrated Security Efficient Management Fast, Secure Access NEW Smartcards & one-time password support NEW Web publishing load balancing NEW Single sign-on for multiple resource access NEW Customized logon forms for most devices & apps NEW Exchange & SharePoint publishing tools NEW Automatic translation of embedded internal links NEW LDAP authentication for Active Directory NEW Enhanced certificate administration NEW Authentication delegation (NTLM, Kerberos) Exchange Intranet Web Server SharePoint Active Directory External Web Server Administrator User DMZ Internal Network Internet HEAD QUARTERS NEW Improved idle-based time-outs for session mgmt

28 ISA Server 2006 as your Branch Office Gateway
Integrated Security Efficient Management Fast, Secure Access NEW BITS caching to accelerate software update deployment NEW Answer files on removable media for unattended install NEW HTTP traffic compression & caching NEW Fast policy propagation with low bandwidth optimizations NEW DiffServ IP settings for better bandwidth utilization NEW Enhanced certificate administration Exchange Intranet Web Server SharePoint Active Directory External Web Server DMZ Internal Network Internet S2S VPN BRANCH OFFICE HEAD QUARTERS User CSS Administrator

29 Web Access Protection with ISA Server 2006
Integrated Security Efficient Management Fast, Secure Access NEW Enhanced protection against DoS/DDoS attacks NEW Enhanced resource control for attack situations NEW Enhanced worm protection through connection quotas NEW Comprehensive alert triggers & responses External Web Site Attacker DMZ Internal Network Internet Extranet Web Server Administrator HEAD QUARTERS

30 Windows Branch Office Appliance R2 Software Architecture for Security Appliances
Internet Security and Acceleration Server 2004 VPN, Firewall and Web caching & MMC interface OEM Differentiators and Implementations Includes all enhancements to drivers, and utilities 3rd Party Applications Anti-virus, SNMP agents, etc… Windows Server 2003 for Embedded Systems Contains complete operating system OEM Microsoft 3rd Party This product used for remote/branch office servers. Speaker Notes: The ISA 2006 block sits atop Windows Server 2003 and are represented in green. As before, the blue block is for OEM enhancements to drivers and utilities and the red block is for any additional third party software the OEM may wish to ship with the unit for additional functionality not prohibited in the Additional Licensing Provisions for ISA 2006.

31 Windows Branch Office Appliance R2
SPEC/Licensing Provisions Microsoft® Windows® Branch Office Appliance R2, Standard Edition (1 CPU 5 CAL Version) Microsoft® Windows® Branch Office Appliance R2, Enterprise Edition (1 CPU 5 CAL Version) Operating System Code Base R2 Storage Capacity FS maximum RAM OS maximum Licensable Physical Processors 1-2 NIC Ports 3 6 Preinstalled OS Mandatory Line of Business Applications No Embedded Application ISA 2006 Remote Management Interface Optional Keyboard, Video & Mouse Firewall, VPN, Web Cache Cache Only Yes Messaging or Enterprise Mail File service over Network Authentication Services Network Infrastructure Services Microsoft NLB Cluster Yes, 2 nodes Print CALs Required Speaker Notes: This slide provides the key differences between our general purpose server operating system and our Embedded Server Products. The highlighted areas represent the difference between the licensing restrictions of the embedded server SKU compared to Windows Server For the purpose of simplifying the comparison, the Standard Edition within each product family is represented. Starting with Windows Server 2003 for Embedded Systems, notice the three key differences, the OS must be preinstalled, it cannot run line of business applications and it must have an embedded application. The same holds true for all the Windows Server 2003 with the Server Appliance Software 3.0 family. For Windows Storage Server 2003, Microsoft already provides the embedded application which is file and print. Similarly, for the ISA 2006 family, Microsoft provides the embedded application. More specific information on each SKU family follows later in the presentation. Highlighted area indicates difference compared to general purpose version

32 Runtime For Embedded Systems

33 Embedded Application Backend Database
4/16/ :00 PM Embedded Application Backend Database Highest Developer Productivity Mission Critical Abilities Better Business Decisions So what do we need to build these connected systems? You need a dynamic application platform - the most productive tools and most advanced database If you have such a platform, which helps you deliver more connected applications faster, you can achieve higher developer productivity, while meeting your mission critical requirements, and help your business make better decisions with more insight © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

34 Developer Productivity
4/16/ :00 PM Developer Productivity Integrated with Visual Studio and .NET Integrated development & debugging experience Execution location & programming language choice SQL Server Service Broker Asynchronous queuing for highly available applications Reliable messaging for scale out CacheSync High performance ASP.NET 2.0 apps XML Data Type Native XML support in the DB S4 S2 S3 S1 Do more with less code and fewer clicks My provides quick access to common functionality Smart tasks, snap lines, in place property editing Data schema used to rapidly create applications Web Form themes, templates, and site personalization Revitalize the iterative development experience Faster and streamlined development environment More efficient interactive debugging cycle Rapidly code solutions with Snippets and AutoCorrect Task oriented MyHelp targeted for VB developers Now that we’ve talked about overcoming software development challenges through IDE and language innovation, let’s shift focus a bit and discuss how we’ll construct various types of applications with Whidbey. We’ll begin with smart client applications. Windows Forms was introduced with v1.0 of the .NET Framework to empower developers with the full capabilities of the Windows client PC. In Whidbey, the Windows Forms classes will be enhanced to include an improved application deployment model, increased developer productivity, and simplified data access. Whidbey will also include notable enhancements to Windows client application performance and security. First, Windows Forms will include features and controls that increase developer productivity. These features and controls include the following: an Active Document Container for hosting Office documents, a Microsoft Office-style toolbar, intuitive splitter controls, a sound component that can run in partial trust, a Web browser control that can be accessed safely by way of managed code, and layout controls that automatically position and resize controls on a form as screen resolution or form dimensions change. In addition, implementation of multithreaded applications will be simplified through large investments in the Windows Forms asynchronous programming model. Many Windows Forms controls will feature asynchronous properties and will be complemented by a new, intuitive BackgroundWorker component to manage asynchronous tasks. These new controls and components will work with enhancements planned for the Windows Forms designer, including smart tags, Snap Lines, data preview, and more. Using smart tags, Windows client application developers can easily customize the look and behavior of data-bound controls with a click of the mouse; Snap Lines will simplify the layout of groups of controls within a form. Whidbey will also improve upon the .NET Framework No-Touch Deployment strategy with the introduction of "ClickOnce," a new technology that will bring the ease and safety of Web application deployment to Windows client applications. Building on the strengths of self-describing assemblies, component manifests, and side-by-side component installation, ClickOnce will enable a developer to publish, install, and service Windows client applications without fear of breaking existing functionality on the client operating system. Whereas traditional deployment builds an MSI package which may require modifications to the system registry and installation to shared system folders, ClickOnce publishing is tailored to install isolated, registration-free assemblies. Developers will have the choice of choosing which model is best for their Windows client application: ClickOnce Publishing, MSI Deployment, or a combination of both. New capabilities for Windows client applications installed using ClickOnce will include: support for running applications offline, rolling back to previous versions of an application, and listing an application in the Windows Start menu, as well as the Remove Programs catalog within the Control Panel. Additionally, ClickOnce Deployment in Whidbey will enable developers to distribute the .NET Framework with a Windows client application. To further support this deployment model, significant investments are being made in code access security, which protects users from malicious code by governing the capabilities of applications deployed from a remote Web server. In Whidbey, the scope of permissible actions that may be carried out safely by the deployed application will be expanded. Additionally, enhancements to the .NET Framework will make it easier for systems administrators to safely roll out updates to code access security policy. Web clients: Providing the thin-client counterpart to Windows client development is the Web application infrastructure ASP.NET, also introduced as part of version 1.0 of the .NET Framework. Through dramatically improved performance, productivity and security, Visual Studio Whidbey and ASP.NET will deliver a simplified, high performance, and powerful Web development experience. In the Whidbey release, ASP.NET will feature a new set of controls and infrastructure that simplify Web-based data access and will include functionality that facilitates code reuse, visual consistency, and aesthetic appeal. First, ASP.NET data access will be refined in the Whidbey release through the introduction of new controls for interacting with data. The DataSource control will be used declaratively or programmatically in an application to encapsulate the query logic required to work with data from databases, XML files, middle-tier business objects, and other sources. The DataSource exposes a set of common interfaces so that data-bound controls can easily consume different types of data without requiring a unique API for each data type it supports. Second, Whidbey will include features that ensure consistency and code reuse across pages within a Web site. The introduction of Master Pages will enable developers to quickly share layout across multiple pages by designing templates that specify the location of controls, menu bars, headers, and footers. Similar to visual inheritance in Windows Forms, Master Pages allow other pages on a Web site to inherit from a Master Page, automatically acquiring its look and feel. Also new to ASP.NET is the ability to incorporate themes and skins to enhance the appearance of Web applications. A skin is a set of properties, templates, and custom code that can be used to standardize the size, font, and other characteristics of controls on a page. A theme incorporates multiple skins and style sheets to specify the overall look and feel of a Web site. Themes and skins will be simple to package, transfer, and apply to other Web sites. In addition, ASP.NET will provide several built-in themes that developers can use to build aesthetically appealing Web sites out of the box. Third, Web application developers using Whidbey will be able to increase their application performance by taking advantage of SQL cache invalidation. This method of data caching facilitates significant performance improvements by caching data retrieved from a SQL Server database until an update to that data is made. When developing against a SQL Server Yukon database, however, developers will be able to cache data-driven pages for an indeterminate amount of time. This ability is due to Yukon's ability to proactively notify ASP.NET of changes made to the data. Internal testing of SQL cache invalidation has demonstrated performance benefits of up to 10 times that of non-cached data scenarios. Fourth, Web application developers will experience dramatic improvements in productivity through the use of the Visual Studio Whidbey IDE itself. With the new Web Developer IDE profile enabled, Whidbey will optimize the development environment and user experience by exposing only that functionality which is pertinent to Web application development. In addition, a new directory-based project model will remove the overhead of solution files while enabling Web developers to enjoy a traditional file system-based project paradigm with support for direct IIS enumeration, FTP, and file system access. As a result, FrontPage Server Extensions are no longer a requirement for building ASP.NET pages. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

35 SQL Server 2005 for Embedded Systems Software Architecture (OS sold separately)
SQL Server 2005 for Embedded Systems Runtime Back end database for the Embedded Application OEM Proprietary Software Embedded Application 3rd Party Applications Anti-virus, Backup agents, etc… Any Windows Server 2003 Embedded Operating System Contains complete OS in support of OEM Embedded Application. OEM Microsoft 3rd Party SQL SKU runtimes can only be used as a back-end database in support of the OEM’s embedded application. Speaker Notes: This software architecture slide depicts the different modules that represent the overall software platform. The green block is Windows Server 2003, the blue block identifies the OEMs embedded application and the red block represents additional utilities or services the OEM may wish add from third parties for additional functionality permitted within the solution. Please note as of April 1, 2005, the enterprise version of Windows Server 2003 for embedded systems is now available through Microsoft’s Embedded Distributor Channel.

36 SQL Server 2005 Runtime for Embedded Systems
SPEC/Licensing Provisions Microsoft® SQL Server™ 2005 Workgroup Edition for Embedded Systems (Runtime Edition) Microsoft® SQL Server™ 2005 Standard Edition for Embedded Systems (Runtime Edition) Microsoft® SQL Server™ 2005 Enterprise Edition for Embedded Systems (Runtime Edition) RAM 3GB OS maximum Processors 1-2 1-4 64-bit Support Windows on Windows Yes Preinstalled Mandatory Embedded Application Database Size No limit Partitioning No Parallel Index Operations Index Views Database Mirroring Online Indexing Online Restore Clustering Speaker Notes: Windows Server 2003 with Server Appliance Software comes in three different SKUs, all of which appear in the table shown here. For more information on the licensing restrictions for each SKU, please refer to a courtesy copy of the Additional Licensing Provisions. Highlighted areas indicate key licensing differences

37 Data Protection Manager for Embedded Systems Software Architecture (OS sold separately)
SC Data Protection Manager 2006 Disk based backup and recovery software application OEM Proprietary Software Embedded Application 3rd Party Applications Anti-virus, SNMP, etc… Windows Server 2003 R2 for Embedded Systems OR Windows Storage Server 2003 R2 Contains complete OS in support of OEM Solution. OEM Microsoft 3rd Party DPM is a near-continuous backup application that runs over either Windows Sever 2003 for Embedded Systems SKUs or certain Windows Storage Server 2003 SKUs. Licensable SKU: Microsoft® SC Data Protection Manager 2006 for Embedded Systems (3 DPML Version) Additional server agent licenses available Speaker Notes: This software architecture slide depicts the different modules that represent the overall software platform. The green block is Windows Server 2003, the blue block identifies the OEMs embedded application and the red block represents additional utilities or services the OEM may wish add from third parties for additional functionality permitted within the solution. Please note as of April 1, 2005, the enterprise version of Windows Server 2003 for embedded systems is now available through Microsoft’s Embedded Distributor Channel.

38 Embedded Server Roadmap
Windows Vista Server R2 for Embedded Systems Windows Vista Storage Server R2 Windows Vista Server R2 for Telecommunications Systems Windows Vista Server R2 for Embedded Systems w/ISA (2009) SQL Server Runtime for Embedded Systems (2008) Windows Vista Server for Embedded Systems Windows Vista Storage Server Windows Vista Server for Telecommunications Systems Windows Vista Server for Embedded Systems w/ISA Windows Server 2003 R2 for Telecommunications Systems Data Protection Manager v2 for Embedded Systems Windows Server 2003 R2 for Embedded Systems Windows Storage Server 2003 R2 Windows Unified Data Storage Server 2003 Windows Server 2003 R2 for Embedded Systems w/ISA 2006 Windows Branch Office Appliance R2 Windows Compute Cluster Server 2003 Windows Server 2003 for Telecommunications Systems Windows Server 2003 for Embedded Systems w/SAS 3.0 Windows NT Server Embedded Windows 2000 Server for Embedded Systems Windows Server 2003 for Embedded Systems Windows Server 2003 for Embedded Systems w/ISA 2004 SQL Server 2000 Runtime for Embedded Systems (per proc only) SQL Server 2005 Runtime for Embedded Systems Data Protection Manager 2006 for Embedded Systems iSCSI Target Note: Embedded Server Product releases track to general product releases. Changes in a general release will change the embedded equivalent. All items are subject to change or withdraw without notice.

39 Embedded Server Product Guide

40 Dev & Biz Tools Embedded Server Products Marketing & Technical
Evaluation Kit Marketing & Technical Resource Toolkit

41 Information Readily Available

42 Useful Links Windows Server 2003 R2 for Embedded Systems
Information: Download: Windows Storage Server 2003 R2 Information: Windows Server 2003 R2 with ISA 2006 Information: SQL 2005 for Embedded Systems Information: Speaker Notes: Read the slide.

43 4/16/ :00 PM Things To Remember Embedded Server Products are not stripped down versions, they are full binary equivalents, only the licensing provisions are different. Embedded Server Product Guides and Evaluation CDs are available from Microsoft Authorized Embedded Distributors. We value your business. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

44 Contacts Tres Hill EMEA Account Technology Specialist
OEM Specialized Servers +49 (0) (Mobile)

45 © 2006 Microsoft Corporation. All rights reserved.
4/16/ :00 PM © 2006 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. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.


Download ppt "4/16/ :00 PM © 2005 Microsoft Corporation. All rights reserved."

Similar presentations


Ads by Google