We have multiple remote offices that connect to our KBOX office with rather...puny throughput (3Mbps or so). In setting up RSAs at each remote site, I'd like to figure out a way to "seed" these RSAs with a common batch of media, applications, and scripted installs using a physical medium (thumb drive, DVD, whatever...) so that they aren't trying to sync 5GB or more over the course of an entire work day when first fired up. Maybe duplicate the contents of one RSA and mail it to another?
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


We have 80 RSAs with bandwidth as low as 256Kbps on some. Probably the FASTEST we've got is a T1 (1.5Mbps). It took about 2 weeks, but we throttled everything down to 10KB/s on every RSA. So, you can use throttling to solve your problem - assuming you don't need the RSAs built very quickly.

As far as "seeding" goes, you are SoL. The only access you have to RSA shares is read-only. The only thing I can think of is cloning the RSA VM after it is 100% replicated - then change the name, IP, etc. after copying the RSA to one of your other sites.
Answered 05/27/2011 by: airwolf
Tenth Degree Black Belt

Please log in to comment

Cloning the VM after syncronization works, however, it won't link to the k2. Unfortunately, at this time the once you enable linking on the RSA that linking key is set, even if you disable it. Therefore when you go to link it , the K2 reports that the RSA already exists. There is a feature request to add a "Generate new linking key" for future revisions.

Answered 05/27/2011 by: cserrins
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity