NiXC's I.T. Take-Away

When you install an app on a Nokia phone these days it won't install unless it's been signed with a trusted certificate. Problem is you have to pay to get a certificate you can use to allow anyone to install software. That's why you get a lot of free software for Nokias at the moment that you just can't install because they haven't been signed.

So how do we install the software?! The only easy solution is to get a certificate that only works on your phone, and is locked to your phone's IMEI number. The easiest way to do this is to use a free site in China that will give you the bits you need.

1. Go to http://cer.opda.cn/en
2. Click register at the top right
3. Fill in the details and register
4. Once you've registered click the "My Certificate" link at the top and log in
5. Now click the orange "Apply cer" button near the top right
6. Fill in the details, the only bit that matters in this page is your IMEA number (get it using *#06# on your mobile), the rest of the fields are to help you identify your certificate
7. After clicking the button you'll go to the My Certificate page where you certificates get listed. It'll show your newly applied for certificate and that it's in the 'apply' stage
8. Now go down the shops or play your favourite computer game and wait a few hours. It took about 3 hours for my first one to get approved. Perhaps they're running the system on a 486 or maybe it's a manual approval thing, either way it takes a while. I've heard it 'can' take 24 hours sometimes. So keep coming back every few hours. The site will time our after a little while so you'll need to log in again.
9. When your certificate is approved you will be able to click the "Signing" link on the certificate line that's been approved. You can then upload your .sis file that you want signed and then download a signed version.

Easy! Pity the Symbian Foundation or Nokia couldn't make it that easy.

Microsoft recently created up to date Forefront Client Security installation packages. According to KB976669 these are only available within WSUS. So at least existing installs can get the latest version of the client via WSUS. But what about newly installed clients? Why should we have to install an out of date 2007 version and then do an update just to get the latest client. I want the latest version installed right at the beginning dammit!!!

Well there's a way of finding the install files if you're prepared to crawl the WSUS SQL database.

Here are the direct links to the install files with their associated language and architecture.

fcsclientpackage language 2052 x64
fcsclientpackage language 1028 x64
fcsclientpackage language 1033 x64 English
fcsclientpackage language 1040 x64 Italian
fcsclientpackage language 3082 x64
fcsclientpackage language 1041 x64 Japanese
fcsclientpackage language 1031 x64 German
fcsclientpackage language 1042 x64
fcsclientpackage language 1036 x64 French
fcsclientpackage language 1033 x86 English
fcsclientpackage language 2052 x86
fcsclientpackage language 1028 x86
fcsclientpackage language 1041 x86 Japanese
fcsclientpackage language 1040 x86 Italian
fcsclientpackage language 3082 x86
fcsclientpackage language 1031 x86 German
fcsclientpackage language 1042 x86
fcsclientpackage language 1036 x86 French

Basically download the one/s you want and extract to a folder by using /extract
You will then have a folder with the files you should use to overwrite your FCS deployment share.

Of course it's possible these links might change, in which case you will have to crawl WSUS yourself. The secret is to query the dbo.tbFile table for a value like %fcsclientpackage% in the FileName column. Reasonably easy when you know what to look for :)

Thought I'd try out the new Adobe Flash ActiveX control for IE, and naturally I wasn't expecting a smooth installation process - this is Adobe after all - and low and behold the plug-in would not install on Windows 7 x64.

In a normal administrative user account (hint hint), and running 'as admin' the setup process will get to 100% and then gets killed by Windows with the familiar "program unresponsive" dialog. Even setting compatibility settings on the installer or running it from an administrative command line interface will produce the same results. Plus I did the install on 2 completely different machines with different anti-virus, same thing.

The answer? Enable your proper "Administrator" account, login as that and then do the install. It works perfectly. That sort of points the finger at Adobe not know how to handle UAC again. Yes it's only a beta, but that's still quite lame.
I don't doubt running the installer as the system user would probably work too :)

Recently I setup one of my work laptops to allow me to login using my fingerprint without the need for any client software other than a driver. A handy new feature built-in to Windows 7, and it works fabulously well. One finger on each hand for different things, one for admin, one for my normal user. Love it!

However I have been finding occasionally that when I switch the laptop on (usually after being in hibernation or standby) that I can't login with a fingerprint and have to resort to legacy means (typing!).

I think that this is because the "Windows Biometric Service" service has stopped. There are events notifying that it's happened but no explanation why. I made sure the service was set to automatic (it was) and I've added recovery options to the service telling it to restart if it stops. Seems that hasn't fixed it because the problem cropped up immediately afterwards when I tested it. I'm not quite sure what else to do yet...

Just thought I'd blog this in case someone else runs into it.

When you have been delegated the right to delete items from someone else's mailbox the default functionality is to have the deleted items go into your mailbox's deleted items folder instead of the owners mailbox.
This functionality can be changed with a registry key, see here: http://office.microsoft.com/en-us/outlook/HA100750921033.aspx

HOWEVER, there is a group policy introduced with Office 2007 that can alter this functionality for all users. It's located here:
"User Configuration\Policies\Administrative Templates\Microsoft Office Outlook 2007\Tools | Options...\Delegates"
The policy is called:
"Store deleted items in the owner's mailbox instead of delegate's mailbox"

The help text says it needs to be enabled to set the functionality to have deleted items remain in the owner mailbox.
Guess what, it's WRONG! Yes Microsoft have not tested it properly. It turns out if you enable the policy you enforce the default, to have deleted items go into the delegates mailbox, not the owner's mailbox.
To get this policy to work properly you must set it to DISABLED.

When disabled, a policy key is created that enforces the alternate functionality for deleting mail.
HKLM\Software\Policies\Microsoft\Office\12.0\Outlook\Options\General
DelegateWastebasketStyle = 4

Hope this helps someone else!

Microsoft are calling it the "Windows Management Framework" but in reality this is PowerShell 2.0 and it's now available for download: http://support.microsoft.com/kb/968929

If you install over the top of PowerShell 1.0 on XP the startmenu link will go but you'll be left with the documentation links. So it might be better to uninstall 1 then install 2. Not sure yet.
Part of this is the new ISE (Integrated Scripting Environment) too and it's wonderfully good. Just go start, run, then type: powershell_ise

Note: it supports only XP SP3, Server 2003 SP2, Vista SP1+, and Server 2008 SP2.
Windows 7 and Server 2008 R2 have PowerShell 2 built-in of course.