|
|
With the release of SolidWorks 2005 we have been given some extremely powerful tools to improve SolidWorks’ mass deployment capabilities. These tools take the SolidWorks Administrative image* functionality one giant leap forward, making the lives of CAD Administrators with more than a few seats much more bearable. New functions that have been added include:
· New Wizard** interface for creating the Admin image
· Ability to create a setup ini answer file for installation of clients
· Ability to deploy standard registry settings to everyone
· One button deployment via linked html page
· Auto update functionality for clients
· Active Directory support
As some users have already found these added capabilities can cause some confusion and a certain amount of grief. I hope to alleviate some potential problems and answer some questions with this article. I will start with a brief description of each of the above features. After that I will discuss issues that have been found and potential work-arounds to problems and issues that we have seen to date.
Feature descriptions
- The new wizard interface gives the CAD Administrator the ability to quickly navigate through screens of pertinent questions regarding the administrative image being created. This tool helps the user avoid command line entry of cryptic commands and switches. The new interface also leads the CAD Administrator through the creation of the installation answer file and/or a company standard SolidWorks reg file.
- The installation answer*** file is created via the admin image wizard during the creation of the Admin image itself. This file is referenced anytime SolidWorks is installed from the image to answer the normal questions that are asked during a SolidWorks install. Serial number, Reg Code, unit standards, etc… are all taken care of with the answer file. This can speed the installation by allowing users to install on their own machine while ensuring implementation consistency by auto answering the install questions.
- The registry settings for SolidWorks hold everything variable in a SolidWorks installation. The new wizard allows the CAD Administrator to deploy a standard registry file to all users upon installation. This file can either be created during the creation of the admin image itself or created on another system and then copied into the image. This function can aid a company in establishing consistency with the use of their design tool.
- As an option for deploying to the client machines SolidWorks has created a method for initial install of the client machines that is extremely simple. The Administrator can send a link to the client users. This link points to an html file residing in the same directory as the admin image. When the user opens this link, their Internet Explorer shows them a page with a single button; “Install SolidWorks Now”. The user clicks this button and the install begins.
- The new auto update function with SolidWorks 2005 can be a huge time saver for the CAD Admin. When SolidWorks is installed via the Administrative image the client then checks references the installation answer file in the loadpoint of the admin image each time SolidWorks is launched. If the admin image has not upgraded then SolidWorks launches. If it has been upgraded then the client automatically goes into the upgrade process. No disks are required and no one has to go to each machine to initiate the upgrade.
- SolidWorks now supports Active Directory for automated pushed installation. This allows the CAD Admin to force the installation of SolidWorks onto the client machines without worrying about security privileges of the users.
- The previous method of creating an Administrative image is still valid. (Using the command line and scripting the installation answers into that msiexec command.) Some CAD Administrators that have established procedures may want to continue using proven methods.
In working with this new functionality we have found several items of interest that can cause a CAD Admin some issues. I would like to point out a few of these items and hopefully help others from running into the same issues.
- As of SP0.0 of SolidWorks 2005, the Administrative Image could only be loaded on the local machine. Despite the instructions within the installation routine, network locations cannot be selected for the install path. This issue is scheduled to be fixed in SP1.1. Unfortunately, for this to make a difference, the CAD Administrator would have to use CD’s that are at the SP1.1 level. These CDs are available and you can call CATI technical support and they will get CDs sent to you if you require them. The ramifications of this issue are not devastating by any means. It just means that the CAD Administrator cannot create his admin image from a remote machine across the network onto his server. He must be on the server directly to install the image. Another item of note is that SolidWorks 2005 does not support anything prior to Windows 2000. The Installation program will not even run on older versions of the operating system.
- The ability to create the installation answer file is a great time saver for CAD Administrators. We have run into situations where the answer file was not referenced when running the setup through the swsetup.exe but it is referenced when initiating an install using the html file. This is due to the need for a switch to be added to the command when running swsetup.exe and the proper swsetup.ini file needs to be referenced. The command should be launched similar to: [path to image]\swsetup.exe /ini [path to image]\SolidWorks_2005_SP0_client_options.ini
- For some companies it is desirable to maintain consistency right down to the level of the layout of the SolidWorks environment, what toolbars show by default, what commands are instantly available, what options are set, etc…. For these companies the new registry functionality for the administrative image allows the CAD Admin to force these registry settings upon installation of the software. When creating the admin image, the installer is asked if he would like to deploy a default registry file and, if yes, would he like it to be referenced from an existing location or should a new one be created. The important thing to remember here is that to create registry file SolidWorks itself must be loaded onto the machine from which the install is occurring. This can be very difficult if machine that the image is being installed from does not support SolidWorks from a hardware or OS perspective. Also, even though this allows the registry to be loaded for everyone by default; nothing keeps the user from adjusting his own machine.
-
 The ability to send an html link to the user community for installation can be a tremendous time saver. However, companies that employ tight security in their network environment may not allow the users on the client machines to install software. If the users don’t have the permissions required to install software, the link will not  work. Also, there are two security settings that are required to be set in Windows Explorer. From the Tools menu in Windows Internet Explorer select Internet Options, then the Security tab. Select Local Intranet and choose custom Level… button. The two triggers that need to be enabled are under ActiveX controls and plug-ins.
- Initialize and script ActiveX controls not marked as safe.
- Run ActiveX controls and plug-ins
- Automating installations with Active Directory and Group Policy Objects can streamline installations and upgrades. However, the company must employ Active Directory services as well as have a system administrator that understands the Active Directory capabilities.
- If you choose to install using the previous methodology there is an issue that you must be aware of. The automatic update functionality new in SolidWorks 2005 does not function properly if the administrative image is created using the command line methodology. The automatic update functions only work when the wizard is employed and all 5 steps are completed. If you use the previous method updates must be handled manuals with the service pack manager on each client individually. This is slated to be fixed for service pack 2.0.
As mentioned before the new wizard and functionality for creating and maintaining administrative images has greatly simplified the process. With planning, these tools can greatly improve your installation and upgrade process, saving you time and money. The key to understanding these tools is to experiment outside of the production environment. These tools, if employed improperly, have the ability to shutdown SolidWorks for your entire installation. But, when employed properly, installations and upgrades for large implementations becomes much more manageable.
|
