Entries for Neil Hutson

Best Places to find Windows HPC Server 2008 Resources [Best Places to find Windows HPC Server 2008 Resources]

Neil Hutson — Tue, 23 Sep 2008 03:36:00 GMT

Within the team we compiled a great lists of "best places" to find information about Windows HPC Server 2008 which just RTM'd.

Community Sites which contain a lot of screens casts and interview content

TechNet Edge - A collection of Windows HPC topical demonstrations for the IT Professionals.

Channel9 - A collection of Windows HPC topical demonstrations for the Developer.

WindowsHPC.net - The HPC Community and technical forums.

http://www.microsoft.com/hpc - The Microsoft product portal. See the on-demand webcasts via the events tab.

http://code.msdn.microsoft.com/hpc - A listing of resources for developers.

A great list of bloggers on this subject from within Microsoft

http://blogs.technet.com/gmarchetti

http://blogs.msdn.com/volkerw

http://blogs.msdn.com/hpctrekker

http://blogs.msdn.com/philpenn

http://code.msdn.microsoft.com/hpc

Whitepapers

Microsoft Windows HPC Server 2008 Overview Data Sheet
Here's a quick overview of Windows HPC Server 2008 benefits and features.
Windows HPC Server 2008 Job Templates
Learn how Job templates can help streamline the job submission process.
Windows HPC Server 2008: Using MS-MPI
Find out more about the new high performance Message Passing Interface (MPI) stack included in Microsoft HPC Pack 2008.
Overview of SOA Programming Model and Runtime System for Windows HPC Server 2008
This white paper provides a technical overview of SOA applications and the Windows HPC Server 2008 functions that support the SOA model.

Windows HPC Server 2008 Technical Overview
Get a detailed overview of Windows HPC Server 2008 new features and benefits.

Windows HPC Server 2008 Job Scheduler
Learn how the Windows HPC Server 2008 new Job Scheduler provides greater scalability and supports advanced policies. It also includes a new service-oriented architecture (SOA) mode that allows interactive applications.

Windows HPC Server 2008 System Management Overview
Learn more about the Windows HPC Server 2008 centralized management and deployment interface with template-based deployment capabilities, and a Network Configuration Wizard that helps to simplify network and topology setup and configuration.

in reply to Best Places to find Windows HPC Server 2008 Resources

Windows HPC Server 2008 released to manufacturing [Windows HPC Server 2008 released to manufacturing]

Neil Hutson — Mon, 22 Sep 2008 16:35:00 GMT

This morning we just announced the release of Windows HPC Server 2008 to manufacturing. This is a major milestone and ensures that the HPC offering supports the Windows Server 2008 release.

This release will enable no scientist to be left behind in their pursuit by making it a lot easier for them to approach the technology, but it will also bring this into the reach of mainstream computing, but provding developers with a high level programing abstraction, so that they can quickly crunch business data.

The community site for Windows Server 2008 is at http://www.windowshpc.net and details about how to download the software can be found at http://technet.microsoft.com/evalcenter/cc835241.aspx after 12pm PST.

If you are new to this area, we have a lot of great screencasts and interviews with the product team on the site which can help guide you through.

The main list can be found by selecting the HPC Tag Section.

in reply to Windows HPC Server 2008 released to manufacturing

Easy Steps to Get your Web Site to Support IE8 [Easy Steps to Get your Web Site to Support IE8 ]

Neil Hutson — Thu, 21 Aug 2008 06:59:00 GMT

Any users accessing your site using the Internet Explorer 8 (IE8) browser ( currently in Beta ) will typically not get a very good rendering experience if your site was designed for Internet Explorer 7 (IE7) because of new standards that IE8 is supporting around HTML and CSS formats. There are two ways to resolve this.

1) The longer term option is to re-write your web application to render IE8 correctly - However this would not be my first choice.

2) The best ( to choose first off ) is to instruct any IE8 browsers to browse your site in IE7 emulation mode so that the current rendering is maintained. How do you do this? Simple

On a Per-site basis, site owners and administrators can include the following custom HTTP header to force Internet Explorer 8 to render Web pages like Internet Explorer 7:

X-UA-Compatible: IE=EmulateIE7

To add a custom HTTP response header at the Web site level in Internet Information Services 7 on a Windows Server 2008-based computer, follow these steps:

