Manjrasoft Site Menu:

Frequently Asked Questions
Aneka Installation

1. How to programmatically interact with the Windows security in order to perform a smooth remote installation without having the security of the system shut down?

2. I cannot configure Aneka Container



1. How to programmatically interact with the Windows security in order to perform a smooth remote installation without having the security of the system shut down?

We have experienced installation failures on Windows 7 both on a local machine and a remote machine because of the security system. Besides the networking issues, which have been solved by activating file and printer sharing and turning on the network discovery features, our software fails in performing the following operations:

  • Copying a bunch of files under the "Program Files" directory
  • Installing a service

We tracked down the root cause of these issues as the fact that the UAC prevents these operations. In a manual installation it would normally pop up a user interface allowing the user to decide whether he or she wants to continue the operation, but while trying to programmatically perform the installation such a UI is not shown (especially in the case of the remote installation) and the operation gets blocked. The current solution we found applicable is the following: shutting down the notification to the "Never notify" level and rebooting the machine. We wonder whether there is another option which avoids to adopt these extreme measures. My understanding is that turning the notification level to "Never notify" just prevents the UI to show up but does not disable security. Therefore, we still need administrative privileges to perform such operation.

Related documents:

  • Windows 7 - Aneka Installation Troubleshooting FAQ [Download]
  • Windows 7 - Aneka Installation Troubleshooting Guide [Download]

2. I cannot configure Aneka Container

Closing the Management Studio does not uninstall Aneka daemons and containers. By closing the Management Studio, it saves the entire current configuration which is loaded on the next Management Studio launch. However, if the IP address or any other environmental variable on the machines running Aneka daemons and containers changes after the closure of Management Studio, upon it's the next launch, the containers may not be shown in the Management Studio and work properly. Furthermore, any attempt for reinstalling problematic containers will fail. In order to rectify this issue, the Aneka daemon and container should be killed manually prior of re-installing. By looking at Windows Task Manager, and process related to Aneka should be manually killed and any corresponding service should be stopped. After this preliminary step, you should be able to re-install Aneka daemon and containers.

As a general guide line, if you think that your environmental in most likely to be changed, before closing the Management Studio, you should perform the following steps in order:

  1. Stop the containers by right-clicking on the container icon and selecting the Stop option.
  2. Uninstall the containers using the Uninstall option in its context menu.
  3. Uninstall the machines hosting the container.