I’ve answered a few comments on recent blog postings on the recent CU release, but thought I’d post again to clear up any misunderstandings.
Just to make sure I understand this correctly, all the Cumulative Updates CONTAIN Infrastructure Update. So what that means is that the way that the timesheet will work change once we apply a cumulative update right?
Not the earlier ones - but all Cumulative updates starting with December 2008 do contain the IU - so any changes introduced in the IU will also be there once you apply either the December or February CU too.
Regarding client/server dependency:
Upon first read, it almost sounds like rolling out CUs server side don't *require* the client side to be on the same patch, once past the IU.
Then, when I re-read it, it sounded like a bug is fixed in the hotfix numbers mentioned, and moving forward, the client/server dependency does require keeping the system on the same patch level.
Can you please confirm what you meant? (I am expecting the latter...)
Please disregard my previous comment, unless you find it useful. I just finished reading your post regarding Feb CU updates, which answered my question.
I guess I should read the blog posts in order... :P
I would like to apply the February CU (SP2?) for Project Server and Project Professional Client, but I am having a hard time marshaling all the bits and installation procedures. I can't even find the downloads...
Is there a roadmap or a master procedure for accomplishing this?
Hope I'm not just being stupid...
Hi Bob, Firstly the Feb CU is not SP2. You can expect SP2 hopefully later this month, followed by the April CU. For the current CU the link at the top of this post will take you to my blog that lists the WSS (961755), MOSS(961756), Project Server (968271) and Client (966308) hotfix pages. Each page then has a link to the download. The article and download pages follow the same pattern, just substitute the KB number. So for the client the article is at http://support.microsoft.com/kb/966308 and the download at http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=966308&kbln=en-us.
I hope this helps.