When Jeff Deleted One Registry Value, You Wouldn’t Believe The Difference It Made or Accessing SBS 2003 Previous Versions on Win 7/Server 2008

Dropped a Server 2008 R2 machine in to a client’s environment to act as a Remote Desktop Host, but when I went to check on Previous Versions functionality, I saw that all the entries were the same date when accessed from the 2008 box, but they were fine on my XP clients and the 2003 box itself.

image_2

Happily, the good folks over the SBS Blog at Technet (where I stole the above screenshot from) had a simple fix there for the searching.  We just had to delete a registry key that was there to help Windows 2000 clients.  Since we don’t have those anymore, we can safely get rid of the key and restore our functionality.  It doesn’t even require a reboot!  (This holds for non SBS flavors of Server 2003 as well.)

  1. On your SBS 2003 server, open REGEDIT and navigate to the following location:
    HKLM\SYSTEM\CurrentControlSet\Services\lanmanserver\Parameters
  2. Right click on parameters and select Export.
  3. Once the export is completed, find the entry for DisableDownLevelTimewarp, select it and then delete it.

That’s it!

DynaZIP OCX Installation Under Windows 7

We have a client who has an old in-house app that relies on the DynaZIP 32-Bit OCX Interface to run.  We’ve been trying to get it to run under Windows 7, but couldn’t find much info — but I happened to come across a text file from DynaZIP that had the dependencies on it, and it turned out we were missing a couple files; loaded them into SYSWOW64 and the OCXs register.

You need to make sure the following files are in your c:\windows\ syswow64 directory:

  • OC30.DLL
  • MSVCRT20.DLL
  • MFCANS32.DLL
  • OLE2.DLL
  • COMPOBJ.DLL
  • STORAGE.DLL
  • OLE2DISP.DLL
  • OLE2NLS.DLL
  • TYPELIB.DLL
  • DZIP32.DLL
  • DUNZIP32.DLL
  • DZOCX32.OCX
  • DUZOCX32.OCX
  • DZSTAT32.OCX

Then open a command prompt with admin privileges and run REGSVR32 on the lot of OCXs.

SBS 2003 Shows 5 Licenses Instead of 20

licenseiconThe SoftwareDistribution.log file on a client’s SBS system went insane and spooled to 66GB and filled up their C: partition. Deleting it was easy enough, but we had a larger issue that didn’t reveal itself until a little later — the server’s licensing database corrupted and the Server Manager was showing only 5 licenses instead of 20, and when the 11th person tried to log on (I assume MS isn’t heartless and gives you some wiggle room before dropping the banhammer) they were shut out.

A restart of the license logging service provided temporary relief, but I was getting ready to head over there to find the license keys that shipped with the server back in 2009.

But, the IT community is nothing if not a bunch of people who watch each other’s backs, and I must throw a GIANT THANK YOU to Chris Knight, an IT guy from halfway across the world in Tasmania, who posted an article — seven years ago!! —  “Small Business Server 2003 – The Dreaded 5 CAL Reset Issue” on his blog.

Long story short, MS makes a backup of your license file called autolicstr.cpa which lives in c:\windows\system32.  It’s made at the time of license install and it should be a copy of licstr.cpa which also lives in the system32 directory.

But, if, like me, your licstr.cpa gets corrupted, you can just:

  1. Stop the License Logging Service
  2. Copy autolicstr.cpa over licstr.cpa
  3. Restart the License Logging Service
  4. Verify in Server Manager that your licenses are back

Worked for me and my client is thrilled; and best of all, I didn’t have to leave my office.

Outlook for Mac Using Wrong Name on Replies

Outlook2011macWe have a client who manages multiple accounts for different identities under one Outlook instance.  He was running into an issue where Identity 1’s name was showing up in replies sent from Identity 2. So, he’d click reply on something sent to Identity 2, Identity 2 was selected in the accounts selector at the top of the message, but in the body of the message was:

————————-
ORIGINAL MESSAGE

FROM:  Sender <sender@example.com>
TO: IDENTITY 1 <identity2@hisdomain.com>

etc…

It was a simple fix once we found it (and we looked everywhere, since Identity 1 is the name the Mac was registered to, we didn’t know where it was grabbing the name from).

There was a contact card in Outlook that had Identity 2’s email address associated with Identity 1’s name; so Outlook “resolved” the name incorrectly – instead of taking it from the account properties, like we assume it should have; it took it from the contact card.

Once we deleted the Identity 2 address from the Identity 1 contact, all was right in the world, and our replies went back to looking like:

————————-
ORIGINAL MESSAGE

FROM:  Sender <sender@example.com>
TO: IDENTITY 2 <identity2@hisdomain.com>

etc…

 

 

Internet File Blocking on Server 2008 and Windows 7

We’ve got a client who recently upgraded their Windows Server 2008 Remote Desktop Services box from Office 2003 to Office 2010.  In doing so, they ran up against Internet File Blocking which Office 2010 seems to take seriously, where Office 2003 ignored it.

In a nutshell, any file you download from an “insecure” location, like say, your email, gets a tag injected in its Alternate Data Stream marking it as potentially unsafe, so when you try to open it using Office 2010, you get this helpful dialog:

blockeddoc

File permissions are fine and disk space and memory is plentiful, so what’s the glitch?  It’s the alternative data stream, a hidden feature of NTFS that allows, well, alternate data to be stored along with your file; so in our case, every downloaded file has a Zone Identifier in its ADS, and Office will hemorrage with an unhelpful dialog if it comes across something.  Internet Explorer at leasthas the decency to tell you the score:

ofsw

So, the question is how does one open these files in Office?

One way is to right click on the file, go into the properties tab and click the UNBLOCK button

fileblock3_30790E2A

But that can get tedious.

You can use SYSINTERNALS’s streams.exe file to strip the ADS out of a bunch of files.

Or, you can turn the behavior off, which is what we did for our client.

A quick trip to the Google brought us to Dixin’s Blog (which is where we cribbed the “file properties” screenshot from) and the steps are laid out very clearly there.

In a nutshell, go to Group Policies and edit or create a policy to enable a single setting in User Configuration > Administrative Templates > Windows Components > Attachment Manager > Do Not Preserve Zone Information in File Attachments.  

Log off and log back on, and you’re good to go.

(We also forced the “Notify Antivirus Programs When Opening Attachments” setting, just to be on the safe side).

Anyway, you should really just go read the article over at Dixin’s Blog and read Understanding The Internet File Blocking and Unblocking, it’s much better than this one.  Lots of screenshots and explanatory text in an easy to read manner.