Click Start, click Administrative Tools, and then click Internet Information Services (IIS) Manager.
Under Connections, double-click the server that you want, and then double-click Sites.
Click the Web site where you want to add the custom HTTP response header.
Under Web site name Home, double-click HTTP Response Headers in the IIS section.
Note In this step, Web site name is the name of the Web site.
Under Actions, click Add.
In the Name box, type X-UA-Compatible.
In the Value box, type IE=EmulateIE7.
Click OK.

You can also modify the IIS7 configuration file with the following details ( or you can check the config after the changes made above )

<system.webServer>
<httpProtocol>
<customHeaders>

<add name="X-UA-Compatible" value="IE=EmulateIE7" />

</customHeaders>

</httpProtocol>
</system.webServer>

To add a custom HTTP response header at the Web site level in Internet Information Services 6 and earlier versions, follow these steps:

Click Start, click Run, type inetmgr.exe, and then click OK.
Expand the server that you want, and then expand Web Sites.
Right-click the Web site that you want, and then click Properties.
Under Custom HTTP headers, click Add.
In the Custom header name box, type X-UA-Compatible.
In the Custom header value box, type IE=EmulateIE7.
Click OK two times.

Per-page basis

Site owners and administrators can include the following special HTML tag after the <Head> tag on the page:

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" />

The following example shows use of this Internet Explorer 7 compatibility mode tag on a per-page basis:

<html> <head> <!-- Use IE7 mode --> <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE7" /> <title>My Web Page</title> </head> <body> <p>Content goes here.</p> </body> </html>

For more information about the EmulateIE7 tag, visit the IEBlog Web site:

http://blogs.msdn.com/ie/archive/2008/06/10/introducing-ie-emulateie7.aspx

To download IE8 for testing, you can go to the following location

http://www.microsoft.com/windows/products/winfamily/ie/ie8/default.mspx

in reply to Easy Steps to Get your Web Site to Support IE8

Application Considerations When Upgrading to Windows Server 2008 [Application Considerations When Upgrading to Windows Server 2008 ]

Neil Hutson — Mon, 10 Mar 2008 07:01:00 GMT

So how do servers upgrade themselves to Windows Server 2008, and how does data, that is not part of the operating system get handled? One of the interesting points to note is that in Windows Server 2008, the data that is part of the operating system, the registry and certain file locations are recreated during the upgrade. Secondly data that is not part of the operating system that is found in certain directories is quarantined. Details at the bottom.

I recommend that you make a clean install of Windows Server 2008, so that you have a good reference point and then go through you system testing from there. While the upgrade process has become more consistent with Windows Server 2008, there are still small paths that the migration could take which could make your OS install unique, and give you no reference point for testing ( which is what all ITPROs really do not want ). The details below comes from a few white papers on the subject which I think will be interesting for those special cases when you need to do the upgrade. ......

Changes When Upgrading to Windows Server 2008

Upgrading to Windows Vista and Windows Server 2008 is more complex than in previous versions of the operating system. Instead of just installing new versions of binaries over those of an existing computer, the new operating system is installed side-by-side with the older operating system. Then the data and settings are migrated from the older version to the newer version, and then the source is deleted. While this is architecturally more correct and certainly build a clean OS install, this does cause some obvious complications that you should be aware of.

Secondly in Windows Server 2008 the upgrade process is destructive to the pre-existing operating system state. The upgrade engine removes all previous data from the operating system (including executable files, settings, the Windows registry, and operating system data files) and creates an entirely new Windows installation. For components and server roles within the operating system, there are upgrade manifests which control the process. The upgrade manifests have metadata for each component that details how to transfer the settings and data files into their new locations. Non-operating system entries in the registry are persisted forward and merged with the new registry in the destination install.

Upgrade Process
Here are roughly the steps the operating systems goes through

Copies Setup sources to the local hard drive.
Dynamic update runs to check for updated setup files and compatibility database updates.
Checks to ensure that the source operating system is supported for an upgrade.
Presents the compatibility report to the user. The report provides details about any applications that must be uninstalled or that may cause problems after upgrading. The report also recommends backing up the server before continuing.
Dynamic update runs to check for updated system components and drivers.
Unpacks the image file to the local hard drive.
Identifies system data including operating system state, user files, and drivers. The operating system state is identified based on upgrade manifests that are authored by Microsoft.
Extracts the WinPE boot files to the local drive.
Restarts the server.

