Prevent Windows from Reinstalling Group Policy Programs

While Group Policy software distribution is a quick and easy way to get software around a network, it isn’t without its problems. One such problem is when a computer is attached to a new domain. If your software distribution is the same, Windows will still reinstall the MSI packages.

The simplest way is to join export a registry key from a computer that is currently joined to the new domain, and then import it into the new system.

And here it is:

<code>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\AppMgmt</code>

Getting that SQL Server 2008 to Work out of the box

I had to set up a new SQL Server database, which I haven’t done in a while as I tend to focus my efforts on mySQL. Nevertheless I needed to get grip on a new site to migrate.

After setting most things up, I managed to get to a point where the database wasn’t starting.

Microsoft OLE DB Provider for SQL Server error ‘80004005’

[DBNETLIB][ConnectionOpen (PreLoginHandshake()).]General network error. Check your network documentation.

I really love unhelpful messages. Anyway, after some head scratching I found an article on on the Microsoft Forums from a chap with a similar issue.

To fix the problem, I loaded up the SQL Server Configuration Manager, and expanded SQL Server Network Configuration. Under Protocols for MSSQLSERVER (this is the instance name of the server), I enabled TCP/IP. The error went away. Tada!

I suppose it would help to read the documentation thoroughly – but I got to where I needed to be anyway. I imagine that it makes sense to disable TCP/IP connections until you’re happy that the server is secure. Even so, I was making connections from the localhost, so I would have expected it to work.

Vista, Why You Eat my Computer?

So, Vista’s been out for a while now – some people think it’s great (usually they are selling it), some think that it’s pants.

Now, I’m not far from the front of the queue when it comes to raving about Linux. Ubuntu was the second Linux distro that I have tried, and I’ve stuck with it quite happily. In fact, things have remained pretty good from my initial post about my first experiences with Ubuntu.

On the other hand, Windows has it’s own place in the world. If you’re a person who can afford Microsoft’s astronomical licensing costs – then Microsoft can offer you some great things too.

Unfortunately, I don’t feel that Windows Vista is one of those great things.

Slug on Mogadon

The thing that strikes me whenever I use Vista is that it is so slow. Not just slow, but slooooooow. I have to use a variety of systems, and when I need to fix somebody’s laptop that is running Vista I should be putting an afternoon aside.

This isn’t entirely Microsoft’s fault. Consumer greed, business greed and the general desire to get more for less has also led to this rocky road to Hell. Computers and notebooks are generally sold cheap. Cheap means under-spec. Even up to the end of Windows XP’s golden lifespan (I’m not saying it’s past it, by the way), computer manufacturers were selling new systems with 256MB RAM. I’m sorry, but I’ve used Windows XP enough to know that as soon as you put on Service Pack 2, some anti-virus software, maybe some anti-malware package and then decide to run a few applications – time begins to speed up around you. Either that or the computer is running slowly. You decide.

Now Vista has mammoth requirements for what is essentially a core program. The minimum amount of RAM to run Vista is 512MB. That’s what I say is minimum for XP nowadays. I recommend having more than 1GB RAM installed for a pleasant Vista experience.

The problem is, noteboook manufacturers might even stump up the extra £5 to put 1GB of RAM in – but when 256MB of RAM is then being stolen by the onboard graphics so that you can see the Aero effects, things are clearly still not right.

Vista will run well on a decent, modern computer system. The problem is that Joe Public will be sold some tat from PC World by a part-time A-level student who will bestow Vista’s Flip-3D as a major selling point. Oh, it can burn DVDs as well.

Real Life

When real-life steps in, this is unsuitable for a lot of computers. Microsoft wants business to be using its latest baby, but on any existing hardware – Vista just doesn’t make the crunch.

My computer is almost 4 years old and runs Ubuntu beautifully. I have 1GB which more than meets any application requirements. In fact, this only becomes a problem when I run Windows XP in a virtual machine. Ironically, XP demands more memory running a few apps than the operating system that it is running on! And Ubuntu has a barrel more services, a 3D desktop, and (when I’m using it), about 10-15 application windows open!

Dual-boot

So I’m dual-booting into Vista at the moment. I do this when I fancy a game of Command and Conquer Generals with my brother over the internet. I often say, “I’ll just boot into Windows – give me 15 minutes.” Usually by the end of that time Windows may have finished messing around with updates, defragging, loading unneccesary services and generally being slow (on a 2.4GHz P4 with 1GB RAM), before I feel that I can get the thing to behave and run reasonably well.

I’ve been stung enough times when Vista decides that the ideal time to start defragging my hard disk drive and running an anti-spyware scan is during the middle of a game.

False Hope

When I was using the Beta versions of Vista, it was slow – but I figured that it was due to being a Beta. There was a clear effort from Redmond to meet Vista’s release date and there was a buzz. Vista naysayers were told to wait for the RTM (release to manufacturing) version. But overall, the performance wasn’t a great deal better in the RTM version.

More False Hope

Service Pack 1 was a glimmer of hope. Some performance increases and a rollup of some updates that fix what I can only describe as stupid problems that should never have been in the RTM version (such as having to Activate Windows after it has already been activated).

