Command Line Switches for the NetDocuments Client-side installs

Follow

Created:
Updated:

This article is directed towards those who are responsible for installing NetDocuments client software on their users’ workstations. Our Software Installation Guide provides the information related to the command line switches and registry entries for the software packages listed below: 

  • ActiveX
  • ndOffice
  • EMS Folders
  • EMS Profiler

Related articles:

Attached below is a .zip file containing sample installation scripts provided by Nik Phillips. He has kindly provided them to us so we can permanently link them to this article. They have not been developed or tested by NetDocuments; they are provided simply as a courtesy.

Back to Top

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

Comments

  • Avatar

    I am having all kinds of trouble deploying application integrations (haven't tried the others yet).  Our users are not allowed to have local administrative privileges on their computers, and because of this, I need to silently install the ND tools via group policy or another method.  

    Is there anyone at Net Documents (or in the Net Documents community) that can provide some input on how to most efficiently accomplish this?  I have checked and double-checked my command line switches, tried installation from a logon script AND a startup script in a GPO, etc. So far it's not installing for me, no matter what I try.  This is also very important for being able to push out updates for the 100+ users who do not have elevated install privileges.

    Thanks everyone for your help.

  • Avatar

    We have sucuessfully deployed ndOffice and the recent update to the ActiveX control using shutdown scripts.  Shutdown scripts are useful as they don't impact on startup/login times and also run with admin rights.  The problem with them (and Startup scirpts) is that they probably won't have access to the network.  I got round this with a GPO deployed scheduled task that copies the installation files and scripts locally for the shutdown script to run later. 

    The ActiveX control is really straightforward, just run 'msiexec /i newebcli.msi /quiet'.  NdOffice was a little more involved as we had to uninstall the old version first.  I'm happy to share the scripts if you think it might help.

  • Avatar

    Very good ideas.  I would very much appreciate a copy of your scripts.  My e-mail address is nrobinson@qslwm.com.  Thanks a lot!

  • Avatar

    In the spirit of sharing I'll post a slightly sanitized version here.  I've set up these scripts so as to be reusable and indeed we have successfully deployed a few other applications with it and tagged it on to our PC build process so that any updates can be immediately applied to freshly imaged PCs

    Attached it a zip of the deployment folder.  In the deployment folder there is a scripts folder and folder for each application to be deployed.  A script called copylocal.vbs effectively replicates the deployment folder on the local PC in c:\temp\sDeploy.  A second script called rundeploy.vbs checks each application folder and then runs the install.bat within.  The install.bat completes the install and then writes a zero-byte file called _DONE.  Rundeploy.vbs will not execute the install.bat if it finds _DONE in the same folder.

    There is also a helper script called WMIInstall.vbs which can uninstall one version of a program and reinstall another.  Our ndOffice updgrade install uses this.

    To set it all up you'll need to:

    • Extract the attached zip to an acessible network location.
    • Edit the SourceFolder constant in CopyLocal.vbs to match the network location.
    • Use GPO to run CopyLocal.vbs (using cscript.exe) from the network location. I recommend creating a scheduled task.
    • Create a shutdown script in GPO to run the local copy of RunDeploy.vbs (again with cscript).  Unless you've changed the paths this would be c:\temp\sdeploy\scripts\rundeploy.vbs.

    There are two nedocuments application deployment folders in the zip as well as an example.  Basically each folder should contain all the necessary files for the install along with an install.bat which will install the application and then create a _DONE file.  You will need to modify/recreate these folders and their contents as suits your needs.  I've removed the MSIs from the zip to keep it small.

    Hopefully that all makes sense.  Having written it all down it does seem more complex than I remember.

    At the risk of stating the obvious,  please make sure you set this up in a test GPO and test each of the install.bat files to make sure they do what you want.

     

     

  • Avatar

    Again, thanks Nick for your help with this!  I'm just now getting a chance to test this out and see how everything works in my lab.  It doesn't seem to be that hard from looking at your notes and examining the file - you did a great job of making it easy to figure out.

    The only thing I may have need clarification on are some aspects of the WMIInstall.vbs script: 

    * Is the "PackageName" parameter going to be the actual title of the software as displayed in the installed programs screen?

    * At the end of the WMIInstall script, you test for a "NewVersionInstalled" variable but I don't see it defined elsewhere in the script.  Just curious how that value is set.  Is it previously set somewhere as an environment variable throughout the process?

    Again, thanks so much for your help.  This is awesome.

     

  • Avatar

    No problem Nate, I'm glad this has been of some help to you. 

    The PackageName should be the same as the Name column in Add/Remove Programs in Control Panel.

    Good point on that variable.  It originally was set by a bit of code further up which checked if the installed version was newer.  That way the script wouldn't install older versions over newer.  I think I gave up on that because of the vagaries of version numbering schemes;  e.g. '1.3.2.1' is actually quite complex to parse and work out if  its newer than '1.3.10.1'; I may revisit it one day.  So the variable and if statement are redundant and because VBScript initializes booleans as false the code will always run.  Feel free to trim out the 'if' and 'end if' lines.

  • Avatar

    I know this is an old topic but I seem to be having the same issue and can find no other method to do this. The attached .zip is unfortunately not available any more but I would appreciate, if you get this comment, to please send to me or post again. Thank you.

  • Avatar

    All,
    The original scripts that Nik posted on Feb 11, 2015 are no longer available. He has provided them to me, and I have linked them to this article above. Please review and test them prior to implementing them in a production environment. Thanks again, Nik!

Have more questions? Submit a request
Powered by Zendesk