So, I've been looking into this systemd "Predictable Network Interface Names" for quite some time and got some understanding on how it works, but I can't for the love of Thor figure out the naming scheme with enpXsY, I know that it's supposed to indicate the physical location of the device, but what exactly does the X and Y mean? Which one is the physical location? What exactly does the other indicate, a bus index, perhaps? I have no idea and really want to know. I searched high and low and could find nothing explaining in detail how this naming scheme works.
I have two AD servers in a domain, both running Windows Server 2019, the second is a Core server configured as a RODC. I have the main server working as a Certification Authority, where I'm supposed to issue the certificates for the internal websites that are running on the Core server. I need to enable SSL on the websites that are running on the Core server, but using the certificates generated on the main server, so far I haven't found a way to do that. The closest I got was through the "Certificates" MMC snap-in, but when I try to import the .pfx file I get the notification that importing a .pfx file to a remote certificate store is not supported. How can I assign these certificates, that are issued and located in the main server, to the websites running on IIS in the Core server?