Find hidden mailboxes in Exchange 2003
Before you can remove an Exchange server from your org, you need to get all the mailboxes off of it. I was working on a Exchange 2007 CCR migration and found that there was still a long dead Exchange 2000 server in the org. The admin had tried to delete it, but it reported that there was still a mailbox on the server. He had checked every AD account for it to no avail. If you want to find out what AD accounts still have resources on a specific server:
- Start ADUC on the Exchange server, assuming it Windows 2003.
- Right click on your domain at the top and choose "Find".
- Click on the "Advanced" tab.
- Under "Field", select User, then "Exchange Home Server".
- Change the "Condition" from "Starts With" to "Ends With".
- In the "Value" field, type in the old Exchange server name and then click add to set the value.
- Click find to start a search.
You can then open that user account and clear out the Exchange settings that are holding you back.
Web Pages Loading Slowly On Vista
Slow web pages under Vista are nothing new. Heck, slow anything on Vista is something you sort of come to expect. But sometimes, you will have just a single machine suddenly get slower, regardless of the browser you are using. This is unusual. If you are running Vista, you may be having a problem with a new security setting.
A recent Microsoft Knowledge base article describes one potential cause of the problem: RFC 1323 compliance. Though the text suggests that it just affects the Enterprise version, the Applies To section lists all versions of Vista. In a nutshell, websites that don’t fully support RFC 1323 or the default Windows Scaling factor of 8 will be very slow or even inaccessible.
There is an easy workaround:
Press the Windows and type cmd, then press CTRL+SHIFT+ENTER to open a command prompt as an administrator. At the command prompt, type:
netsh interface tcp set global autotuninglevel=highlyrestrictedThis will set the autotuninglevel to a somewhat more permissive setting. If you want to put it back to the default setting, type:
netsh interface tcp set global autotuninglevel=normalYou can disable autotuning altogether with this command, but do so at your own risk (note that the date on the RFC spec above is 1992. If this was going to get exploited, it would have been done already):
netsh int tcp set global autotuninglevel=disable
It has been asked if this requires a reboot. In my experience, no it hasn't, but YMMV.
in case you know for sure
that your website is down, you can go here: www.thewebsiteisdown.com
in case you are looking…
This site will actually tell you if a site is really down or just down for you...