Filed under: Uncategorized | Tags: Communicator Phone Edition, OCS 2007, UC Software Update Services
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.
Saw this and thought it was a great idea. Having a console that I can look at and see what is going on without risking root privileges is pretty slick.
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.
I was looking and saw that the Authentication Provider was set to Kerberos by default. I then looked and realized that the AppPool’s were running as a Network Service. I changed them (SharePoint – 80 and the Central Admin AppPool) to be a domain account and everything worked.
I have a feeling the issue is that I used WSS 3.0 SP1 to install WSS. I have read a few comments out on the web that have said there are issues with it. None the less, the lack of good documentation on this piece is sad. Our Tanjay’s are still on beta code cause I can’t get this working but that is for another post (Issue #2). Hopefully if you are facing the same issue as above, this will help you get on to the next step.
Filed under: Uncategorized
Well, it happened. It always does. It is only a matter of time before it happens again. A computer died. Not just any computer, but my home server. Which had been hosting my blog. I had gotten lazy and hadn’t backed anything up in such a long time. Lesson re-learned.
That’s why I’m writing here. I’ve had this blog account open for awhile and never knew what I wanted to do with it. Now I do. I’m shifting all of my blogging to here. So, re-set those RSS feeders to look here instead of www.nbwheeling.org/~aball.
If you want some of my old content, I think the waybackmachine will be your best bet or you can look for a cached Google page. If you find something that I really should re-post, let me know. I’ll be looking through these and re-posting anything I think is really good as well.
