For whatever reasons there is some magic combo of install/uninstall that eventually generates a registry key that triggers a new installation to "think" the software is already installed.
So my other issue was reinstalling Revit 2021 on a PC that had it installed previously.
The answer seems to be use the classic deployment however Autodesk does not support it, and if you need to download it you have to use Ava the automated Autodesk chatbot to get the package. I am not the only person having issues with this, the Autodesk forum has 2-3 threads of peeps with the same issues.
If a workstation won't choke down the installation, I'll install it on a workstation that does and have the team member remote into that machine to work on the job. If we do get a Revit 2021 job I'll just do individual workstation installations. So far we haven't had any clients clamoring for Revit 2021 models so we're good to go at this point in time. He also indicated these issues are all being resolved with the 2022 Revit release. So If you can get the installer to run, it installs all the language packs and wipes whatever libraries, replaces them with all the language versions on your network share. He confirmed that indeed, there is no reliable way to exclude the language packs, nor is there a way to exclude the reinstallation of support files on any network drives. Why is it so bad? Well I opened an Autodesk support case and worked with a great tech there. So when Revit 2021 first came out it used the good old deployment builder we all know and "love/hate" when Autodesk rolled out Revit 2021.x the moved to the new "modern" installer that is as Mudhoney says "flat out f****d". Yep Denis I am indeed trying to get the deployment buil.t with the new installer. Didn't kow about the "classic" tool, might try that instead. Previously I would simply run the resulting file as administrator on the users PC but now the path is built into the deployment and since drive mappings change between user and administrator context it seems to fail quite easily. I've been messing with it – as we are a small firm I use the deployment to ensure that the same settings are applied to everyone, even if it is months later when a PC is upgraded, rather than to roll out to a large group.
bat file and a folder full of components. online) deployment building tool so there is no executable, instead you fill in information online and then download a. So does anyone here do Revit deployments? If so have you had success with Revit 2021? lemme know I'm about out of ideas here.ĭenis Kelley, looks like Big_Mark is using the new (i.e.
This has led me down a deep rabbit hole of trial and error, use a Microsoft uninstall tool for Autodesk products (you know there is a problem when MS has to help developers at this level) ini file back to OOB it still fails on my test PCs with an error of "Revit 2021 is installed on this PC) -[
I was on m圓rd or 4th install/uninstall (it takes a few tries to nail the user settings, narrow down the installation and uninstall all the crap that comes along with all AutoDesk software) when I found I could no longer install Revit 2021 on any of my test PCs. So I did some digging and found that there is a "classic" deployment installation that I can only download through the Autodesk Virtual Assistant (AVA) site were I was able to get my deployment going and start testing. When I went to deploy Revit 2021 I discovered that AutoDesk has responded to our overwhelming requests to make installation and deployments easier by creating deployments with their easy to use handy dandy online deployment creation tool! I tried it but was unable to define the shared working directories and or push out a default user config via revit-2021.ini. Revit 20 had hotfix/patches I was able to deploy those as expected.
I finally have made the time to get my 2021 Autodesk releases published as well as update the existing ones. So I've been building out Revit and AutoCad deployments since version 2009, each release has some kind of new gotcha that is changed/gone/redesigned as far as configuration and deployment setting go but I am usually able to figure it out and get it to install/uninstall via silent command line so I can then turn around and deploy it via the Software Center via SCCM.