Administration, SharePoint

System Center Virtual Machine Manager Self-Service Portal 2.0 Service Pack 1 Beta

System Center Virtual Machine Manager Self-Service Portal 2.0 is a pre-built, role-based, self-service portal for both datacenter managers and business unit IT consumers to simplify the provisioning of infrastructures for their applications and services.  The System Center Virtual Machine Manager Self-Service Portal 2.0 provides automated workflows designed to help on-board business unit IT departments and enables partners to expose their unique hardware capabilities through familiar Microsoft scripting technologies.

System Center Virtual Machine Manager Self-Service Portal 2.0 Service Pack 1 Beta

Built on Windows Server 2008 R2, Hyper-V technology, and System Center Virtual Machine Manager, the System Center Virtual Machine Manager Self-Service Portal 2.0 Service Pack 1 Beta enables you to offer infrastructure as a service, and respond more effectively to the rapidly changing needs of your organization.

What’s new in System Center Virtual Machine Manager Self-Service Portal 2.0 Service Pack 1 Beta

System Center Virtual Machine Manager Self-Service Portal 2.0 Service Pack 1 Beta provides users the ability to import virtual machines created outside the self-service portal but managed by System Center Virtual Machine Manager and additionally to re-import virtual machines previously removed.  Fully supported by Microsoft, the System Center Virtual Machine Manager Self-Service Portal 2.0 SP1 Beta is a partner-extensible solution that enables customers to dynamically pool, allocate, and manage their computer, network, and storage resources to deliver a private cloud platform inside their datacenter.

Get started with the System Center Virtual Machine Manager Self-Service Portal 2.0 Service Pack 1 Beta

Standard
Administration, SharePoint

Supporting Geographically Disperse Users

BranchCache

If you manage a centralized, regional, or distributed infrastructure with a distributed or clustered user base, a combination of Windows 7 and Windows Server 2008 R2 may be the best pairing to mitigate the impact of bandwidth and latency penalties that are commonly incurred under such distributions.

Windows 7 and Windows Server 2008 R2 introduce a new feature (BranchCache) that can reduce wide area network (WAN) utilization and enhance Microsoft SharePoint Products and Technologies responsiveness when users access content in a central office from branch office locations. When you enable BranchCache, a copy of the content that is retrieved from the Web server is cached within the branch office. If another client in the branch requests the same content, the client can download it directly from the local branch network without needing to retrieve the content by using the Wide Area Network (WAN).

The three (3) basic deployment models where BranchCache should be considered can be described as:

Centralized where a single datacenter serves geographically remote users.

image

Regional where geographically disperse datacenters serve users clustered around those datacenters.

image

Distributed where geographically disperse datacenters serve geographically disperse users.

image

BranchCache can be implemented in two modes, Hosted or Distributed Cache. The Hosted Cache mode is where a one or more servers configured with Windows Server 2008 R2 acts a host in the branch office. The clients in the branch office are configured with the FQDN of the server acting as the host and will request resources from the Hosted Cache when available, if the Hosted Cache is not available, it is retrieved from the content server by using the WAN and then offered to the Hosted Cache so that subsequent clients can benefit. The Hosted Cache mode is supported for use with Microsoft SharePoint Products and Technologies.

The Distributed Cache mode is intended to support smaller regional models (less than 50 clients) where it is not possible to deploy a dedicated server to the branch office(s) and operates as a peer to peer model. In this mode, local Windows 7 clients keep a copy of the content and make it available to other authorized clients that request the same data; however, unlike Hosted Cache mode, this configuration works across a single subnet only, in addition, clients that hibernate or otherwise disconnect from the network are not able to provide content to requesting clients.

Configuring BranchCache with Microsoft SharePoint Products and Technologies

Configuring Web Servers

The configuration of Web Servers in preparation for BranchCache requires only installing the BranchCache role on the server machine through the Server Manager or optionally the Command Prompt.

  1. Open Server Management on each Web server by clicking Start | All Programs | Administrative Tools | Server Manager.
  2. On the Server Manager dialog select the Roles node.
  3. On the Server Manager dialog in the Roles window, select Add Role.
  4. On the <> dialog select BranchCache from the list of available options and click Next.

Configuring the Hosted Cache Server

