I created an application (.NET Windows Forms) which shall be launched after a user presses the "Logoff" key in Windows 8. I created a gpo in my domain environment which works in Windows 7. However, Windows 8 shows instantly the logoff screen and there is no chance for my application to pop up. Is there some kind of GPO that prevents the application from showing up?
The purpose of the application is to show users their projects and they have to tell the application how long they worked for a specific project. This would be nice if this works on logoff.
Quote from Ƭᴇcʜιᴇ007 from my superuser-thread:
The Windows 8 logoff screen is the topmost window, and that's why you can't see Windows launched during Logoff.
A fix that has been suggested to work is to enable the Display instructions in logoff scripts as they run group policy in User Configuration/Administrative Templates/System/Scripts
Description
Displays the instructions in logoff scripts as they run.
Logoff scripts are batch files of instructions that run when the user logs off. By default, the system does not display the instructions in the logoff script.`
If you enable this policy, the system displays each instruction in the logoff script as it runs. The instructions appear in a command window. This setting is designed for advanced users.
If you disable this policy or do not configure it, the instructions are suppressed.
Related
i have a question regarding auto-start an application:
I have a C# WPF Application, packaged as an MSIX installation.
And i successfully setup a StartUp Task via entry in the Manifest.
That works fine - after user logs in, the app is started automatically.
But as an additional feature we would need to be able to auto-run the app BEFORE user logs in.
After Windows startup, before user login.
Is there a way to do so?
I didn't find a solution until now...
Creating a scheduled task for example i found to be not possible, because i can only run a regular .exe file, but no installed application.
Thank you for help!
Best regards
Emanuel
An easy way for a application to start before the user logs in is to have a Windows Service for it.
If your application does not need any user interaction (and I am assuming it does not because you need it launched before the user logs in) that would be a viable option.
If your application does need user interaction in the Windows Login screen, you will need to do a google search on SysNotify but it is not for the faint hearted :)
Still no answer, so at least I´ll let you know a dirty workaround.
I figured that my msix app starts before login, when in Windows Personalization under LockScreen i set that the app should show status info´s on the lockscreen..... so it starts now in the users context, even before login.
under Application I already have the follwing, so the app can be selected to deliver lock screen content. (see 1. link below)
<uap:VisualElements
<uap:LockScreen Notification="badgeAndTileText" BadgeLogo="Images\BadgeLogo.png"/>
</uap:VisualElements>
https://learn.microsoft.com/de-de/previous-versions/windows/apps/hh700416(v=win.10)
Those are the documentation trails might leading to a better solution:
https://learn.microsoft.com/en-us/previous-versions/windows/apps/hh781238(v=win.10)?redirectedfrom=MSDN
https://learn.microsoft.com/de-de/previous-versions/windows/dn934782(v=win.10)
The app I am testing uses a website-based login. So as soon as you click on the login button in the native app a webview opens up where you can enter your credentials. Once done, a single-sign-on cookie is set, the webview closes and the native app opens back up.
Because of the SSO closing, resetting or even reinstalling the app does not log the user out. However, in order to make the automated tests independent of each other I want to have the user always logged out at the beginning of each test run.
I know you can delete cookies with Selenium/Appium with https://appium.io/docs/en/commands/web/storage/delete-all-cookies/, but this apparently only works when in a webview context.
Is there any other way to delete SSO cookies in Android and iOS and reset app the state?
I have a Windows Desktop WPF application that is using the MSAL libraries to authorize a user against Azure Active Directory. It is all working, except the prompt where the user selects their account sometimes ends up behind the application (I assume when a user selects a different application in the taskbar prior completing the MSAL prompt).
I have added the WithParentActivityOrWindow option and pointed it to the main window of the application, but that doesn't attach the prompt to anything or force it in front of the application.
Is is possible to do one of the following, and if so, how?
Force the prompt to receive focus whenever the application is the 'active' Windows application
Embed the prompt within a WPF UserControl
For reference, the example code here is almost identical to what I'm using:
https://learn.microsoft.com/en-us/azure/active-directory/develop/scenario-desktop-acquire-token-interactive?tabs=dotnet
Edit: I noticed today that Visual Studio blocks until the OAuth prompt is completed, but I'm not sure how this is accomplished or if Visual Studio is using the MSAL libraries at all.
As the documentation states, AcquireTokenInteractive should be ran on the UI thread. My application is embedded within another application, so once I changed the call to run on the main application's UI thread it started working as expected.
I have an application I Am developing that will be installed into a Citrix Server Farm environment where multiple Users will connect using Citrix XenApp. I want to incorporate ' into the application so that when a User runs up the application it will check for updates and prompt the User to update the application.
I have some uncertainties about this, specifically what considerations I need to make when installing my application on Citrix, e.g. If User A (and many other Users) is in the application and User B launches the application and gets prompted to update how will should this get handled if the application is installed in Program Files where it typically should be installed?
Should I install the application in Program Files and "shadow copy" to the User directory for execution?
Should I install the Application per user when each User first logs in?
Or are there other considerations to be made?
Hope someone has encountered this and can help
I would recommend to install the application per user when each user first logs in. In this way, when a user starts the app, it will update that user's copy and you will avoid file locks that will happen when a second user starts the app when it is being updated.
I have a C# application that is used to capture users screen, this application will be installed using an installer that requires administrator permissions. the application itself needs an active user session but doesn't display any UI elements of its own. My question how to make sure that the application is running whenever a user logs in? and how to make sure that no user (with no admin permission) can close the application?
The application should run on windows XP, 7, 8.
You can install the application so that it starts with every start of windows. You can use the registry for that or the (default user) startup folder.
An user without admin rights will not be able to kill an application that is not his, so if you start the application using i.e. the local system account, he won't be able to kill it. He will not even be able to see it, because the function "show processes from all users" in task manager is limited to users with admin permissions.
Disclaimer: Be aware that under certain legislations, it might be illegal to install such an application in a company network without the users knowing about it.
Use the Task Scheduler. It can launch apps at user logon with elevated privileges. Otherwise if it does not have to be a foreground App use a Windows service.