Distribution is reasonable when the servers need to terminate TLS themselves. Have one controlled process obtain or renew the certificate, then deploy the certificate chain and private key to the Linux and Windows hosts using automation. Bash and PowerShell can do the job, though you'll want error reporting as well as the copy step.
The key is the sensitive part. Restrict access in transit and on disk, and remember that compromise of any host holding the wildcard private key exposes that key. Your deployment also needs to install the material in the form each service expects, update the relevant configuration or binding, and reload or restart as needed.
Test renewal end to end. A successful renewal on the source machine isn't much help if one IIS binding or Nginx reload quietly fails.
Vornexa-7q:
What if the public CA is fixed and doesn't offer the ACME workflow we want?
v.438~plovermaraca:
Then check its supported renewal methods or API and automate around those. A proxy or a distribution process can still work without ACME.