14.3 - Beta Announcement - July 3, 2014 - 8:00 AM Eastern - US and EU Datacenters



The Beta of the 14.3 Update will officially begin on July 3, 2014 at 8:00 am Eastern (1:00 PM London) with the release of the Update planned for July 24, 2014.

We continue to refine many of our internal testing procedures and have been pursuing a much more rigorous testing process for this and future Updates.  There are minor training requirements with this Update.  It primarily includes a number of bug fixes in addition to some key changes as described below.

We encourage as many users as possible to test using the beta software to ensure that it works well in your own environment.  As you know all environments are different and we test for the main functionality of the software.

Also, in case you may have missed it with the previous Update, we ceased support for Windows XP, Office 2003, IE 8 and previous IE versions. With this 14.3 Update if you are using IE8, you will be re-directed to the ND2 limited interface in the same way as previous versions of IE do.  We are forced to discontinue support because a number of functions will not work and the new modern browsers require us to use new development software which no longer supports the older browsers.  We also have ceased support for Adobe 8 and 9 - both Reader and Acrobat.

A 14.3 Release Notes announcement with more detail is available in the Announcements section of the Support portal.  Please refer to this Release Notes for more information on the changes.  The 14.3 Release Notes will be moved from the Announcement section to the Knowledgebase section at support.netdocuments.com following the Update.

The 14.3 Update DOES require an Update to the ActiveX program. This ActiveX should be installed prior to the release of the 14.3 Update.

With this Update, we are recommending that customers install the ActiveX prior to the July 24, 2014 Update.  If it is installed now, users will not be prompted to install it on July 24th when the Update is released. You can also install other new client software versions up to a week prior to the Update.  This ensures that you are installing the latest version for production of any client software in case changes are made during the beta period.  Client software version numbers are available in the Update Release Notes.  Please double check the version number with the Release Notes article prior to installing to ensure that you are installing the latest version. 

The ActiveX control can be downloaded from this link:


If you participate in the Beta testing, please consult with your NetDocuments Administrator and use the information below. The Beta period allows you to give us feedback and gives you an opportunity to use it in your environment and get familiar with the changes.

Please make sure you do a Control F5 on your browser to remove any old cookies and cache as you begin to use the beta.

To report bugs related to the Beta, send them to beta@netdocuments.com. If you have other questions as you look at the Beta, please go to support.netdocuments.com and create a ticket.


The beta servers are Server 13 and 14 for your reference.


For each PC accessing the beta, please following the steps listed below.

U.S. Datacenter - If you use the US Datacenter at vault.netvoyage.com, set your Host file (located at C:\Windows\System32\drivers\etc) to include this line:    vault.netvoyage.com        #US beta pool

E.U. Datacenter - If you use the EU Datacenter at eu.netdocuments.com, set your Hosts file (located at C:\Windows\System32\drivers\etc) to include this line:    eu.netdocuments.com     #UK Beta

NOTE: If you want to test the beta 14.3 EMS Profiler or EMS Folders (and we encourage this) you MUST also put one of the following lines in your host file depending on which datacenter you are using.  If you are installing ndOffice, you ALSO need to include this in your host file and insure that you have installed the new ActiveX.    api.vault.netvoyage.com                                                 #netdocs US beta pool    api.eu.netdocuments.com                                         #netdocs EU beta pool


Remember you must remove the Beta host information AFTER 14.3 is released to be able to login to the service after the beta servers are removed.

We recommend that you include as many testers as you feel you can manage. These should be individuals who use the product each day and who would recognize a defect in the product and report the steps to recreate it.  They should actively review the new features and report bugs they discover.

We appreciate your willingness to participate in the important beta testing process. NetDocuments reserves the right to modify the process at any time and to determine who may participate.



URL-based Beta Testing

We also encourage during the last week of the beta that you make the beta available to a wider set of users than the normal testing group.  To help with this, we have introduced a new capability that will lead into an easier way to access the beta in the future. When the 14.3 Beta is ready, you will be able to enter a URL to go to the beta software.  You will be prompted to add the URL to your Trusted Sites list.

Depending on which datacenter you are using, you would use one of the following URLs to access the beta with this new URL method:

- US datacenter - use the URL https://beta-vault.netvoyage.com to get to the beta software.

- EU datacenter - use the URL https://beta-eu.netdocuments.com to get to the beta software. 

Be aware that when using this method, you will not have access to any client-side software such as the integrations or EMS. This is just meant to provide access to the browser-based features available in the beta. 

With this URL capability to beta test, a user can easily test the web software associated with the new Update without going through the steps of changing their host file.  For 14.3, general beta testers should still use the host file method to test so they can have a complete test including the client software.  Even though the new URL method will be available for 14.3 it should not be treated as the main way to test the new Update because it does not include the ability to test the client software.



Back to Top

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


Have more questions? Submit a request
Powered by Zendesk