Cannot create deployment Revit 2021

[nguyenndSQN7Y]

Hi guys,

I am trying to create a deployment for Revit to be installed through SCCM. I just downloaded Revit 2021 and it came with 6 different files, I ran the executable to combine those into an installation file with setup.exe. I then run the Setup.exe to try to create deployment as I have done with AutoCAD, Inventor and Architecture. But, after running Setup.exe, it does not give me the option to create deployment, all I could do is a normal install as if I was going to install into that one particular machine. Have you guys seen run into anything like this with Revit 2021? or know a way to create deployment for Revit 2021?

Please let me know if you have any questions.

Thank you,

Nhan

[danny.polkinhorn]

Hi all,

I wanted to respond to the "WHY?" question.  First though, I want to acknowledge that the installer changes are significant (both for you and Autodesk) and we appreciate your patience with us.  Your concerns and feedback are very important.  As a long-time Revit user myself, this community means a lot to me personally.

We have received a LOT of feedback in the past from customers about the challenges with the old installer:

• Downloads and installs are slow
• Uninstall is often incomplete
• I don't know where to get my software, or takes too long to get to it.
• Deployments aren't optimized (too big)
• I want to install multiple products (looking at you Suites users)
• I don't know when updates are available
• Delivery of updates to my users takes a lot of time and effort

So, last year we embarked on a project to rebuild from the ground up to address these challenges, with a modern technology stack, a simplified installer, and streaming delivery.  Keep in mind that we're not the first software company to do this; Microsoft, Adobe, and others are ahead of us in this regard.

