File Repository/Default File Destination has been reset to the factory default twice

[TS2]

Yes, there is a Fiery. Great information. Thank you for the quick response.

[Joe Arseneau · Accepted solution]

If you have a Fiery, you can't use the default repository, the Fiery requires it, so the Fiery will reset it back to what it needs to be, which is:

FTP

100.100.100.102:21 and the username is template

It is required to be that way because the Fiery needs to be able to push its own templates to the copier (via the template pool)

and the templates need to be there because that is primarily how the Calibration is done for the Fiery.

In short, stop trying to use it, just rename it to Do Not Change

Then create an alternate repository, and point the default template to that one, no when you create a template, it will look to the alternate by default instead of the main one.

This behaviour cannot be changed, you just have to work around it, because the copier is sold more often on its own, without a Fiery, so it has the default repository as it would be seen in those typical environments. It would be nice if they could make separate firmware branches for has Fiery and ones for doesn't have Fiery but would be financially and logistically.

[TS2]

Hello.  The Network Scanning File Repository Default File Destination has been reset to factory twice within the last two months.

I am the sole programmer.

I have reprogrammed it for SMB in each instance and verified functionality. 

Is there a known or common cause for the reset?  

Thank you.

Dave