Problem with WHS add-in?

[Wonko]

After considering windows home server for a long time, I eventually bit the bullet and swapped from xp. It installed ok on my pc server, and I then loaded device drivers and the 7.5.0 WHS build, and at some point during this the whole system slowed to a crawl. So I start again from scratch, with the same results - several seconds to respond to anything even though cpu wasn't anywhere near 100%.
At first I didn't attribute it to SBS, but eventually tried stopping SBS and everything was suddenly ok again (apart from the squeezeboxes, that is...).
So, I had a look at the server log (which didn't enlighten me TBH) and then tried various other WHS builds including 7.4.2 and 7.5.1 nightly - both caused the same slow-down.
I then try the standard (non-WHS) 7.5.1 - r30688 build, and everything is running normally again.
So, I suppose the questions are:
- is the 'add-in' the only difference between the WHS and standard windows builds?
- am I alone (my search didn't turn up others with the same symptoms)?
- is there a fix?

Thanks in advance.

[Wonko]

Well this is embarrassing having just said I didn't find anyone else with similar symptoms (which was true a couple of days ago when I searched). I now find this from sbs4000 which looks rather similar:
http://forums.slimdevices.com/showthread.php?t=77899

[spile]

I installed the WHS software and it has performed without any problems.

[Kuben72]

I have done a upgrade on WHS 3 times now and every time SBS rescans my whole library which takes about 10 - 15 minutes. In that time the SBS is unresponsive. The rest of the server works okay but is a bit slow due to the heavy CPU-use from SBS.

[gcurrie]

After considering windows home server for a long time, I eventually bit the bullet and swapped from xp. It installed ok on my pc server, and I then loaded device drivers and the 7.5.0 WHS build, and at some point during this the whole system slowed to a crawl. So I start again from scratch, with the same results - several seconds to respond to anything even though cpu wasn't anywhere near 100%.
At first I didn't attribute it to SBS, but eventually tried stopping SBS and everything was suddenly ok again (apart from the squeezeboxes, that is...).
So, I had a look at the server log (which didn't enlighten me TBH) and then tried various other WHS builds including 7.4.2 and 7.5.1 nightly - both caused the same slow-down.
I then try the standard (non-WHS) 7.5.1 - r30688 build, and everything is running normally again.
So, I suppose the questions are:
- is the 'add-in' the only difference between the WHS and standard windows builds?
- am I alone (my search didn't turn up others with the same symptoms)?
- is there a fix?

Thanks in advance.

Michael of Logitech has stated that the WHS add-in and the regular Windows version are exactly the same code, just one is wrapped in a different installer. When running they are indistinguishable.

That said, you could probably stick with the version you are running, although you won't be able to access it via the Console (you'll have to RDP in to make changes or use the web interface).

No idea why one would run differently. It sort of points to a possible WHS misconfiguration...

[mherger]

> Michael of Logitech has stated that the WHS add-in and the regular
> Windows version are exactly the same code, just one is wrapped in a
> different installer. When running they are indistinguishable.

Correct: it's actually a wrapper around the normal installer we have, adding the add-in and launching the regular installer. As long as the WHS console isn't running you shouldn't see any difference at all.

--

Michael

[Wonko]

Thanks for the thoughts chaps.
It's possible that it's a WHS install problem, but as I mentioned in the OP, I reinstalled WHS from scratch so if it is then it would seem to be a repeatable one (albeit with a sample size of 2). As WHS amd SBS are running normally without the add-in, that's what made me wonder whether it was the add-in itself... It is also unrelated to whether the scanner was running or not, BTW.
So whatever the cause, it looks like it's pretty specific to my setup (gigabyte GA-MA78GM mobo with latest drivers downloaded).
Now it's running ok, I'm quite happy without the console add-in, and as suggested, have been able to do whatever I want the 'old way' via the web interface or RDP.
The mystery remains for now, but I won't be losing any sleep over it!