IT Dribble

Using this website PCI Database.
Just enter the Vendor or Device ID and boom thats the unknown hardware device!

Currently I am entrusted with developing a Windows 7 Professional Image for deployment and have until recently been stuck with getting the default user profile to ‘keep’ pinned start menu items.

While I was copying them to C:\Users\USERNAME\AppData\Roaming\Microsoft\Internet Explorer\Quick Launch\User Pinned\StartMenu they still wouldn’t show up. There is actually a complementary Registry key which makes the magic happen. So without further ado: How to set Pinned Start Menu Items for Default Profile in Windows 7 (more…)

Upon Sysprep-ing our first test image of Windows 7 using an unattend.xml our WDS enviroment would produce the error ‘Windows could not apply unattended settings during pass (null).’ At first I thought my unattend.xml file was wrong BUT the actual problem was that WDS was using a Windows Vista Image for the Image Deployment. The required fix was copy boot.wim from the Windows 7 DVD\Sources directory and add that to the ‘Boot Images’ within WDS. After that you PXE boot as per normal and select your newly appointed image!

This post was inspired by this blog post

After a colleague of mine installed WDS at a client site they found that certain laptops and desktop PCs would not be able to pick up the images that have been captured.

The problem lies in the HAL Type of the PC that was captured and then WDS finds the HAL type for the PC asking for an image and if one doesn’t match then you will most probably get the error: “There are no images available”

My scenario was that we had a generic image built and working for Single CPU and MultiCPU PCs but only the Multiple / Newer PCs could see the image in WDS – that is because the HAL type was “Advanced Configuration and power interface (ACPI) PC” but these older PCs were being recognised as Uniprocessor HAL Types.

The solution: Get the image onto the Older PC type (via Ghost or Clonezilla etc) login to the system. Download DevCon and extract into C:\Windows or any other %PATH% variable you like.
Then run:
devcon sethwid @ROOT\ACPI_HAL\0000 := +acpiapic_up !acpiapic_mp
devcon update c:\windows\inf\hal.inf acpiapic_up

Reboot and Login two times then Sysprep and capture again!

Hopefully your good to go!

Reference: http://www.ngohq.com/processors/11891-how-to-update-the-hal-without-reinstalling-windows.html

Keywords: WDS, Force HALs, Force HAL, Windows Deployment Services, WDS, ACPI Multiprocessor PC, acpiapic_up, acpiapic_mp, No Images after Capture, Change HAL Type

Can’t open this item. The text formatting command is not available – Outlook. This error was received when trying to open an Outlook item. Also it seems that Internet Explorer 7 (IE7) couldn’t render a page and it would just be blank. After trying to remove profiles and repair office etc I traced the fault to a recent Windows update KB978207 for IE to be exact. After removing the update and rebooted everything worked again!

I came across a Windows 7 Skins for KDE – It looked really….exact but the install script was crap it installed a new user and was only Kubuntu based and was pretty brutal at overwriting stuff so I (more…)

Seems I’m in fix it mode tonight – amazing what you get done when you don’t have women distracting you!
Anyway it seems that my fail2ban has been broken for quite a while, the resolution of this was me running:
fail2ban-client -x start and that worked ok

So I modified /usr/sbin/rcfail2ban and added the line:
[ -e $FAIL2BAN_SOCKET ] && rm $FAIL2BAN_SOCKET;

Here it is in context:

case "$1" in
start)
echo -n "Starting Fail2Ban "
[ -e $FAIL2BAN_SOCKET ] && rm $FAIL2BAN_SOCKET;
/sbin/startproc $FAIL2BAN_BIN start &>/dev/null
rc_status -v

Well you get the drift. Happy Banning!

I have been pulling my hair out trying to resolve a backup issue with a client’s backup on Veritas BackupExec 9.1. What happened was that backup was failing on 1 message because the antivirus couldn’t scan it, and locked the backup from reading it.

BackupExecs error was:
0xa0008488 - Access is denied
Backup - \\SERVER\Microsoft Exchange Mailboxes
Access denied to file FirstName LastName [user]FW: Your Tracking # 835503826372.

Now this particular message was found in the Inbox, I then deleted it and emptied the Deleted Items.
Backup still failed! But this time the message was it the root_store IE. The top level of the Mailbox and I couldn’t see it with OWA Client etc. I had to pass it on to another engineer who started looking at it, who then gave me the right tact to search.

I deleted the message by using a Microsoft tool called MDB Viewer, this is a low level tool for Mailboxes,  It’s on the exchange CD-ROM CD-ROM_Drive\Server\Support\Utils\I386\Mdbvu32.exe

I then basically (Remember I don’t do Step by Steps, I do summarys) Choose the Server, Choose the Mailbox (username), then clicked  OpenMessageStore on the MDB menu,
Click Open Root Folder on the MDB menu
From there I saw the message in Messages in Folder Column, I selected it, Choose the operation IpFld->DeleteMessage() and called the function!

Woo Hoo Backup now works!

Merry Christmas to me and you!

So I was back the stupid clients that had the crappy mdaemon / IMAP setup. This time upgrading there MS Office version to 2003 in an effort to stop the IMAP pst file hitting the 2GB limit. Anyway after pulling my hair out to get it to use the 2003 UNICODE PST type store I came across this post: link

“This issue occurs if the DWORD value for the NewPSTFormat registry entry is set to 2. This condition requires Outlook to use the Unicode-based personal folders (.pst) file format. This file format is incompatible with IMAP. ” Fuck! Looks like stupid internet standards win again!

You know the worst part – The client is a lawyer and he explicitly asked me in a email if this will fix the problem, to which I replied “Yes it will”

Now I just need to find that damn message…….

Had a client whose print queue would jam up and they couldn’t restart the printer spooler until you manually cleared the spooled documents. So I stole this piece of code and put it in a batch file. Works wonders!

@echo off
net stop "print spooler"
del /q "%SystemRoot%\system32\spool\PRINTERS\*.*"
net start "print spooler"

Update: The reason the spooler was dying was because when he printed a PDF document he would close Acrobat before the document finished and in turned killed the Print Spooler. Because we charge by the hour, he didn’t want it to be investigated any further, which is fine by me!