Install the BranchCache Feature

  1. Open Server Manager on the Hosted Cache server by clicking Start | Administrative Tools | Server Manager.
  2. On the Server Manager dialog select the Features node.
  3. On the Server Manager dialog in the Features window, select Add Features.
  4. On the Add Features Wizard select BranchCache from the list of available Features and click Next.
  5. On the Confirm Installation Selections dialog click Install.
  6. On the Installation Results dialog click Close.

Enable Hosted Cache Server Mode

  1. Open an elevated Command Prompt on the Hosted Cache server by clicking Start | All Programs | Accessories | Command Prompt.
  2. Enter netsh branchcache set service mode=HOSTEDSERVER in the Command Prompt and press Enter.

Configure the Cache

  1. Open an elevated Command Prompt on the Hosted Cache server by clicking Start | All Programs | Accessories | Command Prompt.
  2. Enter netsh branchcache set localcache directory=<drive>:<share>
  3. Enter netsh branchcache set cachesize size=<size in percent> percent=TRUE

Create a new Certificate

  1. On the Hosted Cache server open Microsoft Management Console by clicking Start | Run… and entering MMC in the Open… field.
  2. On the Microsoft Management Console click File | Add / remove snap-in.
  3. On the Add or Remove Snap-ins dialog select Certificates from the list of available snap-ins and click Add.
  4. On the Certificate snap-in dialog select Computer account from the list of available options and click Next.
  5. On the Select Computer dialog select Local computer (the computer this console is running on) and click Finish.
  6. On the Add or Remove Snap-ins dialog click OK.
  7. On the Console1 – [Console Root] dialog expand the Certificates (Local Computer) | Personal | nodes and then select Certificates.
  8. On the Console1 – [Console Root] dialog select Action | All Tasks | Import…
  9. On the Certificate Import Wizard* dialog click Next.
  10. On the Console1 – [Console Root] dialog double-click the certificate imported from the previous steps and select Details on the Certificate dialog.
  11. On the Certificate dialog select Thumbprint and copy the Thumbprint.
  12. Paste the copied Thumbprint into a text editor and remove any spaces.
  13. Open an elevated Command Prompt on the Hosted Cache server by clicking Start | All Programs | Accessories | Command Prompt.
  14. Enter netsh http add sslcert ipport:0.0.0.443 certhash=<paste from text editor> appid= and press Enter.
  15. Enter netsh branchcache show status all to confirm the configuration

* The Hosted Cache server requires a certificate with the Server Authentication EKU. Follow the steps on the Certificate Import Wizard to install your certificate. Once the certificate has been imported, follow the remaining steps in this section.

Configure Client Machines

Refer to http://technet.microsoft.com/en-us/library/dd637820(WS.10).aspx.

BranchCache can be used with Windows SharePoint Services 3.0, Microsoft Office SharePoint Server 2007, Microsoft SharePoint Foundation 2010, and Microsoft SharePoint Server 2010.

Learn more here http://technet.microsoft.com/en-us/library/dd755969(WS.10).aspx.

Office Document Cache (Upload Center)

Office Document Cache (ODC) is a concept new to Office 2010. ODC is a client repository that is used both when Office files are downloaded and uploaded to a server. In a download scenario, the files is downloaded to the cache and opened from that location, conversely, when a file is saved the document is saved to the cache where the upload occurs in the background asynchronously.

image

In the interest of performance, ODC manages changes differentially in that only file differentials are sent across the wire, so in the event a user edits a document, only those changes are transmitted as opposed to the entire document.

ODC uses the File Synchronization via SOAP over HTTP (FSSHTTP) protocol which requires both Microsoft SharePoint Foundation or Server 2010 and Office 2010 and supports Office Xml formats, for example docx, pptx, and xlsx.

The benefits of the Office Document Cache can be summarized as follows:

  • Clients can access documents even if the server is offline if the document has been previously downloaded to the cache.
  • Reduction in network utilization to support remote clients.
  • More efficient user experience by providing background data transfers.

SharePoint Workspace

Microsoft SharePoint Workspace replaces Microsoft Office Groove enabling fast, anytime, anywhere access to your Microsoft SharePoint team sites.

SharePoint Workspace allows users to synchronize SharePoint Server 2010 document libraries with SharePoint Workspace so you can access, view and edit files anytime and anywhere from your computer. Lists such as Discussion, Tasks, and custom lists are supported as well. You can even synchronize Business Connectivity Services lists so access to your backend systems is easy and painless.

