Windows API - Win32
A core set of Windows application programming interfaces (APIs) for desktop and server applications. Previously known as Win32 API.
2,707 questions
COM application launching as different user in terminal server
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 36%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
Anshul Mittal
201
Reputation points
This issue is specific to terminal server only. I have 2 applications (both COM exe's) 1 implemented as singleton and launches as administrator everytime correctly. The application 1 launches second application using CLSCTX_LOCAL_SERVER. The issue is that the application 2 is launched as the first user(User2) who launched the application 1. Example : there are 3 users (User1 (administrator), User2, User3). I launch app1 from User2 which launches app correctly but second time when i try to launch from user3 the app2 still launches as User1 instead of User2.
Windows API - Win32
C++
C++
A high-level, general-purpose programming language, created as an extension of the C programming language, that has object-oriented, generic, and functional features in addition to facilities for low-level memory manipulation.
3,824 questions
{count} votes
-
Song Zhu - MSFT 906 Reputation points2021-03-19T03:04:36.587+00:00 I think this may not be a problem caused by the API, Could you please show a minimal, reproducible sample without private information?
-
Anshul Mittal 201 Reputation points
2021-03-24T12:22:53.35+00:00 Hi,
It is difficult for me to extract code from the huge code base to show here. But there are 2 COM exe's "Exe1" and "Exe2" (names changed). There is a COM server which is a windows application. The COM server initializes Exe1 using CoCreateInstance. In terminal server the Exe1 is initialized as User1 even though COM server initializes it from User2. In normal remote desktop services Exe1 is initialized as User2 which is the user currently running COM server.
This is critical because we need to support terminal services also for our application and cannot be restricted to only remote desktop services.
Sign in to comment
Sign in to answer