locked
whs 2011 connector significantly slows down boot time RRS feed

  • Question

  • 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


    • Edited by jsyv3 Saturday, January 12, 2013 6:42 PM
    Saturday, January 12, 2013 6:40 PM

All replies

  • P.S. One additional phenomenon I have just noticed: If I let my PC sit at the log in screen for several minutes and then enter my password (as opposed to entering the p/w immediately after that screen appears), the time to desktop is nearly immediate (i.e., the usual ~2 seconds). Thus, it appears that whatever is causing the delay I have experienced after the log in process is a function of something occurring pre-login; that is, whatever process is severely slowing down the time-to-desktop after entering my password I'm observing seems to be independent of the post-login processes (e.g., reading the registry). What's really confusing me is (as above) if I disable the Service Provider Registry, the delay issue goes away (along with the majority of the functionality of WHS 2011).

    Does this shed any light on the issue or suggest a trouble-shooting path to anyone?

    TIA,

    JS

    • Hello? Anyone out there?
    • Edited by jsyv3 Saturday, January 26, 2013 3:09 AM
    Saturday, January 19, 2013 11:34 PM
  • I have no answers for you but I have been experiencing the EXACT same issues. I do not have an SSD so the problem is even worse for me, sometimes 10 minutes before the PC is even usable because while the backup process is running (whatever it is), the PC absolutely crawls and the disk is maxed out to 100% utilization. I had this problem with Windows 7. Then I removed the connector and the problem went away, upgraded to Windows 8, still no problem, then reinstalled the connector and its back again. This is absolutely nuts.

    Same problem here as well, all wireless PCs do not have the problem, but my wired PC does. I'm not really sure where to look for answers, but I'm thinking of ditching this server all together once I can find a comparable backup solution.

    What do you have your System Protection disk space usage set to? Mine was all the way down to 1%. I thought maybe since it was so low it couldn't keep a restore point so one was created at each backup... just guessing. That could be way off.

    I also noticed that the backup task was scheduled for 4:41PM, which is earlier than my PC is on most days. Usually I turn it on at 5pm or later, so I'm going to change this to a later evening time and see what happens.

    I can recreate the slowness by running this command, which I pulled from the scheduled task and I believe triggers a backup, which starts off by creating a restore point and volume shadow copy, and that I think is the main cause of the slowness:

    "C:\Program Files\Windows Server\Bin\RunTask.exe" /asm:"C:\Program Files\Windows Server\Bin\BackupClientProvider.dll" /class:Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientManager /method:DoScheduledBackup /task:"Backup"

    • Edited by jkillebrew Thursday, February 28, 2013 6:09 AM
    Thursday, February 28, 2013 3:19 AM
  • Is the backup running as soon as you boot up? On my computers the WHS 2011 that do not wake themselves for backup (because they are set not to), the backup starts the same time the log in screen loads. This puts a huge load on the hard drive and makes the computer almost too slow to use until the backup task is done. Laptops will not backup unless they are plugged into AC power. One way to test this out is to disconnect your WHS 2011 server or turn it off. If you boot up fine then you know the problem is NOT with the connector software but instead with a connection to the server such as a running backup task. Good Luck! I am trying to toy around with BACKUP task in Task Scheduler (in Task Scheduler under Microsoft>Windows>Windows Server>Backup) to see if I can set it to wait a few minutes after boot up before running. This works but reverts back to the default settings after a boot or two and am stuck with the slowdown. My only option now is to let the computers wake up at night and backup. One in my room near my bed so it will also wake me up. It does however solve the slowdown on login during the daytime though.
    Wednesday, March 20, 2013 3:13 PM
  • For what is it worth, see my post at We Got Served:

    "Connector Slows Down Boot Time"

    I found that a failing drive might have been to blame


    Monday, November 25, 2013 11:20 PM