To learn more see http://www.microsoft.com/office/2010/en/sharepoint-workspace/default.aspx.

Office Web Applications

The Office Web Applications online companions to Word, Excel, PowerPoint, and OneNote that provide the ability to work with Office documents from virtually anywhere with a supported browser.  Office Web Applications enable remote users to access only segments of information as opposed to downloading the entire document, spreadsheet, or presentation providing improved time to first page rendering when compared to the Office client in a similar scenario.

Browser View

image

Client View

image

Mobile Views

Mobile Views in SharePoint 2010 provide a version of pages optimized for mobile devices.  Mobile Views are effectively a standard SharePoint list view marked for additional use as a mobile list view. For more information see http://msdn.microsoft.com/en-us/library/ms462572.aspx.

List Item View

image

Thumbnail Preview

image

Next Generation TCP/IP Stack

Beyond BranchCache and Office Document Cache both Windows Vista/7 and Windows Server 2008 (incl. R2) feature the Next Generation TCP/IP stack which is a complete redesign of TCP/IP functionality for both Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6).

Performance enhancements to increase throughput in high-bandwidth, high-latency, and high-loss networking environments included in the Next Generation TCP/IP Stack include, for example, receive window auto-tuning which continuously determines the optimal receive window size by measuring the bandwidth-delay product and the application retrieve rate, and adjusts the maximum receive window size based on changing network conditions.

Despite supporting scalable windows in Windows Server 2003 and Windows XP the maximum receive window size still limits throughput because it is a fixed maximum size for all TCP connections, which can enhance throughput for some connections and decrease throughput for others. Additionally, the fixed maximum receive window size for a TCP connection does not vary with changing network conditions. In Windows Vista and Windows Server 2008 scaling is enabled by default allowing up to a 16 MB window size. As the data flows over the connection, the Next Generation TCP/IP stack monitors the connection, measures the current bandwidth-delay product for the connection and the application receive rate, and adjusts the receive window size to optimize throughput.

For additional information on improvements in network throughput and task completion times see also Enhanced Network Performance with Microsoft Windows Vista and Windows Server 2008 which examines the benefits of Next Generation TCP/IP Stack across a combination of Windows XP with Service Pack 2 and Windows Vista with Service Pack combined with Windows Server 2003 R2 and Windows Server 2008.

Windows Internet Explorer 8.x

Internet Explorer 8 can help further improvement performance for distributed users through increasing the number of parallel connections per server from 2 to 6, effectively tripling the number of elements that can be requested from a server in parallel translating into faster page download times when bandwidth is available. In Internet Explorer 7 there was the concept of blocking external scripts, in Internet Explorer 8 when an external scripts is encountered, it continues parsing on a second thread to ensure that it can continue downloading page elements as fast as possible resulting in both faster and more efficient downloads. The JScript engine included with Windows Internet Explorer 8.x speeds up many common user scenarios. Windows Internet Explorer 8.x includes improvements to widely-used JScript functionality such as faster string, array, and lookup operations and changes to the core architecture to reduce the cost of functions calls, object creation, and lookup patterns for variables scoped to the window or objects.

General

Search SharePoint Products and Technologies with Windows 7 Search Connectors

Windows Search Connectors are simply OSDX files that represent syndication syntax that references one or more resources.  Windows Search Connectors allow you to search the content of the location specified in the OSDX file from the Windows Shell.

The following example can be used to create a Windows 7 Search Connector for SharePoint.  This example assumes the Information Worker Demonstration Virtual Machine that can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=751fa0d1-356c-4002-9c60-d539896c66ce&displaylang=en.  Modify the values to suit your individual specifics.

Copy the Xml below into a new text document.

<?xml version="1.0" encoding="UTF-8"?>
  <OpenSearchDescription xmlns="
http://a9.com/-/spec/opensearch/1.1/" xmlns:ms-ose="http://schemas.microsoft.com/opensearchext/2009/">
    <ShortName>Contoso Intranet Search</ShortName>
    <Description>Search Contoso Intranet.</Description> 
    <Url type="application/rss+xml" template="http://intranet.contoso.com/SearchCenter/_layouts/srchrss.aspx?k={searchTerms}&amp;s=All%20Sites"/>
    <Url type="text/html" template="http://intranet.consoto.com/SearchCenter/Pages/Results.aspx?k={searchTerms}&amp;s=All%20Sites"/>
    <ms-ose:ResultsProcessing format="application/rss+xml">
    <ms-ose:LinkIsFilePath>-1</ms-ose:LinkIsFilePath>
    </ms-ose:ResultsProcessing>
