posted on May 07, 2007 23:20
We did a considerable amount of work to ensure that Automise 2 is fully compatible with Windows Vista. Apart from a couple of cosmetic bugs, we're confident that Automise 2 is wholly Vista-compatible.
Nevertheless, some of the new features in Vista (specifically, User Account Control or UAC) mean that some things need to be kept in mind when using Automise. The following is a summary of notes for Vista users who are using UAC.
Microsoft TechNET has an article called User Account Control Overview which explains the features of UAC at a technical level. Note that UAC can be disabled as well. If UAC is disabled on your computer, you don't need to read this article.
Automise Runs as the "highest available user"
If you're logged into your computer as an Administrator user, then Automise will run as an administrator and you'll see the UAC Prompt when you launch it:
Once it's started, you'll be able to launch any program and perform any administrative task.
On the other hand, if you're logged into your computer as a non-Administrator user, then Automise will run as a normal user. You won't see any UAC Prompt when you launch it. You'll be able to use most programs and perform many administrative tasks, but some tasks (which require elevated administrative privileges) will fail. Also, you will not be able to use the GUI Automation actions to automate any program which is running as Administrator.
If you are a non-Administrator user and you want to run Automise as an Administrator, you can right-click on the Automise 2 shortcut and choose "Run As Administrator". You will need the username and password of an Administrator user in order to do this.
Scheduling Automise Projects
You can still schedule Automise projects to run at specific times. If you schedule a project while running as an Administrator with elevated privileges, then that schedule will run as an elevated Administrator (no UAC Prompt will be required.) On the other hand, if you schedule a project while running as a non-Administrator then it will run as a normal user.
ActionStudio and the ActionDefs Directory
Normally, you save any ActionStudio custom action packages to the ActionDefs directory inside the Automise 2 program directory. With User Account Control, there can be more than one "virtualized" ActionDefs directory on your computer. This is only an issue if you are running ActionStudio as a user who is not a member of the Administrators group.
If you run ActionStudio as an Administrator, you will save packages to the "real" ActionDefs directory under the Automise 2 project directory. However, if you run ActionStudio as a normal user, then any files that you save to the ActionDefs directory will actually get saved to a "virtual" directory which only that user can access. This is fine as long as you run Automise as that same user, but other users will not be able to see the virtualized directory and can't load your custom action package.
The workaround is to always run ActionStudio as a user who is a member of the Administrators group.