More info on November 2008 update ...

re: More info on November 2008 update ...

j and v — Wed, 26 Nov 2008 01:31:05 GMT

"After installing the November 2008 update gets installed on your home server,"

Do you want to edit that sentence?

For example -

"After installing the November 2008 update, your home server will be rebooted....(etc)"

re: More info on November 2008 update ...

hserverbuffer — Wed, 26 Nov 2008 05:52:46 GMT

Can I ask about something else?

Do you know when exactly will Windows Home Server be released on MSDN subscriber downloads? It has been confirmed like a month a ago that WHS will finally get MSDN but nothing happened for this long...

And is there any way to integrate Power Pack 1 directly into the installation file? There is WHS Power Pack 1 available on Newegg.com, so I guess the version they sell is the one that has PP1 integrated. So there got to be a way to get that Power Pack integrated, am I right?

Did File Conflicts get fixed?

Bodogbodog — Wed, 26 Nov 2008 10:26:53 GMT

I notice that there is a new version of DE included with this update - was there anything in it that might fix the "File Conflicts" that many have reported on the Microsoft WHS forums?

re: More info on November 2008 update ...

Kipu — Thu, 27 Nov 2008 11:58:35 GMT

Then you're the lucky one, because I just got an update and after my client computer (Vista Ultimate) rebooted:

- Visual Studio cannot be started again (license corrupted, at least reinstal required)

- Outlook ost file claim to be unusable (created for another account?)

- Outlook can't connect to POP3 accounts any more (doesn't seem to retain passwords)

- VPN connections don't work any more

And that is just the start; it is going to cost me hours to get basic communication back, if I get it fixed at all...

And best of all: I can't reach https://connect.microsoft.com/WindowsHomeServer or is it down?

re: More info on November 2008 update ...

Kipu — Fri, 28 Nov 2008 01:22:10 GMT

Back... and much happier now. I thought I'd share the solution :-)

simply repairing the Connector installation (via the control panel) and restarting a few times apparently did the trick.

Nothing needed to be reinstalled. My guess is the access rights on certain registry keys got screwed up for some reason...

BlogMS Weekly Articles Published – 24th November 2008 to 30th November 2008

BlogMS - Official Microsoft Team Blogs — Mon, 01 Dec 2008 17:31:32 GMT

203 Microsoft Team blogs searched, 66 blogs have new articles in the past 7 days. 120 new articles found