Windows Vista Section - The State of Windows Vista (November 2005)

Two years ago, Microsoft intrigued Windows Hardware Engineering Conference (WinHEC) 2003 attendees with visions of dancing windows, an interface that cast off its ties to pixels and scaled to the highest resolution displays, and seamless integration of 2D, 3D, video and animation that would greatly enhance users' experiences without taxing their CPU. Later that year at the Professional Developer's Conference (PDC), Microsoft offered developers an updated view of Windows Vista and discussed its proposed featureset in great detail, asking the developer community for feedback that would help shape the new OS and directly contribute to the product's direction. This was the start of a long dialog that resulted in many changes to the original product roadmap. Previously Windows Vista-only technologies such as Avalon have made their way to down-level platforms due to direct feedback from the developer community. Likewise, WinFS has been separated from the Windows Vista roadmap so that customer-requested capabilities may be added without delaying the operating system's release. Several builds of the OS have since been distributed to developers, each build containing changes and improvements to Application Programming Interfaces (APIs), largely based on feedback.

With WinHEC 2004 came a new build, more details, and more enhancements to the codebase. The WinHEC 2004 build also offered (with minor tweaking) users the opportunity to personally experience the accelerated Window Manager and Compositor on their own hardware. Since WinHEC 2004, early versions of Avalon and Indigo were released via the WinFX SDK Community Technology Preview (CTP) for Windows XP/Server 2003, further extending the evaluation and feedback loop to the general public. The expanded availability of several Vista technologies to down-level platforms has prompted some people to contemplate just what Windows Vista will offer that makes it a compelling upgrade compared to current platforms when they are equipped with WinFX. The short answer is that while down-level platforms will receive WinFX, it will only be a subset of the WinFX APIs offered in Vista.  Windows Vista will also include many new features and enhancements from the kernel up that will be exclusive to Vista.  For those that remember, think of down-level WinFX as analogous to Win32s which allowed partial API compatibility between Windows NT and Windows 3.1. With Win32s, developers could create 32-bit applications that ran on both Windows 3.1 and NT. However, while Windows 3.1 received some application compatibility, it did not receive the platform or user interface enhancements contained within Windows NT or Windows 9x.

At WinHEC 2005, Microsoft announced the completion of the Windows Vista driver model. Beta 1 was released in July 2005 and contained roughly 1/3 of the features expected for the final release  -- mostly developer-oriented. The release to manufacturing (RTM) is scheduled for 2006. In this article, we'll cover some of the features that make Windows Vista a worthwhile upgrade based upon currently known details about the platform. This is by no means a complete listing of expected Windows Vista features. Look to this section for future updates and to the ActiveWin.com homepage for the very latest in our continuing coverage of Windows Vista.

-- Jonathan Tigner

Preliminary information -- subject to change.

Presentation

Aero and Diamond

Windows Vista includes multiple graphical experience tiers that will be available to the end-user based on their hardware capabilities:

Classic

Classic is the base graphical experience offered in Vista.
The minimum display hardware requirements for the Classic experience include:

• Windows XP Display Driver Model driver

Aero Experience

The Aero Experience-capable minimum display hardware requirements for both discrete and UMA solutions include:

Aero Glass Experience

The Aero Glass-capable minimum display hardware requirements for both discrete and UMA solutions include:

Diamond

Diamond is the codename referring to the graphical experience associated with the Windows Vista Media Center interface.
The Diamond-capable minimum display hardware requirements for both discrete and UMA solutions include:

At a minimum, a Diamond-capable solution must have a signed driver that implements the Windows Vista Display Driver Model required for Diamond experience. The Diamond experience will not run with earlier display drivers. The Diamond experience is built specifically around the functionality provided by the Windows Graphics Foundation.

Windows Explorer / Information Visualization & Organization

Virtual Folders

Virtual Folders are similar to normal file folders in Windows except the files they contain are based on dynamic queries. Users can create virtual folders that list files based upon any attribute (such as Author, Keyword, etc.) of the files you want the virtual folder to contain. Usage of virtual folders may be similar to Outlook 2003's search folders.

