Should you install SOLIDWORKS products on each computer individually, or should you create an administrative image and deploy the installation to all clients with one command?
If you are installing on only one computer, or if you manage dozens or hundreds of computers, the choice is obvious. For situations in between, consider the following comparisons.
| Individual installation |
Administrative image |
|---|
| Users can do their own SOLIDWORKS administration. |
The system administrator can customize multiple installations using the Option Editor, specifying installation options such as creating a new installation or updating an existing one, running the installation as an administrative user, running external commands before or after the installation, different product groupings, and so on. |
| The computers must be physically accessible to the person performing the installation. |
Client computers can be distantly located as long as they are accessible from the same network. |
| You can install different versions, service packs, or products on different computers, with independent settings. |
Using the Option Editor, administrative images can maintain consistency in versions, service packs, products, and settings for multiple installations. |
| The computers must have network or email access. A network or email connection is required to activate SOLIDWORKS and download files. Network access is also required when collecting licenses. |
A local network connection is required to deploy the application; media drives are not required on client computers.
Clients can be updated automatically. All clients deployed from the same administrative image are at the same service pack. To maintain multiple versions, you can create multiple administrative images.
License activation can be automated.
An administrative image requires additional disk space on the server; clients require the same space as individual installations.
|