![]() The plugins still require setting up by Admin. This used to be a total pain to manage, but we moved to a License server version, now it is pretty easy to push out. I use Jamf to push out the installers, and as we have an autodesk license server, I just need to log in as Admin and point them to the server. Takes a while to sort, but then it works. I will then bundle the installers into folders up to around 5Gb in size, and compress the folder and then run a post install script to install everything from each compressed archive. I then use a test Mac to capture the essential sounds for each, and then I will do the same for the full sound library. What a faff to get the ISO files, you have to do them one at a time and as soon as the ISO downloads, and starts to install you grab the ISO and move it to a different folder. I do have a copy of all of the ISO files of all of the installers, and when I get the time I intend to build it again using them so I get a proper vanilla install of them. Then on each Mac I log in as Administrator and open Native Access and let it authorise each install. Then I use Composer to make pkg's of the library files, keeping them down to a suitable size.Īnd push this lot out with Jamf. I normally use Composer to capture the main install of the Apps, but make it ignore the location for the libraries. Suggested method - Install Native Access and then use it to install everything, on each Mac. I use Jamf to push this lot out to the Labs required, then Log in as Administrator and authorise Live and establish the connection to Max4Live. Then with Composer taking a snapshot I then open Live and install the Packs. I then authorise the app on the test Mac. I use Composer to make a pkg of the install (copy the app to Applications) for both Live suite and Max4Live. You do need to manually login to Native Access as an administrator post install. Remove-Item /Volumes/Native -Force -ErrorAction "Continue" -Verbose Remove-Item /Volumes/nisoftware -Force -ErrorAction "Continue" -Verbose Hdiutil unmount -force /Volumes/nisoftware} Start-Process 'installer' -ArgumentList "-pkg "$pkg" -target /" -Wait} $pkgs = Get-ChildItem /Volumes/nisoftware *.pkg | Select-Object -ExpandProperty FullName ![]() Hdiutil mount $iso -mountpoint /Volumes/nisoftware/ ![]() New-Item /Volumes/nisoftware -ItemType Directory -ErrorAction "Continue" -Verbose} $nisoftwaredir = Test-Path "/Volumes/nisoftware" $softwarenamespace = $softwarename -replace " "," " $softwarenames = Get-ChildItem -Path "/Volumes/Native/Native Instruments/data" | Select-Object -ExpandProperty "BaseName" $isos = Get-ChildItem -Path "/Volumes/Native/Native Instruments/data" | Select-Object -ExpandProperty "FullName" Start-Transcript -Path "/temp/logs/NI.log" -Verbose New-Item -ItemType "Directory" -Path /temp -ErrorAction "Continue" -Verbose} Pwsh -File /private/var/tmp/ni.ps1 $tempdir = test-path "/temp" ![]() I decided just to start it from Self Service rather than after enrollment.Īdd this as the Script within the policy $4 and $5 parameters are Username and Password defined within the policy. Powershell Core 6 PackageĬreate a Policy called "Install Native Instruments"Īdd the powershell script as a package and make sure the script goes into /private/var/tmp/ni.ps1 So you need to deploy Powershell Core 6 as a package. So I've used the same script and adapted it for Macs. I had to write a powershell script to deploy Native Instruments on Windows. I'm quite new to JAMF and primarily a Windows SysAdmin.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |