What can we help you with?
Search
Sorry, you do not have permission to carry out this action.
Avolve Software - Powered by Kayako Help Desk Software
What can we help you with?
Search
knowledgebase : Installation > ProjectDox Client Components
How to Enable Silverlight in Safari for MAC Users to Upload Files

ProjectDox Versions: 8.1-8.3

 

Solution

1. First, you have to install Silverlight for Mac.

2. Then open Safari and select Preferences.

3. Then Security -> Web Content

4. Then select Allow for the unsecure mode for Silverlight.

 

Then following the directions on the following post, users will have to do the steps below as well. 

http://social.msdn.microsoft.com/Forums/silverlight/en-US/e763205a-d978-4f65-b595-3cc325494eab/problems-with-safari-and-silverlight-plugin-on-mac-os-x-maveric?forum=silverlightgen

The post explains to do the following:

1. Open Safari

2. Select Settings

3. Select Security

4. Select Internet-Plugins: Allow Plugins

5. Organize Website Settings and then select Silverlight on the left side, on the right side select hostname, then pulldown "Execute in unsecure mode".

How to Push the ProjectDox Client Components MSI from Central Loc...

 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

Is There a Client MSI? Can the client Files Be Pre-Installed on E...

Is there a client MSI? Can the client files be pre-installed on end user workstations?


Yes, there are two ways that this can be performed:

1. IGC distributes a client .MSI that you can host for download and installation by a Systems Administrator. In a default install of Brava Enterprise (using Tomcat as the application server) you can find this file at C:\Program Files (x86)\IGC\Brava!\Brava! Enterprise X Client.msi, where X is the version number for Brava Enterprise.


2. IGC distributes a .ZIP file that contains the decompressed .CAB file contents, along with a .BAT file. The contents of this .ZIP can be copied to each workstation and then the .BAT file executed for installation. In a default install, this .ZIP file can be found at C:\Program Files (x86)\Apache Software Foundation\Tomcat 6.0\webapps\ROOT\IGC\ClientInstallScript.zip .

If you have created a custom integration.dll (typically named generic_ENU.bin) for use by your integration, it is important that this file be included in either distribution. (You would re-build the .MSI to include this, or include it in the .ZIP distribution.)

A couple of considerations for the System Administrator performing the installation:


1. The MSI or ZIP should be run so that it uses the user's profile directory for directory paths and not the System Administrator's login.

2. As an alternative to #1, if multiple users on the same workstation will be using the viewer, install the components to a shared location (based on network policy permissions). As an example, you might run: msiexec /qn /i "Brava x.x Client.msi" INSTALLDIR="C:\Brava_AllUsers\" TARGETDIR="C:\Brava_AllUsers\"

3. With Windows Vista, the Brava Server machine must be added to an IE Security Zone that does not have Protected Mode enabled.

4. More information about using Group Policy to remotely install software in Windows 2003 and Windows 2008 can be seen in this Microsoft Knowledge Base article: http://support.microsoft.com/kb/816102 .

 

Revised 02-25-2015

Silverlight Upload Issues - File Browse Results in Error Message

Issue: 

The user received the error message below when attempting to use the File Browse button to select files on their local machine for upload to a particular project. The user is able to drag and drop files into the Upload Window and is successful.  All other Projects are able to use the File Browse button in the uploader control as well.  The issue is only affecting a single project. 


 

Solution:

 

The issue is caused by improper syntax of the Print Ready File Extensions list or the Pass Thru File Extensions list.  If the list in incorrectly formatted or the syntax is bad then the users will be displayed with the error message when they click the File Browse button on the Uploader Control.  See screenshot below of incorrectly formatted string of file extensions.  To fix the issue, correct the syntax of the field.