Search

In Windows Vista, users can search directly from the start menu. Click the Start button, enter a search query and have results immediately returned within the start menu's item pane. This feature can also be used to execute applications. This is great for starting applications that may be nested several level into the start menu. This capability is similar to that currently offered by MSN Desktop Search.

Vista's Explorer allows users to not only execute fast searches to find their data, but also has several features and methods that allows users to build relationships around their data, group files according to personal preference, and visualize files without opening its associated application. All of this increases user productivity and decreases the time it takes to find the right information.

Lists

Users can create ordered lists of files that they want to keep together. The lists contain references (shortcuts) to the files instead of the actual files themselves. This is great for working with data that is located across several computers. Lists can be sent to other users (via email for example) and allowing all users in a group to keep a set of files together while always having access to the latest version of those files. Windows Vista Beta 2 will support using lists to access documents published via RSS feeds and internet sites.

Live Icons

In Windows Vista's Explorer, icons are not just static images. The icons are now live, scalable views of the actual document, allowing you to quickly and easily find the correct document you need.

Preview Pane

In Windows Vista's, Explorer windows have a preview pane at the bottom that presents relevant information about currently selected directories or documents and allows users to quickly modify document metadata.

Windows Sidebar

The Windows sidebar is a future technology which allows mini-applications called 'gadgets' to reside on the desktop. Gadgets are mirco-applications written using either the Windows API or standard web technologies which allow the user instant access to any and all information imaginable. These micro-applications reside either in the Windows sidebar, which docks unobtrusively to the side of the desktop, or they can float freely on the desktop, providing users with access to content.

Fundamentals

While Aero and Diamond provide the most visible changes to Windows Vista, the features that fall under the category of "Fundamentals" provide a more universally compelling case for adopting the new OS.

Security

Protected User Accounts

Since its first release, Windows NT has had a robust, granular security model capable of restricting applications from running with full privileges.  Unfortunately, due to the existence of applications that won't run without requiring administrative privileges at some point, the default user account for most Windows installations is an administrator. Due to the defaults and the possible troubles of running as a normal user, generally, only businesses and some power users take full advantage of the security model and run with least privilege. With Vista, Microsoft seeks to change the current situation and make it much easier to run as a normal user on Windows systems. They will accomplish this primarily via two fronts. The first change involves getting more developers to code and test their applications while running as a normal user. Second, the security model is being extended in Windows Vista to not only make it easier to run with least privilege when using normal applications, but also to limit a user's exposure while running applications that require elevated privileges.

LUA -- Limited User Account

In Windows Vista,  user tokens will be split between the application and the user. Even if you login as an administrator,  LUA apps run as a limited user.

 Application Impact Management 

Application Impact Management (AIM) manages applications that make changes to the system.  Vista monitors system changes (files, folders, registry settings, etc.) and can roll them back.
 

PA -- Protected Administrator

On Windows Vista, administrators also run with least privilege.  Applications requiring administrator privileges will run with elevated privileges. Only trusted applications can run with elevated privileges. By default, these applications must have a signed manifest to be trusted to run with elevated privileges. Manifests can be automatically generated for most legacy applications, however, some applications may break if AIM cannot make it run without administrator privileges. In this case, the Administrator may intervene and designate the application as trusted and allow it to run with elevated privilege.

Code Access Security

Windows Vista builds on the managed code infrastructure of .NET. Therefore, it offers the same Code Access Security (CAS) base that allows code to be verified based on evidence that extends beyond the currently running user. Code can be given or denied execution permission based on a number of factors such as its location, whether it is signed, or by whom it is published. This evidence is also combined with policies set by the administrator to determine whether the code can be executed. CAS makes it possible to run code that can be restricted to having a set of privileges below even that of a normal user.

 Secure Execution Environment 

