Forum Discussion

johnkingman's avatar
johnkingman
Copper Contributor
Nov 06, 2023

Server 2022 IIS install not creating Registry keys in InetStp\Components

Hi I'm hoping someone can help or has run into this before, I've got a production server we installed IIS on as part of a VEEAM ONE install but the installer failed as it complains its missing several IIS components.  When checking the Server Manager I can see the components are installed so as a work around VEEAM gave me an installer that didn't check for the components which then fails to register a website and still rolls back.  On further investigation the Veeam tech asked me to check for several registry entries see image:

When checking the servers registry all of them are missing and the folder has permissions to only allow the Trusted Installer to make changes (Default behaviour I assume).  I have run both an SFC and DISM then uninstalled/reinstalled IIS but with the same result.

 

Oddly when I open the IIS manager it looks to be running ok but yet these keys are missing?  Can someone please advise on possible fixes or is this expected and something that Veeam need to change??

1 Reply

  • I would not manually create the missing IIS registry values, especially under TrustedInstaller-controlled keys.

     

    First verify which IIS features Windows actually considers installed:

     

    Get-WindowsFeature Web-* | Where-Object InstallState -eq 'Installed'

     

    Also check:

     

    Get-WindowsFeature Web-Server

     

    If required:

     

    Install-WindowsFeature Web-Server -IncludeManagementTools

     

    If IIS Manager and the websites work correctly but Veeam ONE still reports missing prerequisites, this may be a prerequisite-detection issue in that Veeam version rather than an IIS problem.

     

    I would identify exactly which registry values Veeam checks before manually modifying anything.