Done. Whoo-hoo. I’m stoked that I passed first try. While I may know the product pretty well, I don’t tend to test well, especially with Microsoft tests. I scored a 785 which is much lower than I would have liked. I’m just a bit competitive with myself.

Here is my take on the test, I thought the questions were either very hard or very easy. I also disliked when you could get it down to two answers and they only varied by a few words. Now, I know where and what I need to change but I don’t always remember off the top of my head what the EXACT dialog is on that box.

So, the second biggest issue that I faced in getting the UC Software Update Services up and working was getting the configupdatesserver.vbs script to run correctly. Whenever I ran it I got a Unknown Username or bad password error. Well, turns out we must have an invalid character in our password cause I changed it to something without a special character (^,$,~,etc) and everything worked.

Seriously, this is just one crappy product. I spent at least 15 hours trying to get it to work. The documentation is ok but is missing key steps (see my previous post) and then this. I love OCS 2007 but the Phone Edition is not nearly as easy to update.

Over the past week, I have been setting up UC Software Update Services to be able to push out the updates to our Tanjay phones. Man, talk about a crappy solution. Sorry Microsoft, but this one needs a lot of polishing.

I got to the step where you create the UCUpdates SharePoint site and everytime I ran the command I would get a “The request failed with HTTP status 401: Unauthorized.” I was running the command with the same user account that I installed SharePoint with and verified that it was a local admin on the box as well as a Farm Administrator and a Site Collection admin. Still no go.