How to Push the ProjectDox Client Components MSI from Central Location to Users?

 Gathering of information:

1. Are there group policies that stop the user from writing to C:\ or user home? The installation must be able to write to C:\ and %userhome% (user that will log in).

2. Are you using roaming profiles? Roaming profiles will prevent pushing the msi from central location.

Prerequisites:

• Ability to write to C:\ drive and %userhome% (user that will log in).

• UAC will need to be disabled (or set to never notify)(Windows Vista, Windows 7, Windows 8.1, Windows 10)

• Windows firewall must be turned off (if used)

Push:

• To push the MSI, use the appropriate commence from the distributing application, and include the flags /q /n with the appropriate scripts in place.

   

  After the push command (still needs to be provided for in the script):

• For 64-bit clients grant full access to “\Program Files (x86)\Avolve Software\ProjectDox Components”

• For 32-bit clients grant full access to “\Program Files\Avolve Software\ProjectDox Components”

• We recommend adding your ProjectDox URL to the trusted sites in Internet Explorer (this can also be scripted)

End-user test (this is a manual procedure):

• Test viewing and uploads (this is required to complete the installation of components for all non-admin users, and must be done by each user on the PC)

After end-user test:

• Turn UAC back on.

• Turn Windows firewall back on (if used)

• Revert to original group policies and permissions

Revised 02-26-2015