Select the option that you are most familiar and comfortable with. One is through Windows PowerShell and another through Windows Server Manager. This takes a bit of comparing + hit & miss tries but hopefully it will help someone else as well. There are two ways to configure IIS 6 Metabase Compatibility on your environment. Most of the SMTP configuration I needed was already in there, as I did configure the WS2019 before backing up those settings, so I only needed to make small manual changes. Make sure to take a copy of the WS2022 one, and to not replace any Security IP or ACL owner configuration and not delete the extra stuff if not 100% sure!Īfter this I restarted the IIS and SMTP services and tested. From the Start menu, click Control Panel. I then used the text compare tool for the last file and added in all the missing rows from the WS2019 MetaBase.xml. To install IIS, add components, or remove components using Control Panel. I cannot guarantee that replacing these files will also work for you, but it did work for me - and I did do a text compare between the existing config files beforehand (which showed they were identical). I Stopped IIS in WS2022 and replaced all the original files on my WS2022 machine with the ones in the WS2019 all BUT the MetaBase.xml one. The files you will have in the backup are as follows: I then installed SMTP Virtual Server on my WS2022 instance and copied over the backup files from the WS2019 machine (the backup is stored in C:\Windows\System32\inetsrv\Backups\). The rest of the process is actually almost the same: Once SMTP was configured and tested, backup the configuration on the WS2019 server (as mentioned here. What I did to get it to work in WS2022 was install & configure the SMTP Virtual server on a WS2019 instance (decommission that instance once done).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |