IT Knowledge

Archive for February, 2009

Problem

After installing SQL Server 2005 on your windows 2003 SP2 server you run windows update, find a whole collection of SQL related updates, including SP2 for Visual Studio. However you find that you cannot install it.

Reasons

Event ID 1008

The installation of C:\WINDOWS\Installer\473946c.msp is not permitted due to an error in software restriction policy processing. The object cannot be trusted.

Event ID 11718

Product: Microsoft Visual Studio 2005 Premier Partner Edition – ENU — Error 1718.File C:\WINDOWS\Installer\473946c.msp did not pass the digital signature check. For more information about a possible resolution for this problem, see http://go.microsoft.com/fwlink/?LinkId=73863.

Event ID 1023

Product: Microsoft Visual Studio 2005 Premier Partner Edition – ENU – Update ‘Microsoft Visual Studio 2005 Team Explorer – ENU Service Pack 1 (KB926601)’ could not be installed. Error code 1603. Additional information is available in the log file.

Solution

Install the hotfix for Windows Server 2003 KB925336.

However, for some unclear reason not all installations require this patch

Ebuild are builds that are not in portage, but very usefull to install software that is not supported by the main portage team.

Here is a short manual on how to install an ebuild.

– First create an overlay

“mkdir -p /usr/local/overlay”

– Add the following line to /etc/make.conf

“PORTDIR_OVERLAY=”/usr/local/overlay”

– Now create a catagory directory in the overlay directory

“mkdir -p /usr/local/overlay/mail-client”

(remember, this can be any catagory listed in /usr/portage/profiles/catagories)

– Now create a application directory

“mkdir -p /usr/local/overlay/mail-client/evolution-brutus”

– place the ebuild file(s) in the application directory and run the following

“ebuild <name>.ebuild digest”

that’s it. Now you can run emerge -va <application> and build it.

I’ve found that most applications are still blocked, so the file /etc/portage/package.keywords and add the following line :
“mail-client/evolution-brutus     ~amd64″

(replace ~amd64 with ~x86 if required)

ever had the issue that you need to clean up the mailboxes but keep the accounts alive because of forwards or stuff like that. In exchange 2003 it was a hell of a job, logging in to the users mailbox, clean everything up and leaving it at that. But now, in exchange 2007 you have powershell, which makes this a whole lot easier. Just move the group of users to an organizational unit and run :

get-mailbox -OrganizationalUnit “<unitname>” | export-mailbox -PSTFolderPath <path> -DeleteContent

This will give you an amount of PST files with the original content of the mailboxes and then clean them out without deleting the mailbox itself.