Software Deployment Question

Replication Share Hardware Requirements and Endpoint Connection Inquiry

06/01/2016 1478 views

- I have to provide a detailed hardware minimum and recommended requirements for Replicator Shares to use, but could not find too much information other than mentioning of hard drive space.  Can someone tell if there is such requirements posted somewhere?  Currently using Asus Atom PCs now and I definitely don't think its powerful enough.  What about using a NAS with Linux, such as Synology NAS solutions? 

- I understand only 20 connections max for Windows 7 PCs.  If the Replication share reaches the maximum connections, does it automatically reject connections from other endpoints and terminate? Or will the endpoints keep trying to connect until a connection to the replication share is established?

5 Comments   [ + ] Show comments


  • I believe the minimum requirements for a replication share are very modest.

    Even an intel atom pc should suffice as it is mostly used as a storage medium

    for the agents from the machines on the remote site to copy software and

    patches from. Most of the processing power is used on clients connecting

    to the replication share.

    If you have more than 20 connections , then you need to set it up on a server.

    Also yes..... you can use a NAS as a repluication share.

    I have read somewhere that Kace can be used on Ubuntu servers.

    Have a look at this article on ITNINJA.

  • Thanks for the clarification. I have to setup RS at our offices throughout Latin America and needed the info. Just to be on the safe side, I will be recommending them a medium spec PCs.

    As far as the OS, I can't install any server OS. Half of the offices have more than 20 PCs. Do you think this will cause any issues? The reason I ask is, when I deployed patches it looked like it deploys them to small batches PCs at a time. Because of this I don't think it will be too much of an issue?
  • I don't think this will be an issue. Kace agents should be smart enough to create a queue when
    looking to download software from a replication share. The process will take a little longer than usual due to the limitations of 20 devices at a time, but should still complete with no problems.
    If a kace agent looks to download patches from a replication share and find that the queue is full......it will time out and wait for the next inventory cycle to get patches.
    • It IS an issue - my company was cheap and we used Windows 7 for the replication shares. 20 connections and it's done, and that, as you know, is a Windows limitation. The Windows 7 machines were a waste of time. However, you can get around this by creating manual labels containing fewer than 20 machines, then run patching at intervals. Be careful, however, you'll have to do some testing to see how long the first batch takes so you can time the second, etc. Or do different batches on different days. You get the idea.
  • Thanks.

    I'm in a similar boat. We have quite a few sites and setting a server OS as RS on each site can be very expensive(licensing wise). Since we name the PCs based on the business group I can deploy in small amounts via smart label.
  • FYI we have the same problem with Win7 replication shares. However, I just set up a new replication share using Ubuntu 16.04 LTS. You can use any linux distro, as long as it supports samba. By default, there is no 'max connections' and the practical limit is ~13,000

Be the first to answer this question

This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