The Secure Execution Environment (SEE) is the default set of CAS permissions for Windows Vista. Security is enforced via the Common Language Runtime (CLR). Only safe operations possible in the SEE. SEE permissions are similar to the permissions set .NET applications executed from the Internet Zone have today. Only a set of trusted libraries may be called in the SEE. Only isolated storage is available (applications cannot obtain file path information). Only trusted operations are allowed (file access, for instance, requires the user to use the file open dialog to give the application the file). Applications may request elevated privilege, if necessary, via a standard user interface. Applications may also restrict themselves to a subset of available permissions to further limit possible attack vectors.

Virtualization of Protected Resources

Access to protected resources is virtualized. Sandboxing is used for COM component extensions such as Windows Explorer shell extensions or Internet Explorer ActiveX controls. This helps to protect the host application from being crashed by an extension. Extensions can be enabled or disabled through attestation.

Windows Login

Winlogin (GINA) is being rewritten for Windows Vista to reduce number of necessary processes and components loaded. The new GINA will not be replaceable. A new Credential Provider Model will be used for extensibility. New mechanisms will also be provided to support existing functionality. A new Eventing and Stacking, and Chaining model will be provided.
 

Trusted Platform Module Services

The Trusted Platform Module (TPM) is a microchip designed to provide certain basic security-related functions to the software that utilizes TPM. The next version of Microsoft® Windows®, Vista, provides a set of services for applications that use TPM technologies. TPM Services in Windows Vista enable the development of several kinds of applications that provide significant value for customers. For example:

• Data protection and security. Examples of applications that help secure customer data include:
  
  • Key management utilities
    
  • Document-signing applications
    
  • Data protection/encryption applications
    
  • Attestation services
    
• System administration. Examples of applications that help administrators control TPMs in the enterprise include:
  
  • Remote Administration through WMI
    
  • Group Policy
    
  • Easy deployment and decommissioning
    
• System security for end users. Innovative features that are based on TPM technology in Windows Vista include:
  
  • Secure Startup
    
  • TPM-based Key Storage Provider

A detailed white paper about Trusted Platform Module Services is available for download: Trusted Platform Module Services in Windows Vista

Secure Startup

Secure Startup is a hardware-based security feature that addresses the growing concern for better data protection. The feature uses a Trusted Platform Module (TPM) 1.2 to protect user data and to ensure that a computer running Windows Vista has not been tampered with while the system was offline. Secure Startup provides both mobile and office enterprise information workers with more data protection when systems are lost or stolen. Detailed white papers about NAP is available for download: Secure Startup - Full Volume Encryption: Executive Overview | Secure Startup - Full Volume Encryption: Technical Overview.
 

Network Access Protection

Network Access Protection (NAP) for Windows Server "Longhorn" is a new set of operating system components that provide a platform for protected access to private networks. The NAP platform provides an integrated way of detecting the state of a network client that is attempting to connect to a network and restricting the access of the network client until the policy requirements for connecting to the network have been met.
To protect access to a network, a network infrastructure needs to provide the following areas of functionality:

• Policy validation Determines whether the computers are compliant with security policy. Compliant computers are deemed “healthy.”
• Network restriction Restricts access based on health state.
• Remediation Provides necessary updates to allow the computer to get healthy.
• Ongoing compliance Permits access to the network as long as the users’ computer meets policy requirements.
 

The NAP platform provides enforcement for Dynamic Host Configuration Protocol (DHCP) address configuration, virtual private network (VPN)-based network connections, and Internet Protocol security (IPsec)-based communications and an architecture through which policy validation, network restriction, remediation, and ongoing compliance can occur via additional components supplied by third-party software vendors or Microsoft.
The NAP platform requires servers running Windows Server "Longhorn" and clients running Windows® XP with Service Pack 2 (SP2). A detailed white paper about NAP is available for download here.
 

Performance and Reliability

Device Drivers

Windows Vista introduces a new, simplified device installation architecture that is more user-friendly, more flexible, and more secure than device installation for previous versions of Windows. This new device installation architecture solves problems with device installation on earlier versions of Windows, including issues related to client-side installation, missing files, digital signatures, and permissions needed to install drivers.

Windows Vista Device Installation Architecture

