Bug 2521

PB Apps will not run on Windows 2016 Server without Administrative Rights 23 November, 2020

Jim Klocksin
25 March, 2019
Product: PowerBuilder Category: Other
Version: 2017 R3 Build:
Classification: Issue Publishing: Public
Priority: P3
Status: Closed Reason: RESOLVED
Ken Guo @Appeon 23 November, 2020
#16
Hi Jim,

Thank you very much for your suggestion!
We then proceed to close this ticket, please remember that you can always open
another ticket in case you need it.

Regards,
Ken
Jim Klocksin 21 November, 2020
#15
This issue can be closed.  I apologize for this one, but I didn't realize it was still open.  We found a way using Group Policy to get around the UAC prompts and all users have access.  Thanks!
Ken Guo @Appeon 20 November, 2020
#14
Hi Jim,

I would like to check with you if the response provided has been helpful enough
to resolve your case. If so, can we proceed to close the ticket?
Otherwise, do let us know if we can provide you with any further assistance and
keep in mind that you are always welcome to open another ticket in case you
need it.

Regards,
Ken
Ken Guo @Appeon 26 March, 2019
#13
Hi Jim,

For UAC, if the EXE programs are trying to do some necessary authorization actions, UAC will prompt you or the actions will be disabled.

The UAC functionality itself is the Windows’ security mechanism so that PB can’t bypass it.

If you don’t want to turn off UAC and also don’t want the program to trigger UAC, I suggest you use some other ways to add the EXE programs to white list and see if it is OK.


Regards,
Ken
Chris Pollach @Appeon 25 March, 2019
#12
Thanks Jim ... lets see what the W2016 experts say!  ;-)
Jim Klocksin 25 March, 2019
#11
Sample Manifest file

This is what the PB IDE generates as a manifest file for my applications...FYI
Chris Pollach @Appeon 25 March, 2019
#10
Hi Jim;

  Thanks for that extra feedback. I will now pass this issue on to the main Appeon  Support/Engineering group and see if they have any suggestions for the W2016 UNC issue. I only have W10 PC's here at my location - so I cannot perform any W2016 testing.

Regards ... Chris
Jim Klocksin 25 March, 2019
#9
I can try that and I would bet that it would work.  What I've been doing to keep the "Classic" look and feel is, use the External Manifest option, but delete the manifest file that gets generated!  When I do this, I get the look and feel that I'm looking for in both Windows 10 and Windows 2016 server.

The only problem with what I'm doing is my second issue (in some respects the most important...) that the basic users can NOT run the application because of UAC.  

If I disable UAC (through the Registry "EnableLUA" entry), everything works.  While I'm hoping to get my client to "sign-off" on disabling the UAC on the server (since all user access is via RemoteApp), I can't count with that and, if I can find another way to resolve this issue without having to disable the UAC, that's the preferable solution.
Chris Pollach @Appeon 25 March, 2019
#8
Can you  try checking the "Windows Classic Style" an resetting the "Generate Options" to no manifest just as a quick test?
Jim Klocksin 25 March, 2019
#7
I am checking off the "Windows Classic Style" and it doesn't change anything.  So, bottom line, I have two issues here: 1) How to keep the Win 7 "look and feel", and 2) how to allow standard users (no admin rights) to run my application without butting into the UAC prompt.
Chris Pollach @Appeon 25 March, 2019
#6
   The other way is to check the "Windows Classic Style" in the Project Painter for the profile that builds your EXE. That should restore the old look & feel used by W7 that includes the 3D look. Newer PB versions are geared up to the new W10 flat and bland (boring) look. ;-)
Jim Klocksin 25 March, 2019
#5
I rebuilt my smallest application (to save time) using the "Embedded Manifest" option and it "flattened" out everything in my datawindows.  I need help from one of my users to determine whether or not it will run on the Windows 2016 Server, and I haven't been able to test that, but there MUST be some way to keep the "3-D" look in these datawindows....they show the "3-D" look in the PB IDE, but when run in either Windows 10 or Windows 2016 Server as executables, everything is FLAT....!?
Chris Pollach @Appeon 25 March, 2019
#4
Hi Jim;

  Sounds like your "External" manifest might be controlling the Look & Feel. Try using the "Embedded" option.

Regards ... Chris
Jim Klocksin 25 March, 2019
#3
No, I can try that (and I believe I did that at some point), but the main issue I have with the manifest file (external in my current setup) is that if I include it in the folder, my entire application "goes flat" with that horrendous, totally flat look for all datawindow fields (that are coded as "lowered" or "sunken"), so I lose that 3-D effect as well as the colors on all of my tab pages (and I tend to use tabs a lot in my application).  That said, I will try it and report back, but I really, really don't want to force my users to have to use the application with that "colorless, flat" look!  Also, checking off the Windows Classic Style doesn't change the look!?
Chris Pollach @Appeon 25 March, 2019
#2
Hi Jim;

  In the project object where you selected run "As Invoker" ... did you also select "Embedded manifest" from the above DDLB?

Regards ... Chris
Jim Klocksin 25 March, 2019
#1
Build Parameters.JPG (17KB)

*Phenomenon: Mature PB application will not run for users with standard user rights...receives a UAC prompt for elevation.  Code is signed and runs correctly if the user has Administrative rights.  The program has been built to execute "As Invoker", with no access to protected system UI (see attachment).  


*Reproduce Steps:  Frankly, I'm not sure how you can reproduce my exact scenario.


Remarks:  I'm looking for any advice or something that I may have overlooked when dealing with UAC and a PowerBuilder application running under a Windows 2016 Server environment?
OS:
Windows Server 2016
Platform:
32-bit
Database Type:
Microsoft SQL Server
Database Version:
SQL Server 2008 R2