The upgrade engine performs the following actions from within WinPE:

The server boots into WinPE
Files marked for gathering are moved to an in-place transport directory.
Moves operating system binaries from the source operating system into quarantine.
Collects SID and local account data.
Installs a language-neutral version of the operating system.
Installs a language-specific MUI package.
Installs any optional components that are needed for parity with the source operating system.
Configures access control lists.
Installs any updates collected by dynamic update.
Apply SIDs, computer name, and local accounts to the server.

Specialization phase

Installs Plug and Play drivers.
Creates user profiles for the user accounts on the source computer.
Applies machine-specific operating system state.
The upgrade engine migrates data to the new installation including the following:
Applies the operating system state that was captured by the upgrade manifests
Applies settings from the unattend file (if an unattend file was provided to Setup).
Deletes files from the quarantine directory that were from the source operating system. Restarts the server.

Application Compatibility Checks

Because upgrading to Windows Server 2008 may cause problems for certain applications, a message is presented to all users through the compatibility report that is shown after you initiate the upgrade. If necessary, the report will recommend the appropriate action before upgrading. To verify software compatibility on the Windows Server Catalog and to download tools and documentation, go to http://go.microsoft.com/fwlink/?LinkID=85172.

If software isn’t supported on Windows Server 2008, or if the software vendor does not support software that is installed during the upgrade of the operating system, uninstall that software before you upgrade. If you do not uninstall the software, your system will be unsupported, the software might not work, and software settings or other information might be lost.

There are several different types of upgrade blocks within the compatibility report. The database used to identify applications to block is shared with Windows Vista and does not generally cover server applications.

The types of blocks that you may see are:

Upgrade hard block: These blocks prevent the upgrade from continuing until the issue causing the block is resolved, which may be a bad driver, incompatible source operating system or known bad applications (malware, for example). Users can not circumvent a hard block.
Upgrade soft block: These blocks recommend against upgrading without taking preventative measures or validating that a software vendor has provided an upgraded version for the new operating system. Users can choose to continue past a soft block, because there is no known risk of upgrade failing with the application installed.
Program Compatibility Assistant hard block: The Program Compatibility Assistant is a runtime mechanism which can prevent applications from running on the system. The process is prevented from loading, and the user can not circumvent the block.
Program Compatibility Assistant soft block: The Program Compatibility Assistant can also provide a soft block which advises the user that the application may not run successfully without being updated. Users can still choose to run the application and continue with the upgrade.

Changes that May Impact Your Applications

Because of the differences in the upgrade process in Windows Server 2008, it is possible that pre-existing applications will not be authored in such a way that they function predictably post-upgrade. Most will just work, but there are specific changes that application developers should be aware of, and which may necessitate testing or patching.

The Quarantine Directory

During the collection phase, the upgrade engine goes through all system folders that need to be recreated in the new operating system. When booted into WinPE, the upgrade engine moves files into the quarantine directory that 1) are not listed in upgrade manifests and 2) are located in places that conflict with the new operating system (for example, %SystemRoot% and %ProgramFiles%). These files remain in this directory throughout the upgrade, so that they can be restored in case of a rollback.

However, in addition to making a rollback possible, the quarantine also serves as a safety net. It prevents permanent data loss of any files that have been gathered by the upgrade engine. When the upgrade is complete and the rollback has been disabled, the quarantine is purged -- that is, files are deleted from quarantine if the upgrade engine determines that they were from the source operating system (user data files in the quarantine directory will not be deleted).

Consequently, if an application is unable to find particular files, they may have been moved to the quarantine directory during the upgrade process. The structure of the quarantine folder (%SystemDrive%\$WINDOWS.~Q) mirrors that of the source operating system, beneath a subfolder called “Data”. For example, user profiles are stored at %SystemDrive%\$WINDOWS.~Q\Data\users\<username>. Application developers should expect that files installed to common system locations may end up in the quarantine directory after the upgrade.

Folder Hierarchy and Names

Windows Server 2008 has a different default folder hierarchy than any of the previous operating systems that you can upgrade. Specifically, note the following two changes:

