Simplify Logon scripts in Intune without Schedules

Intune does not have a native solution for logon scripts. The community has designed some interesting solutions to this problem using the Intune Management Extension, such as Nicola’s Azure storage based method, Michael Mardahl’s IME reset method and my own hidden vbscript scheduled task method.

The problem with all these solutions is that they rely on scheduled tasks. This is not the most reliable method as the user can easily influence it, and it usually does not support uninstalling or unassigning the script unless you write a specific script for that, assign it to the user, etc yada yada.

This solution can run at logon, at set intervals or both and supports ANY script you write in Intune. invoke-asIntuneLogonScript on Git

Upload to Intune as usual, and set the properties as follows and assign to your users:

Edit: doesn’t happen often that people create the same thing on the same day, but Michael wrote the almost exact same thing so he’s not using scheduled tasks anymore either 🙂

41
Leave a Reply

avatar
10 Comment threads
31 Thread replies
14 Followers
 
Most reacted comment
Hottest comment thread
14 Comment authors
AndyJosJorge SuarezDennis Mauritssam Recent comment authors

This site uses Akismet to reduce spam. Learn how your comment data is processed.

  Subscribe  
newest oldest most voted
Notify of
Sasaus
Guest
Sasaus

Seeing the last code block, I assume this script goes before all your deployed scripts.

Do I set “Run this script using the logged on credentials” to Yes, in case I do have a user targeted script?

Mark
Guest
Mark

How do you remove it so it no longer runs?

Thomas de Roo
Guest
Thomas de Roo

Why don’t you just put your commands or logon-script in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run ?

Dennis Maurits
Guest
Dennis Maurits

How do i remove the script with intune from a computer?

Andy
Guest

Phil is right. Reg add delete did not work when a colon present in the variable. Don´t change it to Remove-Item command, because it doesn´t run in user context, so the “no script run” on logon still occurs.

Replace the script Part against this and everything goes fine:

#set removal key in case computer crashes or something like that
$regpath2 = $regpath.Replace(“:”,””) # must be done because “reg add / delete” did not work when variable contains a colon.
New-ItemProperty -Path “HKLM:\Software\Microsoft\Windows\CurrentVersion\RunOnce” -Name $(Get-Random) -Value “reg delete $regpath2 /f” -PropertyType String -Force -ErrorAction SilentlyContinue

Jorge Suarez
Guest

Hi Jos,

Sorry if this was asked already before but does the script assume the user has no local administrative privileges?

I am testing it on my device but I have local admin rights and the text file does not show up in my test directory. Logging is enabled but no sign of the file being created.

sam
Guest
sam

In what context does this script run? I need to make a regersty change to the HKCU when they log in but if it’s in a system context I don’t think it will work?

Christian
Guest
Christian

So, after some testing I can confirm this script doesn’t work unfortunately.
I tested with the testfile + append. But the file is only created once, and will not be updated later on.
Tested on Windows 10 1909 and Windows 10 1903

Mark
Guest
Mark

I set it up with $autoRerunMinutes = 0. It ran for one login and hasn’t run since. Win10 1903.
No other script modifications made other than replacing ac (Join-Path “c:\temp” “test.txt”) “$($Env:USERNAME) at $(Get-Date)” #example code with my code.

Bicky B
Guest
Bicky B

Hi Jos, Thank you for the I have added following lines of code at the end of your script. Script successfully created the test.txt, a folder with TestOOO. however it failed to add registry entries. If I add a script file with just following (without your code) then all works i.e. registry entries are added as well. Is this known behaviour or it will not support adding registry entries via your code ? ##YOUR CODE HERE ac (Join-Path $Env:temp “test.txt”) “$($Env:USERNAME) at $(Get-Date)” #example code #Test $mydate = Get-Date -Format “ddMMMyyyy_HHmm” $Filename = “TestOOO-$mydate” New-Item -Path $Env:temp -Name $Filename -ItemType… Read more »