/build/static/layout/Breadcrumb_cap_w.png

Problem with Firefox replication

I have replication setup to numerous sites and all of a sudden while everything else will replicate the Firefox updates will not.  It shows still needs I also looked up on the replication share and those folder are not there.  Anyone else ever see this?



0 Comments   [ + ] Show comments

Answers (2)

Posted by: AbhayR 5 years ago
Red Belt
0

This is a known issue with Replication and Firefox. Please reach-out to support so they can provide you a fix

Posted by: worzie 5 years ago
Fourth Degree Brown Belt
0

I too have seen this issue.  I too have used Firefox.  Tried deleting the offending file, then re-uploaded using Chrome.  Manually removed the offending file from the replication share and forced an inventory to sync the open sync time.  This did upload but still showed the file needing to be synced in the queue. So I'm not convinced this is entirely a Firefox issue.


What I did do to overcome this was: duplicate the script, delete the original, delete the replication share manually as it would take 2 weeks to otherwise, then did another forced inventory.  This time the script did sync the "copy of" script but even with the offending script gone in KACE and on the replication, it shows up in the queue but without a script number this time.


I have seen other scripts do this in the past and they all seemed to have fleshed themselves out over time.  I make a habit of duplicating scripts when needing to update them and this is a great reason to do so.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

View more:

Share

 
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