Under the Windows Vista device installation architecture, devices and kernel-mode device drivers can be installed only through approved device installation functions. These functions restrict an external component's ability to access or modify the internal resources of the device (the registry settings and files used for device installation) through unsupported means.

Using these functions ensures that driver installation packages cannot take actions that might conflict with other device installations, applications, or Windows components, and that any installed driver can be rolled back cleanly or uninstalled in the event of problems. Many of the rules that driver packages must follow to be installed successfully in Windows Vista represent best practices for Windows Server 2003, Windows XP, and earlier versions of Windows. Existing driver packages that implement these best practices should require few if any changes to work for Vista.

Driver packages designed to the Windows Vista device installation architecture help to ensure that drivers and associated applications are removed cleanly, without leaving files, state, or registry settings on the system that might cause instability or loss of functionality. Such driver packages also help preserve the stability and functionality of the system over time, as more devices are installed and uninstalled.

A new Driver Store holds complete device driver packages on disk. The packages are validated and checked for dependencies up front to mitigate the issue of problem drivers entering the Driver Store. The Driver Store and new installation rules eliminate partial driver installation scenarios where a driver may only install some components, then later prompt the user for a CD or the location of the source package to continue installation. This prevents situations where the user may no longer have access to the source media after an initial installation. Only driver packages located within the Driver Store may be installed.

Windows Driver Foundation

The Windows Driver Foundation (WDF) is a new object-oriented, event-driven driver model that includes several components:

• Kernel-mode driver framework
• User-mode driver framework
• Driver verification tools

Driver Quality Signature

Windows Vista enables installation of device drivers by non-administrator users. An installation rules engine checks the user's driver installation policy to determine whether or not to permit installation. Device drivers must be signed by a trusted source to allow non-administrator installation. Device drivers may be signed by Microsoft via the "Designed for Windows" Logo Program or Driver Quality Signature Program, or they may be signed by the hardware vendor or system administrator using Microsoft Authenticode technology. A local administrator can sign a driver package that is trusted on that system only; a domain administrator can sign a driver package that is trusted within that domain. Authenticode signing allows administrators to identify the publishers of all driver packages installed on a system and to verify that driver packages were not altered after publication.
Because all driver packages are signed in one way or another, signatures no longer affect the rank of a driver for Plug and Play.
 

Power Management

The are several changes and enhancements in the area of power management on Windows Vista. A new kernel power manager called the Device Power Policy Engine (DPPE) maintains and coordinates power policy behavior on behalf of devices and applications. The DPPE provides notifications about power policy, power state, thermal events, etc. Power policy is set by the user either by selecting one of the default  power policies (e.g., Maximum Battery, Automatic, Maximum Performance), or by defining a custom policy. Applications can respond to changes in power state or policy, for example, Windows Explorer could transition to a less graphically intense shell to conserve battery power if the Maximum Battery policy is set.

Platform Virtualization

Windows Virtualization Architecture

Windows Vista will support hypervisor-based platform virtualization. Some proposed features include:

• Support for 32-bit and 64-bit guests
• x64-only hosts
• Guest multiprocessing support
• Virtualized devices
• WMI management and control
• Save and restore
• Snapshots
• Virtual machine-related OS optimizations

Storage

WinFS

The new Windows File System (WinFS) will enter beta testing around the time of Windows Vista's retail release, and will be available as an update to Windows Vista following it's retail availability. WinFS lets users build relationships between various data such as Microsoft Word documents, emails, contact information, appointments, web pages, and other data types. It provides storage for non-file-backed items, increased data extensibility and  accessibility through the use of standardized schemas. WinFS provides access to a universal storage platform that can span multiple local or networked sources, providing general purpose and domain-specific data management and synchronization.

Transactional NTFS

With Windows Vista, transactions become a fundamental part of the platform with the inclusion of the Kernel Transaction Manager (KTM). This service is leveraged to provide full ACID transactional support for local and remote file shares. Check here for more info on Transactional NTFS.

Images Copyright Microsoft Corporation.

Return To The Windows Vista Section