Technically openSUSE Leap 15.3 is equal to SUSE Linux Enterprise Server 15 SP3, both share the same code and binary packages, the only difference is community vs. commercial support. It's even possible to quickly migrate from Leap 15.3 to SLES 15 SP3 (Archive: , ) if you decide vendor support is preferred at a later point.
VMWare still doesn't officially support Leap 15.3 as VM on vSphere neither allows Guest Customization, but for sure, when you run SLES 15 SP3 it's not a problem and fully supported?!
Keep in mind that
/etc/issue is a symlink to
/run/issue, a volatile and temporary file,
managed by systemd service
issue-generator. So you have to remove the symlink and create a new
/etc/issue file, otherwise your changes will be lost after the next reboot.
sudo rm /etc/issue && echo "SUSE Linux Enterprise Server 15" > /etc/issue
In addition I had to change the OS Type in the VM Settings on vSphere to "SUSE Linux Enterprise Server 15" as well, otherwise the Guest Customization couldn't even be started without an error message.
I like the generated issue file and the additional information, so after the new deployed VM is up and running, let's just revert the change:
sudo rm /etc/issue && ln -s /run/issue /etc/issue
Little more complicated, but also possible, is to replace
/etc/os-release with the content
from a SLES 15 SP3 System. It has the same effect as changing
/etc/issue, the Guest
Customization will think it's a SUSE Linux Enterprise Server and apply all settings.
NAME="SLES" VERSION="15-SP3" VERSION_ID="15.3" PRETTY_NAME="SUSE Linux Enterprise Server 15 SP3" ID="sles" ID_LIKE="suse" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:suse:sles:15:sp3"