Configure IIS per the ‘ Installing Bit9 Security Platform Guide – V7.2.0’Ĩ. *Any privilege issues will require rebooting into Safe Mode.ħ. Start /w pkgmgr /uu:IIS-WebServerRole IIS-WebServerManagementTools IIS-IIS6ManagementCompatibility IIS-Metabase IIS-WMICompatibility IIS-ManagementConsole IIS-ManagementScriptingTools IIS-WebServer IIS-CommonHttpFeatures IIS-StaticContent IIS-DefaultDocument IIS-DirectoryBrowsing IIS-HttpErrors IIS-HttpRedirect IIS-ApplicationDevelopment IIS-ASP IIS-ASPNET IIS-ISAPIExtensions IIS-ISAPIFilter IIS-NetF圎xtensibility IIS-ServerSideIncludes IIS-HealthAndDiagnostics IIS-HttpLogging IIS-HttpTracing IIS-LoggingLibraries IIS-RequestMonitor IIS-Performance IIS-HttpCompressionStatic IIS-Security IIS-RequestFiltering IIS-WindowsAuthentication WAS-WindowsActivationService WAS-ProcessModel WAS-NetF圎nvironment WAS-ConfigurationAPI Copy the text below to remove all services related to IIS. Perform a complete uninstall of IIS from the server, and then reinstall IIS with the proper settings.ģ. The full installer corrupts the IIS settings, which prevents the console from coming back up properly upon roll back. All same major version (7.2.x.x) upgrades need to use the patch. No access to the Bit9 console after roll back.

This error results in a roll back of the installation.

Towards the end of the installation, they should see the error “Bit9 Console could not be deployed on IIS. Upgrade to an existing 7.2 installation with the full installation package (rather than the patch)

Total uninstall