I have 25 rep shares in my org. Two of them are really far behind (almost 60 GB) and they keep halting. The rep page has the red square and says Halted (see details) but I cannot find any details for the life of me! I'm new to KACE and I'd love to figure out why these keep stalling. To fix, I remote in and reboot the machine.

PS what is a good number for Hi bandwidth? Currently I have 524288 (0.5 MBps), which seems low.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0

Bandwidth really depends on your infrastructure, but 60GB is gonna take a while at 0.5 Mbps for sure.  We don't limit the bandwidth on our rep shares but they reside on dedicated machines so there's nothing else happening bandwidth-wise.

Can you authenticate to the rep shares that are halting manually from a machine?

Answered 10/09/2013 by: nheyne
Red Belt

  • > We don't limit the bandwidth on our rep shares but they reside on dedicated machines so there's nothing else happening bandwidth-wise.
    Our replication PCs are dedicated also - just old boxes with Win7Pro and some TB drives thrown in - do you have a really huge circuit to support unmetered replication?

    > Can you authenticate to the rep shares that are halting manually from a machine?
    Do you mean can I remote into one? Yes. EDIT: Usually. RDP sometimes doesn't work but LogMeIn Rescue does. And sometime it has to be manually rebooted.
    • I was thinking more like browsing to \\ipaddress of machine\rep share folder.
      We're gig at least between locations so bandwidth hasn't been an issue yet.
      • Ah, yes. I can do that too. I had a support call with KACE this morning. We found a patch (Chipset/DRVR_WIN_R304291.EXE) that I had seen over and over on the rep shares that we think is causing the machines to hang.

        Will know for sure after rep tonight, but after testing two rep shares by rebooting, de/re-enabling rep, and allowing a temporary Lo bandwidth window, the To Do list is now 100%.
Please log in to comment
Answer this question or Comment on this question for clarity

Share