Live installer update

Following on from my post on trying to install windows live photo gallery I tried to install it again yesterday by uninstalling all of my .net frameworks and reinstalling them and then updating all of the frameworks with their respective windows patches – a process that took over an hour to complete….and the installer still doesn’t work.
It did work on the office laptop, but that doesn’t really have any pictures on it but at least I know the installer *should* work sometimes.

My thoughts and experiences with Live Installer

I downloaded the new Windows Live Installer program yesterday which provides the ability to install Messenger, writer, mail and photo gallery from one “easy to use integrated installer”. There are two downsides to this – one is that the installer is really a stub that doesn’t contain the full product – this is normally fairly annoying as it means that you can’t download the full install copy for offline (or multiple) installs – instead you have to be connected to the network each time the software is installed.

The other downside is that in my case, the installation of Photo Gallery (the only piece of software that I actually wanted from this bundle as I already have the rest) doesn’t work. Instead I get the error message “Install failed with error code 0x80240022” – a google search yesterday only came up with details for Windows Defender which didn’t help me much.  Also, for those of you who are not aware, you need to hover the mouse over the error message in order for the full message to be displayed on screen in a tool tip. This means that there is no copy/paste functionality of the error message into google – instead you have to type it in manually. The link to “More about this error” only goes to a generic web page which tells you about the mouse tip.

image

The software also keeps checking the toolbar each time it is run – even though I don’t want it to be installed but oddly enough doesn’t check the Family Safety checkbox. It should be consistent to check both or leave both unchecked.

Symantec product activation down

I had the good fortune to get through to Symantec support in under a minute this afternoon – probably because there tech’s can’t actually do much as their licensing portal is down. For some reason the system doesn’t actually bother to tell you this, even after you spend ages filling in all the details they need and hitting the final submit button. It would be nice if they put a notice at the login screen to say that the server is down, don’t bother wasting 30 minutes to get a serial number so that you can install the product you’ve purchased and use it!
Grrrrr

Vista and SBS2003 (in)compatability

One (new) client has unfortunately a Vista desktop purchased a couple of days before we took over IT and it needed joining to the domain. This has proved a difficult task to say the least. Our remote control software stops showing the users screen whenever the UAC prompt pops up (and freezes our screen until the local user clicks ok) which means the end user has to remain at their desk when we are doing any troubleshooting rather than letting them use another computer to do some work.
Anyway, the server/connectcomputer wizard was complaining that I needed admin rights (which I had already) and a patch is available, KB926505 but when I try to install that on the server I get the very wonderful error message “Failed to install” with no details as to why. Nothing in the eventlogs either. Add/Remove Programs now says the patch is installed and when you try to remove it, I get a message about all sorts of programs failing to work and the end of the world so I’ve left it in place until I get a chance to remove and reinstall the server whilst I am on site as opposed to RWW’ing into the server. In the meantime I joined the computer to the domain manually, and I’ve had to change the logon script so it doesn’t UAC whenever the script does the sbs setup program. Apparently this is fixed with the patch, so the patch obviously doesn’t work – watch this space.

120 eval of WHS to be available

I’m really glad to see that a 120 day evaluation of Windows Home Server will be available as per the WHS blog. This is great news as I love the product but the bugs in the beta would stop me buying the released product unless I know they work. I need a backup interface that actually works (after all the main point of whs is backing up pc’s) and I was very reluctant to purchase the product without knowing it would work first.
I’m also considering tying this into a vpn with my in-laws computer to see if I can back up their computer to my whs server so that they have off site storage but that will need extra disk space as I’m almost full already.

Peer is not authorized to use remote address and Cyberguard firewalls

One of my customers has a cyberguard firewall that was working perfectly when I configured it in the office. However on shipping it to the customer, it was placed behind a horrible Verizon modem that broke most of the configuration parameters I had put in place. Most of them were fixable straight away, but I’ve never been able to get it to vpn back to the head office. I was getting the error message “Peer is not authorized to use remote address” in the log files.
Various responses in google mentioned I had to add noauth to the /etc/ppp file but this file doesn’t exist on the cyberguard unit. However, using the Advanced section and editing the “pptp.connect to office” file, adding “noauth” (without quotes) to the end of the file, the vpn connection worked.
This isn’t documented anywhere in google that I’ve seen so hopefully this will help someone else.

Event ID 5050 in Source (IAS ) cannot be found

Finally found a solution/explanation to the Event ID 5050, Source IAS that reads “The description for Event ID ( 5050 ) in source ( IAS ) cannot be found. Apparently this is A LDAP connection with domain controller <domain controller name> for domain <domain name> is established. and therefore nothing to worry about. It’s taken ages to track this down – I wasn’t able to find it on eventid for quite a while, but this morning it was there.