Hi Ernaldo,
The error message is, of course, correct if the central configuration file repository is not available. Would this not be normally available during normal operation? So that obtaining this error would indicate either a network problem or something else?
Or are you trying to provide for two different scenarios, one for workstation users (always on the network) and another for laptop/remote/vpn users who would not normally want to use central configuration files? If this is the case, my suggestion would be to create two different installation packages on your installation server, one for local/always-on clients and the other for remote/vpn clients. In the second one, setup the installation scripts so as to not point the client to the central config, but instead copy the files locally during installation and use those.
Regards,
Matt