Faster Deployment Experience for Revit 2021.1

Product news

By Danny Polkinhorn

The Autodesk® Revit® 2021.1 release features a new end-to-end modern deployment experience for administrators that significantly improves the speed and reliability of your product installations.
Time to create a deployment with the new online deployment experience vs. time to create a deployment with the Old Deployment Wizard

You may have already seen parts of this new deployment experience with 3ds Max and Maya, but let’s take a closer look at the experience you will see with Revit 2021.1. A faster deployment experience allows your users to get up and running more quickly than ever beforeWith the old Deployment Wizard, you had to download the entire product (or worse, an entire Suite of up to 45GB)  before you could even start creating the deployment. The online deployment creation tool makes it fast to configure, and more importantly fast to download only what you want in the deployment (image below).Unselected items will not be downloaded and included in the deployment. 

[IMAGE: Deploy only what you want with Revit 2021.1.]

Some deployments are three times faster to create from start to finish. Deploying to computers is also faster, as the installer is up to twice as fast as prior versions. We’ve also made it significantly easier to get updates into a deployment. You can simply specify what version of Revit you want in the deployment, and we will automatically include exactly what you needNo more hunting around for updates to include in the deployment. When you deploy out to your computers, it will determine what’s on the machine and install only what is necessary to get the machine to match what’s specified in the deployment. For new computers, it will install everything.  For machines that already have what’s in the deployment, it will simply exit quickly.

[IMAGE: Specify the version of Revit you want and deploy without having to hunt for updates]

The new deployment experience is also much more reliablemeaning that installs finish successfully the first time and uninstalls actually remove everything that was installed. The new installer does a better job of keeping track of installed items and successfully cleans the machine afterwards. We’re also minimizing the impact of prerequisites to make sure they are installed with fewer errors. 

You might be asking: “What happened to the old Deployment Wizard that came with Revit 2021?” Frankly, it’s going away soon. If you already have a deployment for Revit 2021 that you created using the old Deployment Wizard, we recommend that you continue to use that deployment for your Revit 2021 installations to all your computers. You can add Updates (more specifically, Patch Updates) by downloading and modifying your existing deployment to include them as you have done in the past.  

We also recommend that you take a look at the new online deployment creation tool by creating a deployment in a new local folder, and take a look at how it can work for you. Notice that you only have the option of Revit 2021.1 or later with the online tool. Next year with Revit 2022, the downloadable installer will no longer include the Deployment Wizard. The online deployment creation process will be the only option. 

These new tools and processes are early versions and we are constantly working on improvements. I’m super excited about what our vision looks like because I know it will improve how you manage deployments, saving you time and effort.  At the same time, we realize that changes like this can take time and energy for both IT staff and the CAD/BIM/App Managers out there. We’ll do our best to keep you informed of what’s happening, provide documentation, and most importantly set expectations for you so you’ll know what to do when change arrives. We look forward to solving many of the installation challenges you have been having over the years. 

Related Articles

Add comment