</OpenSearchDescription>

Save the document as ContosoIntranet.odsx.

Double-click ContosoIntranet.odsx to install the connector.

Standard
Uncategorized

Windows Server 2008 R2 Enterprise Edition and SharePoint Server 2010 Better Together Whitepaper

A recently published whitepaper is now available on TechNet that describes the benefits of deploying Microsoft SharePoint Server 2010 on Microsoft Windows Server 2008 R2 Enterprise Edition and scenarios in which its features can be applied.

Excerpt

Microsoft® SharePoint® Server 2010 is the business collaboration platform for the enterprise and the Internet. SharePoint Server 2010 has become a business-critical application and an integral part of business processes. To help IT infrastructures to remain flexible and scalable to help support, manage, and secure expanded functionality, an influx of additional users and locations, and increasingly robust applications such as SharePoint Server 2010, we recommend that you choose the Windows Server® 2008 R2 Enterprise operating system during initial deployment.

Download the whitepaper today…

Standard
Uncategorized

Windows Server 2008, SQL Server 2008 Disaster Recovery Notes with SharePoint Products and Technolgies

In recent months there has been a great deal of discussion and debate on disaster recovery and high availability with Microsoft SharePoint Products and Technologies and with the recent releases of both Microsoft SQL Server 2008 and Windows Server 2008 there are open opportunities to leverage components available natively to these technologies and compliment a SharePoint Products and Technologies disaster recovery design.

One of the most significant challenges has been overcoming latency penalties applied through distance between the active and passive datacenters, particularly with Microsoft SQL Server Log Shipping since we’re dealing with SMB and a synchronous process.  This is where both SQL Server 2008 and Windows Server 2008 come in…

