Select to view content in your preferred language

ArcGIS Administrator should work without admin rights to computer

7953
15
08-23-2012 01:56 PM
Status: Open
AdrianneBlack
Deactivated User
My understanding is that using ArcGIS 10 on Windows 7 requires admin rights in order to be able to change the level of license (ArcView, ArcEditor, ArcMap) in the ArcGIS Administrator or make changes to the registry keys.  We need users to be able to change the level of licensing and have many users such that this would require a lot of effort to make changes to the registry keys on each computer.  Can ESRI change this so users have access to make this change without admin rights on their computer (company policy does not allow this). 
Tags (1)
15 Comments
ChelseaRozek

I just used this guide to add Open License Switcher (.bat file) from the .mxd context menu: https://www.howtogeek.com/107965/how-to-add-any-application-shortcut-to-windows-explorers-context-me... You could make simple bat files for Basic and Advanced with this help article: https://support.esri.com/en/technical-article/000011374

JeremyHayden

@ChelseaRozek 

I understand the approach (both), but for those of us with very locked down permissions, we won't be able to edit the registry either? So I'm assuming this won't work? Can you confirm the simple bat file approach involves editing the registry?

LorindaGilbert

I know this is old, but what about when your license manager server changes.  Admin rights to change that as well?  Come on.  There should be a way of changing the license manager without calling out your army of computer specialists that have to log on as admin to update.  And don't even get me started on an 'all user' install of ArcPro that requires you to be admin to get the updates.

DarbasDarbas

Any news regarding this topic, because still strugling void this situation without administrative permisions? !!!

JoshuaBixby

@DarbasDarbas, ArcGIS Desktop/ArcMap reaches Mature Support in a couple weeks, and for all intents and purposes development has stopped on it.  In short, it isn't going to get addressed for ArcGIS Desktop/ArcMap, and it isn't an issue for ArcGIS Pro.