License Delivery maintenance is expected to occur on Saturday, November 30, between 8 AM and 11 AM CET. This may cause a short 3-hours outage in which license-related tasks: license key upload, download, update, SSA validation, access to the license pool and Graphisoft ID authentication may not function properly. We apologize for any inconvenience.
Installation & update
About program installation and update, hardware, operating systems, setup, etc.

Enterprise updates deployment

Anonymous
Not applicable
Would like to know whether anyone has implemented ArchiCAD updates on a Windows Environment "WS2012".

I looked at http://www.graphisoft.com/downloads/archicad/updates/DeployedInstallation.html but not sure whether this is the best solution, as IT would have to download the new update and setup an new GPO pointing to that MSI.

Basically looking for an option that the Design manager would either update his local ArchiCAD, and push the update himself, or, download the update and put it into a shared folder that a GPO would pickup and update the clients.

Not sure whether or not the link above explains the whole thing.
2 REPLIES 2
Anonymous
Not applicable
No one?

At the moment I'm looking at doing it manually.

download the update, write a script to run psexec on on each machine...
Anonymous
Not applicable
We've struggled with this very same question. ArchiCAD is not very enterprise-friendly in a Mac environment, especially with teamwork projects.

The solution we are using right now is a custom "ArchiCAD Updater" which is a graphical AppleScript wrapper for this shell script I wrote:

https://gist.github.com/filipp/8975071

The AppleScript looks something like this:

activate
display dialog "This application will update ArchiCAD to the latest version. Do you want to continue?" with icon 0 buttons ["Cancel", "Continue"] default button 2 cancel button 1
display dialog "Please close all open copies of ArchiCAD. The update will take about 5 minutes." with icon 2 buttons ["Cancel", "Continue"] default button 2 cancel button 1
do shell script "curl -fSsk https://gist.githubusercontent.com/filipp/8975071/raw | sh -s - http://example.com/latest-18.dmg" with administrator privileges
do shell script "curl -fSsk https://gist.githubusercontent.com/filipp/8975071/raw | sh -s - http://example.com/latest-19.dmg" with administrator privileges
activate
display alert "Update complete!" as informational message "Close this application by clicking OK"
... notice we're updating both AC 18 and 19 at the same time.

To update the servers, you can use ARD's Send UNIX command (assuming they're also Macs):

curl -fSsk https://gist.githubusercontent.com/filipp/8975071/raw | sh -s - http://example.com/latest-18.dmg
So the workflow becomes:

- Notify users of impending update, include instructions in the notification email
- Update the servers and shared machines (conference rooms, etc)

It's actually not a bad solution since we have more and more laptops that might not even be at the office for weeks (making a "centralized" update very difficult). Once the server's been updated, the users will get an error once they try to connect to the teamwork server so they just use that update tool. Our users all have admin privileges on their machines.

I've also played around with Munki, and you could def. make it work with it, but I ran into all sorts of weird issues and didn't have time to investigate further since this solution works well enough for us, at least for now.

We have 45 AC licenses and about 60 users.