FOG (Free Opensource Ghost) Multicast problem

I managed to get FOG up and running on everything bar multicast - I thought it might be something to do with VirtualBox until I dicovered a configuration gotcha.

If you set a MYSQL password, the installation instructions tell you to change the password in /var/www/fog/commons/config.php.

What I got was the following error message in /opt/fog/log/multicast.log:

Failed to connect to database, will try again in next iteration.

After trying mysql -u root -p to debug the password and altering the connection_timeout to 5000 as suggested elsewhere, I finally found the fix here:

http://community.spiceworks.com/how_to/show/373

Turns out I had to edit the file here as well:

/opt/fog/service/etc/config.php

Having done this, I was able to run a multicast session great!

Ubuntu boot error in VirtualBox - piix4_smbus 0000.00.07.0: SMBus base address uninitialized - upgrade bios or use force_addr=0xaddr

Been having an annoyance with Ubuntu and other Linux distro's running in VirtualBox for while. It didn't seem to have an impact on functionality, but it possibly had an impact on speed of boot.

I managed to find the answer here:
http://finster.co.uk/2010/11/16/virtualbox-piix4_smbus-error/

Essentially, you do the following:

• Start a terminal 
• sudo vi /etc/modprobe.d/blacklist.conf 
• Add the line blacklist i2c_piix4 to the end of the file and save 
• sudo update-initramfs -u -k all 

You might want to optionally remove unneeded kernal images before updating the initramfs to cut down on how long that part takes.

Unable to add search provider to IE8

This has been bothering me for a while on my server, and only just had some time to do something about it.

 I found the answer here:
http://www.google.com/support/forum/p/Web%20Search/thread?tid=4d9cc69c2ac5abd3&hl=en

The contents of the registry entry:
HKEY_CLASSES_ROOT \ TypeLib \ {EAB22AC0-30C1-11CF-A7EB-0000C05BAE0B} \ 1.1 \ 0 \ win32

Was set to:
C:\WINDOWS\system32\shdocvw.dll

Instead of:
C:\WINDOWS\system32\ieframe.dll

Windows Live Messenger 2011 - 0x80048820 Logon Failure

I don't use Windows Live Messenger much, but after the install of the recent IE9 RC, I noticed that the darn thing wouldn't sign in properly.

I did the usual Google-Fu and tried stuff ranging from deleting cached contacts folders, repairing the install, removing and reinstalling, checking IE proxy settings to re-registering various DLL's all without luck.

I then tried logging (under Options > Connection > Logging) and got the following:

1aec            Messenger:              Zone_Voice (voicevideoplatformlogon.cpp:66): ERROR: [OnLogonResult called with an failure hrLogon] "" failed with 0x80048820 in .
1aec            Messenger:         Zone_LogonState CUIManager::OnLogonResult hr=[0x80048820] m_dwUILogonFlags=[2]
1aec            Messenger:                 Zone_UI CUIManager::OnLogonResult@0270CEC8: enter
1aec            Messenger:         Zone_LogonState CSignInUIController::OnLogonError> hrError=[0x80048820]
1aec            Messenger:         Zone_LogonState CLogonErrorHandler::DisplayLogonErrorDialog> hrError=[0x80048820] s_fDisplayingLogonError=[0]

I did a bit of network tracing, and found that messenger was trying to use my work proxy. Strange for several reasons:

• I wasn't connected to my work VPN
• I didn't have any proxy settings in IE9
• Work blocks messenger, so it could never have worked like that

After a little more head scratching, I remembered using the "netsh winhttp" commands to set a proxy to try and fix some VPN proxy issues we had, and when I checked, I could still see the winhttp proxy settings set.

Entering the following command cleared the proxy, and allowed messenger to run:

• netsh winhttp reset proxy

IE9 Beta Crashes on every page with Intel Express 4 Chipset Graphics

I have a Dell Lattitude E5400 running Windows 7 x64 and decided to try the IE9 beta that has just been released. Unfortuneatly, the browser crashed on every page load. After some investigation I found it was caused by my graphics driver. The E5400 uses the Intel GMA graphics driver from the Express 4 chipset.

