1 Making the move to a New Autodesk Inventor Presenter: Steve Warren D3 TECHNOLOGIES MA105-3P This session will dive into the best practices for moving from your current version of Inventor to the newest version. Key Topics: -Migrating Templates and Styles Libraries -Content Center Considerations -Software Deployments -File Migration -Task Scheduler Target Audience: CAD Administrators deploying Autodesk Inventor 2008 About the Speaker: Steve is a Senior Solutions Engineer for D3 TECHNOLOGIES in Tulsa. He has used Autodesk software since 1998 in various industries including custom sheet metal, consumer goods, custom retail fixtures and process facilities design. At D3 he is an Autodesk Certified Inventor Expert and Autodesk Manufacturing Implementation Certified Expert (MICE). In addition to his extensive knowledge in Inventor, he is also skilled in AutoCAD Mechanical, AutoCAD Electrical and Data Management. In 2006 he was a speaker at Autodesk University and also received an award for the most improved Solutions Engineer of the year from Autodesk.
3 What is the purpose of this class? As we all know, today implementing a new software package consists of much more than just installing the software. Things such as server client structures, deployments, multi-user libraries, and even Windows user permissions have made this task much more complex than it used to be in the past. More than ever, time is money, so taking weeks or days to test new software in a controlled environment isn t a luxury afforded most CAD Administrators. This class is intended to cover not only the installation of the new Autodesk Inventor, but to discuss, explain and work through the benefits as well as the drawbacks of all the options available to today s CAD Administrator during the implementation process. What will we cover in this session? 1. Software Environment Overview This section will be a quick overview of the overall environment of the Inventor software. New users and administrators to the Inventor software may not understand the purpose and involvement of all the modules and utilities of Inventor. Understanding all of this before attempting to implement the software is vital for success. 2. Migrating Templates and Styles Libraries Many problems and errors can occur if the proper migration of templates and styles libraries does not take place. This section will cover the proper way to complete these tasks. 3. Content Center Considerations Content Center can be configured in different ways which may be different in single-user environments versus multi-user environments. Add the new functionality of being able to run Inventor 11 and Inventor 2008 side by side into the mix and it s enough to confuse Sean Dotson himself. This section will help clear up any questions that might come up when planning your installation of Content Center. 4. Software Deployments Software Deployments have been widely used for installing past versions of Inventor with network licensing, but creating deployments to install standalone licensed software is also possible saving all administrators time and hassle. This section will highlight on the settings while creating deployments and discuss the benefits of creating and maintaining deployments for both network and standalone software. 5. File Migration Though migrating all your data isn t a requirement for Inventor 2008, it is a good idea. This section will walk you through the steps necessary to properly migrate your existing data for best use with Inventor 2008.
4 6. Task Scheduler This section will discuss the proper way to use the task scheduler to migrate your data for you. We will also discuss the settings and some tips to making the task scheduler work best for migrating your data. Software Environment Overview Before diving into implementing Inventor, let s take a look at some of the systems that are affected by the settings that need to be changed and/or files that will need to be migrated. This section will only provide an overview of these systems, not an in-depth exposure Styles Library.pdf Project files To make it simple, look at the project file as simply a mapping file that tells Inventor where to look for files. If you have an ipt part file named my-part, Inventor will look to the project file to find out what folders to look for the file my-part.ipt. In addition to handling these mapping functions for Inventor, it also controls where Inventor looks for templates, styles libraries, and also the location where Content Center generated ipt files are stored. The project file also controls what Content Center libraries are available. To find more information on project files, search the Inventor help system for projects. Styles libraries Styles in Inventor control the format and characteristics of objects inside of documents. Examples of this might be dimensions inside the Inventor drawing or color inside the Inventor part. This collection of styles is kept within the Inventor document, but it is also possible to create a library to store this collection of styles on the network. By using a styles library, it allows users to maintain styles in one location keeping all documents uniform and meeting certain standards. For more information on creating and maintaining styles libraries, read this whitepaper: Styles Library.pdf Content Center The Content Center is a database based functionality that gives the Inventor user the ability to search through a massive amount of standard content such as fasteners, standard shapes, standard pipe and conduit fittings, etc. Management of this system is discussed below in the ADMS section. Since this is a database driven system, there are no pre-created ipt files for all these components. They are created as the Inventor user uses them in an assembly or part file. Once it is used, Inventor will create the ipt from the information in the database on the fly. Once it is created, Inventor needs to know where the user would like to store this ipt. It finds this in the setting for Content Center Parts in the project files described above. It is important for this location to be on the network in a multi-user environment so that users can share designs appropriately. If this were set to the local drive of a machine, one user could create the content in an assembly and if another user were to open that assembly, they would get an unresolved link error because the software can t find the ipt for that component on that particular local drive. Autodesk Data Management Server The Autodesk Data Management Server is often referred to as just ADMS. Last year it was version 5 and referred to as ADMS 5. With the new releases following the yearly theme of AutoCAD, the new version is called ADMS The Vault and Content Center functionality are both database based utilities. While discussing ADMS, we will refer to Vault databases
5 as databases and the Content Center databases as libraries. SQL handles the Microsoft database management tasks in the background, but ADMS is Autodesk software that is the interface where administrators handle tasks like new database creation, attaching and detaching of libraries and databases, backup of libraries and databases, and user creation and management. This software is typically installed on a server unless you are an individual user, in which case you would have the option of installing it locally since no other users should need to access the data from this software. This ADMS software is required if users plan on taking advantage of the Content Center functionality. All of the Content Center databases in the ADMS are read only as they are standard components. In order to modify the data, an administrator must create a user library in ADMS for use within the Content Center of Inventor. Once this is done, a user with the Content Center Editor rights will be able to copy content from the standard libraries into the new user library and edit it in that library instead. Migrating Templates and Styles Libraries Before creating any new data from Inventor 2008, we first must make sure that the Templates are migrated. If styles libraries are used, there will be a relationship between those styles and the templates, so they will need to be migrated as well. The order in which they are migrated is not of concern. In this section we will also discuss how to migrate a project file as it will need to be migrated as well. Before deciding to migrate these components of Inventor, you must first decide if you wish to run Inventor 11 and 2008 side-by-side or if you are going to fully move forward to Inventor Once these components are migrated to 2008, Inventor 11 will not be able to use them. If you wish to run version 11 side-by-side with 2008, then making copies of these components, and then migrating the copies is the best method. Some changes have been made to Inventor 2008 that need to be discussed before exploring the methods used for migrating templates. With previous versions of Inventor, file migration automatically took place upon the opening of legacy files. This has been changed with Inventor 2008 in order to save system resources and time when opening files. With 2008, no file migration takes place during the open process. Instead, the file migration happens during a save of legacy files. There is also a new check box option in the applications options dialog box on the Save tab for Prompt to save for migration. If this option is checked, then no changes have to be made to the legacy file for Inventor to prompt to save the file. Of course, if you say yes to this dialog box, then the file will be migrated. If this option is not checked and no changes have been made to the file, Inventor will not prompt for you to save the file upon closing thus resulting in a non-migrated file. Obviously this setting is vital while trying to migrate data.
6 Migrating Templates Migrating templates is as simple as opening them in Inventor 2008 and saving them. If the setting in application options is checked then simply opening and closing the template will prompt for the save in order to complete the migration. The task scheduler can be used to migrate templates and project files, but the preferred method is to migrate them manually to insure that there are no errors. Since there are generally a low number of templates, doing them manually is not a problem. If Autodesk Vault is being used (and the templates are in the Vault), then the preferred method is to first upgrade the Vault server and client, then check out the templates, migrate them, then check them back in. Migrating Project Files To migrate a project file two things must happen first. First, if Vault is not being used and the project file is located on the network, then all users must switch to a different project or shut down Inventor so that the file isn t being referenced by any instances of Inventor. If Vault is being used, then the project file needs to be checked out. Second, all documents must be closed in the Inventor session that is being used to do the migration. By accessing the project dialog box through the File menu, you can browse to load the project you wish to migrate if it is not already loaded. To finish the migration simply hit the Save button. A dialog box will appear warning that after this migration is complete that Inventor 11 will not be able to use this project file. Hit Yes to continue and the project file migration is complete. Migrating Styles Libraries There is a utility that will be used for migrating the styles libraries. This utility is called the Style Library Manger. You can access this utility by going to the Start Menu All Programs Autodesk Inventor 2008 Tools Style Library Manager. The first step is to load your style library into this manager. To do this select the browse button near the top center of the dialog box in the Style Library 1 section. Browse to the folder location where you library is stored as seen in this picture to the right.
7 Once your style library is loaded you will notice a message near the bottom of the dialog box that says Some style collections require migration Migrate before editing. The next step is to select the Migrate button below the message. Upon selecting this button, there will be a confirmation message listing the styles that will be migrated. Once you select yes to continue with the migration, the manger will migrate all the styles listed and also some additional tasks. These additional tasks are due to some changes to Inventor There have been changes to the way that the Frame Generator works among other operations along with changes to the spreadsheet that controls threads. In past versions of Inventor, the styles library consisted of only a folder with xml files to control the styles. Now there are these files, plus some additional folders for controlling the Frame Generator and others. There are also two additional spreadsheets. The threads spreadsheet has been moved to this directory as well as a new spreadsheet for controlling clearance of threaded features. After the manager is done migrating the styles, it will automatically copy the default folders and spreadsheets from the hard drive to this Design Data folder that holds your styles library. It will show a process dialog box like the one to the left. Once this is done, you will need to make changes to this new spreadsheet for threads to match any changes that you had made to the spreadsheet for Inventor 11. It does have a different format, so just overwriting this spreadsheet with the one from Inventor 11 will not work. Once all these tasks are complete, then your styles library should be fully migrated to work with Inventor Your Design Data folder containing your migrated styles should now look like the one pictured here:
8 Content Center Considerations There can be several different scenarios to consider when looking at a Content Center install. These include a new install (not upgrading from an older version of Inventor), upgrading from a version of Inventor older than Inventor 11, and upgrading from Inventor 11. As stated above, most installations of Content Center are on a server rather than a local workstation to help standardize data in a multi-user environment. Throughout this section, discussions will be based on a server install of Content Center but most functions behave the same for a workstation install. Also, system requirements for ADMS 2008 are listed below. This information is also available on the Autodesk website on the Inventor page. Though it is possible to migrate Inventor 10 Content Center libraries into ADMS 2008 (see the whitepaper on this at and navigating to the Whitepapers page), in this section we will consider that any Content Centers older than 11 be uninstalled and the new Content Center be installed fresh. In the scenario of a new install or an upgrade from a version older than Inventor 11, this is simply a matter of installing ADMS 2008 on the server considered to be the host for the Content Center. This is done by inserting the DVD in the server and selecting to install both Autodesk Data Management Server 2008 and Content Center Libraries on the product selection screen. This dialog box can be seen on the figure on the next page.
9 In the scenario of upgrading from Inventor 11, again a decision needs to be made if Inventor 11 is planning to be ran side-be-side next to Inventor An overview of how this accomplished is provided here, but if more information is needed, you can reference the documentation provided on the installation DVD by running the install and selecting Documentation in the bottom left corner of the dialog box. There is a pdf that provides great detail in this process named CC_2008_and_R11_side_by_side_install. The first step in this process is to backup any Vault and custom Content Center libraries in ADMS 5. Once these backups are complete, un-install ADMS 5 through the add/remove programs in Windows. Do not remove the Microsoft SQL Server Database Engine (AUTODESKVAULT) or remove the existing database files from the machine. Next, insert the DVD and let the install autostart. Once you reach the product selection screen, select both Autodesk Data Management Server 2008 and Content Center Libraries to install. Upon completion of installing ADMS 2008, a dialog box stating that some libraries need to be migrated will appear. Select to open the ADMS Console to migrate the database at this time.
10 A new dialog box will appear giving options for which versions of Inventor are to be used with the Content Center Databases as seen to the right. Choose Inventor 11 and Inventor 2008 and select OK to utilize the side-by-side functionality of both Inventor 11 and Inventor After the ADMS Console is complete with the migrations, it will display the libraries listed on the left side of the console. You will notice two copies of each library, one named as it was before, and one with the prefix AI2008_ before each name. The last step to running Inventor 11 and 2008 side-by-side is to install a client upgrade for the Inventor 11 installations to communicate with the new ADMS This upgrade will have to be installed for each Inventor 11 client who wishes to use the Content Center or Vault. Making the move to a New Autodesk Inventor
11 Software Deployments Before discussing the details of creating deployments you must first check to make sure all client machines meet the system requirements for Inventor Below is a list of the accepted operating systems that work with Inventor 2008 and hardware requirements (copied from the Autodesk website as of Oct 31 st, For up to date requirements visit ): Windows 2000 Professional SP4 (2) Windows XP Professional SP2 Windows XP Professional x64 Edition (3) Windows Vista Business (3,4) Windows Vista Enterprise (3,4) Windows Vista Home Basic (3,4) Windows Vista Home Premium (3,4) Windows Vista Ultimate (3,4) (1) For single user local installations of Autodesk Inventor with Content Center functionality and/or Autodesk Vault Click here for Autodesk Data Management system requirements for remote installations. (2) Autodesk Inventor 2008 is the last release for which Windows 2000 Professional will be an officially supported operating system. (3) Autodesk Inventor 2008 and Autodesk Vault 2008 applications are supported to run compatibly as 32-bit applications on 32- or 64-bit operating systems. AutoCAD Mechanical 2008 and Mechanical Desktop 2008 are supported as 32-bit applications on 32-bit operating systems or as 64-bit applications on 64-bit operating systems. AutoCAD Mechanical 2008 and Mechanical Desktop 2008 applications are not supported and will not install as 32-bit applications on 64-bit operating systems. (4) Official support for Windows Vista requires Service Pack 1 for Autodesk Inventor Hardware Requirements Recommended For part & assembly design (less than 1,000 parts) For large assembly design (more than 1,000 parts) RAM 1+ GB 3+ GB Graphics 128+ MB Direct3D 9 or OpenGL Capable 128+ MB Direct3D 9 or OpenGL Capable, Workstation Class CPU Intel Pentium 4 or AMD Athlon or later, with 2 GHz or faster processor; or compatible Intel Pentium 4 or AMD Athlon or later, with 3 GHz or faster processor; or compatible Free Disk Space (for installation) 3.5+ GB 3.5+ GB Also, before installing Inventor, update the graphics card driver with the latest approved driver from the Autodesk website. The Autodesk Inventor Hardware Site (http://www.autodesk.com/inventor-graphiccards) will have the latest information on approved cards and approved drivers for use with Inventor. When downloading don t forget to get the latest configuration database and over-write the default configuration installed with the software.
12 The first step in creating a deployment is to create a share location for the admin image to be created. This shared folder/location will have to be accessible by all workstations that are desired to run the deployment. You will need full permissions to this folder in order to create a deployment also referred to as an administrative image. It is recommended to name this folder Deployments and create a subfolder underneath it named Inventor2008. No spaces are allowed anywhere in the deployment path. Instead use an underscore if needed. It is also not possible to move a deployment to a different folder or different share name without modifying the image. Because of this, it is best to plan on not moving this deployment after it has been created. After the share has been created, shut down any anti-virus or anti-spam software on the machine you are using to create the deployment. The deployment does not have to be created on a server; it can be created on any workstation with access to the share. It is also recommended to shut down any Microsoft Office product during the process of the deployment creation. The next recommended step is to copy the DVD media to the hard drive of the machine being used to do the installation. This will help reduce the chance of any communication errors during deployment creation, help speed up the deployment creation and eliminate the need for someone to watch the deployment to switch media when needed. The easiest way to copy the media is to use Windows Explorer, create a temporary folder on the local hard drive for this media. Explore the media for disc one and select all files on this media. Copy this to the temporary folder location on the local workstation. Once that is complete, switch the media to disc two and copy all folders and files to the same temporary folder location. When Windows asks you to over-write files, select Yes to All. After this is complete you can run the Installation Wizard by simply double-clicking the setup executable file (setup32.exe for 32 bit operating systems and setup64.exe for 64 bit applications). New to Inventor 2008, you no longer have to install any software to the machine that is being used to create the deployments. In the past, you had to install an application called Deployment Wizard on the local machine being used. With 2008, the wizard runs right from the setup. Once the setup has finished loading (this can take a few minutes for the setup to load), you can select the middle option for Create Deployment. The next window will ask for the deployment location, deployment name and an option for the installation to be silent or not. Use the shared folder that was created earlier and create a name for this deployment like AIS2008_SP1. Remember to not use any spaces. The client silent mode is recommended. This means that during the installation of the product, there will be no options or dialog boxes that need any interaction from the user. This is a nice feature as you can start installs from deployment and walk away to do other tasks or work while it does the installation.
13 The next window will display options for which software you wish to include in your deployment. You should see four options. One for Inventor 2008, one for AutoCAD Mechanical 2008 (this also includes Mechanical Desktop and Vanilla AutoCAD as well), Autodesk Vault 2008 (Client application, not the server portion), and Design Review Select the products that you wish to include and select next in the bottom right. The next window will be for your first and last name, company name, and also the serial number for your product. Even if you have a standalone version of software, you can request a multi-seat standalone serial number. This means that you could have one serial number or group number, and have as many seats or license apply to that serial number that you wish. This is important for deployments since the deployment can only have one serial number assigned. The next screen will give the option for two different log files. It is recommended to use both a network log and a client log. A client log is simply an installation log that is created in the temp directory of the client machine. If there are errors during a silent installation and it fails, this is the best way to identify what went wrong so that it can be fixed. The network log will keep track of all the clients that have used the deployment to install software on their machines. The next window that appears will allow you to configure each product you have selected to install. Simply select the product you wish to configure and select the configure button. Once you select configure, a new dialog box will appear with each application having a tab across the top. Select the Inventor tab and it will allow you to select between a stand-along license or a network license. If you have any questions about which license type you have or questions about the different configurations for a network license, select one of the questions on the left side of the dialog box. This will bring up very helpful information about any of those questions. The next couple of windows will allow you set typical installation options with Inventor such as if Internet Explorer will be required for the deployment to be ran on the client s machine or if part modifications will be allowed from Inventor drawings. After this there is a window allowing a user to add additional files to the deployment. This is especially useful for people with custom programming that normally have to copy these files to each workstation
14 after all software has been installed. With this, you can add these files to the deployment and all the work will be done for you. The default installation directory is added as a folder for you. If you don t wish to add files to that directory, simply create a folder on the machine where you are creating the deployment from and add all the files to that directory just as if you were adding them to a workstation after an installation. Once that is done, select Add Drive to add the local drive, then select Add Folder to create any subfolder structure needed. After that is complete select the browse button at the top right of the window and select the files you wish to add. The next screen is one of the most important. Everyone hates having to install software on multiple machines, but it seems even worse when you have to add all the latest service packs to the machines after installing all the software. This screen will allow you to add service packs to the deployment so this doesn t have to be done anymore. The service pack has to be in.msp format to be added to the deployment. Most times, Autodesk will package the msp inside a service pack executable file, so this msp will have to be extracted. To do this, go to Start Run and type in the service pack location path\service pack name, then a /e switch at the end followed by the name you wish it to be extracted to. An example of this would the service pack one for ADMS2008. This patch needs to be applied to both the server portion and the client portion. This means that it should be applied to a deployment that includes Vault To extract this, you would download the exe service pack to the local drive like C:\, then you would type in C:\ADMS2008_SP1.exe /e C:\ADMS2008_SP1.msp and select run. This will extract an msp file from the exe file downloaded. This can now be used during the deployment. There is also an option to append or merge a service pack to a deployment. If you append it, it will install the software, then run the service pack right after. If you merge it, it will change the deployment so that the first time it installs it is correct. Merging the service pack is the recommended method. I see no reason to install files only to turn around and change them with a service pack. After the service packs have been configured, there are a couple of screens with options for the communication center and online resources for Inventor. Once that is done, you can click the configuration complete button, then the create deployment button to start the creation of the deployment. Creating the deployment can take quite a bit of time especially if your network is slow. There is a lot of data being created and copied. Be patient once the deployment creation starts, it will also seem like it is stuck on a certain area and that the status bar doesn t change, but trust me it is still working and it will finally show up with a Deployment created successfully screen to let you know it is complete. The screenshot to the left is what you will see in your deployment dialog box while it is working to create the administrative image. As it works through required services and installations, it will replace the dots with check marks.
15 After the deployment has been created there is still some work to do. There is a hot fix for Inventor 2008 to fix an issue with copying 2D dwg data to an Inventor sketch that results in an End of Evaluation Period error. This hotfix can be downloaded here: If you read the instructions for this hotfix the process is to un-install Autodesk OEM View 2008 and reinstall from the downloaded files. The best way to fix this is to download the files after the deployment has been created, then copy all those files and over-write the files that were created in the deployment directory. They should be located in \\<server name>\deployments\inventor2008\adminimage\support\aoemview2008\. Once these are replaced, the deployment will install the latest updated version of OEM View so the error will be fixed. Another suggestion is to download the correct database configurations for most standard video cards. This is mentioned above in the section for the Inventor requirements with the link to the webpage. If most video cards are the same, then the database files can be added to the deployment just like the OEM View files were. Additional information on network utility installations and recommendations can be found on the documentation on the media. The documentation is called Autodesk 2008 Network Administrator's Guide. File Migration Of course the first step before migration of any data is backing up that data. Always make sure that you have a good backup before attempting to migrate data. Once you have a good backup, you can begin the migration process. Did I mention that you need to backup your data? In the section about migrating templates I mentioned some changes that have been made to Inventor 2008 when it comes to migration of files, but it is worth mentioning again. With previous versions of Inventor, file migration automatically took place upon the opening of legacy files. This has been changed with Inventor 2008 in order to save system resources and time when opening files. With 2008, no file migration takes place during the open process. Instead, the file migration happens during a save of legacy files. There is also a new check box option in the applications options dialog box on the Save tab for Prompt to save for migration. If this option is checked, then no changes have to be made to the legacy file for Inventor to prompt to save the file. Of course, if you say yes to this dialog box, then the file will be migrated. If this option is not checked and no changes have been made to the file, Inventor will not prompt for you to save the file upon closing thus resulting in a non-migrated file. Obviously this setting is vital while trying to migrate data. With manual file migration it is easiest to open large assemblies that you plan to work on that need migrated. Make sure that the option for prompt to save for migration is checked and open the assembly that needs to be migrated. Click save and Inventor will display a dialog box with all the non-migrated parts listed with the option to save them or not. Select yes to all to migrate all part and subassembly files that are referenced by
16 this larger assembly. This is the easiest, fastest way to migrate older Inventor data into the 2008 release of Inventor. Task Scheduler The Task Scheduler is a utility that is installed by default with Inventor 2008 that can help complete repetitive tasks much easier than a user could manually. You can run access the task scheduler by selecting Start Menu All Programs Autodesk Inventor 2008 Tools Task Scheduler. There are several tasks that can be completed by the task scheduler, but for this session we are going to concentrate on the Migrate Files task. Rather than opening assembly files and manually updating the files, we will examine how we can use this utility to do this for us overnight or over a weekend. After the task scheduler is open, select Create task from the menu and select Migrate Files from the drop-down. Once this complete it will display a Migrate Files dialog box. In this box there are four main areas of concern.
17 The first is the Project File selection. Select the browse button to select the applicable project file for the files that you wish to migrate. The next area of concern is the Add Files Selection. There are three different options for adding files, add files, add folder, or add an entire project. The recommended method is to use the add files selection. In the log file settings you can select where you want the process log to be saved after this task is complete. If this is set to run overnight, you won t have any idea of what was successfully migrated and wasn t if you don t create a log file. The last section to look at is the Time Selection area. This is where you can set a start time and date for this task to start. Once this is all set, you can also set the options by selecting the options button at the bottom of the screen next to the OK button. Options include Total Rebuild, Skipping files that are already migrated, skipping files (assemblies mostly) with unresolved references and Set Defer Updates. Once all these are set, select OK and then OK to create the task. Once the task is created it should be listed as a row in the Task Scheduler. Some guidelines for best results with Task Scheduler: Separate data into manageable groups Migrate part files first, then subassemblies, then top level assemblies, then drawings Setting the option for Total rebuild will take longer for the task to complete but reduce the chance of errors Wrapping Up In this session we have provided an overview of the general steps that need to be taken to make an implementation of Inventor 2008 successful. There is a plethora of information available on the media for many, many different installation scenarios that an administrator might encounter. As always your local Authorized Autodesk Reseller should be able to provide some assistance and/or recommendations to help you along the way.