Monday, 30 November 2009

Wireshark on Snow Leopard

Nasty startup problem solved thanks to Nick Klienschmidt.

cd /Library/StartupItems
sudo chown -R root:wheel ChmodBPF 

Sunday, 29 November 2009

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:

My card was the 3000 version.

Wednesday, 25 November 2009

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 "" 'Where to create the dynamic distribution group
e.g. New-DynamicDistributionGroup -Name "Group name" -IncludedRecipients MailboxUsers -OrganizationalUnit ""

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 "" '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 ""
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:

Sunday, 15 November 2009

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:

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

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!

It now all looks good!

Saturday, 14 November 2009

Google Wave invites

These are looking really hard to get - Any one have one?
Please send an invite to

Friday, 6 November 2009

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):

-Path C:\NewCert.req
-DomainName fqdn1.domain.tld,fqdn1,fqdn2.domain.tld,fqdn2
-FriendlyName "fqdn1.domain.tld"
-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.