I thought I’d give this a try on my system. Guess what? It didn’t install. I wasn’t surprised. The update need prerequisites installed, and othr bits and bobs. I’d already had difficulty getting these installed on other computers, so I have a grave thought that it would mess up my system.

It didn’t install – but at least it didn’t wreck my system. Microsoft’s answer is to just keep trying until it works. Umm, I don’t have hours to piss away waiting for my work computer to continuously fail to install an update that takes around an hour to work out if it wants to install or now.

So, I gave up after attempt 3 or 4. I tried installing manually from the downloads. It’s not right. Vista feels inherently broken.

Time to Upgrade

So it’s time to upgrade to XP. It’s a joke I’ve seen floating around the internet for a while now, but it’s exactly how I’m feeling. I’m going to dual-boot into XP for playing games. It can run fast, and doesn’t have some of the hardware quirks that I’m still experiencing with Vista.

Over time, my disappointment with Vista has settled. It’s OK – but it’s extremely lacking in key areas. And these key areas tip the boat for me.

I’m just thankful that I run a Linux O/S as my main home operating system. I know it’s stable. I know it will behave itself most of the time. It’s still frustrating to use occasionally, but these times of frustration occur much less than when I use Vista.

Virtual Desktop for Windows XP and Vista

Yes, it’s true!

Windows Vista may actually start making use of the 3D effects enjoyed by other operating systems for so long now.

Most notably, the virtual desktop has been toyed around with before in Windows, but it never seems to be executed well. So it seems fitting that there’s a Vista / XP Virtual Desktop Manager open-source project on codeplex. The current version is 0.5, which is a release candidate.

The desktop manager itself works, but isn’t fantastic. It’s still a little buggy and as such, the live updating doesn’t seem to work exactly as advertised. What is more appealing is that the next version is showing promising signs that it may include an Exposé-like feature for task switching. If this can replace or be added onto the rather lame Flip-3D feauture, then that’s even better.

Whatever next? Fast file access in Vista?

Open docx files in OpenOffice on Ubuntu

I’ve been using Office 2007 quite happily for some time now. But the niggles are starting to hit me.

One of the main issues is the new .docx format not being supported across the board yet. And with me being a sucker for all things new, I have to make a point of saving an alternate version to open in OpenOffice.

Until now.

I found this little nugget on the Ubuntu forums to install the Novell converter in Ubuntu:

1) Download the file odf-converter-1.0.0-5.i586.rpm from http://download.novell.com/SummaryFree.jsp?buildid=ESrjfdE4U58~

2) Use alien to convert it to a Slackware tgz file

<code>alien -ct odf-converter-1.0.0-5.i586.rpm</code>

3) Unpack the slackware tgz file

<code>tar xzf odf-converter-1.0.0.tgz</code>

4) Copy three files into your OpenOffice.org directories — note that the usr that you’re copying from is a directory that was inside the tgz file (3 lines here)

<code>sudo cp usr/lib/ooo-2.0/program/OdfConverter /usr/lib/openoffice/program/</code>
<code>sudo cp usr/lib/ooo-2.0/share/registry/modules/org/openoffice/TypeDetection/Filter/MOOXFilter_cpp.xcu /usr/lib/openoffice/share/registry/modules/org/openoffice/TypeDetection/Filter/</code>
<code>sudo cp usr/lib/ooo-2.0/share/registry/modules/org/openoffice/TypeDetection/Types/MOOXTypeDetection.xcu /usr/lib/openoffice/share/registry/modules/org/openoffice/TypeDetection/Types/</code>

Once I restarted OpenOffice, I found that it could import basic docx files quite happily.

This worked nicely for me in Feisty Fawn – although it’s a good idea to make sure that OpenOffice is up-to-date.

Office 2007 Deployment Computer Startup Scripts

Now that MS Office 2007 is doing the rounds, I suppose it’s time to lookat some of its shortcomings.

It has a few when it comes to deployment. The biggest nuisance being deployment.

You have four options:

  • Install it on a PC manually (not great)
  • Deploy through group policy with no customisations
  • Use a deployment system such as SMS
  • Use a computer startup script

You may as well just say “no” to the first one. Anything more than a handful of PCs and you have a tedious task.

Group Policy has always been my method of choice. Most of my clients have less than 100 PCs, so Group Policy deployment is ideal. But as pointed out in the list, you cannot customise the installation with any defaults.

SMS is out. It’s not worth explaining to clients why it’s a good idea to buy software that makes my life easier. Even though the effort and management might simplify things somewhat.

So we’re stuck with computer startup scripts. Another method I hate – but if you want to control Office Deployments, then this is the way to do it. Thankfully, Aaron Parker has posted some startup scripts to help with this using the MSP method.

If you are using a network with WSUS, then updates become a non-issue, and I think that the only time to need to redeploy is if you decide to change the application packages that you want. At which point, you could check that executables of the programs exist or record your own registry entries that you can check for.

It’s not a great method (I’ve managed to avoid having to use ANY computer startup scripts in 2000-based networks) – but there’s no reason why it shouldn’t work. Especially if you make sure to use the quiet options in the Setup /admin tool.

Office, eh?