Windows Shell. Many of the standard Windows folders are now under different paths. For example, the path for My Documents in Windows Server 2003 is C:\Documents and Settings\username\My Documents while the path for the same folder in Windows Server 2008 C:\users\username\Documents. The new folder structure is determined by querying the system for constant special item ID lists (CSIDLs). CSIDLs are a system-independent way of checking where a special folder is located. CSIDLs have been supplanted in Windows Server 2008 by KNOWNFOLDERID, but are still used when upgrading from a previous operating system.
English folder names. Non-English versions of Windows Server 2003 sometimes contain folders with CSIDLs that have localized folder names. In Windows Server 2008, the same language installation will now have English language folder names.

These changes are mitigated by directory junctions. Directory junctions are hidden redirectors that translate requests for the old system folders to the new directory structure. This process is typically seamless to applications that rely on the old paths, but you should test this to ensure the hidden directors work for your application.

If the source operating system is not English, directory junctions will be written to remap the English namespace. For example, a German operating system which once pointed to C:\Dokumente und Einstellungen\<username>\Eigene Dateien will now utilize an equivalent folder in Windows Server 2008 found at C:\users\<username>\documents. Consequently, a directory junction will redirect any requests for the original folder. So, in English and non-English computers, the junction will have the same target folder, but the source folder may be different.

The upgrade engine will also write additional directory junctions in some situations. For example, if a user upgraded to Windows Server 2003 from Windows Server 2000, the operating system folder may be called \WinNT, so calls to \WinNT would be redirected to the correct system folder in the new installation.

Unsigned Software in x64

In the x64 version of Windows Server 2008, any kernel-mode software (for example, drivers) that runs on the computer must have a signature, which is referenced each time the operating system is started. If a piece of software is not signed, it will not be loaded. This prevents unknown kernel-mode software, such as many low-level viruses, from compromising a computer.

Previous x64 versions of Windows Server did not require signed drivers, which creates a challenge when upgrading to Windows Server 2008. Because security is a primary concern, the upgrade process for the x64 version of Windows Server 2008 contains additional steps and considerations . The upgrade engine performs the following actions in addition to those in the initial phase (Step 1 in the Detailed process section):

Copies any necessary in-box signed drivers to the local hard drive.
Dynamic Update downloads a list of available signed x64 drivers that are not available in-box. The actual driver packages are not yet downloaded.
Scans kernel-mode software on the source operating system to determine whether each is signed. Unsigned drivers are compared against a local catalog file to see if Windows Server 2008 contains a signature that can be used to validate the driver.
If unsigned kernel-mode software are found, they are displayed in the compatibility report. The upgrade may be blocked, but you can provide signed drivers to the setup engine at this time.
Downloads any driver packages (which were identified in Step 2)
Gathers any valid driver packages in the source operating system for installation during the specialization phase (Step 3 in the Detailed process section). Valid packages are any that have either been signed or are unsigned but have a valid signature in the operating system catalog file.

Because of how upgrade works with x64, one risk for software developers is the disabling of kernel-mode application drivers, as used by many firewall, file system, antivirus and copy protection vendors. These drivers will typically block the upgrade until the application is uninstalled. If an application does not uninstall cleanly, it may continue to block Setup. For drivers that are not Plug and Play, vendors should distribute a version of the driver where the signature is embedded in a file rather than in an external catalog file. Boot start drivers must be signed using this embedded method. Plug and Play does not recognize embedded signed drivers, which are new in Windows Server 2008. For details on how to sign drivers for Windows Server 2008, or to see what drivers have passed the certification, go here.

in reply to Application Considerations When Upgrading to Windows Server 2008

Windows Server 2008 Clustering [SCREEN CAST] [Windows Server 2008 Clustering [SCREEN CAST]]

Neil Hutson — Fri, 08 Feb 2008 07:59:00 GMT

This week I had a chat with Adam about the new failover clustering capabilities within Windows Server 2008 and he showed this in action. After a discussion on the whiteboard, Adam walked me through the installation of clustering support on Windows Server 2008, which involved setting up the clustered configuration across two machines and finally selecting a clustered service, which is this case was to configure Hyper-V in a clustered environment. After starting the Hyper-V virtual environment on one physical machine, Adam failed over the virtual machine to the second physical machine while still maintaining all the state and the running applications. Pretty damm cool, all in less than a minute.

There is quite a lot of information about Windows Server Clustering in Windows Server 2008.

For more details on the features of the new version, the best place to start is here

For more technical information and a step-by-step guide to setting this up start here More next time.

