2012
Autodesk, Backburner, FBX, Maya, MotionBuilder, Mudbox, Softimage, and 3ds Max are registered trademarks or trademarks of Autodesk, Inc., and/or its subsidiaries and/or affiliates in the USA and/or other countries. All other brand names, product names, or trademarks belong to their respective holders.
Contents Chapter 1 Network Administration and Deployment . . . . . . . . . . . . . 1 Network Administration and Deployment . . . . . . . . . . . . . . . . . 1 Understanding Deployments . . . . . . . . . . . . . . . . . . . . . 1 Planning a Deployment . . . . . . . . . . . . . . . . . . . . . . . 2 Check Deployment Readiness . . . . . . . . . . . . . . . . . 2 Determine the Installation Type . . . . . . . . . . . . . . . . 3 Determine the License Server Model . . . . . . . . . . . . . .
Use Group Policies to Assign a Deployment to Computers . . . . . . . . . . . . . . . . . . . . Verify a Group Policy Deployment . . . . . . . . Use Microsoft SCCM to Deploy Products . . . . . . . . Set Up a Source Directory for SCCM . . . . . . . Create the SCCM Software Installation Package . Distribute Products Using Imaging Software . . . . . . Distribute Multi-Seat Stand-Alone Products . . . Distribute Network Licensed Products . . . . . . Restore the Master Image . . . . . . . . . . . . .
When I uninstall my software, what files are left on my system? . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Chapter 4 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi
Network Administration and Deployment 1 Network Administration and Deployment Understanding Deployments A deployment provides an efficient way to install one or more Autodesk products with a standard configuration on multiple computers. The files required for the installation process are stored on the network, in an administrative image, in a folder to which all users have shared access. To install the products, users navigate to the deployment folder and double-click an installer shortcut (.LNK file).
■ Deployments can be configured to generate a log file for each installation. Network administrators can use these log files for troubleshooting. Planning a Deployment Check Deployment Readiness This checklist identifies preliminary tasks to complete, information to gather, and decisions to make before creating a network deployment. TIP To review deployment settings, including details of product configuration, you can create a test deployment.
Deployment Checklist If your product has language options, decide which language to use for each deployment. NOTE Languages can be included when you initially create a deployment, or when you create a new deployment configuration, but not when you modify a deployment. Determine whether to create log files on individual computers, in the deployment folder, or both. Determine whether to run installations in silent mode.
servers. You also define the NLM configuration. When an Autodesk product starts up on a client computer, it requests a license from NLM, then returns it when the product is stopped. Computers running the product based on a network installation do not require individual activation. For more information, see Choose a License Server Model (page 4).
You can find the Licensing Guide by clicking the Installation Help link in the installer. Configure Individual Products When you create a deployment, you can accept the default settings for any product you choose to install, or you can configure these settings to create a custom deployment. Configuration details for each product are usually covered in a product-specific appendix to this guide.
If you select the Install Service Pack from autodesk.com button, the service pack will be automatically downloaded and you will not need to extract the MSP file. You can add multiple service packs to a deployment only if the service packs are locally stored, not if you are downloading them from autodesk.com. NOTE If the deployment process for the main product is canceled or fails, the service pack installation will automatically be canceled.
To include a service pack with the deployment To include a service pack with a deployment, an MSP file must be extracted from the downloaded service pack executable. 1 On the Include Service Packs page, click the Browse button. 2 In the Open dialog box, locate the service pack you want to include with the deployment. 3 Select the MSP file and click Open. 4 Specify whether you want to append the service pack to the deployment or merge the service pack into the administrative image. 5 Click Next.
Creating a Deployment Create an Original Deployment Use this procedure to create a new deployment from the installer. In the process, you can create a default deployment by accepting the default configuration of each installed product, or you can create a custom deployment by customizing the configuration settings of one or more products in the deployment. To create an original deployment 1 Close all running applications on your computer. 2 Start the installer.
5 In the Installation Settings section, select one or more of these options: ■ Silent mode runs the installation in background, without prompting the user for any input. NOTE Silent mode can automatically restart the user's computer without warning after installation. ■ Log file on each workstation can enable users to review and troubleshoot their own installations. ■ Network log file in a central location supports the network administrator in reviewing data for all installations.
Modify a Deployment Inside each deployment folder is a Tools folder that contains a shortcut (.LNK file) named Create & Modify a Deployment. You can use this shortcut to ■ Create a new deployment configuration ■ Create a new deployment configuration that uses an existing deployment as a template ■ Modify the configuration of an existing deployment The installer pages guide you through the process, similar to when creating an original deployment.
Alternative Distribution Methods 2 Alternative Distribution Methods Overview of Distribution Methods In addition to standard deployments, you can use the following alternative methods of distributing Autodesk programs on Windows platforms: ■ Scripting. See Use Scripts to Deploy the Program (page 11). ■ Group Policy Objects (GPOs). See Use Group Policies to Run a Deployment (page 17). ■ Microsoft System Center Configuration Manager (SCCM). See Use Microsoft SCCM to Deploy Products (page 20).
more commands, as well as command switches that specify options, and flags that modify the options. An installation script also contains path names. An installation script points to the location of the product's setup.exe file. You must point to the setup.exe file on your installation media. For example: Autodesk product CDROM1\setup.
dim dim dim dim dim dim dim dim dim dim dim dim dim ' productType strADSKSNPrefix strADSKSNNumber strADSKProdKey strLocale strACADStandaloneNetworkType strADSKLicenseServerType strADSKLicenseType strADSKServerName strADSKServerPath strADSKServerHostID strADSKPath strSourcePath ' Script initialization Set shell = CreateObject("WScript.
' For Single Network License Server 'RunSingleLicenseServerInstall() ' ' End of Script Wscript.quit() ' Function RunStandaloneInstall shell.
retString = retString & "ACADSERIALNUMBER=" & strADSKSNNumber & " " retString = retString & "ADLM_PRODKEY=" & strADSKProdKey & " " retString = retString & "InstallLevel=5 " DefaultCommand = retString & " " end function ' Function MakeCommand dim retString retString = DefaultCommand() & " " retString = retString & "ACADSTANDALONENETWORKTYPE=" & """" & strACADStandaloneNetworkType & """" & " " retString = retString & "ACADLICENSESERVERTYPE=" & """" & strADSKLicenseServerType & """" & " " retString = retString
Switches in Installation Scripts Switch Description ACADSERIALNUMBER= Specifies the serial number. ADLM_PRODKEY= Specifies the product key (found on the same label as the serial number). User Interface Flags Flag Description q Designates that the installation is performed in silent mode. Run Scripts After creating a script, you move it to a server or use a mapped drive letter or a UNC (universal naming convention) path.
Use Group Policies to Run a Deployment With group policies, you can advertise and install a program by assigning a deployment to computers. A deployment that is assigned to a computer can be used by any user of that computer. Generally, you would assign the deployment to a computer that is shared by several users. NOTE Autodesk products are designed to be installed on a computer so that any user who logs on to the computer can run the software.
3 Verify the installation. Confirm that the program has been correctly installed. See Verify a Group Policy Deployment (page 20). Use Group Policies to Assign a Deployment to Computers Perform the following procedures from a Windows XP computer or a Windows 2000 or 2003 server that has Group Policy Management Console installed, and has access to the Active Directory server. NOTE For more information, go to Microsoft TechNet and search for "Group Policy Management Console".
7 In the Deploy Software dialog box, select Advanced and click OK. 8 In the Properties dialog box, Modifications tab, click Add. 9 In the Open dialog box, select the Transform Package file called acad-.mst). Click Open. 10 In the Properties dialog box, Modifications tab, click Add. 11 In the Open dialog box, navigate to \Tools and select the Transform Package file called gpo.mst. 12 Click OK to complete the package.
7 In the Open dialog box, navigate to \Tools and select the Transform Package file called gpo.mst. 8 Click OK to complete the package. The GPO is now assigned to all computers that are members of the organizational unit for which the GPO was created. The next time a computer in the organizational unit is restarted, the program will be installed and will be available for all users of the computer.
3 Create an SCCM package to deploy to your target systems, and notify users that the software package is available. See Create the SCCM Software Installation Package (page 21). NOTE Distribution of DirectX 9.0C to Windows XP by SCCM is not supported. For an Autodesk product to run properly, you must manually install DirectX 9.0C from the product media (\3rdParty\DirectX\DXSETUP.exe). This version of DirectX 9.0C is customized for use with Autodesk products.
package to users. The deployment process creates the files and instructions, but SCCM must be configured to use these files. To create a software installation package using SCCM 1 Click Start menu ➤ Programs, or All Programs ➤ Microsoft System Center ➤ Configuration Manager 2007 ➤ ConfigMgr Console. 2 In the Configuration Manager Console window, expand Software Distribution. 3 Right-click Packages ➤ Distribute ➤ Software. 4 In the Distribute Software wizard, click Next.
12 In the After Running drop-down list, select an action to take after the program has been installed. Your choices are ■ No Action Required ■ Program Restarts Computer ■ ConfigMgr Restarts Computer ■ ConfigMgr Logs User Off NOTE Some products require a system restart after installation. Click Next. 13 In the Advertise Program dialog box, select Yes to advertise the program to users. Click Next. 14 In the Select a Program to Advertise dialog box, select the package you want to advertise. Click Next.
Distribute Products Using Imaging Software You can use imaging software, such as Norton Ghost, to create a master image to distribute Autodesk products. Once created, the master image can be replicated to other computers throughout your facility. IMPORTANT Autodesk does not recommend or support the distribution of products using imaging software. However, if you plan to use this method of distribution, please review the following instructions carefully.
the product. Launch the product on the other machine, and register and activate it. Users have a trial period to register and activate the product on their machines. ■ Launch and customize the product as necessary. Create a master image and distribute it to users. If users’ computers are connected to the Internet, the product is automatically activated. Users whose computers are not connected to the Internet have a 7-day grace period to register and activate the product.
2 In Windows Explorer, copy the AdLM folder from the appropriate path shown below to a location other than the disc that will be restored. C:\Documents and Settings\All Users\Application Data\FLEXnet 3 Reformat the computer and restore the master image. NOTE Do not perform a low-level format of the hard drive. 4 Copy the AdLM folder that you created in step 2 to its original location on the reformatted computer.
Installation Troubleshooting 3 Installation Questions This section provides answers to some frequently asked questions about installation and deployment. For additional advice and assistance, go to Autodesk Support, click your product name, and search in the Knowledgebase for your product. Licensing Questions What is the difference between a stand-alone license and a network license? A stand-alone license supports one or more Autodesk products for an individual user.
What is the benefit of using a network licensed version of the software? Network licensing provides ease of license management for large drafting/design facilities, classrooms, and other environments that need to support many users. The Network License Manager provides centralized control of licenses, including their registration, activation, and distribution to users. One main advantage of a network license is that you can install products on more computers than the number of licenses you have purchased.
When should I select all products for the administrative image, and can I add products later? If you include all products in your deployment, the administrative image will be larger, but you will be able to modify the deployment or create new ones without restrictions. If you select the checkbox "Include only products required by this deployment configuration", the resulting deployment includes a subset of the available products.
When you merge a service pack, the service pack is merged into the administrative image. Once merged, a service pack cannot be removed from the administrative image. You can choose to append or merge service packs from the product configuration panel when creating a deployment. Where can I check if service packs are available for my software? To find out if a patch or Service Pack is available, visit the Support page for your product at http://autodesk.com/servicesandsupport.
Uninstall and Maintenance Questions How can I see what is included in a default installation? To see what is installed during a default installation, go through the installation process to the Product Configuration page. The products selected here are installed in a default installation. If you click a selected product box to open the configuration panel, you can see the default settings for subcomponents and features.
Do I need the original media to reinstall my product? Yes. When reinstalling a product, you are prompted to load the original media. If the product was installed from a network deployment, you need access to the original deployment, unaltered by later changes such as the addition of a service pack. When I uninstall my software, what files are left on my system? If you uninstall the product, some files remain on your computer such as files you created or edited (for example, drawings or custom menus).
Glossary 4 activate Part of the Autodesk software registration process, it allows you to run a product in compliance with the product's end-user license agreement. administrative image A collection of shared file resources created by the deployment process and used to install the program to network computers. deployment The process of installing Autodesk products to one or more computers on a network. hot fix Autodesk terminology for a minor application patch that contains a few code fixes.
silent mode An installation that proceeds without any explicit user input. No dialog boxes are presented that require interaction from the user.
Index A F administrative image 29 shortcut 10 advertising deployments 17 assigning deployments 17, 18 firewall and license server flags 15 30 G C glossary 33 group policies 17 verifying deployments group policy object (GPO) cleaning hard drives 26 client computers assigning deployments 18 restoring master systems 26 verifying deployments 20 configuration 5 defaults 31 customized deployments 5, 8 20 18 H hard disks, cleaning 26 D I default installation 31 deployments assigning 17, 18 checklist 2
P K Knowledgebase profiles, user 27 29 L R language pack, adding 19 license server models 4 license types 27 redundant license server model reinstall product 31, 32 restore damaged installation 25 operating system 26 running scripts 16 M master images 24, 25 master systems 26 Microsoft Installer Patch files 6, 30 Microsoft System Center Configuration Manager 20, 21 MSP files 6, 30 multi-seat stand-alone installations 24 N network installations deployment 2 group policies 17 imaging software deploy
U V uninstall product 32 user profile settings 29 VBS files (installation script) 11 verifying group policy deployments 20 Index | 37
38
