I just installed Windows Server 2003 on a private test-server.

After the installation I wanted to install Windows Live Messenger 2009, however it’s not possible according to the installer.

It seems that Windows Live Messenger cannot be installed on Windows Server 2003 and 2008.
I have found some posts online saying that it can’t even be installed on Windows XP 64 bit. However I have not checked if that is correct.

I searched the internet and found a solution for the problem and it worked for me.
I have made a step-by-step guide below on how I did:

1. First download Windows Live Messenger from http://download.live.com/?sku=messenger

2. Then download Resource Hacker.
You can find the official site here (contains info and download-link).
I have however added an extra download-link here to the current version (as of 5h November 2009).

3. Open the Windows Live Messenger installer-file in Resource Hacker.

4. Open the resource tree and goto “CONFIG” > “CONFIG0″ > “0″.

5. In the line to your right find the XML-tag <os productType=”workstation” />.

6. Replace “workstation” with “server” and recompile the script by clicking the “Compile Script”-button in Resource Hacker.

7. Save the modified file in Resource Hacker (that is done through the “File”-menu).

8. Now you are ready to install – simply run the saved file and the installer should not give any error now.

I hope this step-by-step guide helped you.
I now have Windows Live Messenger 2009 installed on my Windows Server 2003 enviroment – and that was my mission.

I have often had problems with deleting a Windows Service. Normally you shouldn’t delete a Windows Service, but sometimes (for example if a BETA program doesnt uninstall correct or something like that) it is needed.

I have listed two methods on how to delete a Windows Service here:

The first method is by changing in the Registry Database:
1. First run regedit or regedit32 (You can do that from the Start-menu > Run > Type “regedit” and then OK).

2. Find the registry-entry “HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services”

3. Look for the service in the tree-structure and delete it.
You can look at the keys (mostly the key ImagePath) to see what files the service is using and delete them as well (if necessary).

The second method is a bit more simple – it is by typing a command in the command prompt:
1. First run the Command Prompt (You can do that from the Start-menu > Run > Type “cmd” and then OK).
If you are running Windows Vista or Windows 7 you need to run the Command Prompt as an Administrator (that is done by right-clicking the short-cut and choose “Run as…”)

2. When the Command Prompt is running simply just type: sc delete “the-service-nam”.

Both methods require that you reboot the computer afterwards if you want to see the changes in the Service Manager.

When I started with my Synology DiskStation 207+ I had the problem with Windows losing the connection to my shared folders on the DiskStation.
Sometimes it simply just said that I used an incorrect username and password - eventhough I had written the correct username and password when I set up my network drive.

I found out that by creating a user on the DiskStation with the same username and password as my Windows User the problem stopped. You actually don’t have to logon to the drives after this “fix” – you can just simply access it by adding the network drive or by the default network address. Of cource you have to give the new user the correct rights, but after this is done it works perfectly.

This way you can also control the different users on your Windows-machine and give them different access on the Synology DiskStation. Easy as hell

Have a nice try !

I’ve had a problem on my laptop at work. Suddenly my CD/DVD-drive was not found in “My computer” and looking in “Device Manager” just showed me a yellow exclamation mark for my CD/DVD-drive and an error that my driver was corrupted or missing (Error code 39).

The exact error-message was: “Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)”.

At first I tried to remove the drive through the “Device Manager” and reboot my computer, but that didn’t help at all. I then started looking on the internet hoping I could find a solution. After about an hour I did.

The problem – on my computer – proparly is that I have installed or uninstalled an application that has an CD/DVD filter driver. That could make this error occur. Microsoft made a description of the problem and has made a solution for it too. You can see this here.

However instead of using the slow manual Microsoft has described as a solution, I chose to find a VBS-file that could do the same just by double clicking it. You can find this file here.

I downloaded the file, executed the file and rebooted my computer. After that my CD/DVD-drive was found in “My computer” and was no longer tagged with a yellow exclamation mark in the “Device Manager”.

Please notice I do not take any responsibility for errors this fix might do. Running the script or following my guide is 100 % your own responsibility.

My CD/DVD-drive was the following model: HL-DT-ST DVDRAM GMA-4082N.

I hope this solution will work for you aswell.

Jeg har tidligere beskrevet problemet omkring det røde kryds, der fremkommer, når man forsøger at sende en e-mail eller lign. via Outlook Web Access og man sidder på en maskine med Windows Vista og Internet Explorer 7.0.

Du kan finde mit blog-indlæg omkring problemet her.

Jeg kom også med en løsning på problemet den gang, men der er faktisk en endnu nemmere løsning.

I en dansk-sproget version af Outlook Web Access, kan det løses ved at gå ind i “Indstillinger”, herefter nedunder “E-mail-sikkerhed” og klikke på knappen “Hent”. Herefter vil man blive spurgt om man vil downloade en lille fil. Denne fil skal man køre, hvorefter S/MIME control bliver installeret.

Efter installationen skal man gerne via Outlook Web Access igen kunne skrive e-mails.

Teknisk set skyldes det at Microsoft i Windows Vista har fjernet den såkaldte “DHTML Editing Control” for at højne sikkerheden i styresystemet. En af de applikationer, der benytter sig af denne control, er Outlook Web Access.

Problemet kan nemt løses – men ikke af brugeren selv. Det skal i stedet løses af den/de systemansvarlige, idet der skal installeres en opdatering til Exchange-serveren. Microsoft har udgivet opdateringen som krævet, og den findes til både Exchange 2000 og Exchange 2003.

Opdateringen kan du også finde her (KB911829).

Det gode ved opdateringen er – foruden at den selvfølgelig løser problemet – at den ikke kræver en genstart af Exchange-serveren.

Lad os håbe, at de forskellige systemansvarlige snarest får taget denne opdatering til sig – jeg oplever nemlig selv flere steder dette problem!

God fornøjelse!