The installer and the deployment tool are the first parts (but those alone don't address all the challenges above).  Having an online deployment configuration tool allows us to iterate quickly, add new features, and address issues.  We're far from done.  Some requested in this thread are already in progress (like removing ADA).  The new deployments are smaller, faster to create (3x), and faster to install.  We have been working very closely with Gerry and the Revit team on further optimizations coming with 2022 and beyond.  See the recent Revit blog post for more info, and our recommendation to continue using the old deployment wizard for this year if you wish.  Also, I go into more detail in my upcoming AU class (search "faster install").

To answer some specific questions:

• We dropped the ball on getting documentation out earlier.  It's standard for all products now, and shown in 3ds Max here.  Revit team is working on that for their help as well.
• If your install or deployment creation isn't working as expected, please create a support case and attach the logs from here: %localappdata%\Autodesk\ODIS.  It's the only way we can help you directly.  If you're not getting the right answers, ask them to escalate.
• The small file that downloads at the end of the online tool is NOT the deployment, it is a small executable that creates the deployment in the "Deployment image path" you specified.  It supports both UNC paths and mapped drives, and must have write access to them when you run the executable.
• 3rd party extensions/addons.  This year, we could only focus on the main Autodesk applications, and we may add support for this in the future.  There are many ways to install these that do not involve the Autodesk installer, such as scripts, SCCM, PDQ, etc.

Hope that helps,

-Danny

[opesch_]

Hi Gerry,

I agree with the others, You should never remove an old method until the new one is properly tested and documented !

The new method seems to be perfectly fine for the little companies that don't make use of the deployments ! Maybe you didn't get a lot of complains in the Summer because most of the companies that use deployments will do them after a few updates to correct early bugs (and merely because the old method was not that good at pushing updates to the users who doesn't have admin rights especially when they use SCCM) and Beta testers will not test a deployment using a beta version on their user's PCs.

• Download now method
  1. Download the package that can be extracted but result in a single user direct installation.
  2. Cannot set the content installation path
  3. Many located contents are missing (French, Dutch,…)
  4. Cannot install content without Revit
  5. Cannot disable some addins (ADA and Worksharing Monitor)
  6. Do not ask for ADA download folder
  7. Require a computer restart
• Deployment Method
  1. Have to set the NLM server but cannot configure the deployment name to identify different setups
  2. Cannot be deployed to a network location but need to download to C:\ and then said the folder isn’t available !

[huotger]

Opesh,

Thank you for your observations.

The classic installer for Revit 2021 is available as a direct download from https://ava.autodesk.com if you prefer that workflow.

For the new install experience via Download Now, the experience is definitely simplified for single installation users whom are in PC environments which are not managed.

- Content location can be specified on the Choose where to install page.  However only a single Content Location can be specified, this path with be utilized as the based location for all the Content installed, regardless of Content type.

- As specified in the Revit 2021 online help, Default content is not installed with software installation. Only the core content (templates and sample files) needed to run the software is installed during software installation. Base families for US, UK, and German can be selected during installation. Additional content can be downloaded from: Content Download Page .  This change occurred to drastically reduce installation time and success caused by an outdated content pack installation framework.

- While some components like ADA and Worksharing Monitor have not been provided as optional install components in past Revit releases, in Revit 2021 we did move the FormIt addon and MEP Fabrication configurations to no longer be optional.  Again this was done with the non-managed PC environment in focus.

- As with any installation which requires some Microsoft based prerequisite applications, those applications may require a reboot after the product installation completes.  Without knowing more, I suspect that this may be the case in your environment.

For the new Deployment experience:

There are modifications which can be made to a deployment image once downloaded into your environment, these processes would be similar but different than modifying a classic deployment image once created.  If your install or deployment creation isn't working as expected, please create a support case and attach the logs from here: %localappdata%\Autodesk\ODIS.  It's the only way we can help you directly.  If you're not getting the right answers, ask them to escalate.

I hope this helps,

Gerry

[Patrick.De.Neef]

Hello

@danny.polkinhorn: thanks for the information about the location of the log files, at least we know where to look when things go wrong 🤔

My current status:

Revit

I managed to download the "old" Revit installers from the AVA site and created/tested an image (with patches 2021.1 and 2021.1.1). Everything looks OK, I'll now modify the image to include some localised libraries and see what happens

3DSMAX

The download files on AVA are also in the "new" format so I'm completely stuck here as the image that I created on the accounts site refuses to download to F: (which worked perfectly for Revit and is apparently supported ??) and I am not going to travel the whole country to install over 40 workstations manually

I agree that the old methods of installs and images had to be updated but Autodesk should not have been done without intensive testing, warnings and documentation

Autodesk is using customers in full production as test "victim", this is not acceptable

Regards

Patrick

[danny.polkinhorn]

@Patrick.De.Neef , can you give me the case number that you submitted with the logs for the F: drive issue?

[Patrick.De.Neef]

Hello Danny

I tried it again today and now the download works

Only difference is that the failures occurred on a WIN7 workstation and now I tried on a W10

don't know if anything was changed on the Account site

I'll try the install later today

will let you know

Regards

Patrick

[ithelpdesk]

hi the https://ava.autodesk.com option you give above just opens to a blank screen when i select stay within AVA only other option is to go to the "manage" url and that ends up in the new downloader that i don't want as i'm trying to create a new SCCM package. and we don't have any documentation for the new method yet. 

[ROD_IT]

This is absolutely crazy - changing a deployment process with virtually zero end user / client consultation etc.

1. It looks like this is designed for end users to manage themselves not for organizations to administer -

2. The previous deployment method was flawed but it worked - we, as a community, supported each other, figured out issues / workarounds and made a flawed process usable - now its all up in the air again.

3. This process is not more streamlined, not more manageable and certainly not fit for purpose currently.

4. I'm not sure how on-demand deployments are more efficient in any situation vs one big download,  centrally controlled, prepare your image, add your addons and deploy to end users as needed.

I had finished my 2020 deployment using powershell which I am very happy to share at the bottom of this post - isnt the prettiest of code but it works every time without fail and was pretty delighted that I could do away with my old batch scripts etc but looks like that was a waste of time and effort...

- - note - I've removed the paths to my servers and you need to download the add-ons etc and put them in the img\update folder of your deployment

this is a total backstep in my opinion - we had a process that worked (albeit with a bit of effort), now I dont and I have my end users shouting looking for the new product - disaster Autodesk - just a disaster - total lack of consideration for your userbase.... 

PS below is my deployment code for powershell 2020 - might help someone....for 2020 at least...

if ((Test-Admin) -eq $false) {
if ($elevated) {
# tried to elevate, did not work, aborting
} else {
Start-Process powershell.exe -Verb RunAs -ArgumentList ('-noprofile -file "{0}" -elevated' -f ($myinvocation.MyCommand.Definition))
}
exit
}

'running with full privileges'

$env:SEE_MASK_NOZONECHECKS = 1

<# ** Install REVIT 2020 ** #>

Set-Location "PATH TO YOUR IMG FOLDER"
Start-Process -Wait -FilePath ".\setup.exe" -ArgumentList '/W /q /I Img\REVIT_2020.ini /language en-gb' -PassThru

<# ** Install REVIT 2020 Service Pack / Hotix 2.3 **#>

Set-Location "PATH TO YOUR IMG FOLDER\Updates"
Start-Process -Wait -FilePath ".\01_Autodesk_Revit_2020_2_3.exe" -ArgumentList '/quiet' -PassThru

<# ** Install REVIT 2020 Addons** #>

Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\Updates\02_ABRB.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\03_AdSSO.msi /quiet /norestart' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\04_BIMInteropTools_7.2.7509.0_forRevit2020.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\05_IWExportToRevit.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\06_PeopleFlowToolkit2020.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\07_RDBL.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\08_Revit_20ExtSharedReferencePoint.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\09_RevitFabricationExtension.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\10_RPRE.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\11_RSCE2020.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\12_RSD.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\13_STLExporterForRevit2020.msi /quiet' -PassThru
Start-Process msiexec.exe -Wait -ArgumentList '/I PATH TO YOUR IMG FOLDER\\Updates\14_AutodeskIFC2020.msi /quiet' -PassThru

<# ** Install NavisWorks Exporter 2020 **#>

Set-Location "PATH TO YOUR IMG FOLDER"
Start-Process -Wait -FilePath ".\setup.exe" -ArgumentList '/W /q /I Img\EavWrks_Exprt_2020.ini /language en-us' -PassThru

$Shell = New-Object -ComObject "WScript.Shell"
$Button = $Shell.Popup("REVIT Installation Complete. Click OK to exit.", 0, "REVIT 2020 Complete", 0)

[mrogalski]

Thanks god the architects haven't jumped on this release, this new deployment experience is really no fun to 'figure out" You guys should have completed your documentation before dropping this on us. 

In my case I am able to get the software to install, and I can even type in our network locations for the libraries etc, however the libraries seem to get installed every time Revit 2021 is installed on a new workstation.

Used to be I could install the new libraries, support file once, then just point the installer there, where it would find them, NOT recreate them.

Like I said Documentation before dropping this on us would have been a better way to find out about these changes.

FOR THE LOVE OF GOD DON'T DO THIS TO AUTOCAD!!! I DON'T HAVE THE TIME TO FIGURE OUT HOW TO DO THE THING i FINALLY FIGURED OUT IN A NEW WAY (DEPLOYMENTS VIA SCCM)

I am currently downloading the "original Revit 2021" installer from Ava, I hope it behaves as expected.

[MattPettengell]

Hi Danny and the Factory team, thanks for taking the time to respond to the community.

I've only just discovered yesterday that the new installer and online deployment tools don't allow for addins and other customization.  While having a faster installer\deployment from Autodesk is useful, the two main reasons I create deployments is to include our custom settings (INI changes, colours, library locations, etc) and various addins that we include in our workflow.  The number of addins can vary from 2 to 6! and these are all required to augment Revit daily, so I see these as critical. 

In short, please add the ability to include addins etc in any future updates.  I will be using the AVA direct download method (this really needs to be documented...) and starting the process again.  It took me 4+ hours and help from a supplier to eventually find that solution... which could end up making the deployment cost me more time than it would have saved.  

Thanks all for your help and I hope changes to this process are considered and resolved before the 2022 release

[mrogalski]

After downloading the "classic" deployment tool I was able to create a deployment of Revit 2021 HOWEVER as with any deployment as I went through my test install/uninstall at around the 4th attempt to reinstall I can no longer install Revit 2021 on my test PCs.

there is no Revit 2021 specific deployment information (to be fair there was never any full documentation of earlier releases either) so this makes deployment creation tricky.

I have been able to get the "Modern" deployment to work but it doesn't seem to respect the custom .ini file that I defined in the online deployment creation tool when I place it into the "deployment image folder" not sure if there is a specific place in there or if I needed to add .ini to the end of the name when I defined it in the web app.

Again lack of clear, Revit 2021 specific documentation is causing headaches and I am still unable to reliably deploy this release to my workstations.

[Anonymous]

Like others on this thread, I am having difficulty creating a Revit 2021 Deployment, using the new "Online" deployment tool.

A few things that are causing me consternation:

• Requirement that file servers are NTFS.  We are using REFS for our file servers.  When I asked my IT guy about setting up a NTFS share just for deployment, he had some choice, profanity-laced thoughts on using older technology.  From my limited knowledge, the Resilient FS is becoming more and more prevalent, and it is important that Autodesk support it.
• The Modern "online" deployment appears to be unreliable.  When it is a vanilla deployment of 2021.1.2, without any customization, I can occasionally get it to work on some workstations.  If I try to add network paths for our content, the deployment fails consistently.
• There does not appear to be a clean way to distribute custom keyboard shortcuts.  Do I create a .bat script to drop the KeyboardShortcuts.xml file to the usercache folder?
• On one machine, I tried to uninstall Revit 2021 using the method outlined here:  
  https://knowledge.autodesk.com/support/revit-products/troubleshooting/caas/sfdcarticles/sfdcarticles...
  It basically made it impossible to reinstall the 2021 deployment back on to this machine.  Doesn't matter if it's vanilla, custom network paths, deployment on server, deployment on C: drive.  Nothing works.  You guys should really update that web page and advise people to use the Autodesk Uninstall Tool.
  
  Interestingly, the stand alone "classic" installation, downloaded through AVA did work on that machine.

[danny.polkinhorn]

Hi@Anonymous ,

Looking just at your Powershell script, this doesn't look like a classic Deployment Wizard deployment other than the line where you're installing Revit.  It looks like you're just downloading updates, and addons, and putting them in a folder.  Your Powershell script works just fine with new deployments as well.

[danny.polkinhorn]

Hi @mrogalski,

Agreed that we need better documentation around the customization options for products.  We're working on it for 2022 products.

For custom Revit.ini files, you need to specify the full path and name of the Revit.ini you want to include.  For Revit 2021, this file will be copied from the path you specified into the "Image" folder in the new deployment image folder. 

For those who host Content on a network location, we should provide a checkbox to not actually install the content as part of a deployment installation.  The content path fields in that case would just be used to populate the Revit.ini if necessary.  cc: @huotger 

[danny.polkinhorn]

Hi @Anonymous,

1. Are you getting a specific error when trying to create a deployment on ReFS?  Where are you storing your existing deployments?  You might also be able to move the deployment after you have created it in another supported location.
2. Please create a support case and include the logs from %programdata%\Autodesk\ODIS if you are having installation issues.
3. You're correct, there's not a current way to include the keyboard shortcuts, but you can definitely copy them with a batch file.
4. Also create a support case for this.

[ROD_IT]

Hi Danny,

Yep, that's exactly right and that's the beauty of it - it's simplicity

The deployment has to be built using the classic deployment method then the PowerShell calls the different elements - main product and all updates add-ons etc...

I've tested on 2021 as well 

For smaller organizations like ours where we don't have the time and resources to invest in figuring out the new process this gets us over the line for now.

I would ask AutoDesk to leave the classic deployment available to those who need it - don't go changing a working process.

[mrogalski]

@danny.polkinhorn sadly my full path exceeds 50 characters and since SCCM uses the machine account to install software I can't use a mapped drive path so my file name goes over 50 characters.

otherwise is this how I need to input the path for the custom ini file?

[danny.polkinhorn]

Hi @mrogalski,

This path is just needed to copy the file during the deployment creation.  Can you move the file to a shorter location temporarily?

I will look to see why we have this limitation.  Not sure why it's there, but thank you for pointing it out!

We have plans to introduce the ability to browse for the file which will save all this hassle.

Hope that helps,

-Danny

[mrogalski]

I moved it to a different share with a shorter path. and will try installing again.

[mrogalski]

Still no joy, the installation fails around 45% saying "contact your administrator" (thats Me) I'm trying a local install on the affected PC now to see if I can just get the application to install period.