Verification:installing user & operating user are related

This forum can be browsed by the general public. Posting is limited to current SAPIEN license holders with active maintenance and does not offer a response time guarantee.
Forum rules
DO NOT POST LICENSE NUMBERS, ACTIVATION KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.

Any code longer than three lines should be added as code using the 'Select Code' dropdown menu or attached as a file.
This topic is 6 years and 10 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.
User avatar
bgsapien
Posts: 5
Last visit: Tue Mar 26, 2024 6:14 am

Verification:installing user & operating user are related

Post by bgsapien »

Product, version and build: PowerShell Studio 2017 v5.4.138
32 or 64 bit version of product: 32
Operating system: Windows7 Enterprise SP1
32 or 64 bit OS: 32
PowerShell Version: 5

Hello, I just want to know, do I got it right that :
- the "installing user" and the "operating user" are related to run PowerShell Studio.
In other words the best to use PowerShell Studio is the "installing user" and the "operating user" are the same.
- if another user other than the "installing user" wants to use PowerShell Studio, there you will need to copy manually some folders from the
"installing user" to the "operating user's" profile and adjust the user rights accordingly.

Regards AM
User avatar
Alexander Riedel
Posts: 8479
Last visit: Thu Mar 28, 2024 9:29 am
Answers: 19
Been upvoted: 37 times

Re: Verification:installing user & operating user are related

Post by Alexander Riedel »

No. The installing user doesn't matter. It is typically someone with admin privileges.
The software, one started by the 'operating user' will take care of any per user files and unlocking the license for the 'operating user'.
There is no need for manually copying files under normal circumstances.
There are systems that are so locked down that the normal user cannot even store settings in per application data folders or the per user registry, but that is an entirely different story.
Alexander Riedel
SAPIEN Technologies, Inc.
This topic is 6 years and 10 months old and has exceeded the time allowed for comments. Please begin a new topic or use the search feature to find a similar but newer topic.