Saturday, August 21, 2010

App Installation as Admin in Windows Server 2008

Today at work, I tried to get help from Capstone on their application work in Windows Server 2008. The application is a 32-based application as a VBS script host with ability to communicate with their ParcView suite. The application has a configuration setting for data connection, by using UDL connection string.

The issue I encountered was that the UDL is a connection to an Oracle database, and it seems that the UDL string cannot be accepted by the application. To cut the story short, Captone's tech support guru finally identified that the issue was caused by Oracle drive installed on this Windows box. The network team at work installed 64-bit oracle driver (Oracle g10), while the application requires the 32-bit driver. Unfortunately, the person who is responsible for the installation is on vacation this week. Therefore, Capstone person helped me to install the Oracle g11 client, 64-version first and then 32-version next.

The 64-version installation went OK. However, we had trouble to install the 32-version. There were several failures during the preparing stage. He finally figured out that he has to run the installation oui as administrator. I saw it so simple to run installer as administrator. Since my log-in name is a member of Administrators group, in Windows Server 2008 (VISA-like Windows), just right click on oui and run it as administrator:

to my surprise, no password was requested. I think it might be Windows Server 2008 and my log-in is in Administrators. Anyway, that reminded me a case I did before: to configure PowerShell Execution settings.

By default, the execution policy for PS is Restricted. I needed to change it to RemoteSigned. However, I could not do it even my log-in name is in Administrators. It seems Windows Server 2008 has strong security. What I did was to make a request to the network team to log in as administrator to run Set-ExecutionPolicy command with RemoteSigned.

When I realized that it was so simple to run installation as admin, I tried PS right afterward.

Now, after I run the PS as admin and I can set policy. That's pretty cool!