Customer was upgrading from Exchange 2003 to Exchange 2007. Installed Windows Server 2003 Enterprise x64 on a new server, ran all the updates, installed Exchange. Started migrating users over to the new server and no issues. Or so we thought.

A couple users had problems retrieving new emails in Outlook. Their iPhone/Blackberry showed the newest emails. Outlook web access showed the newest emails. Even Exchange 2007 showed DELIVERED for the new emails. The only solution to fix this problem at first:

Remove Cached Mode for Exchange
Remove the offending user’s shared mailbox
Magically Mail would start flowing after either of these two steps were done. However, since the problematic users were remotely located, cached mode must be used and the users required the shared mailbox.

The only users complaining had:

Cached Outlook Profiles
Other users mailboxes shared in their profile
Wireless connection to the network

First check (after making sure the email actually went through) was to look in ADSI Edit to verify that the users had proper permissions (you can also check on the client).

Start, Run
adsiedit.msc
Navigate to your Domain, and then your Users group.
Right-click on the user and select Properties
Make sure that homeMDB and homeMTA have your new servername in there

Second was to fix the OST file. We scanpst.exe (program files/microsoft office/office12/scanpst.exe) and repaired any errors.

Third was to start a new profile – we even tried on a test machine to be sure that it wasn’t a local issue.

Nothing worked. Final step (which worked) was to go to the following:

Open Outlook
Navigate to Tools – Account Settings
Click on your Exchange account and then click Change…
Click the More Settings… button
Click on the Advanced tab
Uncheck Download shared folders (excludes mail folders)
Restart Outlook

And here I thought I would be done with Windows 2000 Advanced Server. Oh well.
Basically you’re allowed 2 RDP sessions and 1 console (local) session on win2k server. Server 2003/2008 allow you to use all 3 sessions remotely, which is a definite plus. Easy way to get to the console session of 2003/2008:

Start, Run
mstsc /admin
IP or Name of your server

Easy way on Windows 2000. Uh, THERE IS NO EASY WAY.
Our situation:
2 Windows 2000 Advanced Servers
Located 120 minutes away
Not on the domain (workgroup)
One of the servers had the maximum number of connections
The other server we could login no problem

As long as you have rights (privs) to the admin share (c$) of the computer, you can very easily connect:
1.) I logged into the win2k server that still worked
2.) Pulled up the command prompt
3.) Typed qwinsta /server:192.168.20.150
4.) Typed rwinsta /server:192.168.20.150 sessionid

Basically qwinsta will query for all the active/disconnected RDP sessions on the server. Rwinsta will remove the session id you pick. Check out the picture for more information.

Then just connect as usual.

******EDIT******
OK, so sometimes I’m a little slow on the uptake. I forgot how to manage remotely without being part of the domain. Authenticate as a user on that system and you can do it all remotely – ie if BOTH of those servers had max connections, what would I do?

net use /user:usernamehere \\ip_of_the_server\c$
This will prompt you to enter a password for the username you selected
Now you can run the same commands above.

ALSO, it looks like you can use:
query session /server:192.168.20.150
and
reset session 36 /server:192.168.20.150
as those are easier to remember on new systems.

Daemon Tools would not run. I was receiving the error:

This program requires at least Windows 2000 with SPTD 1.60 or higher.
Kernel debugger must be deactivated

Awesome. And it was after I had installed Threatfire and then rebooted.
I tried setting TF to delayed automatic service startup, but still no dice.

Here’s the work around:

Hold Ctrl and right-click on the Threatfire icon in the taskbar tray
Select Exit
Windows Key + R, and type in CMD and hit enter
net stop threatfire
Load Threatfire by opening the program

Supposedly a temporary work around, but it’s been almost 6 months. Apparently you can also delay the startup by using WinPatrol.

Customer had complained he was seeing his domain (we’ll call it domain.tld just to be on the same page), several workgroups, and several other connections he wasn’t sure about.

So I fired up my trusty XP virtual machine (workgroup) to view all the workgroup computers in the Microsoft Windows Network (My Computer — My Network Places — View Workgroup Computers — Microsoft Windows Network). I could see “Domain.tld”, “Workgroup”, and “Workgroup1”. Now you should be able to open each of these up and list the systems that belong to the groups, but I wanted to know more information about each one.

Download NetResView. Run the program and after a short period of time it should display a bunch of information about each system. Works under XP Pro and 7 64bit.