Problem driver version was 8.15.10.2141.

Working driver version is 8.15.10.2202.

You can get the new driver here:
http://downloadcenter.intel.com/download.aspx?url=/19336/a08/Win7Vista_64_151711.exe&DwnldId=19336&lang=eng 

Connnect bug is here:
https://connect.microsoft.com/IE/feedback/details/599630/running-internet-explorer-9-with-gpu-accelleration-crashes-the-browser

Exchange 2007 Backup Woes

We use Exchange 2007 and backup using CommVault Simpana 8.0. We had an issue with a store that ran out of disk space, and then dismounted. The store logs were moved to another drive and the store mounted again. From this point on, backups (full or incremental) failed with CommVault with the following error:
Error Code: [28:163] Description: The Exchange server returned the following error message: [0x50d] - [Unknown]. Api: [HrESEBackupSetup()], Item: [Fourth Storage Group]

NTBackup could backup the store but took 20 hours compared to ComMVaults just over 2.

Investigating the event log produced an event id 9840 with error 1293:
An attempt to prepare the storage group 'Fourth Storage Group' for backup failed because the storage group is already in the process of being backed up. The error code is 1293. (Note that if a backup was recently aborted, then it may take several minutes for the system to detect the aborted backup and initiate backup cleanup procedures, so this message may be generated if an attempt was made to backup a storage group before a previous backup attempt had fully terminated.)

Turns out, the store filled during a backup leaving the backup in progress flag set. NTBackup works because it uses the old Exchange backup API's, not the VSS backup used by CommVault.

The fix was to dismount and then mount the affected store. 

Ubuntu x64 10.04 - Inital issues

Decided to upgrade to Ubuntu 10.04 using an in place upgrade - This failed horribly. There were several errors to do with likewise-open (my laptop belongs in a Windows AD domain). The final one told me that it had left my distro in an unusable state (some 3 hours into the upgrade).

I took the opportunity to reinstall the x64 version of 10.04 but ran into a few issues.

1. The Citrix ICA client install is complicated somewhat by the x64 architecture. The ICA client assumes you're running an x86 environment with 32 libs and a 32bit browser. It's fairly easy to work round - See the previous post.

2. The Cisco VPN client is a bit flakey. I can connect fine from the command line using vpnc, but the Gnome GUI hardly ever works. Sometimes it asks me for the password, only to fail the connection. Sometimes it doesn't ask me anyhting, just tells me the connection has failed. Sometimes it does nothing at all. I would prefer to use the GUI because you get a nice visual app showing if you're connected to the VPN or not.

Citrix Receiver on Ubuntu 9.10 x86

1. Install libmotif3
sudo apt-get install libmotif3

2. Create libXm.so.4 as needed by the Citrix receiver
cd /usr/lib
ln -s libXm.so.3.0.2 libXm.so.4

3. Download the Citrix receiver as a TGZ file from www.citrix.com

4. Extract this to a tmp directory and install
cd ~/Downloads
mkdir /tmp/citrix
cp linuxx86-11.100.158406.tar.gz /tmp/citrix/
cd /tmp/citrix
tar xvf  linuxx86-11.100.158406.tar.gz
sudo ./setupwfc

5. Follow the prompts - This is quite straight forward

6. Stop the EULA showing (As a blank dialog box)
 touch ~/.ICAClient/.eula_accepted

This now allows me to run Citrix apps through the web interface using Firefox.

Things still to fix:
Fix ugly Citrix GUI font
Authenticate to Xenapp View
Run access in Chrome

Changes for x64:
I had to download libmotif3 manually and copy stuff into lib32
This post helped a lot:
http://ubuntuforums.org/showthread.php?t=333534

Get Device Manager to show non-present devices as hidden devices

Start a command prompt and set the following variable:

set devmgr_show_nonpresent_devices=1

Start Device manager from the command line:

devmgmt.msc

On the view menu, click Show hidden devices.
More info here:

