Userinit :\windows\system32\userinit.exe,

Userinit :\windows\system32\userinit.exe, 1a8 8 0 1 0 0 16A8 8 0 0 0 9 1zm. I found the following question, with a similar premise, however the answer to the question, was the question rephrased as a statement! In order to allow remote app, I’m seemingly having to add the users to the “Remote Desktop Users” group.

Agreed, though the premise of our service, is they are only allowed to use the Application. They are not given a full login to desktop to reduce overhead on the system. If they work around it like Evan mentions, then we can deal with that case by case. This is a resources issue, not a security issue tough. You could do something silly like use Group Policy to set the user’s shell to be “logoff.

However we are attempting to restrict them down to simply using the application. Will attempt that idea and see how it goes. Where is the policy for this located at? If I need to do this at a domain level, need to bring in the owner of the company and walk him through it.

Don’t forget to set software restriction policies that allow them to run only what you are expecting them to run. 1 for setting the shell to logoff. Aequitarum No, you don’t need to do it at the domain level. If you want to edit Group Policies locally for one machine only, just run gpedit. You can take advantage of the fact that full user sessions launch the userinit. Please be sure to answer the question. Provide details and share your research!

Asking for help, clarification, or responding to other answers. To learn more, see our tips on writing great answers. Not the answer you’re looking for? I give the client access to remoteapp but prevent ts login? How to allow active directory users to remote desktop in? Replacing VNC with Remote Desktop, how do you share a desktop between users like VNC? Is the formal power series ring integrally closed?