Public Report
Report From: InterBase/Install    [ Add a report in this area ]  
Report #:  47604   Status: Closed
(Pulled) InterBase Server Manager starts as an ordinary user even if you are an administrator on Windows Vista     On Windows Vista, as s
Project:  InterBase Build #:  8.0.0.53
Version:    8.0 Submitted By:   QC<->Raid Replicator Account
Report Type:  Basic functionality failure Date Reported:  1/3/2007 12:00:00 AM
Severity:    Serious / Highly visible problem Last Updated: 7/10/2008 9:10:30 PM
Platform:    Windows 95/98/NT 4.0 on Intel Internal Tracking #:   243679
Resolution: Fixed (Resolution Comments) Resolved in Build: : 8.1.0.257
Duplicate of:  None
Voting and Rating
Overall Rating: No Ratings Yet
0.00 out of 5
Total Votes: None
Description
InterBase Server Manager starts as an ordinary user even if you are an administrator on Windows Vista

On Windows Vista, as seen by Fredrik Haglund, Nordic:

"Windows Vista User Account Control (UAC)

Trying to register InterBase as Server fails with an Access Denied.
Starting InterBase Server not as service makes it run as a user. It will not succeed in updating or saving file in the Program Files folder. These files are redirected to virtual folders per user creating a mess of duplicated files.
It is not possible to open example databases in Program Files. They are read-only.
IBConsole saves settings in IBConsole.xml in program files.


Workaround: Use compability mode and always launch ibmgr.exe and ibconsole.exe with administrator privileges. Only run IB as a service.

My Recommendation:

1) Add Manifest with requestedExecutionLevel set to requireAdministrator on IBMgr.exe. Otherwise it will not be possible to install InterBase to run as a service.

2) Remove possibility to start ibguardian with HKLM\Software\Microsoft\Windows\Currentversion\Run.

3) Make InterBase run as a standard user   this will probably also be necessary for future in-process version of InterBase. A tips, use Microsoft Standard User Analyzer (SUA) tool to identify problems. Problem running as user I have identified is License management (use global namespace for semaphore used in license check), Interbase.log located in Program Files and access to HKLM\Software\Borland\InterBase\Servers, etc.

4) Let IBConsole save settings (IBConslole.xml) in user directory instead of program files.

5) IBConsole appears to open HKLM keys in Read/Write mode and that fails running as standard user."
Steps to Reproduce:
None
Workarounds
None
Attachment
N
Comments

None

Server Response from: CODE1