I'm running WHS 2011 and have successfully connected 6 PCs (3 desktops, 3 laptops) all but one of which are connected wirelessly and running Win 7 Home (64-bit). The 6th PC (desktop) is connected by Cat 5 and is running Win 7 Pro (64-bit). I have no issues
with any of the wirelessly connected PCs - only the wired one is giving me fits. The issue is that with the WHS connector installed, the boot time (post-password to desktop) takes nearly 2 minutes, while without the connector it's more like 2 seconds (SSDs
are magical things).
I have uninstalled the connector twice and each time the post-password time from password screen to the desktop reverts to its previously snappy behavior and each time I successfully reinstall the connector, I'm back to waiting longer than I did with
a mechanical boot drive.
I presume there is some confusion occurring related to establishing the connection between client and server, but I am at a loss as to how to troubleshoot this and would sincerely appreciate any guidance anyone may care to offer.
The server has a static address on the wireless router (through which this troublesome PC is wired), Realtek network drivers are current (I even reverted back to the latest Asus version, circa 2009, to no avail), backups work just fine, I've checked to make
sure the SSD is using AHCI and not IDE in the BIOS, I've swapped out the Cat 5 cable and plugged it into various ports on the router. PC has an Asus P6T motherboard with 12GB DDR3, an Intel i7-965 CPU, 180GB OCZ SSD as the boot drive, 3 TB mechanical hard
drive for storage, Blu-ray burner, etc.
I count 11 services which are added after Connector is installed. I've listed each below, followed by the post-password-to-desktop times (min:sec) when each is disabled, one by one:
1) Windows Server Client Computer Backup Provider Service - 1:55
2) Windows Server Connector Update - 1:58
3) Windows Server Download Service - 1:55
4) Windows Server Health Service - 1:58
5) Windows Server Initialization Service - (default = automatic stopped)
6) Windows Server LAN Configuration - 2:10
7) Windows Server Media Center Client Service - 1:40
8) Windows Server Media Center TV Archive Transfer Service - (default = automatic, delayed start stopped)
9) Windows Server Notifications Provider Service - 1:54
10) Windows Server SQM Service - 1:57
11) Windows Server Service Provider Registry - 0:02 (disabling this also stops Client Computer Backup Provider, Download, Notifications Provider, Health svcs, Server SQM). If I try "Automatic, delayed start" (vs. diabling altogether) - 1:57 all svcs
which were stopped by disabling are still stopped. If I try "Manual" - 2:00 all svcs which were stopped by disabling are still stopped.
So, it appears as if the WS Service Provider Registry is the culprit, but unfortunately, disabling it also cripples all useful functionality of using the server as a backup (one primary reason for its existence, in my world). As noted above, any option short
of disabling this service equates with these stupid-slow boots to the desktop. Certainly I could disable it, then manually add back the necessary services one-by-one, but I'd likely spend more than the two minutes saved during boot using this workaround.
Any other ideas anyone might have? Might there be some sort of event logger I can have run automatically which would record failed attempts by the PC to connect with the server, which I might then use to diagnose the reason for the delay?
Thanks in advance,
JS
View this thread
with any of the wirelessly connected PCs - only the wired one is giving me fits. The issue is that with the WHS connector installed, the boot time (post-password to desktop) takes nearly 2 minutes, while without the connector it's more like 2 seconds (SSDs
are magical things).
I have uninstalled the connector twice and each time the post-password time from password screen to the desktop reverts to its previously snappy behavior and each time I successfully reinstall the connector, I'm back to waiting longer than I did with
a mechanical boot drive.
I presume there is some confusion occurring related to establishing the connection between client and server, but I am at a loss as to how to troubleshoot this and would sincerely appreciate any guidance anyone may care to offer.
The server has a static address on the wireless router (through which this troublesome PC is wired), Realtek network drivers are current (I even reverted back to the latest Asus version, circa 2009, to no avail), backups work just fine, I've checked to make
sure the SSD is using AHCI and not IDE in the BIOS, I've swapped out the Cat 5 cable and plugged it into various ports on the router. PC has an Asus P6T motherboard with 12GB DDR3, an Intel i7-965 CPU, 180GB OCZ SSD as the boot drive, 3 TB mechanical hard
drive for storage, Blu-ray burner, etc.
I count 11 services which are added after Connector is installed. I've listed each below, followed by the post-password-to-desktop times (min:sec) when each is disabled, one by one:
1) Windows Server Client Computer Backup Provider Service - 1:55
2) Windows Server Connector Update - 1:58
3) Windows Server Download Service - 1:55
4) Windows Server Health Service - 1:58
5) Windows Server Initialization Service - (default = automatic stopped)
6) Windows Server LAN Configuration - 2:10
7) Windows Server Media Center Client Service - 1:40
8) Windows Server Media Center TV Archive Transfer Service - (default = automatic, delayed start stopped)
9) Windows Server Notifications Provider Service - 1:54
10) Windows Server SQM Service - 1:57
11) Windows Server Service Provider Registry - 0:02 (disabling this also stops Client Computer Backup Provider, Download, Notifications Provider, Health svcs, Server SQM). If I try "Automatic, delayed start" (vs. diabling altogether) - 1:57 all svcs
which were stopped by disabling are still stopped. If I try "Manual" - 2:00 all svcs which were stopped by disabling are still stopped.
So, it appears as if the WS Service Provider Registry is the culprit, but unfortunately, disabling it also cripples all useful functionality of using the server as a backup (one primary reason for its existence, in my world). As noted above, any option short
of disabling this service equates with these stupid-slow boots to the desktop. Certainly I could disable it, then manually add back the necessary services one-by-one, but I'd likely spend more than the two minutes saved during boot using this workaround.
Any other ideas anyone might have? Might there be some sort of event logger I can have run automatically which would record failed attempts by the PC to connect with the server, which I might then use to diagnose the reason for the delay?
Thanks in advance,
JS
View this thread