Reputation
Next privilege 200 Rep.
See reduced ads
Badges
1 8
Impact
~8k people reached

Mar
5
comment Task scheduler ran a task twice
We are also experiencing this issue at my company. We also had to recreate the task to fix it. It would be nice if MS would update the Knowledge Base article linked in the OP to include Windows 2012. I mean if it's fixed in 2012 R2 then it should have an official KBase article, defect number, or something...
Dec
10
awarded  Autobiographer
Sep
11
awarded  Excavator
Sep
11
revised Windows Update: can't apply updates even as domain admin on Server 2008 R2
Typo in original. Also clarified that you can just set it to 0 instead of deleting it.
Sep
11
suggested approved edit on Windows Update: can't apply updates even as domain admin on Server 2008 R2
Sep
11
comment Windows Update: can't apply updates even as domain admin on Server 2008 R2
This fixed it for me except there is a typo in the path above: "\windowsupdage" should be "\windowsupdate".
Aug
22
awarded  Notable Question
Dec
8
awarded  Popular Question
Nov
13
accepted “Service Unavailable” when browsing to static HTML page in non-application IIS website on Windows 2003 (possibly SharePoint WSS 2.0 related?)
Nov
13
answered “Service Unavailable” when browsing to static HTML page in non-application IIS website on Windows 2003 (possibly SharePoint WSS 2.0 related?)
Nov
12
awarded  Tumbleweed
Nov
5
awarded  Editor
Nov
5
revised “Service Unavailable” when browsing to static HTML page in non-application IIS website on Windows 2003 (possibly SharePoint WSS 2.0 related?)
spelling
Nov
5
asked “Service Unavailable” when browsing to static HTML page in non-application IIS website on Windows 2003 (possibly SharePoint WSS 2.0 related?)
Oct
25
awarded  Supporter
Oct
22
awarded  Student
Oct
22
awarded  Scholar
Oct
22
comment Apache seems to be using old expired certificate even though new one is installed
Yes! Thank you Shane, that was very logical. Boy this was a tough one. The process turned out to be a proxy server called nginx, listening on an IP address that I didn't even know was associated with the server and then relaying HTTPS and HTTP requests to Apache. I have no clue why the last guy thought this was a good idea, it seems to be a pointless performance hog. And nginx required me to reformat the certificates that GoDaddy provided to put the server cert and the authority chain in one file in a certain order. Anyways, it works now! Thank you!
Oct
22
accepted Apache seems to be using old expired certificate even though new one is installed
Oct
21
comment Apache seems to be using old expired certificate even though new one is installed
I'm not really sure, I think it's complaining that www.gentlemanjoe.com does not match gentlemanjoe.com, but that does not explain why the site is still using an expired certificate. If it was only a common name/server name mistmatch error, wouldn't I see that reflected in the browser security warning? The new certificate shouldn't show up as expired, but with a different warning about the name mistmatch, right?