By default applications run without any administrative permissions and therefore they cannot make any changes to the system. For some Adam commands, administrator privileges are required though. In Windows XP / Windows Server 2003 you could open your command prompt with "Run this program with restricted access" unchecked. In that case and if you do have administrator privileges, you are running the command with administrator privileges, but still as the logged on user. So these commands have access to your profile information like user folder, etc.
Windows Vista / Windows Server 2008 / Windows 7 on the other hand uses User Account Control forcing you to select "Run As Administrator" to be able to run a command with administrator privileges. In that case you are not executing this command with the logged on user, but with the administrator account, thus these commands don't have access to your profile information and have access the administrator's profile information instead. This can lead to unexpected results regarding Adam tools
Adam Commandline Tool
When starting the Adam Commandline Tool, runned as Administrator, you no longer end up in the Adam installation folder, but in the C:\Windows\system32 folder instead. So before proceeding you should navigate to the installation folder yourself.
Install Visual Studio Templates
When running as administrator, the same problem occurs as above: instead of running from the adam installation folder, the C:\Windows\system32 folder is used. Since this batch command needs the adam installation folder to continue properly, this results in an error. To bypass this you should execute the following steps:
- Fire up the command prompt with administrator rights.
- Move to the VSTemplates folder within the Adam installation folder.
- Start InstallTemplates.bat