http://support.microsoft.com/kb/315539

Error installing Dell OpenManage Server Administrator 6.1.0

First I had an error saying Windows Remote Management wasn't installed. I got it here:

http://www.microsoft.com/downloads/details.aspx?FamilyID=845289ca-16cc-4c73-8934-dd46b5ed1d33&DisplayLang=en

Second problem was this error:

"The installer has detected that HTTPs Listener is not enabled for Windows Remote Management. Enable HTTPs Listener for Windows Remote Management to use Standards Remote Management capabilities. See "Remote Enablement Requirements" section in the Installation and Security User's Guide for detailed information. Note: Remote Enablement is applicable only for systems that support Server Instrumentation."

This led to this post:

http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx

The fix was to run:

winrm quickconfig

This enabled an HTTP listener, but not an HTTPS one. Re-reading the above url, this worked:

winrm quickconfig -transport:https

ActiveSync - Guest only

To force an ActiveSync to allow guest only access (therefore with no prompts) carry out the following registry edits:

HKLM \ SOFTWARE \ Microsoft\Windows CE Services

Add a new DWORD Value called ‘GuestOnly’ with a value of ‘1’

Blog off the air - Oops!

My blog has been off the air for a while. I moved the blog to a new server and recreated the domain.

Turns out the account used to run the blog needed modify access to C:\Windows\Temp - Looks ok for now!

Transistion to Cloud Servers

I'm moving all my locally hosted content to cloud based servers. So far I have moved my email to Google Apps For Your Domain and I have created a new blog (no content yet) to replace this one.

The Gmail move went pretty well as all I had to do was update MX, SPF and some CNAME records. The only non-working part was the start page as Google seem to have dropped support for this. I had actually setup apps before this limitation was implied, and I can activate the start page but it just doesn't work. There are others who mention this and the work-round seems just to use a Google Sites page if you want this. In fact there's quite a complete template for sites, just for this. I don't really need it anyways.

The blog will move slower. I have moved it off to a smaller sevrer for now and I'm trying to find a way to export the posts from CommunityServer to Blogger. I may just have to use the smaller server to setup redirects to the new blog.

Latest hotfix for DPM 2007

I think I explained earlier that my DPM 2007 product does not get updated by Microsoft update.

I tried reseting Windows Update components, but that didn't help:

http://support.microsoft.com/kb/971058

I've discovered I'm a little bit behind on hot fixes, and that Microsoft have released KB976542 on October 23rd 2009.

This seems to include all the hotfixes posted since DPM 2007 SP1:

• KB961502
• KB963102
• KB968579
• KB970867
• KB970868

Still, looks like DPM 2010 will soon be here.

Wireshark on Snow Leopard

Nasty startup problem solved thanks to Nick Klienschmidt.

Run:

cd /Library/StartupItems

sudo chown -R root:wheel ChmodBPF 

http://kleinsch.com/2009/10/03/wireshark-chmodbpf-errors-on-snow-leopard/

Belkin N1 Expresscard with DLink DIR-615

I was supplied with a DLink DIR-615 router as part of my Virgin Media package. Tried connecting my personal laptop using a Belkin N1 Express card (F5D8071), but it just wasn't happy. This same card would connect with a Belkin Vision N1 quite happily (surprise, surprise).

Anyway, I downloaded the Vista drivers and they worked fine. Find them here:
http://en-us-support.belkin.com/app/answers/detail/a_id/468

My card was the 3000 version.

Creating a dynamic distribution group with advanced filtering on Exchange 2007

In Exchange 2003, it was very easy to build a dynamic distribution group with the GUI. Exchange 2007 is much more limited unless you use Powershell. I needed to create a dynamic distribution group targeting a particular server, as long as the user mailboxes didn't have a forwarding address. The reason for wanting to avoid the mailboxes with forwarding addresses is we still have Quest's Exchange Migration Wizard creating forwarding details for users on the legacy Exchange system.

The process is a two part process:

• Create the dynamic distribution group
• Set the filter criteria for the distribution group