in reply to Windows Server 2008 Clustering [SCREEN CAST]

Forget the "Super Bowl", Windows Server 2008 has RTM'd!!! [Forget the "Super Bowl", Windows Server 2008 has RTM'd!!!]

Neil Hutson — Mon, 04 Feb 2008 16:49:00 GMT

Today we announced that Windows Server 2008 and Windows Vista SP1 released to manufacturing. In this release of Windows Server 2008 we are delivering a world-class Server product, which has got high level of praise throughout the industry. To see the Ch9 interview with the Server 2008 program manager (Alex Henrichs) on RTM and how it happens, check it out here.

There are numerous technologies which are ground breaking in the release and you tend to forget how far we have come. Here are just a few:-

Internet Information Services (IIS) 7.0 – Modular architecture, high levels of administration
.NET 3.0 - Highly productive Application Platform, with key features such as Windows Communication Foundation and Windows Workflow built-in to the latest version of the .NET Framework as part of the Application Platform Server role.
Server Core – Low footprint with no GUI version of the OS to drive appliance type functions in the enterprise
Server Manager – ONE console to setup roles and features for the server machines
Terminal Services Gateway – Allows access to apps without the need for a RAS client
Network Access Protection – keep network safe from un-healthy clients by placing them in quarantine until tested to corp policy.
PowerShell - Object based scripting host which is taking the world by storm.
Failover Clustering – Improved cluster management as you have seen in my posts on edge
Next Generation Net Stack – Super fast and reliable networking stack
Read-Only Domain Controller – Provides a safe solution for domain controllers residing in branch offices which would not be compromised if stolen
Hyper-V Beta – server virtualization. Hyper-V RTM in 180 days

So if you are an ITPRO, where do you go to get hold of all this? Well if you have TechNet or MSDN subscriptions or access through Connect you can download it from these sites today. For people that do not, you have two options. 1) Wait until the end of the month when it can be downloaded from the Microsoft site as eval or 2) Purchase the base TechNet+ subscription which will get you the bits.

Secondly, where do I get the information I need about. The best place is the TechNet Windows Server Center.

Finally, enjoy the ride......we will be back over the next few weeks with many screen casts on certain areas of the product.

in reply to Forget the "Super Bowl", Windows Server 2008 has RTM'd!!!

How to setup iSCSI on Windows Server 2008 [11 mins] [How to setup iSCSI on Windows Server 2008 [11 mins]]

Neil Hutson — Wed, 30 Jan 2008 07:59:00 GMT

This is the second in a series of “How To’s” with Adam Carter. This time around, he provided a quick introduction to iSCSI, which is a technology which is part of Windows Storage Server which allows SCSI commands to be shared over the network to enable cheap and simple network storage options. In this 11min screen cast, Adam walks through iSCSI basics on the white board and then sets up an iSCSI target disk to share on one machine and then connects to this disk over the network to a second machine using the iSCSI initiator. This creates a new disk on the second server machine, which he then formats and puts into action. This is very useful for creating clustering scenarios, reduces the complexity of managing shared nothing SCSI ID’s and can be a very cost effective storage scenario. While the simple setup shown in this video works fine in a lab environment, in real life you would connect to your iSCSI disk using a dedicated high speed network cards on a private network to reduce latency. Adam provided more information on how you can get access to Windows Storage Server and 3rd party iSCSI Target providers in this recent post. Please watch this and comment.

in reply to How to setup iSCSI on Windows Server 2008 [11 mins]

Introduction to Windows Deployment Services [6 Min ] [Introduction to Windows Deployment Services [6 Min ]]

Neil Hutson — Fri, 18 Jan 2008 07:59:00 GMT

Last week I popped into Adam’s office to ask about Windows Deployment Services which is a feature that is built into Windows Server 2008. He showed me a quick 6 minute demo which shows how you can easily deploy operating systems to many desktops over the network without having to be physically present at each computer and without having to install CD media on each machine.

As you can see, Adam needs to clean his monitor a little.

Post any technical questions on the post and I will help answer them.

More details on Windows Deployment Services can be found at http://technet2.microsoft.com/windowsserver2008/en/library/7d837d88-6d8e-420c-b68f-a5b4baeb52481033.mspx?mfr=true

in reply to Introduction to Windows Deployment Services [6 Min ]

