Hi.

I've also found something about running the IDE as admin in case one want to use the PowerServer deployment features.

This is also related to powerclient. It's a requirement when you directly deploy to IIS...

As for installation, I have done many times the installation without any issues with an account having admin privileges, but if you run to any problem then you can run the installer as administrator. Anyway, if you don't have admin privileges then you should run it as an administrator. Also many issues during installation are often related to antivirus programs. Take a look to the following links:

Starting the Offline Installer - - Installation Guide (appeon.com)

PowerBuilder Installer blocked by Windows Defender SmartScreen - - Installation Guide (appeon.com)

While the second links is about Windows Defender, in the past there were some issues with other AV software... With Symantec Endpoint the only problem I had was related to Autorun.exe... With BitDefender I had no issues so far...

Andreas.

@Andreas

Thanks for the input.

My concern is that someone with admin privileges will start the installer. So another account than me, the one who will be using PB.

Should I have temporary admin rights or doesn't it matter who installs it?

My life was so much easier when we had admin rights :-).

If I understand correctly I should be able to install and run without admin as long as I don't want to do something with PowerServer/IIS?

Although I would like to have that route open for future testing/evaluating.

Installation is done under Program Files (or Program Files (x86)), where elevated privileges are required, otherwise any write attempt may fail... Also, installer will write some keys and values to registry under Computer\HKEY_LOCAL_MACHINE\... For those keys you also need elevated rights to write (but not to read)... Any installer that does writes in those locations will require admin rights. Not only powerbuilder.

Your personalized entries in the registry will be created when powerbuilder will be first executed. In that case you don't need admin rights of course. The only exception is related to powerclient & powerserver deployment. Those project types will make changes to inetpub\wwwroot and a simple user may have no right to do all those changes.

In my case, I'm a local administrator on my pc, and when I deploy to my local IIS I don't need elevated privileges. But to deploy to a remote (production) server, I guess elevated privileges would be required.

Andreas.