I reinstaleed SP1 on a clean enviroment and had a few issues getting the new user account to log into the Core Service.
In the end I stopped the FreeFlow Core service first, then added the new log in account deatils before starting the service again.
Previously I was getting an "initialisation" error on the browser window so maybe it does not like you entering the new log in until you physically stop the service first. If so the install guide needs to be amended slightly.
With regard to needing "network passwords" to access remote servers I can confirm that adding these credentials to your Windows Credentials in has fixed up our SAVE functionality.
Control Panel\User Accounts\Credential Manager\
Please make sure that you have v3 SP1 before attempting to save to a shared directory.
The FFCore service needs to run under a service account (details in the installation instructions) and that service account needs access to the shared folder.
The simplest way to test this: log in as the service account, bring up the Run... dialog and enter the UNC for the shared directory. If the window pops open in windows explorer then the account has the requisite priviledges.
BTW> You can add credentials to the service account using the credentials manager control panel.
We have set up the windows share as per the FFcore guide but have no joy in saving to a server path that is not local.
Do you have any further documentation on the process.
I can save to an External process with no issues but the "save" node only allows local saving to a shared folder or to the sandbox?
Saving to a shared directory requires use of a windows account (aka a service account). The installation instructions have details on the required configuration changes to enable FFCore to use a service account.