## If deferral is being shown and 'close apps countdown' or 'persist prompt' was specified, enable those features.
If ($showDefer) {
If ($closeAppsCountdown -gt 0) {
Write-Log -Message "Close applications countdown has [$closeAppsCountdown] seconds remaining." -Source ${CmdletName}
$showCountdown = $true
}
If ($persistPrompt) { $persistWindow = $true }
} If (!($showDefer)) {
If ($closeAppsCountdown -gt 0) {
Write-Log -Message "Close applications countdown has [$closeAppsCountdown] seconds remaining." -Source ${CmdletName}
$showCountdown = $true
}
}
If ($showDefer) {
If ($persistPrompt) { $persistWindow = $true }
}But installing as user is hard... when users are not local admin. What is your solution?We are looking into using Beyond Trust Power Broker to resolve issues like this and other privilege elevation issues. Some applications will still install fine in the system context but are missing user settings. I am going to tackle this problem in the future with active setup rather than Group Policy preferences or say a log on script.
So you have an AD group for each user?Sorry. I should be been clearer. We have an AD group for each application. This also allows applications to easily follow to users primary devices. We use all three methods of UDA. User, Usage and administrator defined methods.
This is during OSD but on day to day. I was thinking showing a message to the user with PSADT asking for a reboot and then using fast retry to see if the problem is solve before returning a true error code. Might it be a good idea? The problem I might see would be in OSD because fast retry in OSD... not sure or being sure all reboot happen when need during OS setup...The PSADT will detect session 0 or task sequences and run non-interactive automatically. If you use Show-InstallationRestartPrompt it is automatically bypassed in this mode. This might be your solution?
What is your average time to create a package for simple to really hard software?
1 to 32 hours. Hard would classify having no option but to repackage.