This Blog is a supplement to my website. Please also visit: www.DavidCocke.com

Saturday, June 25, 2011

Copy an SSL Certificate from one Server to Another

I have customer that received a new web server from a vendor.  We needed to transfer the SSL certificate from the old web server to the new one.  I have many times created and/or renewed SSL certificates for websites, but this was the first time I needed to transfer it from one to another.


I found this great resource that stepped me through the process:

How to Move or Copy an SSL Certificate from one Server to Another

Turns out it was super easy.  The important things to remember are:

  • The name must be exactly the same (such as mysite.myplace.com)
  • The original certificate issued by the SSL provider must have the private key marked as exportable
It also helped that the old and new Windows servers used the same version of IIS.

Tuesday, June 7, 2011

QR Codes

I have a new Android phone and kept seeing these funny looking barcodes so I decided to learn more. Here is a quick reference for my friends and colleagues.

They are called QR Codes (Quick Response Codes).

Found a great video on CNET that gives a great general overview of how you can use this day to day:

Wikipedia gives you a more detailed and technical description:

On this website you can use their tool to create your own QR Codes:

For my Android phone I'm using an app called Barcode Scanner. I have a Sprint EVO 4G with an 8 megapixel camera and this Barcode Scanner app does amazingly well for several types of one and two dimensional barcodes.


The QR Code below will take you to my website:


Friday, April 22, 2011

Mouse not working in MS Word 2002 SP3 Office XP

Worked on a Windows XP computer today that has Microsoft Word 2002 SP3 (This is part of MS Office XP). When you open Word and type some text, you cannot highlight that text or click on it in any way with your mouse.

Using your mouse to click the menus works OK, and you can highlight the text using the keyboard.
This symptom was unique to certain people's profiles on this machine. Others logged into this machine did not have the problem.

I'm not totally sure what fixed it. I was trying the options listed in this Microsoft Support article (link below) including the Fix-It button and after a couple of steps would try it again.


I think the cure was deleting all template files (*.dot) from this directory:
C:\Documents and Settings\username\Application Data\Microsoft\Templates\
I was about to do the step regarding COM Add-Ins (have to open Word for that) and viola it was working.

I had already tried deleting the normal.dot file from this and other folders, but that didn't help.




Sunday, April 10, 2011

Errors installing Microsoft Security Essentials

During the install of Microsoft Security Essentials I was receiving the following errors:
  • 0x80070643
  • 0x8004FF37
In the end I found a Windows OneCare Cleanup Tool here:

This machine never had OneCare installed, but as I watched the cleanup tool do its work I noticed it was cleaning up older versions of Windows Antimalware and Windows Defender. This machine did have Windows Defender once upon a time.

For what its worth the Cleanup Tool wanted a reboot, but I declined, and MSE installed successfully.


Rogue antivirus still showing after removal

While in Spiceworks I noticed a computer that said it had two antivirus packages installed. One was legitimate (Symantec Endpoint) and the other was called "Personal Internet Security". After Googling I find this is malware; a fake antivirus package.

I found that once upon a time this machine had been infected with this. Somehow it had registered itself with Windows Security Center thus was still showing as an installed antivirus package. Funny thing too, it said it was current on its virus definitions.

To correct this I issued the following commands from a CMD prompt on that PC:

net stop winmgmt
cd /d %windir%\system32\wbem
ren repository repository.old
net start winmgmt

As I understand it, if you had an issue where no antivirus package was being found by Windows Security Center, the above commands might work for that too.

After issuing the above commands, I forced Spiceworks to rescan and it correctly identified that just Symantec Endpoint was installed.

Friday, April 8, 2011

System Restore eating up disk space

Today I was working on a PC that kept failing backups. Once I started the backup I was intrigued at how long it estimated to complete. Upon further investigation I could see that the disk space used was over 45 Gigabytes. This is extremely high for this PC.

Using TreeSize Free it reported only 13 Gigabytes being used. TreeSize Free cannot access the hidden System Volume Information folder. It then occurred to me that the System Restore might be the culprit.

As it turns out on Windows XP, the default for System Restore is to use up to 12% of the total disk space. This is huge when you consider the size of hard drives today. Obviously I wanted to reduce this size not only on this machine but for many others that we are responsible for.

Many thanks to Steen Kirkby's Blog for leading me in the right direction.

Using one of our favorite tools called VNCscan we were able to create some scripts to help roll-out the changes to several computers at once.

By reducing all of the computers to use just 1% of their total hard drive space will save us a ton of space on our backup volumes. On the troubled PC that started all of this, we went from using over 45 Gigabytes of space to just 13 Gigabytes.

In VNC Scan we broke this up into three scripts.

Script 1 - System Restore Cap to 1 percent (a CMD script)
%SYSTEMDRIVE%
cd \temp\vncscan

:: The following sets the maximum percentage of disk space used by System Restore

REG ADD "HKLM\Software\Microsoft\Windows NT\Currentversion\SystemRestore" /v DiskPercent /t REG_DWORD /d 1 /f

REG ADD "HKLM\Software\Microsoft\Windows NT\Currentversion\SystemRestore\Cfg" /v DiskPercent /t REG_DWORD /d 1 /f

ECHO Now you must stop and restart System Restore
PAUSE

Script 2 - System Restore OFF (a VBS script)
strComputer = "."
set objWmi = GetObject("winmgmts://" & strComputer & _
"/root/default:SystemRestore")
objWmi.Disable("")
WScript.Echo "System Restore disabled"

Script 3 - System Restore ON (a VBS script)
strComputer = "."
set objWmi = GetObject("winmgmts://" & strComputer & _
"/root/default:SystemRestore")
objWmi.Enable("")
WScript.Echo "System Restore enabled"

Hoping this will help someone else in the future.







Tuesday, April 5, 2011

Manually Updating GoToMyPC

Since GoToMyPC released their IPad client I have been wanting to try it out. I finally learned that in order for it to work your PC must be running at least version 7.x of their software.

If I went to a PC that had version 6.x you're supposed to be able to right-click the tray icon and "Check for Updates" but it always said I had the latest version.

Finally found this web page:


At the very bottom in fine print they tell you to manually upgrade click this link:

I went there, had to login first, but was then offered the download. Had to install it twice to get it to take, and even after it took, it then told me I had an update to apply. By the way, this is on a Windows XP SP3 machine.

This update process is obviously very buggy.