Additional Mailboxes

Q: I have openened aditional mailboxes in Outlook. When I remove it it is still in my folderlist but I can’t find it in Tools | Services | Exchange Server | Properties | Advanced . How can I ger rid of it?

A: Start Regedit and go to HKEY_CURRENT_USERSoftwareMicrosoftWindows NTCurrentVersionWindows Messaging SubsystemProfiles<Name of Outlook Profile>

Look through the subkeys till you find the one containing the name of the mailbox thar you want to delete. Remove that key and start Outlook.

Shared vs. Open Authentication



When a wireless client (or station) connects to a wireless access point, there are 2 steps involved. First the station must be authenticated. If that passes, the station can then be associated. Once that’s done, traffic can pass.

As a part of using WEP, there is a type of authentication called Shared Key that can be used (not available if you’re not doing WEP). Shared Key Authentication is considered to be a BIG security hole! In fact, the upcoming 802.11i amendment prohibits its use.Here’s why:

For shared key authentication, the Access Point (AP) generates some random string of ASCII, sends it CLEARTEXT to the Station, the station encrypts it using his configured WEP key, sends it ENCRYPTED to the AP, and the AP then decrypts it to see if the starting ASCII string is produced. This is meant to insure both sides have the same key. The problem is that 2 of 3 parts of the encryption scheme are sent over the air, and makes it much easier for a hacker to figure out the WEP key. Therefore it’s generally recommended to not use shared key authentication anymore.

(For the curious Using Open Authentication ends up being better than shared key, because the authentication step ends up being a NULL step – the station is just automatically authenticated, and subsequently associated. But they still have to have the right WEP key for the encryption/decryption on the actual packets to work. A station that is allowed to associate, but can’t pass traffic is considered a lesser threat.

Original thread location: – Establish a Wireless ISP Operation – Start a WISP Powered by Mambo Generated: 15 September, 2005, 09:06

Unable to add SQL Server ODBC DSN

If you are unable to add a new SQL Server DSN in Datasources it is probably due to a missing or corrupt sqlsrv32.rll file in c:windowssystem32.

Extract a new one from MDAC (the version you are currently using) with mdac_typ.exe /C /T:C:destination and copy the file to c:windowssystem32

This has also been known to stop Axapta from starting.

MDAC uninstall workaround

Here is the trick we bought from Microsoft customer support for $250.00

Let me know if you have any additional questions/concerns.
1. Download the MDAC version you want on the box from:

2. Open the registry editor by entering the following at a command prompt:

3. Navigate to the following hive and delete the exception components:


Note: this prevent you from overwriting MDAC is they exist therefore they need deleted.

4. navigate to the following hive HKEY_LOCAL_MACHINESOFTWAREMicrosoftDataAccess

and set the following key to the following value: FullInstallVer, RollbackVersion, and Version to 2.60

Note: when MDAC checker it will see it’s old and allow the upgrade to 2.6 SPx or higher

5. Disable anti-virus(very important), stop services such as SQL server, IIS, etc., close applications

6. Run the MDAC_typ.exe from step 1 above to install they version on the box.

7. Reboot and verify the install by running the MDAC Component checker downloadable from

OR try

1. Windows operating system repair to get to the RTM release of MDAC.

2. Download the version he wanted on the box from

3. Disable Anti-virus(VERY IMPORTANT), close all applications, stop services such as SQL and IIS, then run the MDAC_tpy.exe for the version downloaded in step 2 above to install it.

4. Verify the install via the MDAC Component Checker also on

5. Apply Windows updates and hotfixes.

Why does my Exchange 2003 server take 10 minutes or more to shutdown?

Why does my Exchange 2003 server take 10 minutes or more to shutdown?

It seems that most users that install Exchange Server 2003 on a Windows Server 2003 machine that is also configured as a Domain Controller may experience a slow shutdown when they try to reboot/shutdown the server.

This is because the Active Directory related services shut down before the Exchange services, thus causing the Exchange services to fail repeatedly while looking for the DS. Exact and detailed explanations for this behavior and restrictions can be found in the KB articles listed below.

There are 2 known solutions for this problem (besides listening to me and NOT installing Exchange on a DC in the first place…). One is to change the timeout for a failed service to shutdown itself, and the second is to manually stop the Exchange services BEFORE shutting down the server.

Method #1: Services kill timeout
Follow these easy steps:

Run Regedit and navigate to


The default value of WaitToKillServiceTimeout is set to 600000. Change it to 20000.

Exit the registry editor and reboot the server.

Note: Changing the WaitToKillServiceTimeout value may have some undesired effects on other services, use this method at your own risk.

Method #2: Manually stop Exchange related services
The best choice is to manually shutdown the Exchange related services before trying to shutdown or reboot the server. You can do so manually by going to the Services snap-in in the Administrative Tools menu and stopping the specific Exchange related services, or, you could use a script.

Source: Daniel Petri

How can I create the DomainDNSZones directory partition?

Question: How can I create the DomainDNSZones directory partition?

Answer: Windows Server 2003 typically creates an application directory partition to hold the DNS information that’s replicated only to domain controllers (DCs) that are DNS hosts. If you upgraded from an earlier version of Windows, this partition might not exist. You can create it by performing these steps:

  1. Start the Microsoft Management Console (MMC) DNS snap-in (click Start, select Programs, then click Administrative Tools, DNS).
  2. Right-click the DNS server name and select “Create Default Application Directory Partitions.” A window like the figure at Figure appears.
  3. Click Yes when asked whether you want to create a single partition for all DNS servers in the domain.

You can also create the DomainDNSZones partition from the command line. To create a partition for only the domain in which the DNS server resides, execute the command

dnscmd <DNS server> /CreateBuiltinDirectoryPartitions /Domain

where <DNS server> is the name of your DNS server. To create a partition for every domain in the forest, execute the command

dnscmd <DNS server> /CreateBuiltinDirectoryPartitions /AllDomains

Source: Windows IT Pro