Kerpau!

Although, I have no idea why this happens, here is how to fix RDP/RDC connections after a SQL Server 2005 installation breaks it.

• Control Panel > Administrative Tools > Terminal Services Configuration > Connections
• Delete the RDP connection
• Right-click Connections and select Create New Connection
• Accept the wizard’s defaults
• Name it RDP-tcp or something descriptive
• Reboot, and you’re back in business!

Unfortunately, the reboot is necessary.

Sorry but it won’t work. I can’t imagine why Microsoft would have dsquery and dsget operate on only a partial set of the user’s properties and leave out others but they did provide TSPROF to bridge this particular gap.

tsprof

TSPROF /UPDATE [/DOMAIN:domainname|/LOCAL] /PROFILE: username
TSPROF /COPY [/DOMAIN:domainname|/LOCAL] [/PROFILE: ] src_usr dest_usr
TSPROF /Q [/DOMAIN:domainname|/LOCAL] username

A simple dsquery command piped to dsget will show us the home directory for all users in an Active Directory domain.

dsquery user -limit 1000 | dsget user -hmdir

To change the home directory setting, use a variation on the same command.

dsquery user -limit 1000 | dsmod user -hmdir \\server\share\$username$

The $username$ variable will be populated with the value of the current user’s account name.

I have been seeing requests for notified-Compliance_page, a non-existent page in my Web logs lately. They are coming mostly from Google networks with Mediapartners-Google/2.1 as the user agent. Does anyone know what these are about? If so, drop me a line or leave a comment. There isn’t much information on the Web about this and I would love to know more. Thanks!

This DSQUERY lists all e-mail addresses in Exchange, and Active Directory including Public Folders, Contacts and User mailboxes.

dsquery * forestroot -scope subtree -filter “(&(mail=*)(proxyaddresses=smtp:*))” -attr proxyaddresses - limit 10000

The output is a bit messy but nothing a little bit on time in vim can’t fix. Bharat Suneja has a very elegant script that does the same thing but it doesn’t include the SMTP addresses of public folders.

I was pretty geeked out about this - Are Sysadmins Really that Bad?. I submitted it about two months ago. It’s the only article I’ve ever submitted and it got accepted! Smakynet suggested I write about it because it gives me “street cred” as a geek.

The actual name of this is Intel(R) Processor Identification Utility and can be found by searching at http://downloadfinder.intel.com. However, I have to poke around Intel’s site for a few minutes every time I want to download the utility. For convenience, here is the URL - http://www.intel.com/support/processors/tools/piu/

The fix for this error condition is relatively simple. If your Exchange server has network interfaces on more than one network (perhaps a SAN or a dedicated backup network), it may be attempting to locate global catalog servers using the wrong network.

Event Source: MSExchangeDSAccess
Event Category: Topology
Event ID: 2103
Description: Process MAD.EXE. All Global Catalog Servers in use are not responding:

Go to Control Panel > Network Connections > Advanced > Connections and move the network interface that has access to your global catalog servers to the top of the list. No reboot or service restart is necessary. The Exchange server “checks in” with a global catalog server every 15 minutes so watch it for a while to get the warm fuzzy feeling of having saved the day yet again.

This error is the result of either Windows restricting access to a file downloaded from the Internet or a zip file that contains unexpected path separators. In case number one, go to the properties of the file and select Unblock. Your group policies may need to be adjusted for you to see this button. In case number two, the path separators may start with a leading backslash. If this is the case, download WinRAR and use the Extract without confirmation option to unpack the contents of the zip file.

The solution to this is to delete the FRMCACHE.DAT file located in the Documents and Settings\user.name\Local Settings\Application Data\Microsoft\FORMS folder. This fixed it for me on an Outlook 2003 system. I think it had something to do with some custom forms I had installed.