So who is looking to install Windows Server Core in production? [So who is looking to install Windows Server Core in production?]

Neil Hutson — Thu, 03 Jan 2008 16:00:00 GMT

Server core is a major new capability of the Windows Server 2008, allowing the ITPRO to deploy and configure a “minimal-install” version of the operating system which does not include features like a GUI, browser and other technologies ( some people say baggage) not required to run server or appliance based applications. Once installed you can install a number of services such as Active Directory Domain Services (AD DS), Active Directory Lightweight Directory Services (AD LDS), DHCP Server, DNS Server, File Service, Print Services, Streaming Media Services, Hyper-V (Virtualization) and Web Server (IIS) roles.

The main reason for this capability stemmed from feedback we got from some of our larger customers. They were all moving to global datacenter models, with a very small number of datacenters which needed to be managed 24x7 worldwide. They wanted to be able to procure a new operating system instance quickly, download across the wide-area-network (so it had to be small) and have a reduced attack surface and reduced patching. A Server Core installation only requires about 1 gigabyte (GB) of disk space to install and approximately 2 GB for operations after the installation.

Lets see it in action

To give you an idea of some of the capabilities, we recommend that you first go to Keith Comb’s blog and check out the 8 small screencasts that he has created on the subject.

http://blogs.technet.com/keithcombs/archive/2007/11/04/windows-server-2008-core-screencast-series-watch-all-eight-parts-here.aspx

IIS7 Support

IIS7 and the Web Server role is the most interesting role on server core, but it has one drawback on the full OS version. Server Core does not contain the.NET Framework (this means no PowerShell too). This means that IIS7 on server core can serve up static pages, run classic ASP and PHP, but it is cannot run applications written to take advantage of ASP.NET. To give you an idea of the simplicity of the administration experience for IIS7 on Server Core, you should take a look at the blog article on the IIS team site which provides a lot of details. http://blogs.iis.net/metegokt/archive/2007/06/26/administering-iis7-on-server-core-installations-of-windows-server-2008.aspx

Managing a Server Core instance

The next area is management of server Core as there is not GUI. We have been seeing a lot of questions internally and externally about managing server core machine and then trying to connect to it remotely. Here are some answers if you run into this issue.

C:\>netsh advfirewall set currentprofile settings remotemanagement enable

After which point the firewall should allow all your remote admin tools to connect (computer management and DNS snap-in for example).

If you're looking to instrument your systems using WMI you need to do the following

C:\>netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes

The big question

Who is planning to use Windows Server Core and what scenarios are you planning to use it for?

in reply to So who is looking to install Windows Server Core in production?

Failed Request Tracing in IIS7 [Failed Request Tracing in IIS7]

Neil Hutson — Fri, 23 Nov 2007 17:00:00 GMT

In this screencast, Ryan Dunn configures IIS7 server for Failed Request Tracing (sometimes called FREB). Failed Request Tracing is a powerful new capability in IIS7 that allows us to easily set rules on our web applications, that once triggered will log that request to disk and pull in all the relevant trace information. This feature is immensely useful for troubleshooting running applications where attaching a debugger is impractical.

in reply to Failed Request Tracing in IIS7

Installing PHP Applications on IIS7 [Installing PHP Applications on IIS7]

Neil Hutson — Thu, 22 Nov 2007 17:00:00 GMT

In this screencast, Ryan Dunn shows how easy it is to get PHP up and configured on your IIS7 webserver using FastCGI. The popular PHP-based blogging application, Wordpress, is used to demonstrate.

Additionally, we see how quickly and easily we can integrate a PHP app with IIS7's integrated pipeline as we convert Wordpress to use IIS7's built-in Forms Authentication.

in reply to Installing PHP Applications on IIS7

Remote Administration and Delegation in IIS7 [Remote Administration and Delegation in IIS7]

Neil Hutson — Wed, 21 Nov 2007 23:27:00 GMT

In this screencast, Ryan Dunn configures a IIS7 server for remote administration and delegation. The remote administration service in IIS7 is a new and powerful feature that allows us to connect securely to our remote IIS server using a firewall-friendly SSL connection. Additionally, we can choose to use traditional Windows accounts for authentication or choose the new IIS Manager user accounts instead.

We will walk through the steps you must perform as the IIS administrator as well as the experience for a remote administrator using delegated features.

in reply to Remote Administration and Delegation in IIS7