[Guide] How to Deploy Matlab 2017a

Comments

6 comments

  • Eugene Meenan

    Tried all of the above and no matter what I cannot get that to deploy without error 1 or not at all.  I can logon to the PC remotely and run exactly the same installation command and works fine as long as I don't select silent install.  Frustrating but heck I still like this guide as it pointed me in the right direction for lots of other steps of MATLAB I wasn't familiar with.

    1
    Comment actions Permalink
  • Eugene Meenan

    Arrrrgh it was something so simple I placed exclamation marks in the licence path as the path had a space in it so thought it would need it.  When I placed in automated instead of silent I was able to identify the marks where in the path so then removed them and worked fine.  I wonder if that job in Mc Donalds is still available :-)

     

    1
    Comment actions Permalink
  • Luke Nichols

    No worries, glad you got it sorted out.

    Be careful about the server that hosts your PDQ repository rebooting because that will break any active Matlab installs halfway through. We have run into this once or twice while trying to push an automated PDQ deployment during our file server's weekly reboot window.

    1
    Comment actions Permalink
  • Priyam Patel

    I don't get how you are doing this. The command step enters commands line by line in cmd. Cmd does not support UNC path. What am I missing here?

    1
    Comment actions Permalink
  • Luke Nichols

    Priyam,

    Are you having an actual issue with the implementation of this package or is your question purely theoretical?

    You say that CMD does not support UNC paths but I have no issues calling an executable from within CMD from a UNC path.

    You might be referring to the fact that CMD does not support UNC paths as the starting directory or as the current directory? As in you cannot CD to a UNC path directly:

    C:\Windows>cd \\server\share
    '\\server\share'
    CMD does not support UNC paths as current directories.

    While it is true that CMD will not allow you to CD to a UNC path you can still call an executable that is within a UNC path as long as you do not try to CD to it first. In this example I have placed a simple whois query executable in a share on my server and called it from CMD:

    C:\Windows>\\server.test\home\lnichols\whois.exe pdq.com

    Whois v1.20 - Domain information lookup
    Copyright (C) 2005-2017 Mark Russinovich
    Sysinternals - www.sysinternals.com

    Connecting to COM.whois-servers.net...

    WHOIS Server: whois.godaddy.com
       Registrar URL: http://www.godaddy.com
       Updated Date: 2016-12-20T13:37:52Z
       Creation Date: 1994-05-24T04:00:00Z
       Registry Expiry Date: 2023-05-23T04:00:00Z
       Registrar: GoDaddy.com, LLC
       Registrar IANA ID: 146
       Registrar Abuse Contact Email: abuse@godaddy.com
       Registrar Abuse Contact Phone: 480-624-2505
       Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
       Domain Status: clientRenewProhibited https://icann.org/epp#clientRenewProhibited
       Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
       Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
       Name Server: NS47.DOMAINCONTROL.COM
       Name Server: NS48.DOMAINCONTROL.COM
       DNSSEC: unsigned
       URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
    >>> Last update of whois database: 2018-03-06T17:49:49Z <<<

    1
    Comment actions Permalink
  • Priyam Patel

    Hi Luke,

     

    Thanks for the response! I am not sure what I was doing but I deleted and created the package and again and it all worked. 

     

    Thanks! 

     

     

     

    1
    Comment actions Permalink

Please sign in to leave a comment.