1. © 2012 Autodesk The Enterprise Guide to Autodesk Revit Harlan Brumm Program Manager - Autodesk

2. © 2012 Autodesk Welcome! Harlan Brumm Autodesk, Inc. @HarlanBrumm #AU2012 blogs.autodesk.com/revitclinic

3. © 2012 Autodesk Agenda  Planning  Building Deployments  Deploying  Hardware

4. © 2012 Autodesk Planning

5. © 2012 Autodesk User Personas

6. © 2012 Autodesk Questions  Do you need to create deployments for different groups of users based on discipline, software features, and settings?  What Revit out of the box content do you need?  How can / do you want to manage content?  How will you manage add-ins?  Where will user projects and files reside?  Which user settings do you want to specify?  Does your organization use Revit Server?  Do you need to create 32 bit and/or 64 bit deployments?  For network licensing, what is your license server type?  How do you want to distribute/access your licenses across your enterprise?

7. © 2012 Autodesk Testing Environment  Virtualization  Simulate your actual network  Test before implementing

8. © 2012 Autodesk Building Deployments

9. © 2012 Autodesk Deployment Best Practices READ THE REVIT NETWORK ADMINSTRATORS GUIDE.  Use short paths  Plan Revit Server  Do not use Create & Modify Deployment tool  Turn Off Any Security Software  Close All Programs  Turn Off UAC (User Account Control)

10. © 2012 Autodesk Revit.ini workflow  Install first standalone on test machine  Launch Revit  Configure  Locate and Save Revit.ini  Use option to include Revit.ini in deployment

11. © 2012 Autodesk Installing Hotfixes and Service Packs  Follow the README  Service packs can be extracted using  E.g:-  Sp1.exe /e sp1.msp  MSIEXEC /I sp1.msp  Hotfixes will be a compressed file

12. © 2012 Autodesk Setup Log vs. Install Log  Setup log is summary  Install log is detailed (Verbose)  Microsoft Windows install Log Analyzer (Wilogutl.exe)  Verbose log for silent GPO/SCCM installation

13. © 2012 Autodesk Revit content  2013 fixed 2012 content install issue  Un-selecting still installed  Clear %temp% prior to launching install or deployment wizard  Content install checks web

14. © 2012 Autodesk Deploying

15. © 2012 Autodesk SCCM  Use Relative path to the “Adminimage” folder as documented  SYSTEM account has no restriction applied using custom policies  Packages can take longer to propagate to the Distribution points due to the size  Please note the /W in the command line  Command lines available in “SMS_SCCM Scripts” folder of the deployment  Failure of certain 3 rd Party pre-requisites might trigger a reboot

16. © 2012 Autodesk GPO  Advantages  Works well with deployment functionality.  Allows you to add custom files to a deployment.  Allows deployment to computers rather than to users.  Disadvantages  Prohibits the passing of command-line parameters to an MSI executable. You must use scripts instead.  Prohibits customization of application settings, other than what is set while creating a deployment.

17. © 2012 Autodesk Batch Scripting  Command line access  Scripting Install and additional functions and items  Roll your own

18. © 2012 Autodesk SETUP.INI  Controls the Install Process  Pre-requisite command lines  Install Sequence for Prerequisites

19. © 2012 Autodesk Batch files for Add-ins OptionDescription Wait or w The first setup instance waits for the installation to complete. This flag is used to support Microsoft SCCM installation. Script or tInstall from the command line or using a script. Reboot or oA reboot is enforced at the end of the installation. Quiet or qPerform a silent installation, with no user interface. BasicUI or qb Perform the installation with a minimal user interface (the progress bar and a Cancel button). Users can cancel the installation, but no user interaction is required to complete the installation. Remove or rRemove the product. ProductCode or P Pass the command line to an installer. Command or cPass the command line to an installer. Language or lang Set the language for the products to be installed. msilog or mlTurn on verbose MSI logging for stand-alone installations and deployment creation. This information can be helpful when troubleshooting.  Options for command line  Based on the add-in  Not all supported

20. © 2012 Autodesk Imaging  Hardware type  Each machine type: create separate images.  License model  Network licensing and license servers.  Standalone possible but not recommended

21. © 2012 Autodesk Hardware

22. © 2012 Autodesk System Requirements http://usa.autodesk.com/revit/system-requirements/

23. © 2012 Autodesk Processor  Speed  Cores – Revit is multi-threaded  Rendering  File open  Etc.

24. © 2012 Autodesk Hard drive SSD = Speed

25. © 2012 Autodesk Memory 20X file size More… not faster

26. © 2012 Autodesk Graphics Card Go HereHere

27. © 2012 Autodesk OS  System Requirements  Not yet…

28. © 2012 Autodesk Network bandwidth  Critical for Revit Server implementations  Network acceleration will help (River Beds)  The better the bandwidth, the better for Revit.  Network latency should not exceed 100ms

29. © 2012 Autodesk Servers  File /Content servers  Windows based  HD speed  License Servers  Bandwidth  Whatever is supported  Don’t do Redundant configurations

30. © 2012 Autodesk Thanks! @HarlanBrumm #AU2012

31. © 2012 Autodesk Autodesk, AutoCAD* [*if/when mentioned in the pertinent material, followed by an alphabetical list of all other trademarks mentioned in the material] 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. Autodesk reserves the right to alter product and services offerings, and specifications and pricing at any time without notice, and is not responsible for typographical or graphical errors that may appear in this document. © 2012 Autodesk, Inc. All rights reserved.