Yes, you will receive a new ArcGIS v10 authorisation number to use during the authorisation process of the software. All ArcGIS Desktop 10 users will need to register their software and receive a new licence file when upgrading to ArcGIS 10.

Authorisation instructions for ArcGIS Desktop Single Use can be found at the following link: http://resources.arcgis.com/content/arcgis-desktop-licensing#Step3

The new Single Use licence file will contain identifiers that will tie it to the computer it is authorized for. The authorisation number can be authorized on only two machines at a time. This should only be for the same user (e.g. the user's desktop and laptop computer). Users will not be able to copy licence files from one machine to another.

Transferring a Single Use licence to another machine can be accomplished by "de-authorising" the licence via the SAW (Software Authorisation Wizard) and authorising the licence on another machine. When you de-authorise your licence, you will de-authorise the core software licence and all extensions simultaneously. You can de-authorise your licence up to four times per year in order to transfer a licence to another machine.

Yes, you will require a new concurrent licence file for ArcGIS 10. You will no longer need to request a licence file based on a hardware key or MAC address. At version 10, Concurrent licences will utilise various machine identifiers to establish Trusted Storage for the host server on which the Licence Manager is installed. This technology means the Sentinel key (dongle) is now obsolete (ESRI is not requesting the return of existing hardware keys). Yes, you will receive a new ArcGIS v10 authorisation number to use during the authorisation process of the software.

All older versions of the licence manager software will need to be uninstalled first. Then the new licence manager can be installed from the version 10 media. The following link provides authorisation instructions for ArcGIS Desktop Concurrent Use: http://resources.arcgis.com/content/arcgis-desktop-licensing#Step1

Yes, you can divide up your licences so that they can be installed on more than one machine. For example, if you have ten ArcView Concurrent Licences, it is possible to run two licence managers hosting five licences each. You can also transfer the desired quantity of licences from one server to another directly from within your network.

Yes, in ArcGIS Desktop 10, you will now have the option to borrow a licence from the licence manager on the server for a specified period of time and return it when you can reconnect to the network. There is no set limit to the number of times a licence can be borrowed. It is also possible to borrow extensions, provided they are part of your licence pool. Note that you cannot use the new "borrow" function to use 9.x licences when disconnected from the network.

There is no change to the current ArcGIS Server licence management technology at version 10. ESRI will be incorporating this new licence management technology in ArcGIS Server in a future release. However there will be a new authorisation numbers for ArcGIS Server 10.

No, concurrent licensing for ArcGIS Engine has been introduced at this release, as well as a single use ArcInfo licence.

VB6 is no longer supported. Support for VB6 was dropped by Microsoft a long time ago. Extensions written in VB6 will need to be re-written for ArcGIS 10. VBA is still supported at ArcGIS 10, but this will be the last release. Developers are encouraged to move to Python.

Python is an integral part of ArcGIS Desktop for automating tasks and the new add-in capabilities allow developers to easily create and deploy ArcMap customisations.

An important change at version 10 is that VBA is not part of the ArcGIS Desktop install. If you need VBA, you need to install the ArcObjects VBA SDK, which will setup the VBA Runtime, Editor, and Help. Please note that an additional authorization file is required for VBA.

This is a no charge license that can be requested from your customer representative. For more information on migrating VBA code see help.