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??
RDP gateway session disconnects on single packet loss
Good Morning, I'm trying to troubleshoot an issue with one of my remote clients losing their RDP session through a gateway server after a single packet drops. I can run a constant ping to their firewall and see when the packet drops, which causes the disconnect. The ms response times average about 34 and the drops don't seem to be occurring in high ms situations. I've been looking for support articles to increase the threshold of that timeout but can't seem to find anything relevant to an RDS Gateway session in conjunction with windows 10 and 2012R2 beyond high ms tolerance. Non-gateway connections will attempt to reestablish session for around 60 seconds before timing out. Any connections through the gateway will immediately drop session and require a new connection. The client pc I'm working with is a Windows 10 setup utilizing a site-to-site connection between a Meraki and a Fortigate. They are still using the older rdp protocol instead of the newer client on Windows 10. Any thoughts or ideas would be great. Thanks much!
