Virtual Server 2005 requires IIS and the IISAdmin service to be installed. However these are not installed by default on Windows Vista.
Thanks to NickMacKechnie’s Weblog, I found the list of IIS components that are required.
Use the following command line to install IIS before installing Virtual Server 2005:
start /w pkgmgr /l:log.etw /iu:IIS-WebServerRole;IIS-WebServer;IIS-CommonHttpFeatures;IIS-StaticContent;IIS-DefaultDocument;IIS-DirectoryBrowsing;IIS-HttpErrors;IIS-HttpRedirect;IIS-ApplicationDevelopment;IIS-ASPNET;IIS-NetFxExtensibility;IIS-ASP;IIS-CGI;IIS-ISAPIExtensions;IIS-ISAPIFilter;IIS-ServerSideIncludes;IIS-HealthAndDiagnostics;IIS-HttpLogging;IIS-LoggingLibraries;IIS-RequestMonitor;IIS-HttpTracing;IIS-CustomLogging;IIS-ODBCLogging;IIS-Security;IIS-BasicAuthentication;IIS-WindowsAuthentication;IIS-DigestAuthentication;IIS-ClientCertificateMappingAuthentication;IIS-IISCertificateMappingAuthentication;IIS-URLAuthorization;IIS-RequestFiltering;IIS-IPSecurity;IIS-Performance;IIS-HttpCompressionStatic;IIS-HttpCompressionDynamic;IIS-WebServerManagementTools;IIS-ManagementConsole;IIS-ManagementScriptingTools;IIS-ManagementService;IIS-IIS6ManagementCompatibility;IIS-Metabase;IIS-WMICompatibility;IIS-LegacyScripts;IIS-LegacySnapIn;IIS-FTPPublishingService;IIS-FTPServer;IIS-FTPManagement;WAS-WindowsActivationService;WAS-ProcessModel;WAS-NetFxEnvironment;WAS-ConfigurationAPI
Filed under: Windows Vista |
Search
You are currently browsing the Grant Holliday weblog archives.
Thanks for this, it works flawlessly on 5384 as well!
Thanks, worked on Vista RC1, build 5600!
Man, this was killing me. It worked perfectly on the RTM bits. After running the mammoth command above and running the command to put it in the .NET Classic App Pool, I saw the admin web page for the first time since I upgraded.Cheers!
You can also create a BAT file with that code and run it. Probably easier for most people. Open Notepad, save as something.BAT and run.
Many thanks, it worked first time.
All that script does is install EVERY component for IIS, not just the *required* components. Anyone could have guessed that it would work if you check everything off in Programs and Features. Now instead of just the requirements you have a bunch of extra services and vulnerabilities running on your Virtual Server box.
thanx