Prior to V11SP3 the complete $CADENAS_DATA directory was mounted from PARTapplicationServer. This made it impossible to check in native parts, because users would need to write to $CADENAS_DATA/pool which was not possible over RFS (remote file system).
With V11SP3 the $CADENAS_DATA/pool is forced to be NOT mounted from appserver by default. This means that - when working with/accessing native parts $CADENAS_DATA/pool (and so $CADENAS_DATA as well) must point to a directory in the filesystem where all clients have access to.[73]
However there may be cases, where a user wants to just open parts in readonly mode without being able to load/store native parts from within the CAD system.
For this cases, there is a config option in $CADENAS_SETUP/pappclient.cfg or $CADENAS_USER/pappclient.cfg that allows to change this behaviour based on client or application:
[common] remotePool=1 remotePool(PARTdataManager)=1

![[Note]](https://webapi.partcommunity.com/service/help/latest/pages/it/partwarehouse/doc/images/note.png)