ColdFusion Does Not Set Up on Vista and IIS 7

loathe,

I did get ColdFusion installed finally, but was not abe to get it to intergrate with II7 correcty. I finally installed it as a "standalone" server and it is working fine. Not at convenient for me, but fine.

I think SafariTech (commented above) was right, so I will wait for the next update. I wish you well and please let us know how it goes.

I found this and it help a bit also:

"Metabase is required in order for the ColdFusion installer to work. See this article for more info on how to install it:

http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=943




Overview
The IIS 7.0 configuration system is compatible with legacy configuration interfaces at the API level. It supports the Admin Base Objects (ABO) interface, also known as IMSAdminBase, as well as the ADSI and WMI providers that were built on top of ABO in IIS 6.0. Existing applications and scripts can still call into those programmatic interfaces on IIS 7.0 and continue to work, as long as the Metabase Compatibility component of IIS 7.0 is installed (note: by default this component is not installed).
Installing Metabase Compatibility Support
You can find this component in setup under Internet Information Services->Web Management Tools -> IIS 6 Management Capability Feature.
This component is not installed by default, because IIS 7.0 itself is not using it. It is using the new configuration system with its new interfaces. The legacy interfaces have some limitations and are not ideal for working with distributed configuration files (see Limitations section below); therefore it is recommended that over time, and especially when opening up the configuration system for more and more delegation (i.e. more and more web.config files with IIS settings in them are present on the system), customers will consider porting legacy scripts and applications over to the new system and its interfaces.
It is also recommended that new scripts and applications will be developed using the new interfaces, so they work ideally with the new system, and can have access to the new properties, concepts and structure of the configuration system.
When all of the legacy scripts and applications are ported to the new interfaces, it is recommended to uninstall the Metabase Compatibility feature.
How Metabase Compatability Works
The Metabase Compatibility feature runs inside the Metabase service (IISADMIN). It intercepts all method calls to ABO. If the information in the method call is related to the web server configuration, it is mapped to the new system. If it is related to FTP, or SMTP, or NNTP configuration, then it follows the regular logic of the Metabase system and ends up in the Metabase file.
Note that even custom properties that are under the web server configuration, are mapped to (and persisted in) the new system.
The mapping decision is based on the Metabase node in question. Web server configuration is typically under LM/W3SVC, including custom properties, with some few additions like Mime Maps.
Mapping is done to translate back and forth between the ABO view back and the new system view. For example, the new system has a concept of applications, under each site and above all virtual directories. The legacy system handles applications differently: they are simply virtual directories with a special property to mark them as applications (AppIsolated, or AppRoot).
When calling ABO to write web server configuration, the Metabase Compatibility component will persist the data in applicationHost.config. This is referred to as "write-through", because the information is not kept in-memory. When calling ABO to read web server configuration, the Metabase Compatibility component will read it from applicationHost.config. This is referred to as "read-through", because the information is again not fetched from memory.
Incomplete data that is not ready for consumption by the server runtime, is persisted into a special section in applicationHost.config, called . This section is used as a persistent store for the Metabase Compatibility feature, and customers should never modify its content. An example of incomplete data is, when the legacy script set the site id but not the site bindings. In IIS 6.0, such a call would have created an invalid site object in configuration. In IIS 7.0, it is kept in the section, which is not consumed by the server. If a subsequent call is made to set the site bindings, then the site object is considered complete, and persisted in its entirety to the section, where it will be picked up by the server runtime. Temporary data will be removed from at that point, so the user will not need to cleanup leftovers from the system. If such a subsequent call is not made, then the server runtime will never see this invalid site, but legacy scripts will have it in the ABO view, just like they did in IIS 6.0. From the legacy script perspective, the system is fully compatible here with IIS 6.0.
Custom web server properties that are set via legacy scripts and applications, are always persisted into the section. They can be retrieved via the legacy interface just like in IIS 6.0, so the system is fully compatible. Obviously, this is very different from the recommended way to extend the IIS 7.0 configuration system, hence another reason to consider porting such applications, over time, to use new interfaces and new features offered by the IIS 7.0 configuration system.
Other Metabase Configuration Data
Note that FTP, SMTP and NNTP configuration is still persisted in the Metabase system and was not ported over to the new IIS 7.0 configuration system. The configuration settings for those can still be managed via legacy programmatic interfaces and direct editing of the metabase.xml file."

Hope it helps

iam

CF won't run on IIS7 as of right now ... believe me, I have tried as part of the Vista/Longhorn Server Beta Team. As a matter of fact, the installer for CF will hang in the x86 version because it cannot figure out your OS, and it says it finishes in the x64 version, but actually didn't install much of anything.

IIS 7 is just "too different", that even despite getting the mappings in place, as they are in other OS's, it will still not function. In addition, if you are running the 64 bit server, it won't work anyways.

One thing I haven't tried yet (but may later in the cycle) is to see if the upgrade process will somehow reconfigure the drivers and configurations to function withing IIS7 using IIS 6 compatibility mode.

Basically, installing CF on Win2003 Server and then upgrading that complete OS (once I know everything is running) to Vista Server should work, if it's going to work at all.