[vectorworks 2019 silent install using sccm as application deployment]

On 6/7/2019 at 5:29 AM, mr-stoo said:

I use SCCM too and I've seen this error before. I couldn't figure out what the error was - I had a department boss breathing down my neck and had to get it done asap. This script works for me and had no problems. Maybe it could be of some help.

 

On 7/28/2022 at 1:42 PM, IcKxSyS said:

🥳Awesome, adjusted PS script for 2022 and still works great. Thanks a ton! Saves a lot of trouble deploying to 200+ lab computers across a couple of campuses.

 

I was seeing this problem with 2022 as well.  I found that enabling "Run installation and uninstall program as 32-bit process on 64-bit clients" is another workaround.

 

Keep in mind if you're copying "LoginDialog.xml" to Program Files, this will cause it to be redirected to Program Files (x86).  To fix that, use the environmental variable %ProgramW6432%.

 

It's been 3+ years but here's to hoping the Vectorworks devs fix this some day.

 

[vectorworks 2019 silent install using sccm as application deployment]

3 minutes ago, georgebpnz said:

I did move the installer from resources\installer to root folder and to run the install from there using script.

 

Powershell script I use

.\Install-Vectorworks2020.exe --mode unattended --unattendedmodeui none --UserName "xxxx" --CompName "xxxx" --Serial "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" --installdir "C:\Program Files\Vectorworks 2020" |Out-Null

Start-Sleep -Seconds 300

 

 

Thanks for taking the time to follow up.  I'm not having any problems with AV or the detection method.  In your original post, it was just not installing/timeout.  Do you think its moving the installer location that fixed this?  Or something else?

 

 

[vectorworks 2019 silent install using sccm as application deployment]

Same problem with Vectorworks 2020.  Application installs silently when using Software Center.  When doing a required deployment, it starts but times out after 2 hours.

 

The devs need to test and fix the silent installer when running under the "SYSTEM" account.