Windows Update and Error 0x8DDD0018 -FIX

I was having a hell of a time trying to get a Windows 2003 R2 Standard x64 server to load the Windows Update site. I was always getting the error: 0x8DDD0018

Sadly, the troubleshooting info at MS focused on starting the BITS service which (seemingly) was working just fine.

Well, I eventually stumbled on the solution. Try this at a command prompt:
regsvr32.exe wuaueng.dll

Presto! Windows Updates should be working for you again :)

64bit (x64 and Itanium) OLEDB provider for ODBC (MSDASQL) Download!

If you've ever tried to link a 64bit SQL 2005 server to something like Excel or MySQL you know that it just isn't going to happen without MSDASQL .

Well, it's finally out! Get it right from MS here: http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be-ca44d18b059b&displaylang=en

Here's the description from the MS download:
The Microsoft OLE DB Provider for ODBC (MSDASQL) is a technology that allows applications that are built on OLEDB and ADO (which uses OLEDB internally) to access data sources through an ODBC driver. MSDASQL is an OLEDB provider that connects to ODBC, instead of a database. MSDASQL ships with the Windows operating system, and Windows Server 2008 & Windows Vista SP1 are the first Windows releases to include a 64-bit version of the technology.


Enjoy!!

Need to transfer logins from one SQL 2005 instance to another SQL 2005 instance? Here's how!

In SQL 2000 there was a DTS package that could do this. I didn't like DTS and never used it, but it is out there. I used the Microsoft-provided sp_help_revlogin stored procedure instead to do this in 2000, but when I looked at the code I realized it would need an update for 2005.
In 2005 the sys.syslogins view exits, but you really shouldn't use it- you should use sys.server_principals (see books online). So, when I looked at that system view I realized this was really going to take some work... so naturally I Googled! ;)

Anyways, I found out that good-ol' MS had already updated the TSQL that generates sp_help_revlogin (and it's required binary stored proc) and posted it online in KB 918992. I copied the code and it worked just like it always had except that I was able to transfer the logins with SIDs and passwords from one 2005 instance to another instead of a 2000 to 2005 or 2000 to 2000 instance. :)

http://support.microsoft.com/kb/918992

Disappearing Symantec Anti Virus Tray Icon (VPTray)

Maybe you want that stupid yellow shield (I think that's what it is... looks like an old mouse to me!) gone, and maybe you don't.

If you want it back and you can't seem to figure out how to get it back check out the directions here:
Symantec Support


Or just go ahead and try this:
To enable the system tray icon on unmanaged clients

1. Exit all open programs.
2. Click Start> Run. The Run dialog box appears.
3. Type regedit
4. Click OK. The Registry Editor appears.

1. Go to the following key:
   
   HKEY_LOCAL_MACHINE\Software\Intel\Landesk\VirusProtect6\CurrentVersion\AdministratorOnly\General
   
   
2. In the right pane, double-click the following value:
   
   ShowVPIcon
   
   
3. Change the value to 1.
4. Close the Registry Editor.
5. Restart the computer.

To add the registry value to the Run key

1. Exit all open programs.
2. Click Start> Run. The Run dialog box appears.
3. Type regedit
4. Click OK. The Registry Editor appears.
5. Navigate to the following key:
   
   HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
   
   
6. Click Edit> New> String Value.
7. Name the value "Vptray" and press Enter.
8. Double-click Vptray.
9. Type the path to Vptray.exe, enclosing it in quotation marks, and press Enter.
   
   Windows 98/Me/NT/2000/XP:
   
   "C:\Program Files\Symantec_Client_Security\Symantec AntiVirus\Vptray.exe"
   or
   "C:\Program Files\Navnt\Vptray.exe"
   
   
10. Close the Registry Editor.
11. Restart the computer.