To create the dynamic user, type the following all on one line in the Exchange Powershell console (don't type in the bold italic comments):

New-DynamicDistributionGroup 'The applett

-Name "Group name" 'What the group should be called

-IncludedRecipients MailboxUsers 'Just include users with mailboxes

-OrganizationalUnit "domain.com/ou1/ou2" 'Where to create the dynamic distribution group
e.g. New-DynamicDistributionGroup -Name "Group name" -IncludedRecipients MailboxUsers -OrganizationalUnit "domain.com/ou1/ou2"

To set the filter:

Set-DynamicDistributionGroup 'The applett

"Group Name" 'What the group is called

-Notes "Blah blah blah" 'Description

-RecipientFilter {ServerName -eq 'ServerX' -and ForwardingAddress -eq $Null} 'Mailbox exists on ServerX and the forwarding address is empty

-RecipientContainer "domain.com/ou1/ou2" 'What container the recipients are under - It can just be the domain

e.g. Set-DynamicDistributionGroup "Group Name" -Notes "Blah blah blah" -RecipientFilter {ServerName -eq 'ServerX' -and ForwardingAddress -eq $Null} -RecipientContainer "domain.com/ou1/ou2"

Once set with Powershell, they can be viewed by the GUI, but not changed. Beware that the preview button does not take account of the -RecipientContainer parameter - It will show you all users in the domain that match.

Inspiration from:

http://technet.microsoft.com/en-us/library/bb123796.aspx

http://technet.microsoft.com/en-us/library/bb738157.aspx

DanW

Windows 7 on an HP DV9000 (DV9292EU)

I've been having a bit of an install fest this weekend with Windows 7 Ultimate on my HP DV9292EU, Windows 7 Enterprise on my Work laptop and Android (!) on my trusty ASUS eeePC 701. All went fine except the HP laptop which had three unknown devices in device manager after the install.

One was labeled as a co-processor. I don't know what it was, but downloading the NVidia Nforce 430 drivers from here solved it:
http://www.nvidia.co.uk/Download/index.aspx?lang=en-uk

Select Legacy, NForce 4 and then one of the 430 drivers. It downloaded this file which worked for me:
15.49_nforce_winvista_win7_32bit_international_whql.exe

The two other device were labeled Base System Devices and proved to be some sort of Ricoh devices.
Downloading the Windows 7 drivers from the Lenovo site fixed these for me!
http://www-307.ibm.com/pc/support/site.wss/WIN7-BETA.html#rmcr

It now all looks good!

Google Wave invites

These are looking really hard to get - Any one have one?
Please send an invite to Karl.Foley@gmail.com.

How-To Prepare A Certificate With Subject Alternative Names Using Exchange Powershell

1. Use powershell from an Exchange 2007 box to generate a certificate request (all on one line and replace italics with your details):

New-ExchangeCertificate
-GenerateRequest:$true
-Path C:\NewCert.req
-DomainName fqdn1.domain.tld,fqdn1,fqdn2.domain.tld,fqdn2
-PrivateKeyExportable:$true
-FriendlyName "fqdn1.domain.tld"
-IncludeAcceptedDomains:$False
-Force:$true
-SubjectName "CN=fqdn1.domain.tld,OU=Department,O=Organisation,L=Location,S=County,C=GB"

2. Request a certificate from your AD certificate server, (http://yourcertserver/certsrv). This needs to be an advanced request, using the request file generated above, and for a web server. Download it to your local drive as C:\CertNew.cer.

3. Import the certificate into your Exchange server using:

Import-ExchangeCertificate C:\NewCert.req

4. On the Exchange server, use the MMC certificate snap-in, export the certificate. Export it with the private key to a PFX file. Make sure you target the computer certficate store when loading the MMC. Use a password to protect the exported certificate.

5. On the target server, load the certificate MMC, again targeting the computer store and import the pfx file.

6. Using the IIS console, switch your webserver to the new certificate.

7. You can delete the original certificate from your Exchange server if you wish.