Updated The problem with corporate Windows Enterprise installations, are that they are locked down and paranoid.

Updated The problem with corporate Windows Enterprise installations, are that they are locked down and paranoid. Running "random" installers is not possible.
To get around this limitation for power users, LAPS is a method used when your regular domain account doesn't have local admin rights, and you instead elevate to local admin using a second local account, with a password provided from AD.

To exemplify:
My normal domain users: Lars (Does not have Local Administrator rights)
The local admin user: AdminLars (Has Local Administrator rights)

The problem seems to be that when you use LAPS and AdminLars, the user context is not my regular domain user Lars - but the special local admin account AdminLars - so any registry settings installed, ends up in the wrong HKEY_CURRENT_USER.

This means that when I start Delphi as Lars - any components installed as AdminLars are not visible.

Recreating registry entries is a possibility - but - complex - since I don't know what keys any specific set of components install.

Any suggestions of how to work around this?

-- original post:

Does any of you have experience with installing components for RAD Studio (10.1 upd.2) under Windows 10, using MS LAPS?

It seems that TMS and EurekaLog installs doesn't appear to be visible to the Delphi installation (also installed using LAPS).

I need a workaround.

https://technet.microsoft.com/en-us/mt227395.aspx
https://technet.microsoft.com/en-us/mt227395.aspx

Comments