Windows Certificate Services – Setup a CRL
May17

Windows Certificate Services – Setup a CRL

Setup a CRL KB ID 0000957 Problem One of the often-overlooked tasks in a Public Key Infrastructure (PKI) deployment is configuring your Certificate Services Certificate Revocation List (CRL). For smaller deployments with only one server, you don’t need to worry about complex design considerations (though a CRL doesn’t have to be hosted on a Certificate Services server). In my test environment, I have only one PKI server,...

Read More
VMware – Replace the ESX Certificate
May07

VMware – Replace the ESX Certificate

ESX Certificate KB ID 0000974  Problem ESXi comes with a self-signed certificate, and for most people that’s fine, but some clients want to have a ‘Trusted’ certificate on theirs, and have their own PKI infrastructure for issuing them. Below I will generate a new certificate for my ESXi server using the Active Directory Certificate Services role on Windows Server 2012. Then replace the self-signed certificate with my new...

Read More
Citrix: mac OSX ‘You have chosen not to trust…’
Feb26

Citrix: mac OSX ‘You have chosen not to trust…’

KB ID 0001520 Problem After a colleague deployed Citrix for a customer the other day, they complained that they had a mac user that was getting certificate errors. They had a publicly signed wildcard certificate, but this user was still having problems. After I  heard a few “tell him to stop using a mac” comments, I said, “I’m using a MacBook here, would you like me to test it?” The URL opened fine in...

Read More
Meraki Block Page http://wired.meraki.com:8090  ‘Not Found’
Nov13

Meraki Block Page http://wired.meraki.com:8090 ‘Not Found’

KB ID 0001365 Problem If you have a Meraki Security device and have enabled ‘Content Filtering’, instead of a nice ‘block-page’ informing you why you are being blocked you may see this; http://wired.meraki.com:8090 This is happening because your Corporate DNS is resolving ‘wired.meraki.com’ to 54.241.7.184, which you can also see if you look at the URL you are trying to connect to it on port 8090. A...

Read More
vCenter – Management Ports
Jul03

vCenter – Management Ports

KB ID 0001324  Problem A while ago my colleague was struggling to get into a vCenter server. Normal https (TCP 443) wasn’t letting him in, I knew you could manage the appliance directly, (but I couldn’t remember the port number!) He knew there was an alternate port number, but we didn’t know what it was. Solution vCenter Appliance (Direct) Management Port TCP: 5480 i.e. https://{ip-or-host-name}:5480 vCenter /...

Read More