Exchange Archive

By brendon on February 16th, 2012

Kudos must go to Tony Redmond for a great article on how Exchange Archiving works and the implications of simply enabling it for example, all management staff.

Moral of the story: Notify users, Confirm ‘Default Policy’ settings, Then tick the box.

My Srvany & Instsvc is broken!!!

By brendon on February 15th, 2012

Rest in Peace instsvc.exe, you have served a good and hearty life. With the invent of 2008 x64 you are no longer required.

A built in tool ‘sc’ is now the command to use for all your services related configurations.

SRVANY.exe can still be used to run applications, simply specify:

sc create MRTG binPath= C:\Windows\System32\srvany.exe DisplayName= "MRTG"

Add the appropriate information into HKLM\SYSTEM\CCS\Services\MRTG\Parameters\ and your favourite multi-router traffic grapher will start with windows. =)

SBS 2011 and .NET Framework 1.1

By brendon on February 6th, 2012

<sigh> New SBS 2011 Essentials server and customer just HAS to install QuickBooks with .NET 1.1 </sigh>

Thanks to several posts on the SBS Diva Blog I was able to identify the issue and fix it in a slightly different way.

All web sites hosted (http://server/Remote, /Connect, etc.) were reporting the following HTTP 500.0 server error -
“Calling LoadLibraryEx on ISAPI filter “C:\Windows\Microsoft.NET\Framework\v4.0.30319\\aspnet_filter.dll”

Is obviously caused by x64 code being executed by x32 .NET – Enabling x32 compatibility in the Application Pool did not help. To resolve: Continue Reading

My certificate is missing it’s public key….

By brendon on November 3rd, 2011

Ever had a problem where you KNOW the certificate private key is on the server but the certmgr says otherwise??

I Found a really usefull post which shows how to fix Just this issue!

Option #1:Repair Damaged Certificate (Windows Server 2003/2008)

    1. Open MMC and add the Certificate Snap-In for the Local Computer account.
    2. Double-Click on the recently imported certificate
    3. Select the Details tab.
    4. Click on the Serial Number field and copy that string
    5. Open up a command prompt session. (cmd.exe aka DOS Prompt)
    6. Type: certutil -repairstore my “SerialNumber” (SerialNumber is that which was copied down in step 4.)
    7. After running the above command, go back to the MMC and Right-Click Certificates and select Refresh (or hit F5 in the MMC)
    8. Double-Click on the problem certificate. At the bottom of this window (General tab) it should state: “You have a private key that corresponds to this certificate.

30 seconds later – Legend!

Just keep in mind, SBS likes to have any certificates with a subordinate authority also have their certificates listed in the MMC -> Certificates -> Server -> Trusted Subordinate Authorities.