7 comments

  1. itservicedeskQFP8W

    Not sure if anything that needed fixing is fixed here; we create one deployment to serve many, the time it takes to create said deployment does not matter. The problems have always been with clean, silent, automated removal. This change had only created me more work to test and adjust the 850+line powershell script templates I'd created to get rid of the software. Heads up to anyone powershelling here, you don't need to use the network uninstall string noted in the batch file, the local string with a quiet switch inserted works fine, e.g. $Revit = 'C:\Program Files\Autodesk\AdODIS\V1\Installer.exe' $RevitArgs = @('-i', 'uninstall', '-q', '--trigger_point', 'system', '-m', 'C:\ProgramData\Autodesk\ODIS\metadata\{AA3C5F33-570B-3989-8542-D5DC0F759221}\bundleManifest.xml', '-x', 'C:\ProgramData\Autodesk\ODIS\metadata\{AA3C5F33-570B-3989-8542-D5DC0F759221}\SetupRes\manifest.xsd', '--extension_manifest', 'C:\ProgramData\Autodesk\ODIS\metadata\{AA3C5F33-570B-3989-8542-D5DC0F759221}\setup_ext.xml', '--extension_manifest_xsd', 'C:\ProgramData\Autodesk\ODIS\metadata\{AA3C5F33-570B-3989-8542-D5DC0F759221}\SetupRes\manifest_ext.xsd') $RevitHolder = Start-Process -FilePath $Revit -PassThru -ArgumentList $RevitArgs $RevitHolder.WaitForExit() Then just manually or with a script, locate all the left overs in the registry and kill those off via their uninstall string. The old packaging process at least gives us some of the uninstall strings, but most importantly gave the order, as removing things out of order can break a components uninstall. For MECM, if using the product guid as detection, it’s not the guid used in this adsk uninstall string, it’s the other one sitting in the registry, or query wmi/cim to find it, this is the same for 3Ds. Once I’d adjusted the scripts however, this new uninstall method does require less copy/paste as it does uninstall more components and the left overs seem to clean out just fine; so, there’s that.

  2. Darrell.shand

    Hi Is there any way you can publish the documentation for setting up your new deployment method for SCCM installs. We use both the standalone (named) install method and a network install. The current documentation isn't very clear on how we can achieve this with your new deployment method. Thanks.

    1. Danny Polkinhorn

      Hi Darrell, There is documentation available, but not yet in the Revit help. You can find the documentation that applies to all products using the new online deployment configuration referenced here in the 3ds Max help. Create two deployments, one for each license type, with the same product and settings. After you have the two deployments, you can take the deployment.xml and the "Install...bat" file from the second deployment and move it to the first one. Edit the second batch file to change the paths to the first folder. Then you can delete the second deployment folder. The ability to combine multiple deployments with minor configuration changes between them is on our roadmap. Hope that helps, -Danny

  3. mark.couch

    I'm not finding the new deployment particularly reliable and certainly it was not efficient. There was no clear notification to account holders of this new deployment method. I wasted a lot of time downloading the Revit 2021 installer to find there was no option to create a deployment and only after studying the Autodesk portal did I stumble onto the deployment option and start a configuration. The portal process itself seems straight forward but having completed my choices and downloading the newly created deployment when the batch file is run on a local PC it fails with the vague message it has failed consult your administrator! - I've tried running from a network server and from a local device, amending the paths in the batch script accordingly. The deployment page provides no information about how to configure or run the batch script or where to look for errors.

    1. Danny Polkinhorn

      Hi Mark, thanks so much for your feedback. Please note that if you already have a 2021.0 deployment, we recommend keeping that one up to date using the same process you always have. Also, your comments that discoverability of the new deployment workflow is poor are spot on, and we are working on improvements there. Finally, if you're having issues with the install, please submit a support case so we can take a look at your logs. They are in %localappdata%\Autodesk\ODIS. Thanks again!

  4. lionel.kai@camara.us

    When will this be released to try out? All I see is an empty box and "We’re adding products to deployments over time...." We normally create separate configurations (using the same deployment) for "All Products" (in case someone needs Navisworks, etc.), "AutoCAD and Revit", and "AutoCAD only". Will this still be possible with the online deployment maker (without having 3x the AutoCAD installer and 2x the Revit)? Or will we now need 3 separate deployments (which take up more space)?

    1. Danny Polkinhorn

      Hi Lionel, If you have an active Revit, 3ds Max, Maya, or VRED subscription, you should see the deployment creation tool. If you should see it and are not, please submit a support request. We have made product deployments smaller through our more modern approach and only including what you want in the deployment. At this time, you will need separate deployments for the scenario you described, but we are aware that this is not ideal and will be working on improving it in the future. Thanks for your feedback, -Danny

Thanks for visiting the Revit blog. Subscribe to keep current on product updates, the Revit public roadmap, and a wide variety of topics in BIM.

Subscribe to keep up with Revit

© 2021 Autodesk Inc. All rights reserved