What's the best approach for issuing client certificates to customers? Should we run our own certificate services (we're on Win 2008 R2), and issue them that way? Is there a CA that will issue them for us? Comodo will issue client certificates for email purposes, but we need them for allowing our clients to access our website (via browser and API).
We've got some Windows services written in .NET. They start fine manually within the services mmc, but despite being set to Automatic, they never start when powering on (or rebooting) the machine.
Update In the event log, instead of seeing "xyz started", alongside all the other services starting, I just see "The xyz service entered the stopped state." and a seperate error that says "A timeout (30000 milliseconds) was reached while waiting for a transaction response from the slsvc service.".
If I manually start them, then I get a normal entry in the event log as expected, and all is fine - until the next Windows Update patch which forces a reboot and all the services are off again.
Any ideas? I've tried setting them to Delayed Start with no apparent difference.
I've got a server with 64GB RAM installed (reported in both the bios and in Windows), but the system information from control panel displays the fact that only 32GB of this is usable.
I've only ever seen this with 32bit windows when there's too much RAM installed before.
It also seems unlikely that precisely half of the RAM is dodgy? Any ideas?
Many thanks
James (warning: dev playing at server admin)