Version Affected: All
Overview
FileSync Helper is a tool that reconfigures the file shares and permissions for a realm that is not properly syncing, without requiring the IIS reset that the older ResetFilePerms script requires. This is typically needed for realms that were created using the Admin Console's API instead of the Realm Management Tool, after FileSync is already installed.
Download and Run FileSync Helper
- Download SAFileSyncHelper from SecureAuth's SharePoint portal.
- Move the downloaded zip file to every server integrated with FileSync.
- Right-click the zip file and open Properties to check whether the file is blocked. If it is, check the Unblock checkbox and click OK. (If the file is not blocked, no Unblock option appears.)
- Extract the zip file and place SAFileSyncHelper in the following directory:
D:\MFCApp_Bin\Extras\RealmManagementTool
- From that directory, right-click SAFileSyncHelper.bat and select Run as administrator.
- Choose one of the two menu options:
- 1 Update: All -- reconfigures the file shares and FileSync service account permissions for every realm.
- 2 Update: Intelligent -- only reconfigures shares and permissions for realms not already configured for FileSync, leaving correctly-configured realms untouched.
- Enter 1 or 2 and press Enter.
Either option should fix realms that are not syncing, without the brief outage caused by resetting IIS.
Special Considerations
FileSync Helper does not work on older versions of FileSync. Running it against an unsupported version displays the following and exits without making any changes:
Unable to read the replication account information from the registry
If this occurs, use the ResetFilePerms script instead -- see Newly Created Realms Won't FileSync, Post Installation for more information.
SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.
Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.
Comments
Please sign in to leave a comment.