You've learned about a new version of the Shinydrive Client – now what? What do you do? What is different? How is it installed? Don't worry – we've got you covered – take a deep breath and review the steps below.

Firstly, we recommend you review the details that are available on our website about what is included in the release on our Shinydrive Change Log page.

For the Shinydrive Client, you can review any new features that have been added, and which significant bugs are fixed in the latest release.

On this page, we also now include information on the following:

  • Whether there is a new Content Server Module version (and if so, what features were added/which bugs were fixed) – specifically called out for CS10, CS10.5 and CS16.
  • Whether the Shinydocs Drivers have been updated (and if so, what has changed).
  • Whether Shinydrive Office has been updated (and if so, what has changed).
  • Whether Shinydrive Outlook has been updated (and if so, what has changed).
  • Whether Shinydrive App Finder has been updated.
  • Whether Shiny Shutdown has been updated.

Since the Shinydrive Client (and possibly Shinydocs Drivers, Shinydrive Office, Shinydrive Outlook and/or the Shinydrive App Finder) is what you would typically deploy via MSI, our suggested guideline for this is as follows:

  1. Test: We recommend that you test pushing out the MSI package on a “typical” small user base. While we do not expect any issues, this is a good step to verify that if there are special considerations that you will have to take into account, you will run into these during a small test, rather than discovering them during a larger deployment. Any adjustments from this test can then be used for when you do a wider deployment.
  2. Notification: Decide whether or not you want your users to be aware of the update. If you do, send around a email notifying them of the update before you do it.
  3. Shutdown Shinydrive: When doing the update, each user needs to have their Shinydrive shut down. A good way to ensure this is to do the update when the users are logged out. If this cannot be achieved, we recommend you use our “Shiny Shutdown” tool (which is included as part of the Shinydrive Software Package Download) which can be used to kill the Shinydrive process.
  4. Push Out MSI Package(s): Push out the desired MSI packages through your software deployment system. Note that many of our MSI packages come in a 32 bit and 64 bit versions. It is important to push out the appropriate package depending on which OS version the end-user is using.

Note that you do not typically need to reboot the end-user PC after an update, unless there has been a change to the Shinydocs Drivers (in which case a reboot will be required).

Note that the MSI installer needs to run using Administrative credentials.

Further information on additional options you may wish to use can be found on our Shinydrive Windows Client Installation page.

If there are changes to the Content Server Module, we recommend you time this to occur during an announced outage. Details on how to apply this can be found on our Installing Shinydrive page, under the Shinydrive Content Server Module heading.