SQL Server 2008 introduces backup compression which can be further integrated in the Microsoft SQL Server Log Shipping configuration (see also http://msdn.microsoft.com/en-us/library/ms188168.aspx).  By compression the Transaction Log backups and scheduling an aggressive backup schedule in the configuration and administrator can apply a general level of predictability surrounding the size and number of Transaction Log backups and make more efficient use of bandwidth where working with limited throughput and maintaining synchronicity is a concern.

To compliment a Microsoft SQL Server Log Shipping configuration, an administrator can leverage the improvements made to Distributed File System in Windows Server 2008 to optimize WAN performance when copying Transaction Log backups to a remote Secondary server instance.  Windows Server 2008 DFSR improvements include:

  • RPC Asynchronous Pipe vs. Multiple RPC Calls in Windows Server 2003 R2
  • Asynchronous I/Os vs. Synchronous I/Os in Windows Server 2003 R2
  • Unbuffered I/Os vs. Buffered I/Os in Windows Server 2003 R2
  • Low Priority I/Os vs. Normal Priority I/Os in Windows Serve 2003 R2
  • 16 Concurrent File Downloads vs. 4 Concurrent File Downloads in Windows Server 2003 R2

In this scenario, Windows Server 2008 DFSR would be configured with the Microsoft SQL Server 2008 backup and load shares as members of a replication group actively replicating Transaction Log backups generated in through the Microsoft SQL Server 2008 Log Shipping configuration.  The Microsoft SQL Server Log Shipping Copy job would be disabled permitting DFSR to perform replication between the shares.

So what about my Domain Controllers?

Windows Server 2008 introduces support for Read-Only Domain Controllers and additionally Windows Server 2008 DFSR improvements can be realized providing AD DS schema version 31.

Standard
Uncategorized

Microsoft Windows Server 2008 as a Host Operating System for Microsoft Virtual Server 2005

Suppose you would like to use Windows Server 2008 as your host operating system, but the system does not provide support for Hyper-V.  The good news is that Microsoft Virtual Server 2005 will install and run under Windows Server 2008 providing the following conditions are met (including the Virtual Server Administration Web site):  see notes http://support.microsoft.com/kb/948515.



  1. You need to run Virtual Server 2005 R2 SP1

  2. You must have KB948515 applied to enable Windows Server 2008 host operating system support (http://www.microsoft.com/downloads/details.aspx?FamilyID=a79bcf9b-59f7-480b-a4b8-fb56f42e3348&displaylang=en)

  3. Internet Information Services 7.0 is configured to support the Virtual Server Administration Web site

Obtaining Virtual Server 2005 R2 Service Pack 1


Microsoft Virtual Server 2005 R2 Service Pack 1 (SP1) QFE contains the latest software updates for Virtual Server 2005 R2 SP1.


Download Microsoft Virtual Server 2005 R2 Service Pack 1 – http://technet.microsoft.com/en-us/evalcenter/bb738033.aspx


Release notes for Virtual Server 2005 R2 Service Pack 1 – http://technet2.microsoft.com/windowsserver/en/library/60009f7c-9a6b-472c-949a-4f047e791dd21033.mspx?mfr=true


Obtaining KB948515


This update for Microsoft Virtual Server R2 SP1 includes support for the following additional Host and Guest Operating Systems


Additional Guest Operating System support:
Windows Vista® Ultimate Edition with Service Pack 1 (SP1)
Windows Vista® Business Edition with Service Pack 1 (SP1)
Windows Vista® Enterprise Edition with Service Pack 1 (SP1)
Windows Server® 2008 Core
Windows Server® 2008 Standard
Windows Server® 2008 Datacenter
Windows Server® 2008 Enterprise
Windows Server® 2008 Small Business Server
Windows XP Professional with Service Pack 3


Additional Host Operating System support:
Windows Vista® Ultimate Edition with Service Pack 1 (SP1) (non-production use only)
Windows Vista® Business Edition with Service Pack 1 (SP1) (non-production use only)
Windows Vista® Enterprise Edition with Service Pack 1 (SP1)(non-production use only)
Windows Server® 2008 Core
Windows Server® 2008 Standard
Windows Server® 2008 Datacenter
Windows Server® 2008 Enterprise
Windows Server® 2008 Small Business Server
Windows XP Professional with Service Pack 3 (non-production use only)


Download details:  Virtual Server 2005 R2 Service Pack 1 Update – http://www.microsoft.com/downloads/details.aspx?FamilyID=a79bcf9b-59f7-480b-a4b8-fb56f42e3348&displaylang=en


Configuring Internet Information Services 7.0


To enable the Virtual Server Administration Web site on Windows Server 2008, Internet Information Services 7.0 should be configured as provided in the steps below:


On the host machine click Start and select Server Manager.


Click Roles.


Click Add Roles (see illustration).


image


On the Add Roles Wizard click Next >.


Select Web Server (IIS) from the list of available Roles.  Click Add Required Features on the Add features required for Web Server (IIS) page if prompted and then click Next >.


Click Next > on the Web Server (IIS) page.


On the Select Role Services page select the checkbox labeled CGI under Application Development.


On the Select Role Services page select the checkbox labeled Windows Authentication under Security.


On the Select Role Services page select the checkbox labeled IIS 6 Metabase Compatibility under Management Tools | IIS 6 Manageability Compatibility.


Accept the remaining default values and click Next > on the Select Role Services page.


Click Install on the Confirm Installation Selections page.


Click Close on the Installation results page.


The Web Server Role Services should appear similar to those as provided in the illustration below:


image


NOTES


If presented with a 401.2 error when browsing the Virtual Server Web application, ensure Windows Authentication is enabled both at the Web server and Web site levels, if the error persists, enable Anonymous Authentication for the Web site.  Authentication models can be configured in the Internet Information Services (IIS) Manager.


The Virtual Server Administration Web site requires scripting to be enabled for navigation.  To enable scripting, either add the Virtual Server Administration Web site to the Trusted Sites zone or optionally disable Internet Explorer Enhanced Security Configuration.


To configure Virtual Server settings using the Virtual Server Administration Web site you must run Internet Explorer as an Administrator in Windows Server 2008.


In the event an access denied-type message is presented when browsing the Virtual Server Administration Web site after performing the previous steps, reinstall Microsoft Virtual Server 2005 R2 Service Pack 1 after configuring Internet Information Services 7.0 as specified above.

Standard
Uncategorized

Add this to your image…

One of the most common configuration inconsistencies I find in SharePoint farms is the Web application path, in most scenarios the Web applications are provisioned under the default root path of C:InetpubwwwrootwssVirtualDirectories.  This is usually the result of oversight during the provisioning process. 


Windows SharePoint Services 3.0 provides a configuration field (see screenshot) that allows administrators to configure the path to the Web application host directory; however, in many cases, this setting is overlooked.  Unfortunately, once a Web application has been provisioned, the only reliable method of moving the Web application is to delete and recreate the Web application on the server farm.


image


Windows SharePoint Services 3.0 derives the directory information from the Web server registry setting at HKEY_LOCAL_MACHINESOFTWAREMicrosoftInetStpPathWWWRoot, this path is subsequently appended with wssVirtualDirectories.   To ensure Web applications are provisioned on the proper disk volume, modify the Registry values later in this post on your Web front-end computers to reference the desired path.  This can be modified either prior to or after Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 has been installed; however, any pre-existing Web applications will not reflect the path change (see above).


A Microsoft Internet Information Services best practice is to avoid using the default path (c:inetpubwwwroot) and moving Web content to a non-system directory.  By configuring the WWWRoot default path it provides a safeguard for oversight and promotes consistency across Web servers.


Configure the WWWRoot Default Path (Windows Server 2003)



  1. Click Start, and then select Run…

  2. In the Open field enter Regedit and click OK.

  3. Locate the HKEY_LOCAL_MACHINESOFTWAREMicrosoftInetStp key and modify the PathWWWRoot Value data to D:Inetpubvroots.

  4. Locate the HKEY_LOCAL_MACHINESYSTEMControlSet001ControlContentIndexCatalogsWeb key and modify the Location Value data to d:inetpub.

  5. Locate the HKEY_LOCAL_MACHINESYSTEMControlSet003ControlContentIndexCatalogsWeb key and modify the Location Value data to d:inetpub.

  6. Locate the HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlContentIndexCatalogsWeb key and modify the Location Value data to d:inetpub.

  7. Repeat steps 1 through 3 on each Web front-end and application server.

Strikes by recommendation of Todd Carter.  Thanks! 


Some of the Registry keys in the steps above may not be available on all Web servers depending on configuration and Operating System versions.  Always backup the registry before modifying any Registry settings.

Standard
Uncategorized

Internet Information Services 7.0, Application Pool Modes and SharePoint Products and Technologies

Internet Information Services 7.0 Application Pool Modes introduces changes in how application pools are managed and process requests that involve managed resources. In Internet Information Services 6.0 worker process isolation mode and in Internet Information Services 5.0, isolation modes are set at the server level. The result is that both isolation modes cannot be run simultaneously. In Internet Information Services 7.0 modes are set at the application pool level allowing applications to be run simultaneously on the same server in application pools with differing process modes (Integrated and ISAPI (Classic). Integrated application pool mode leverages the integrated request-processing architecture of Internet Information Services and ASP.NET, by calling native and managed modules to process portions of a given request and subsequently generating the response; however, SharePoint Products and Technologies is limited to the use of the classic or ISAPI application pool mode for its application pools handling requests as in Internet Information Services 6.0 worker process isolation mode; in this scenario the separation of Internet Information Services and ASP.NET in classic application mode or managed pipeline mode results in the duplication of some processing steps to include authentication and authorization. SharePoint Portal Server 2003 and Windows SharePoint Services 2.0 used stsfltr.dll to provide request intercept functionality, in Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 a .NET 2.0-based HttpModule replaces the ISAPI filter; however, the platform remains metabase bound limiting Windows Server 2008 to using the Classic managed pipeline mode or ISAPI application pool mode, when configuring Internet Information Services 7.0 application pools for use with SharePoint Products and Technologies it is important to understand these limitations.

Determining Application Pool Mode

When introducing the Windows Server 2008 server machine where Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007 has been installed to an existing server farm, your application pools will be configured to use the Classic managed pipeline mode or otherwise, ISAPI application pool mode (see illustration) and/or when provisioning Web applications on a new or existing server farm.

image

To determine the application pool mode for a Web application in Windows Server 2008, open Internet Information Services 7.0 and navigate to the Application Pools node.  The Application Pools node provides a list of available application pools, state, .NET Framework version, and managed pipeline mode including additional information about the credentials running on the application pool.

Standard