We have several network licenses, and several standalone licenses, of BDSP 2014, although we really only use Revit (architecture firm). I typically only deploy the network licenses, since they can accommodate most of our staff. However, we now have a few summer workers, and have had a few issues where there weren't enough licenses available, so we deployed the standalone linceses to about 5 people. Problem solved.
However, on those standalone deployments, Revit refuses to remember the File Path locations for our project templates, family templates, and Places (detail library, project directory, etc.). I can enter them manually, and everything works fine. But when I close out of Revit, and re-start it, all the paths are set to nil (all paths are gone, no templates are listed, etc.).
Any thoughts? My guess is that for some reason the deployment is having trouble finding the Revit.ini file (where those paths are stored). But I went and overwrote the Revit.ini, which removed the recent files, but for some reason still won't remember the paths for the templates/library. The Revit.ini file in the deployment folder is correct, and works fine on the network deployments.
Could this have something to do with the previous network deployment not being properly removed first? I noticed a similar problem on another computer where the network deployment was removed and then redeployed. Our third party IT company is the one actually doing the un-installing and deployment, though I built the deployment package.
Disclaimer: we have a proprietary "cloud" system, so our file paths read "\\arcturis\users\etc." rather than "C:\My Computer\users\etc."
Thanks in advance.
Solved! Go to Solution.
Solved by rosskirby. Go to Solution.
In the past, roaming profile issues have been solved by first putting the profile back to local and running the software. Once it is launched and configured and working, then you can move the profile back to the network. This has had much success as a work-around. Might give it a shot.
Thanks for the quick reply, Travis.
Could you elaborate a little further? Do you mean that I should have our IT log in as the adminstrator, fire up Revit and change all the paths, and then let the user log in? Once we start digging to far into network issues, I'm a little out of my depth, so I might just be missing something with your terminology. I just want to make sure I understand before I relay this back to our IT, as I don't have administrator privileges.
Thanks again.
Yeah. Basically make the user's profile point to C:\Users\Username again then launch as the user. Then after that works, put the profile back to \\Servername. Does that make sense?
Thanks for the update, Travis.
I found a somewhat easier fix, although I'm still at a loss as to how it happened. If I go to (C:\ProgramData\Autodesk\RVT 2014\UserDataCache) and overwrite the Revit.ini file there with the one that I created for the deployment, then fire up Revit, all the paths are back as expected.
My only guess is that there is some problem with the Autodesk Uninstall utility that our IT used that corrupts the Revit.ini file in that location. I can't confirm that, though, so I'll keep this solution in my back pocket if it ever comes up again.
Thanks for your help.
That's actually a pretty good solution. Good job!