29. June 2013 · Comments Off on Veeam FastSCP Windows 64bit Fix · Categories: Microsoft · Tags: , , ,

veeam_logo-big2

Having installed Veeam FastSCP onto my Windows 7 (64) Ultimate workstation I was getting the error messages Retrieving the COM class factory for component with CLSID [5F1555F0-0DBB-47F6-B10B-0AB0E1C1D8CE] failed due to the following error:  800700c1
More »

23. June 2013 · Comments Off on MicroNugget – ASA VPN Connection Profiles · Categories: Cisco · Tags: , , , , , , ,

21. June 2013 · Comments Off on How to Manually Remove Exchange 2007 · Categories: Microsoft · Tags: , , , , ,

How to manually remove an Exchange 2007 that got hosed.

Uninstalling exchange was also unsuccessful because some objects were missing from Active Directory. I also wanted to avoid reinstalling the OS as I have critical software that needs to remain.  So I tried removing exchange manually.

  1. Run setup /m:uninstall (From Exchange 2007 Media)
  2. Stop and disable all the Exchange 2007 services
  3. Use Registry Editor (Start->Run->Regedit) to remove these Exchange related registry keys:
    • HKLMSOFTWAREMicrosoftExchange
    • HKLMSYSTEMCurrentControlSetServicesMSExchange* (all the keys starting with “MSExchange”)
    • HKLMSOFTWAREMicrosoftWindowsCurrentVersionUninstallMicrosoft Exchange
  4. Remove the entire Web Server role (don’t forget to reinstall afterwards as it’s a prerequisite for E2K7!)
  5. Remove the Exchange 2007 server from Active Directory. I ended up deleting the entire “Microsoft Exchange” branch from ADSIEdit (Configuration Container > Services > Microsoft Exchange) as my domain only has one server.
  6. Use Windows Explorer to delete:
    • C:Program FilesMicrosoftExchange Server
    • C:ExchangeSetupLogs
  7. Use Windows Installer CleanUp Utility to remove all the exchange related info from the installer database.
  8. Remove the security groups created by Exchange setup from AD

Note: Manually removing Exchange 2007 is not supported by Microsoft! Official guidance for removing Exchange 2007 can be found in this TechNet article.

04. June 2013 · Comments Off on DNS dropped because packets to big for configured 512? · Categories: Cisco · Tags: , , , ,

6-4-2013 12-02-03 PM

you can safely increase the dns packet length to 1500 ,  512 is the default.

“fixup protocol dns maximum-length 1500 ”

Background on fixup protocol dns

Use the fixup protocol dns command to specify the maximum DNS packet length. DNS requires application inspection so that DNS queries are not subject to the generic UDP handling based on activity timeouts. Instead, UDP connections associated with DNS queries and responses are torn down as soon as a reply to a DNS query has been received.

The port assignment for the Domain Name System (DNS) is not configurable.

Set the maximum length for the DNS fixup as shown in the following example:

pixfirewall(config)# fixup protocol dns maximum-length 1500

pixfirewall(config)# show fixup protocol dns

fixup protocol dns maximum length 1500