Arliss Renwick
-
Posts
10 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Arliss Renwick
-
-
Never mind, I just figured it out - VW 2023 wants the license description file specified. I added "--LDFChoice licenseID" (minus the quotes) to my installation script and it's working. Hopefully this is helpful for others.
-
1
-
-
Since I look after an office of about 36 (non-admin) Mac VW users, the silent install option has been my go to for years. Here's the command I use to install VW 2023 from its disk image (serial number redacted.):
/Volumes/Vectorworks2023-SP0-668937-SeriesBEG-installer8-osx/Vectorworks\ 2023\ Installer.app/Contents/Resources/installer/Install\ Vectorworks2023.app/Contents/MacOS/installbuilder.sh --mode unattended --unattendedmodeui none --Serial xxxxx-xxxxx-xxxxxx-xxxxx --installdir /Applications/Vectorworks\ 2023
with VW 2023, it brings up this error:
"Could not receive License Information String, check your License Description File and try again."
What's changed regarding the silent install from 2022? The "License Information String" error is new. Does anyone know what the syntax is w. 2023?
-
Here's the script I run (on macOS.) This runs on the target machine. in my case, the VW Installer.app is in Applications, but this could be run from a different location as well. Replace the xxxxx's with your serial number:
/Applications/Vectorworks\ 2021\ Installer.app/Contents/Resources/installer/Install\ Vectorworks2021.app/Contents/MacOS/installbuilder.sh --mode unattended --unattendedmodeui none --Serial xxxxxx-xxxxxx-xxxxxx-xxxxxx --installdir /Applications/Vectorworks\ 2021
-
An update to my previous post - I've spoken with VW tech support and there IS a command line method for generating and running VW 2019 updaters which I've had total success with (it works differently than previous silent updates and installs, but essentially does the same thing, making me very happy.)
-
I see where a more 'intelligent" updater could be seen as a boon, but I'm the IT Manager in an environment where none of my users have local admin rights. Previously, I could perform updates via the updater's "silent install" option (and push that command out to my all my Macs with Apple Remote Desktop.) Doing this individually on every workstation would be a huge step backwards, if this is the only option. Is there a something similar to the silent install option using the updater app?
-
1
-
-
Whoops, I needed to look closer at that path! You're right, it's there. Glad to be wrong on this one - thanks for help!
-
Like I said in my post, here's no "installbuilder.sh" located in Vectorworks 2018 Installer.app/Contents/MacOS/. It's now an executable called "Vectorworks 2018 Installer" which ignores any of the switches that allowed installbilder.sh to run silently. The solution for the Mac (which we are using) doesn't work (see attached.)
-
In previous versions of VW, I'd run the installbuilder.sh from inside the installer, and pass along the serial, user, etc with the unattendedmodeui none --mode unattended switches, ensuring the client wouldn't interact with the installer. Now, in 2018, installbuilder.sh has been replaced with "Vectorworks 2018 Installer" which runs with full client interaction, ignoring the switches. Is there a way to perform a silent install of 2018?
-
I've sorted it out in my environment. This was happening to quite a few people in our office, too. No one is logged into their Macs as an admin, and their Workspace folder (for some users) was set to read-only. I changed permissions (via Terminal, as root) - chmod 755 Workspaces - and ta-da, palettes now stay put. Bruce Kieffer - I'd probably lay off running Cocktail - if it's "Repairing" Privileges every morning, it might be resetting your Workspaces folder to read only (just a guess.) We're all on 12.5.3 in my office, FYI
Mac Studio running 12.6 can't connect to site protection server
in Troubleshooting
Posted
We have a brand-new M1 Max Mac Studio that can't connect to our (local) license server. I've manually specified the ip address and port and it still comes back with "can't connect to server". I get the same results using Wi-Fi and/or Ethernet. Firewall is off, no AV running. The ironic thing is that if I run the nc command from the terminal (for example nc -vz x.x.x.x 5053) it will come back with "Connection to x.x.x.x port 5053 [tcp/*] succeeded!" so I know it should be able to connect. Note we've never had this issue before , not with any of our Mac Studio (or Intel Macs and Windows PCs.) This is a total showstopper for us, so any assistance is very appreciated.