There needs to be an xml file in the current user’s home to tell Vectorworks to connect to which license server and use what kind of modules.
/Library/Preferences/net. and (Check permissions!).
Therefore we need to package 2 plist files:
During the initial installation and startup of Vectorworks it ask to put in the new serial number and the old one.
Fix the permissions from 775 admin:admin to root:wheel 755 for both folders!.
If the “/Library/QuickLook/VectorWorksQL.qlgenerator” isn’t available on the harddrive a process is started from “~/Library/Application Support/Vectorworks” called VectorWorksHelperTool asking for admin credentials
These 2 folders need to be packaged in one installer: “/Applications/Vectorworks\ 2015 US” and “/Library/QuickLook/VectorWorksQL.qlgenerator”.
Run the application as admin and as a normal user.
Install the application, plugins and updates.
You can use every tool that suits your need. We have a VW license server running with a USB dongle that the client needs to connect to. One for the application and one for the license. I created 2 different packages to keep things a bit more flexible.
Fix the pop-up message asking for admin credentials to fix some permissions when the application is started up for the first time.
Fix the setup to connect to the license server for the user.
Fix the permissions and group on “/Applications/Vectorworks 2015 US”.
There are a couple of issues I found we need to fix or to make it work for our environment. For our Munki environment I need to create a custom installer to deploy the application on our fleet. Java 6 is also needed for the Vectorworks application. But someone decided to build a custom installer using Applescript and Java….When you start the installer it needs the deprecated Apple Java 6. The original US version contains a s ilent installer. If you received an installation dvd for Vectorworks 2015 educational Benelux version then you’re in for a (little) treat.
0 kommentar(er)
