Hoping someone can help, I am trying to find a script that will install JMP 17 via network drive and also install the SID file and set the per file to a default location.
Hi @PoynomialMink80 , you could do this:
#Load the License File $LicenseFile = $InstallDir+"\jmp.per" Copy-Item $SourceDir"\jmp.per" $LicenseFile -Force # Create directories if needed New-Item -Path $Env:ALLUSERSPROFILE"/SAS" -ItemType Directory -Force New-Item -Path $Env:ALLUSERSPROFILE"/SAS/JMPPRO" -ItemType Directory -Force New-Item -Path $Env:ALLUSERSPROFILE"/SAS/JMPPRO/17" -ItemType Directory -Force $AddinDir = $Env:ALLUSERSPROFILE+"/SAS/JMPPRO/addins" New-Item -Path $AddinDir -ItemType Directory -Force # Create preferences file that links to the license file $fn = $Env:ALLUSERSPROFILE+"/SAS/JMPPRO/17/JMP.PFS" New-Item -Force $fn Set-Content $fn "Preferences( File Location Settings( License File Path( $LicenseFile ) ) );"
More info about installing the license and add-ins:
Anyone manage add-ins using a script or a centralized tool? Maybe a PowerShell script via Microsoft System Center Configuration Manager (SCCM)?
Many thanks this is what I am looking for. Thank you
This scirpt is awesome! I'm deploying via intune / powershell and its exactly what I was looking for. One question, how are you updating yearly? Do you just need to delivery a new .per file to the machine and overwrite the old one? JMP's docs indicate a user-interactive procedure vs an ideal silent update. My thinking is use intune to deliver a new per file and overwrite the old one, which is easy enough, but will JMP notice the new per file? I mean we can tell the users "yeah new per file's already there, just click it and go about your day" but that's less ideal