It turns out that you cannot patch network installation points directly.

Not surprising really. Why should Microsoft make software deployment manageable out-of-the-box?

Nevertheless, I found a useful article at WinnetMag.com.

You can patch the network installation point directly, by using the following command:
msiexec /a < original .msi and localtion > /p < .msp file and location >.

However, you then need to redeploy the application afterwards. This can be done from within group policy.

So, here we are!

Windows XP has shocked me by developing an unexpected ‘feature’.

As I was in a bid to design a pretty backdrop – I thought I’d save a 4 pixel image and save it as a bitmap. When previewing it as a Windows backdrop – I forgot to set the bitmap to tile instead of stretch. What I expected to happen was that some nasty pixilated blocks would appear on the screen.

But no! Instead a pretty gradient graced my monitor.

Obviously there’s limits to what kinds of gradients you can have – but it’s nice that it happens nevertheless.

Having been involved in a few Windows XP/2003 suite installations now – there seems to be a reoccurring problem with people and their USB devices.

Simply put – if you’re not an admin user of any sort, then the machine will not allow you to add or remove USB devices.

As a security issue, this is fine – especially when you don’t want people faffing around with your systems on a corporate level. In a school where you’ve just installed 30 computers – half of which don’t have floppy or CD drives in – USB is quite desired.

I finally got around to carrying out a serch on the web and found someone mention KB 823732. A jolly helpful article on how to disable a users ability to remove the said privilege. I haven’t tried it yet – but I imagine that the opposite is true to allow users. I’ll put up an additional note if it works.

I noticed that some files were disappearing on one of the Servers the other day. A few people had noticed. And it finally happened to me. I was roaming through my ‘My Documents’ folder when I noticed that folders that shouldn’t be empty were.

Checking out the KnowledgeBase, I discovered that if your profile folder is the same as your home directory, then the server sometimes decides that the best thing to do is delete the files.

Although it turns out that if you use a subfolder in the home folder this resolves the problem.

I certainly hope so. I don’t think too many people will be impressed with files randomly disappearing…

I’ve been having problems with the Tally 8006e and 8024 running on Windows Server 2003. On a couple of systems I’ve found that the drivers seem to knock out the Windows spool. Whenever it tries to print, an error message pops up saying Unable to create print job.

The fact that it doesn’t even seem to try was quite frustrating. Luckily I was fixing another problem on one particular server and needed to reboot. On startup I had a more useful message Spooler subsystem app has encountered a problem and needs to close. I should have really checked the system log, but this problem had been around for such a long time, I wasn’t sure if it would actually still be there.

So it was with some fortune that I managed to find this new message on the KB article 810894.
Follow the instructions and it will remove the printer drivers and allow you to add new printers afresh.

An odd problem popped up today. Every time I attempted to save or open a file in my network area, I’d get the following error:

Invalid Page Fault in module Kernel32.dll

It turns out that it’s because I have a folder called ‘My Documents’ in the My Documents folder. Every time I clicked on it, Word 2000 would throw its toys out of the pram and crash and burn, taking my work with it.

The solution was found on in KB304504. Apparently it only affects Office 2000 thankfully.

Needless to say, my punning has pleased me no end today