The default gdb and home folder functionality as it currently exists is preventing my organization from implementing a VDI solution. Our VDI is architected with roaming profiles and the anti virus we use corrupts gdb files created in the VDI. This means that the first time a user log into the VDI the default.gdb is created and is corrupt. Now because ArcMap references the default.gdb every time a saved mxd is opened, ArcMap crashes and no can open a previously saved map file.
If the home folder and default.gdb functionality could be turned off we would be able to implement our VDI solution.
Here is the Esri Case #01941260
I don't think disabling the home folder will really help those of us who use corporate shared/project structures.The concept is baked in to too many places within ArcMap and Pro's assumptions. What I think could work is if ANY folder could be marked and saved as Home for that project, the same way as can be done for default geodatabase now.
I do despise that we can't use "go up" to next folder in tree from the Home folder. Not being able to do so creates so much extra clicking and navigating. We should always be able to navigate the file system. There's is already a button to go to Folder Connections.
10 years later, I still hate the Home folder and want to remove it. For instance, I change the name of a feature class somewhere in the catalog, and the Home folder immediately expands to show me that file. Yeah, I was already looking at it in the catalog. I don't need the Home folder to show me the same file. It's redundant and disorienting. And like others said, when navigating up one level I get sent to the Home folder instead of actually up one level - this is also frustrating.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.