So I got the HP Update first. I read on the MS Team blog that PP1 was included, but it isn't. So I manually downloaded PP1 and when I try to install (execute) it, I get a message saying Windows either can't access it or I don;t have appropriate permission.

Huh?

I'm RDC'd into the Server as Administrator. How can I not have permission?

Anyone?

EX475

Everything went well. Everything works well, except McAfee. It seems to slow down the MSS. Any info on this that can be shared?

I've been running mcafee for a couple weeks with that addin. I haven't noticed any different, but I'm running 2GB ram. If you have the stock 512MB, you're messing up. You'll need to atleast double it. Installing any program except what comes stock will cause memory slowdowns. Stock, it takes up almost 100% of it's memory.

Welcome to my world... The HP AutoUpdater client has to be THE worst bit of software ever written IMHO.

It looks like you need the installer package (I mentioned it above) just like I do so that you can install the update manually. Now if we can only get HP (or some other kind sole) to offer it as a direct download for all of us who have trashed AutoUpdate clients on our MSS's we'll be in good shape.

Well, back from dinner and still no magic. I did however find a solution to the failed install problem over at www.mediasmartserver.net. By following the manual download and install instructions here, http://www.mediasmartserver.net/forums/viewtopic.php?t=1763, I was able to  simply download and install the update via Remote Desktop. Everything seemed to work fine - no reboot even required!

Now it is off to explore the add-ins.

Kurtis

Well, I'm up and running now. A very kind sole provided the v1.3 server-side update EXE file for me and all is well in MSS land once again. In fact, my server-side AutoUpdate client appears to be finally working again. That in itself makes the upgrade worth its weight in gold in my book.

Also, with the old v1.2 server-side update installed, I wasn't able to install any add-ins onto my MSS box (kept getting a 1608 error). Now that's fixed as well in the v1.3 update.

So far, I'll give HP two thumbs up for the v1.3 update.

Having got over the false start with HP V1.3 - now sorted, I installed PP1 and that has also gone in OK (or looks OK so far).

Connector updated all four machines in turn once they were logged into the console.

The only problem I found was the Microsfot installation instructions for PP1 telling users to copy the PP1 exe into the Software folder and running it from there.  That doesn't work and gives a warning about insufficient privileges.  Copying it to the MSS server's desktop and then running it worked like a charm. 

Here's a copy of what I posted to the microsoft WHS dashboard, though to be honest there wasn't a clear "bug" section so who knows if they will get it. But I pass on the info to y'all:

First off, with the original beta, all those ugly "disc is gone" and "data conflict" messages disappeared. Now, after "upgrading" to the RTM/RFTW (anyone get that 80's joke?)

they'rrrrrre baaaaaaack! That really rubs my rhubarb wrong...

Here's the rest of the experience, hope it helps you avoid pitfalls...

My email to the "bug" console at microsoft:

The email sent out by you, to tell me (during the week of 7/21) that the beta has evolved to RTM status was full of some very critical errors. I have no faith in your ability to code if you cannot refer to a file correctly in an email!

1) The links and text refer to KB944298 and KB944289 (we're supposed to delete "98" and install "89" which doesn't make sense).

2) That doesn't matter since if you click the link provided (the "89" link) you get a file which may already have been downloaded. Your email fails to mention that your WHS may have already uploaded the file for you (which mine had)-- this adds even more confusion to this process. Now I'm very aggravated at this point. You guys really need to PROOFREAD and follow the directions you give in your emails to make sure they are right!

3) On top of that, clicking on the file you provide attempts to install the "PRE-RELEASE" version... which is what we just uninstalled!

4) I had to manually fish around the MS downloads to find the correct PP1 RTM file-- I checked the filesize to verify it was indeed a different executable-- with the SAME NAME-- this was very confusing but it did not announce itself as the "pre release" version so I kept going. When it was installed the connector software went haywire.

4.5) Connector messages tell you that it doesn't work, and to try updating, and that it can't update... yada yada yada (that's technical speak for it doesn't matter, see below)

5) You should recommend that connector will do this for a while, and spit out many error messages. I was going to get back to them, but during the course of writing this, it corrected itself and has apparently upgraded connector.

6) Another network computer was showing the same connector messages during this entire process, but after checking it, I see that it corrected itself since I gave it time.

7) All in all, when you provide these instructions, please have someone who is both computer literate and also NOT part of the technical team write them. They are very difficult and not clearly written--- and I am a senior IT engineer! Please give your secretary a WHS and have her or him write the instructions on how to install these pre-releases, after they try the process! It will make things on your beta testers much easier...

Served said: Here's something to watch out for if you have your own domain for your MSS (or possibly other home servers, but who would want that?)... After installing the HP update and PP1, the security certificate for my website was corrupted / deleted (hard to tell what happened to it). I attempted to check my site after the installs and I received a msg that the domain had an invalid security certificate. Solution: re-apply your current cert just like the first application. Problem solved!

Recently installed PP1 without a problem except now when connecting remotely to webshare the message "There is a problem with this wesites security certificate. etc etc" always appears.  Under "Certificate error" it says "mismatched address."  I tried "reconfiguring" TZO from the console but that didn't do anything.  Would appreciate some basic advice on how to resolve this issue.  Thanks