NetDocuments Flexible Updates

Follow

Created:
Updated:

Beginning with the release of 17.2 on September 7, 2017, we are implementing a flexible update model.  Your organization will have the flexibility to choose your go-live date for any given release, within a pre-determined window.  Our new flexible update model allows each customer more control over timing when transitioning to new releases.  This process accommodates customers with policies that prohibit changes to vital systems during critical times of the year (such as year-end or tax season).

Unless you have some users who are testing the 17.2 beta, there is no need to adjust your Hosts file or DNS server in order to make the transition to 17.2.

If you wish to transition to 17.2 on 7 September 2017

A NetDocuments customer can choose to upgrade to 17.2 any time after the release on 7 September 2017. To do this, contact NetDocuments Support and they will assist you in converting your repository to the new Update. All users in the repository will be switched to 17.2.

A Support agent will work with you to schedule a date to make the change. It can be done at any time that is convenient for you. The change will take effect for your users the next time they log in.

This switch to 17.2 will take effect for all users in the repository. Using this method, you will not be able to put a subset of your users on 17.2 and keep others on 17.1. 

If you wish to transition to 17.2 between 7 September 2017 and 31 January 2018

Customers will also have the option to upgrade to the new release at any time of their choosing after September 7th, 2017 through 31 January 2018.

Similar to the option above, contact NetDocuments Support and they will work with you to schedule a date and time when you want to switch your organization to the new Update.

No change is required to customer Riverbeds or MPLS lines. The path to either 17.1 or 17.2 is determined after the user reaches the data center. 

If you wish to move to 17.2 on a per-office basis, NetDocuments Support will be able to provide guidance on this. This option involves a change to the Hosts file or DNS server.  Use the following host information.

US
192.100.0.232    vault.netvoyage.com        #US pool
192.100.0.232    api.vault.netvoyage.com   #US API pool

EU
185.83.176.232    eu.netdocuments.com       #EU pool
185.83.176.232    api.eu.netdocuments.com  #EU API pool

AU
103.225.142.232    au.netdocuments.com       #AU pool
103.225.142.232    api.au.netdocuments.com  #AU API pool

 

If you wish to stay on 17.1 (through 31 January 2018)

No action is required on your part. As with previous NetDocuments Updates, your users will automatically see the new 17.2 Update beginning 1 February 2018 without any changes on your part.

Only the latest version, 17.2, will receive continuous updates.  After the official release of 17.2 on September 7th, the 17.1 version will only receive fixes related to critical defects and security issues. 

The 17.2 Beta servers will be available if you wish to continue testing with a subset of your users before switching your entire organization. If you have users accessing the Beta, they will continue to use the same IP address as described in the previously posted Beta Announcement

 

Back to Top

Was this article helpful?
0 out of 0 found this helpful

Comments

Have more questions? Submit a request
Powered by Zendesk