ShareSync: Mass Client Deployment
ShareSync can be deployed in an organization using a startup script of AD group policy. Users can also install desktop application themselves if they have administrative privileges.
Test this procedure on a small subset of computers before implementing it for the entire domain. To do this you can leave only test computer accounts in security filtering of the group policy or apply the group policy to the organizational unit that contains only test computers.
- Create a group policy for ShareSync installation.
- Download the following files and place them in Scripts folder of this group policy, or in another shared folder that will be accessible to computer account of your domain:
Place the installation script into the Scripts folder of the group policy.
- .NET 4 setup redistributable from Microsoft http://www.microsoft.com/en-us/download/details.aspx?id=17718
- ShareSync windows app setup from ShareSync web app
- Update the script so that paths to .NET installer and ShareSyncSetup.exe are correct and accessible.
- Add this installation script to the group policy in Computer Configuration\Policies\Windows Settings\Scripts\startup.
BAT script for ShareSync installation performs the following actions:
- Check that .NET 4 is installed. If not, install it from a network share.
- Check that ShareSync is installed. If not, install it from a network share.
reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Client2" > NUL 2> NUL
IF %ERRORLEVEL% == 0 GOTO APP_CHECK_INSTALLATION
echo "Installing .NET Framework 4"
IF EXIST "%ProgramFiles%\ShareSync" GOTO APP_ALREADY_INSTALLED
echo Installing ShareSync
\\server\path_to_setup\ShareSyncSetup.exe /quiet /L*V "%temp%\ShareSyncInstallLog.txt"
echo ShareSync is already installed.
ShareSync setup parameters:
- /quiet – no UI will be displayed
- /L*V “%temp%\ShareSyncInstallLog.txt” – the log will be written to a temp folder. If the script is run under System account, that folder would be C:\Windows\temp
Setup will also create messages in the Windows Event Log upon successful or failed installation.