Dusty Cables dot com

a tech blog

Tag Archives: Microsoft

Outlook AutoComplete cache

July 13th, 2010. Published under Uncategorized. No Comments.

Outlook 2007 icon

Many times I have been asked about the Outlook address auto complete cache.  This is the way Outlook provides email addresses you have sent or received mail with in the To, CC, or BCC fields in mail messages.  I thought this wasn’t possible in the past.

Not so, apparently.  This cache is stored in the “profilename.nk2″ file, where “profilename” is the name of the Outlook profile.  This file is hidden, so “view hidden files and folders” must be enabled in Windows Explorer.  It resides in the “%USERPROFILE%\Application Data\Microsoft\Outlook” folder.  Just copy this over to the new location to bring the autocomplete cache along and remember to rename the file if the destination Outlook profile name is different.

More details for this process can be found in this post at mycomputeraid.com.

CD / DVD drive missing / not recognized by Windows

March 3rd, 2010. Published under Uncategorized. No Comments.

Recently an associate came across this issue, where a Windows XP laptop was not showing a drive letter for the DVD drive. The drive was obviously powered since it would open when the eject button was pressed. In Device Manager, the drive was showing the yellow exclamation point symbol for a device that had a driver issue. The usual action of deleting the device in Device Manager and restarting did not change this; it just came back with the yellow exclamation mark.

Googling for this issue let to several forum posts where the solution was a quick deletion of two values in the registry. The solution, which works for Windows 2000, Windows XP, Windows Vista, and Windows 7, can be found at the Microsoft Support site.

A quick reboot after the registry deletions fixed the issue on this laptop.

How to access Administrative Shares on Vista (C$)

November 23rd, 2009. Published under Uncategorized. No Comments.

Found this gem recently about turning on the hidden administrative shares in Vista.

Text clipped from http://www.paulspoerry.com/2007/05/09/how-to-access-administrative-shares-on-vista-c/

To enable administrative shares you gotta make a registry change. Click on the orb and in the search box type ‘regedit’ and hit enter. Browse to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System. Add a new DWORD called “LocalAccountTokenFilterPolicy” and give it a value of 1. Reboot and yer done!

Export Outlook profile settings

January 12th, 2009. Published under Uncategorized. No Comments.

Outlook 2007 icon

This is a great help when moving someone over to a new computer (at least if doing so manually).  You can export Outlook profile settings using Regedit and import them on the new computer.  You’ll have to manually move data files, though.

I know this works in Outlook 2003 and I believe it works in most other versions as well.  Each profile is saved in its own key, with the profile name as the key name, under the following key:

\HKEY_CURRENT_USER\Software\Microsoft\WindowsNT\CurrentVersion\Windows Messaging Subsystem\Profiles

Export this entire key and subkeys and import them on the new computer.  Then move data files over.  If you can manage to make the username the same and the profile path comes out the same, you are golden.  If not, then go into the settings of each profile and change the path to each data file.

UPDATE: Outlook 2013 location is HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\Profiles.

Outlook Anywhere and Exchange Server 2007 – Round 2

December 25th, 2008. Published under Uncategorized. No Comments.

Exchange 2007 logo

OK, I didn’t know I was going to have a “round 2” here (round 1 is here), but apparently I was not done configuring things.  Hey, I never claimed to be perfect.  In fact, this install is the first time I’ve touched Exchange 2007, so I’m learning as I go.  But its all working now (as far as I know, at least).

The first issue we noticed was a syncronization error in the “Sync Issues” folder (sounds appropriate).  More like a bunch of errors, but they all said the same thing (names changed to protect the innocent, of course):

17:11:46 Synchronizer Version 12.0.6315
17:11:46 Synchronizing Mailbox ‘Domain User
17:11:46 Synchronizing Hierarchy
17:11:47 Done
17:12:13 Microsoft Exchange offline address book
17:12:13                  Not downloading Offline address book files.  A server (URL) could not be located.
17:12:13         0X8004010F

This didn’t seem to break any functionality, as the user could still open and use the Global Address List.  But these stacked up quickly, I believe every time a Send/Receive occurred.  It is worth noting these Outlook Address Book sync issues occurred on only Outlook Anywhere (OA) users and only when connected to the internal network and only when the laptops were not joined to the domain.  When they were externally-connected these issues did not occur.  The internally-connected computers joined to the domain did not have this issue.

The second issue was with the Out of Office Assistant (OAA).  Users would receive the following error when opening OOA:

Your Out of Office settings cannot be displayed, because the server is currently unavailable.

This of course was not true; Exchange was working beyond these issues.  What’s more, OA users, when accessing Exchange from outside the LAN, had no problems with OAA connectivity, but this time the internally-connected domain members did have the issue.  Still, OAA worked fine from Outlook Web Access, so I knew it was not an issue with the OAA mechanism itself.

Using the Test E-mail Autoconfiguration tool by doing a CTRL + right-click on the Outlook icon in the System Tray verified I was having internal DNS issues.  These issues were due, I presume, to my original choice of domain namespace, using the “corp” subdomain for the Active Directory domain name (corp.domain.com).

To fix, I created a new Forward Lookup Zone namespace for “domain.com” internally.  This was a Primary zone stored in Active Directory.  This of course would break the ability for internal clients to browse to domain.com, since this website is hosted externally.  No problem, I just made a “same as parent folder” A record and a “www” A record, both pointing to the same IP address the external A record for domain.com.

To solve the issues breaking OAB sync for internally-connected OA users and OAA connectivity for everyone, I added the following records to the internal namespace:

  • “owa” A record pointing to the internal IP address of the Exchange server
  • “autodiscover” A record pointing to the internal IP address of the Exchange server

Once the clients picked up the changes, both issues went away.  Again, maybe I should not have created “corp.domain.com” for the internal AD namespace.  It has worked in the past for me, so I stuck with it when building this network.

I welcome any comments in regard to internal namespace structure.

Windows 7 news

October 29th, 2008. Published under Uncategorized. No Comments.

There have been a number of Windows 7 articles recently, due to Microsoft flaunting it the Professional Developers Conference in LA this week.  I’ve been reading up on a few of them and am a bit excited about Windows 7.  But then again I was excited about Vista before it was released, and we won’t talk about how that went.  Still, as Gizmodo is pointing out, Windows 7 is looking like what Vista should have been.  Check out these two Gizmodo articles:

Windows 7 Walkthrough, Boot Video and Impressions

Giz Explains: Why Windows 7 Will Smash Vista