Putting multiple SSL certificates in IIS

By -
Open up command prompt and run the following for each website/host header

Appcmd set site /site.name:"sitename" /+bindings.[protocol='https',bindingInformation='*:443:certname]

Where:
- sitename = the site's name in IIS
- certname = the certificate name in IIS

Comments

Post a Comment

Popular posts from this blog

Win10 computer can't connect to Win2003 share because of SMB1

By -
 We had an incident today where a new laptop with Windows 10 Pro couldn't connect to the folder share on one of our servers. The server is an old Windows 2003 Standard. After some research, I found that SMB 1.0 is no longer included in the newer releases of Windows 10. Unfortunately for us, we're not ready to upgrade the server yet, so the fix had to be done on the client.  Here's the solution I found on the web. This should be done on the Windows 10 computer. Press Windows key + R  Type: optionalfeatures.exe, Enter Scroll down to SMB 1.0/CIFS File Sharing Support Check "SMB 1.0/CIFS Client" Click OK  Restart the computer And done!
Read more

Remote Desktop to a PC not joined to AD domain

By -
Image
 In cases where you are in an Active Directory environment and you need to remote to a desktop that's not joined to that directory, or is a member of an Azure directory, the login prompt usually leads to an error. Remote machine is AAD joined. IF you are signing in to your work account, try using your work email address: There are a couple of options:  Log in via Azure web (will required 2FT if enabled) Present the login AFTER the RDC connection Here are the steps: 1. Login via Azure On Remote Desktop, click Show Options, Advanced tab Check "Use a web account to sign in to the remote computer" Click Connect Your organisation's Azure SSO login screen will appear.  2. Present the login screen AFTER connecting to RDC Go to your Documents folder and look for .rdp that you are using Right-click this file and edit using Notepad At the bottom of the file, add this line: enablecredsspsupport:i:0 authentication level:i:2 Save the file. Open Remote Desktop and connect to the co...
Read more

Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine

By -
Image
I had an issue today where an Office update caused my C# applications to stop connecting to my access database. I suddenly started getting the error: Here's how to fix it. First, confirm that you do not have Office 12.0 OLE DB Provider by opening up PowerShell and running this command (New-Object system.data.oledb.oledbenumerator).GetElements() | select SOURCES_NAME, SOURCES_DESCRIPTION This screen shot was taken after I fixed my computer. It shows ACE.OLEDB.12.0, 15.0, and 16.0. If you don't have these, run the Access 2016 runtime installer from: http://www.microsoft.com/en-us/download/details.aspx?id=50040
Read more