Knowledge Base - Technical Articles


Technical Article   FAQ:  Why doesn't the ArcGIS Desktop Administrator allow switching of software types or the license manager?

Article ID: 17970
Software:  ArcGIS - ArcEditor 8.1, 8.3, 9.0, 9.1, 9.2, 9.3, 9.3.1 ArcGIS - ArcInfo 8.0.1, 8.0.2, 8.1.2, 9.0, 9.1, 9.2, 9.3, 9.3.1 ArcGIS - ArcView 8.1.2, 8.2, 8.3, 9.0, 9.1, 9.2, 9.3, 9.3.1
Platforms:  Windows NT 4.0, 2000, XP

Question

Why doesn't the ArcGIS Desktop Administrator allow switching of software types or the license manager?

Answer


 See also 24633: How to: Change the ArcGIS Desktop seat type for Citrix or restricted permissions environments


The Desktop Administrator allows switching between ArcInfo, ArcEditor and ArcView (Concurrent Use) and ArcView (Single Use).
Full use of the Desktop Administrator requires a user's permissions to include the ability to write to the following registry keys:

1. HKEY_CLASSES_ROOT\CLSID and
2. HKEY_LOCAL_MACHINE\SOFTWARE\ESRI

For 64-bit operating systems the keys are:

1.HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ESRI
2.HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{E6BDAA76-4D35-11D0-98BE-00805F7CED21

If these permissions are not granted, the user is only able to view Availability. All other functionality is disabled.

 In a network environment, do NOT give permissions to the registry keys to domain users or authenticated users (both need access to the domain to authenticate). If this is done then it will slow the computer down to a crawl. The system administrator needs to give full control permissions to the local users group in order to authenticate everything locally rather than across the domain.



Related Information


Created: 4/12/2001
Last Modified: 5/3/2012

Article Rating: (8)
If you would like to post a comment, please login

Comments

By sbergasse - 04/26/2012 12:10 PM

The article needs to be updated.

We should mention the keys for a 64 bit machine in this article: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ESRI HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\CLSID\{E6BDAA76-4D35-11D0-98BE-00805F7CED21

Rating:

By Scott-HTSI - 12/14/2011 8:06 AM

The article needs to be updated.

The correct CLSID for Windows 7 x64 is [HKEY_CLASSES_ROOT\WOW6432Node\CLSID\{E6BDAA76-4D35-11D0-98BE-00805F7CED21]

Rating:

By mikebudd - 09/01/2011 12:02 PM

I would like to see a new article that discusses the topic outlined below.

ArcGis 10 has the most convoluted, inefficient install process I have seen in 15 years in the computer industry. Thinking about maybe bailing on this entire program. VERY Frustratinig.

Rating:

By ranbarasan - 06/22/2011 2:11 AM

Great article! It helped a lot!

I had this problem and tried lots of things but finally got the solution. Thanks a lot. OS: Windows 7 Enterprise Arcgis 10. sp2

Rating:

By Anonymous - 12/20/2010 12:03 PM

I followed the article’s instructions, but experienced another problem. I’ve provided details below.

You should specify that this article applies to version 10 as well.

Rating:

By Anonymous - 10/22/2009 1:27 PM

The article has missing, misleading, or conflicting information.

I sent a customer this article and he informed me that in a network environment, do NOT give permissions to the registry keys to Domain users or Authenticated Users (which both need access to the domain to authenticate) if this is done then it will slow the computer down to a crawl. The system administrator needs to give full control permissions to the Local users group in order to authenticate everything locally rather than across the domain.

Rating:

By Anonymous - 10/07/2009 1:03 AM

Other - See details below.

Full use of the Desktop Administrator requires a user's permissions to include the ability to full access to the following registry keys: [HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\] [HKEY_CLASSES_ROOT\CLSID\{E6BDAA76-4D35-11D0-98BE-00805F7CED21] Tested on Sofware: ArcGIS - ArcInfo 9.3/9.3.1, ArcGIS - ArcEditor 9.3/9.3.1 Platforms: Windows XP SP3

By Anonymous - 02/22/2007 1:10 PM

The article needs to be updated.

No instructions

By Anonymous - 01/24/2006 12:45 PM

Rating:

By Anonymous - 05/18/2004 12:44 PM

I created a GPO and applied it to AD. Also, I verified that it updated the registry setting on the local machine. However, a regular user still can not change the Desktop Administrator settings.

By Anonymous - 04/22/2004 5:47 AM

Giving access to the entire HKCR\CLSID is pretty generic. This will open the registry up to all kinds of spyware which will wreck the machine. You really need to find the correct keys and only open access to them.

By Anonymous - 07/17/2003 11:41 AM

You could detail the steps necessary to fix the problem. Because of this lack of information, I need to write you and contact our internal tech support

By Anonymous - 03/03/2003 8:32 PM

How about in the next version the install chnages permissions on the Reg Keys?

Rating: