Skip to main content

Generate Event Log for No-Runs on Login

Planned

Comments

2 comments

  • Official comment
    Steven Hajek

    Hi Josh, thanks for the suggestion, we'll see how we can work this in. 

    This might most commonly happen when the INIPath HKCU reg value isn't created in time, or the path it contains isn't accessible. 

    By default, this is applied by a GPO policy that is assigned to the Computers' OU, and contains the Loopback=Merge GPO setting to cause the user-specific policies to be applied to all domain users logging into those machines.  If the Computer policies are delayed, its possible this could happen, or for other reasons. 

    Workarounds might include "moving" the user-side Enabled, INIPath and Logoff script policies into a new GPO that is assigned to the user's OU instead of the computer's OR set these user-side settings within the base image as a local GPO policy.  (and unconfigure the loopback=merge setting in either case in the computer GPO)

    Hope this helps!

  • Jack Smith

    you could try this option as well.

    LogoffIfTemp.ps1 is a PowerShell script that detects whether the currently logged-in user is running under a temporary Windows profile and, if so, safely logs them off. It also performs cleanup of Group Policy logoff scripts — specifically those associated with Liquidware ProfileUnity — to prevent those scripts from firing during the logoff of a temporary session.

    https://github.com/liquidwarelabs/ProfileUnity/tree/master/Scripts/AutoLogoutOnTempProfile

     

     

    0

Please sign in to leave a comment.