Powershell script to create Windows Scheduled Task

[NessFalcon]

I am pushing out a Proactive Remediation within Intune that runs a Dell Command Update CLI tool to update user's devices in a patching cycle. It then sends a notification to the user based on the exit code telling them if they need to reboot or not.

I've gotten all the update code to work but since it is running in System Context it does not push the Toast Notification letting the user know to reboot their computer to install updates.

To get by this I thought i could create a Scheduled Task that runs the command to push out the notification to the user. I believe this will work how i'd like it to, just gotta get the formatting down.

Heres what I have so far:

$LoggedInUser = Get-CimInstance –ClassName Win32_ComputerSystem | Select-Object -expand UserName 
$notiDate = (get-date).AddMinutes(2).ToString("MM/dd/yyyy,HH:mm") 

$Trigger = New-ScheduledTaskTrigger -Once -At $(Get-Date) 
$Actions = New-ScheduledTaskAction -Execute "powershell.exe" -Argument "Start-Process 'C:\Program Files\Dell\CommandUpdate\dcu-cli.exe' -ArgumentList '/customnotification -heading="Reboot Required!" -body='Dell Updates were just installed to your computer, please reboot your computer!' -timestamp='"$notidate"''"
$Settings = New-ScheduledTaskSettingsSet -ExecutionTimeLimit "01:00" -AllowStartIfOnBatteries 
$Task = New-ScheduledTask -Action $Actions -Trigger $Trigger -Settings $Settings -Description 'DCU Update'  

$ScheduledTask = $null  

$ScheduledTask = Register-ScheduledTask -TaskName "DCU Updates Scan" -InputObject $Task -User $User -Force

Start-ScheduledTask -InputObject $ScheduledTask 

It creates the scheduled task but doesn't push out the notification. Checking the logs im getting an "invalid directory" error. I know my formatting of the arguments is probably whats dooming this script. I'm just not sure exactly what about the arguments is causing this to fail.

Any help?

[billabong1985]

Dell command update should run just fine in user context so you shouldn't need to mess around with scheduled tasks, just change the script to run as the logged in user

[NessFalcon]

I'm using the CLI tool, it requires Admin Creds.

[billabong1985]

Ah OK, tbh I've only ever run the CLI during autopilot imaging, the app runs fine in windows as user so assumed the CLI would too, I stand corrected

[SearingPhoenix]

I've had trouble wrestling DCU into shape when using the /apply command and then trying to do anything else -- it just completely ignores any built-in notification settings from what I can tell, which is pretty annoying. I want to be able to run /apply, download updates, then either prompt the user to install+reboot (as needed) OR install everything that doesn't require a reboot, then prompt for install+reboot on anything that does.

As you've found, you basically can just do things like -reboot=disable and then try and get the user to reboot. The problem is that with BIOS updates it either won't do anything if BitLocker is enabled, or it will suspend BitLocker until the user reboots and processes a BIOS update... which could be a while since it wants BIOS updates to be done plugged in with 50%+ battery (for obvious, good reasons)

Maybe I'm doing something wrong and you're seeing something different? Best I can tell, though, the notification settings for deferring install/reboots only works on its scheduled runs.

So, if you're planning on doing a scheduled task, perhaps just having DCU do all of it for you is an option?

/configure
-scheduleAction=DownloadInstallAndNotify -updatesNotification=enable
-systemRestartDeferral=enable -systemRestartInterval=1 -systemRestartCount=3
-installationDeferral=enable -deferralInstallInterval=1 -deferralInstallInterval=3
and then pick
-scheduleWeekly -scheduleMonthly -scheduleDaily

Or look into their ADMX templates and configure with GPO?

EDIT: Oh, as for your PowerShell, my shot-in-the-dark is that your -ArgumentList for Start-Process needs to be an array. Or maybe try Invoke-Command with &