Sunday, 29 November 2009

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

Wednesday, 25 November 2009

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

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.

Sunday, 15 November 2009

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.

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.