Forum Discussion
doctordns
Mar 16, 2021Brass Contributor
[Server Buld 20303.1] IIS 6 Manager crashes trying to edit SMTP Virtual Server Properties
I have installed 20303.1 and added the SMTP Service and add the management tools. Install-WindowsFeature SMTP-Server -IncludeManagementTools After the installation, I bring up t...
- Nov 10, 2022We found that doing the following worked, and can now edit the settings in the II6 Manager without errors (and without crashing when applying settings) every time:
Stop SMTPSVC service [Display Name: Simple Mail Transfer Protocol (SMTP)]
Stop IISADMIN service [Display name: IIS Admin Service]
Edit "C:\Windows\System32\inetsrv\MetaBase.xml"
Find: <IIsSmtpServer Location ="/LM/SmtpSvc/1"
Add (Settings are alphabetical): RelayIpList=""
Save file
Start IISAdmin Service
Start SMTPSVC service
You can now open the Internet Information Services (IIS) 6.0 Manager (InetMgr6.exe) and work like normal. The setting above relates to the Access Tab > Relay Restrictions section, but doesn't set anything in it (i.e. "all except the below list" with a blank list).
After setting this value you can change it to what you need it to be. (i.e. the value doesn't need to be 'null' for the fix to work, just so long as the variable is present in the file).
The above has been tested on a few new installs of Windows Server 2022, and has worked for us every time. If you have done an upgrade there are some other things to consider (seems like the SMTP service is not installed after upgrade so will require a backup of the settings that can be applied post reinstalling the service. But that is discussed in other topics).
PS: Remember to set the SMTPSVC service to start "automatically". By default its set to "manual".
Source: https://serverfault.com/questions/1088555/server-2022-smtp-server-issue
DR896
Oct 03, 2022Copper Contributor
Hi,
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).
Once SMTP was configured and tested, backup the configuration on the WS2019 server (as mentioned here: https://blog.workinghardinit.work/2021/11/25/iis-6-0-smtp-service-in-place-upgrade-to-windows-server-2022/). The rest of the process is actually almost the same:
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 files you will have in the backup are as follows:
-administration.config
-applicationHost.config
-MBSchema.xml
-MetaBase.xml
-redirection.config
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. 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 then used the text compare tool for the last file and added in all the missing rows from the WS2019 MetaBase.xml. 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!
After this I restarted the IIS and SMTP services and tested. 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.
I tested and everything works. This takes a bit of comparing + hit & miss tries but hopefully it will help someone else as well.
Cheers
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).
Once SMTP was configured and tested, backup the configuration on the WS2019 server (as mentioned here: https://blog.workinghardinit.work/2021/11/25/iis-6-0-smtp-service-in-place-upgrade-to-windows-server-2022/). The rest of the process is actually almost the same:
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 files you will have in the backup are as follows:
-administration.config
-applicationHost.config
-MBSchema.xml
-MetaBase.xml
-redirection.config
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. 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 then used the text compare tool for the last file and added in all the missing rows from the WS2019 MetaBase.xml. 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!
After this I restarted the IIS and SMTP services and tested. 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.
I tested and everything works. This takes a bit of comparing + hit & miss tries but hopefully it will help someone else as well.
Cheers