Wildcard Cert Migration Guide
Windows Server • IIS Administration
Wildcard Cert Migration Guide
Exporting and importing a wildcard SSL/TLS certificate (.pfx) between IIS servers
Format
PKCS #12 (.pfx)
Includes Private Key
Pre-Flight Prerequisites
1. Admin Access
Local Administrator rights on both the Source and Destination IIS servers.
2. Exportable Key
The certificate on the source server must have its private key marked as exportable.
3. Strong Password
Prepare a strong temporary password to encrypt the .pfx bundle during transfer.
Phase 1
Export Certificate from Source IIS Server (Server A)
1
Open Server Certificates in IIS Manager
- On the source server, press
Win + R, type inetmgr, and press Enter.
- In the left Connections pane, click the Server Name (root node, not an individual site).
- In the center pane under the IIS section, double-click Server Certificates.
2
Export the Wildcard Certificate (.pfx)
- Locate your wildcard certificate (e.g.,
*.yourdomain.com) and verify its Expiration Date.
- Right-click the certificate and select Export... (or click Export in the right-hand Actions pane).
- In the Export Certificate dialog, choose a secure path such as
C:\Temp\wildcard-cert.pfx.
- Enter and confirm a strong password, then click OK.
3
Securely Transfer the .pfx File to Server B
Copy wildcard-cert.pfx to a temporary folder on the destination server (e.g., C:\Temp\) using an encrypted channel such as RDP clipboard, SMB over VPN, or SCP.
Fallback (MMC Method): If Export is grayed out in IIS Manager, run mmc.exe → File > Add/Remove Snap-in → Certificates (Computer Account). Navigate to Personal > Certificates, right-click the cert → All Tasks > Export..., and select Yes, export the private key (include all certificates in the path if possible).
Security Notice: Never send a .pfx file or its password over unencrypted email or chat. Anyone with both the file and password can impersonate your domain.
Phase 2
Import & Bind on Destination IIS Server (Server B)
4
Import the .pfx into IIS Manager
- On the destination server, open IIS Manager (
inetmgr), select the Server Name, and open Server Certificates.
- In the right-hand Actions pane, click Import....
- Browse to
C:\Temp\wildcard-cert.pfx and enter the password you created in Step 2.
- Select Personal as the Certificate Store (or Web Hosting if managing many sites).
- Optional: Check Allow this certificate to be exported if you plan to migrate it again later. Click OK.
5
Bind the Wildcard Certificate to Your IIS Site(s)
-
In the Connections pane, expand Sites and select your target website.
-
In the Actions pane, click Bindings..., then click Add... (or select an existing https binding and click Edit...).
-
Configure the binding settings:
Type: https
Port: 443
IP Address: All Unassigned
Host name: app.yourdomain.com
SNI: Check Require Server Name Indication if hosting multiple HTTPS sites on one IP.
-
In the SSL certificate dropdown, select your imported wildcard certificate and click OK.
Phase 3
Verify & Clean Up
6 Test & Verify HTTPS
- Browse to
https://app.yourdomain.com from a client machine.
- Click the browser padlock → Certificate to verify the
*.yourdomain.com subject and expiration date.
- Confirm no intermediate chain warnings appear.
7 Remove Temporary Files
- Delete
C:\Temp\wildcard-cert.pfx from both Server A and Server B.
- Empty the Recycle Bin on both servers so the private key is not left on disk.
Troubleshooting Quick Reference
| Symptom |
Likely Cause |
Resolution |
| Export option is grayed out |
Private key missing or marked non-exportable on Server A. |
Try MMC Computer Certs export; if still disabled, re-key/re-issue from your CA. |
| "Network password is not correct" on older IIS |
AES-256 PFX encryption unsupported on older Windows Server builds. |
Re-export using TripleDES-SHA1 (e.g., via OpenSSL or Windows Server 2016/2019). |
| Browser shows wrong cert or warning |
SNI unchecked on shared IP, or old binding still bound to port 443. |
Enable Require SNI on the binding and verify DNS points to Server B. |