Skip to content

Commit fdc351d

Browse files
authored
Update apps-win32-add.md
Updated the Script signature check section as there is no user confirmation is prompted in both cases
1 parent 4a7141d commit fdc351d

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

memdocs/intune/apps/apps-win32-add.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -227,7 +227,7 @@ On the **Detection rules** pane, configure the rules to detect the presence of t
227227

228228
- **Run script as 32-bit process on 64-bit clients**: Select **Yes** to run the script in a 32-bit process on 64-bit clients. Select **No** (default) to run the script in a 64-bit process on 64-bit clients. 32-bit clients run the script in a 32-bit process.
229229

230-
- **Enforce script signature check**: Select **Yes** to verify that a trusted publisher has signed the script, which will allow the script to run with no warnings or prompts displayed. The script will run unblocked. Select **No** (default) to run the script with user confirmation without signature verification.
230+
- **Enforce script signature check**: Select **Yes** to verify that a trusted publisher has signed the script, which will allow the script to run with no warnings or prompts displayed. The script will run unblocked. Select **No** (default) to run the script without signature verification.
231231

232232
The Intune agent checks the results from the script. It reads the values written by the script to the STDOUT stream, the standard error (STDERR) stream, and the exit code. If the script exits with a nonzero value, the script fails and the application detection status is not installed. If the exit code is zero and STDOUT has data, the application detection status is installed.
233233

0 commit comments

Comments
 (0)