Month: September 2009

Solve inconsistencies in the servicing store

Microsoft introduced a totally new servicing mechanism in Windows Vista and Windows Server 2008 which is totally component based. Sometimes information in the servicing store becomes corrupt and inconsistent. This state can cause hotfixes, service packs, security updates and other types of updates to fail.

To solve this problem you can use the System Update Readiness Tool which just have been updated to work with Windows Vista SP2 and Windows Server 2008 Sp2 (it also works for previous service pack levels).

Be aware of a problem when renaming domain controllers

If you have renamed a Windows Server 2008 or Windows Server 2008 R2 domain controller you should be aware of  a problem. The problem is that a DFSR object is not renamed to the new name. This does not cause any problems until you remove the domain controller in question and after doing a demote or cleaning it up with metadata cleanup the object will become orphaned. So if you have renamed 2008 or 2008 R2 DCs you should follow the steps in KB2001271 to fix this.

Multiple Exchange accounts in Outlook 2010

How many times have you created a new profile in Outlook for the sile purpose to try another Exchange account in your Outlook? Well, starting with Outlook 2010 you will be able to have up to three Exchange accounts in one profile in Outlook.

Speaking of Office 2010, having used the technical preview of Office 2010 for quite some time now I am really looking forward to the beta version as it will contain quite a few improvements over the technical preview. Hopefully it will be here soon!

Continuous boot-loop issue with Vista and F-Secure

A serious problem exists with Windows Vista when using F-Secure product, a problem which a lot of users experience. The problem is that when specific versions of F-Secure products are installed Windows enters a continuous boot-loop when installing Windows Update. This issue appears as

Configuring updates stage 3 of 3. 0% complete

after which the computer reboots and reboots and reboots…

The last few weeks I have seen this issue being asked almost every day in the forums over at Anyway, for the solution have a look at the F-Secure guide or take a look at the MS KB article.

Clearing the confusion regarding Libraries and indexed locations in Windows 7

Many users are frustrated to receive the below error message when trying to add network shares or mapped network drives to a Library in Windows 7.

This network location can't be included because it is not indexed.

The error message clearly state what the problem is but it is harder to find out how to solve the problem. You have two options to include the network drive or network share in a Library.

1. Make the network drive available offline by right clicking it and choose “always available offline”. If you cannot control the remote file server as suggested in solution 2 this is the option to use.

2. Make sure that Windows Search 4.0 is installed on the remote file server and make sure that the share or network drive you are adding is indexed on that server. This is the preferred method I would say.

Once either of these two solutions are in place you will be able to successfully add the network share or mapped network drive to your libraries.