In-Place macOS Sierra Upgrade Script

TylerC
New Contributor III

Hello,

I am trying to follow this guide from JAMF: https://www.evernote.com/shard/s398/sh/bec8a262-e33d-4ad9-80fa-05b939db6d8d/f4ca396a63caa510

I am using the script noted here: https://www.evernote.com/shard/s398/sh/bec8a262-e33d-4ad9-80fa-05b939db6d8d/f4ca396a63caa510/res/9163d1d7-3bbf-4e2f-b70a-0cd447c749a1/startosinstall.sh

I got everything else working so far (you do need another policy to place the .dmg in the applications folder that the article neglects to tell you). I would like the script to force the restart instead of being "soft". I tested it and found that any open application will stop the upgrade.

Just need it to forcibly and immediately preform the restart.

Thanks.

Here is the script:

#!/bin/bash
/Applications/Install macOS Sierra.app/Contents/Resources/startosinstall --applicationpath "/Applications/Install macOS Sierra.app" --volume $1 --rebootdelay 30 --nointeraction
killall "Self Service"
126 REPLIES 126

mvu
Valued Contributor

I like this PDF from JAMF better. Worked well for me.

https://www.evernote.com/shard/s398/sh/bec8a262-e33d-4ad9-80fa-05b939db6d8d/f4ca396a63caa510

pcrandom
Contributor

Dumb question: Where are these PDFs from? Can they be found in https://www.jamf.com/resources/?

TylerC
New Contributor III

Hello, I am not debating the PDF. I figured that all out. I just need help with the script.

Thanks.

seann
Contributor

Try the command "reboot now". Or you can use use the restart options within the policy.

TylerC
New Contributor III

Where would I be placing that command? I know nothing of scripts unfortunately.

TylerC
New Contributor III

I keep getting this error. Does anyone know what could cause it?

Error:
Script result: Helper tool creashed...
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
No matching processes were found
Error running script: return code was 1.

seann
Contributor

I would check your syntax. According to here https://macops.ca/new-adventures-in-automating-os-x-installs-with-startosinstall, the nointeraction flag should suppress the agreement.

No matching process found is probably related to your killall Self Service command, as anything being run via jamf is done in the context of root, while the self service process belongs to the user who launched it.

Finally, "reboot now" would just be another line in your script.

TylerC
New Contributor III

Devices do not even appear to be attempting to upgrade anymore..

I think the problem is here: Script result: Helper tool creashed...
Yes the misspelling is actually from the script.

Nonetheless Jamf gave me the script and we have tried many things to get it working with no success. Currently at a complete stop.

stevewood
Honored Contributor II

@TylerC might I suggest you go a different route for doing these upgrades? I would highly recommend the process that @rtrouton outlines on his blog:

Providing OS X Upgrades via Casper

I've used that method to go from 10.10 to 10.11 and am using it now to go to 10.12. It's painless, and it works.

TylerC
New Contributor III

I will have to look into it some more. Some looks a bit over my head and we are not using self-service. Overall pretty upset by the lack of support from Jamf.

stevewood
Honored Contributor II

@TylerC you should be able to utilize Rich's methods without using Self Service. And he does a great job of explaining the details.

I'm assuming you've sent an email in to support@jamf.com, right?

stevewood
Honored Contributor II

@TylerC sorry, just re-read your earlier post that you had been given the script my Jamf.

I'm not certain what all you have tried, but to get the reboot to happen immediately, but looking at the verbs of the binary (startosinstall) the nointeraction flag does not appear to be there anymore:

Steve-Wood:Resources steve$ ./startosinstall --?
startosinstall: unrecognized option `--?'
Usage: startosinstall --applicationpath <install macOS.app path> --volume <target volume path>

Arguments
--volume, a path to the target volume.
--applicationpath, a path to copy of the OS installer application to start the install with.
--license, prints the user license agreement only.
--agreetolicense, agree to license the license you printed with --license.
--rebootdelay, how long to delay the reboot at the end of preparing. This delay is in seconds and has a maximum of 300 (5 minutes.
--pidtosignal, Specify a PID to which to send SIGUSR1 upon completion of the prepare phase. To bypass "rebootdelay" send SIGUSR1 .
--usage, prints this message.

Example: startosinstall --volume /Volumes/Untitled --applicationpath "/Applications/Install macOS.app"

So, I would modify the script as follows:

#!/bin/bash
/Applications/Install macOS Sierra.app/Contents/Resources/startosinstall --applicationpath "/Applications/Install macOS Sierra.app" --volume $1 --rebootdelay 1

Since you are not using Self Service the killall "Self Service" can be removed. As the help on the binary states, the rebootdelay is in seconds, so setting that to 1 should reboot within 1 second of completing preparations.

I have not tested this just yet, but when I get to the office I will try to replicate this in a VM.

stevewood
Honored Contributor II

@TylerC after countless reboots of my VM and countless restores back to a snapshot, I had success with the method you are trying. I utilzed the script you posted (I was wrong about the nointeraction verb):

#!/bin/bash

/Applications/Install macOS Sierra.app/Contents/Resources/startosinstall --applicationpath "/Applications/Install macOS Sierra.app" --volume $1 --rebootdelay 1 --nointeraction

I did not cache the OS because I did not want to put that into my JSS. I copied the Install macOS Sierra app into the Applications folder on the VM, added the above script, and then created a policy that was triggered to At Login with the script. That method worked perfectly.

The only time I had any issues was when I tried to trigger the policy during Recurring Check In. For whatever reason I had mixed results, more often than not resulting in failure.

Not sure how you are triggering this policy, but you might need to look at how you get the policy started.

VladCabrera
New Contributor III

I was provided this script for an upgrade without user interaction. I am still testing and only found that the messages are being sent to system event. this is causing an error when the policy is run.

https://github.com/kc9wwh/macOSUpgrade

Rosko
Contributor II
Contributor II

@VladCabrera Could you provide me with some more details on the issues you are seeing with that workflow? I've tested it on a few systems now with no issue, so very curious as to what you are seeing.

VladCabrera
New Contributor III

@Rosko Thanks for joining. I have 2 policy one delivers a dmg created with Composer, that drops Install Sierra.app to Users/Shared/ with 755 permissions. Owner is root(0) RWX, Group wheel(0) RX, Everyone RX.

The script is set as a separate policy with priority set to after. I can see the machines, Yosemite and EL Capitan, download and attempt to execute but fails with error.

Executing Policy macOS Sierra Silent Install
Running script macOS10.12Upgrade...
Script exit code: 0
Script result: 36:258: execution error: An error of type -10810 has occurred. (-10810)

I'm thinking jamfhelper can't tell the logged on user to send the message and quits.

My hardware are all Mac mini.

If I run the script manually, ./macupgrade.sh it skips to startosinstall command.

Rosko
Contributor II
Contributor II

@VladCabrera Attached is an updated script with some echoes to let us see in the policy logs what is happening. But one thing to note is that we are sending jamfHelper and startosinstall to background processes so the script should actually complete and the processes will still be running until the startosinstall process initiates the reboot.

But if you could run the below script and let me know the output, as well as if you are seeing the jamfHelper screen or not.

#!/bin/bash

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 
#
# Copyright (c) 2017 Jamf.  All rights reserved.
#
#       Redistribution and use in source and binary forms, with or without
#       modification, are permitted provided that the following conditions are met:
#               * Redistributions of source code must retain the above copyright
#                 notice, this list of conditions and the following disclaimer.
#               * Redistributions in binary form must reproduce the above copyright
#                 notice, this list of conditions and the following disclaimer in the
#                 documentation and/or other materials provided with the distribution.
#               * Neither the name of the Jamf nor the names of its contributors may be
#                 used to endorse or promote products derived from this software without 
#                 specific prior written permission.
#
#       THIS SOFTWARE IS PROVIDED BY JAMF SOFTWARE, LLC "AS IS" AND ANY
#       EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
#       WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
#       DISCLAIMED. IN NO EVENT SHALL JAMF SOFTWARE, LLC BE LIABLE FOR ANY
#       DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
#       (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
#       LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
#       ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
#       (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
#       SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
#
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 
# 
# This script was designed to be used in a Self Service policy to ensure specific
# requirements have been met before proceeding with an inplace upgrade to macOS Sierra, 
# as well as to address changes Apple has made to the ability to complete macOS upgrades 
# silently. 
#
# REQUIREMENTS:
#           - Jamf Pro
#           - macOS Sierra Installer must be staged in /Users/Shared/
#
#
# For more information, visit https://github.com/kc9wwh/macOSUpgrade
#
#
# Written by: Joshua Roskos | Professional Services Engineer | Jamf
#
# Created On: January 5th, 2017
# Updated On: February 13th, 2017
# 
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 
# USER VARIABLES
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 

##Enter 0 for Full Screen, 1 for Utility window (screenshots available on GitHub)
userDialog=0

##Title to be used for userDialog (only applies to Utility Window)
title="macOS Sierra Upgrade"

##Heading to be used for userDialog
heading="Please wait as we prepare your computer for macOS Sierra..."

##Title to be used for userDialog
description="
This process will take approximately 5-10 minutes. 
Once completed your computer will reboot and begin the upgrade."

##Icon to be used for userDialog
##Default is macOS Sierra Installer logo which is included in the staged installer package
icon=/Users/Shared/Install macOS Sierra.app/Contents/Resources/InstallAssistant.icns

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 
# SYSTEM CHECKS
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 

##Check if device is on battery or ac power
pwrAdapter=$( /usr/bin/pmset -g ac )
if [[ ${pwrAdapter} == "No adapter attached." ]]; then
    pwrStatus="ERROR"
    /bin/echo "Power Check: ERROR - No Power Adapter Detected"
else
    pwrStatus="OK"
    /bin/echo "Power Check: OK - Power Adapter Detected"
fi

##Check if free space > 15GB
freeSpace=$( /usr/sbin/diskutil info / | grep "Free Space" | awk '{print $4}' )
if [[ ${freeSpace%.*} -ge 15 ]]; then
    spaceStatus="OK"
    /bin/echo "Disk Check: OK - ${freeSpace%.*} Free Space Detected"
else
    spaceStatus="ERROR"
    /bin/echo "Disk Check: ERROR - ${freeSpace%.*} Free Space Detected"
fi

# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 
# APPLICATION
# # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # 

if [[ ${pwrStatus} == "OK" ]] && [[ ${spaceStatus} == "OK" ]]; then
    ##Launch jamfHelper
    if [[ ${userDialog} == 0 ]]; then
        /bin/echo "Launching jamfHelper as FullScreen..."
        /Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType fs -title "" -icon "$icon" -heading "$heading" -description "$description" &
        jamfHelperPID=$(echo $!)
    fi
    if [[ ${userDialog} == 1 ]]; then
        /bin/echo "Launching jamfHelper as FullScreen..."
        /Library/Application Support/JAMF/bin/jamfHelper.app/Contents/MacOS/jamfHelper -windowType utility -title "$title" -icon "$icon" -heading "$heading" -description "$description" -iconSize 100 &
        jamfHelperPID=$(echo $!)
    fi

    ##Begin Upgrade
    /bin/echo "Launching startosinstall..."
    /Users/Shared/Install macOS Sierra.app/Contents/Resources/startosinstall --volume / --applicationpath /Users/Shared/Install macOS Sierra.app --nointeraction --pidtosignal $jamfHelperPID &
    /bin/sleep 3
else
    /bin/echo "Launching AppleScript Dialog..."
    /usr/bin/osascript -e 'Tell application "System Events" to display dialog "Your computer does not meet the requirements necessary to continue.

    Please contact the help desk for assistance. " with title "macOS Sierra Upgrade" with text buttons {"OK"} default button "OK" with icon 2'
fi

exit 0

Thanks!
Josh

dan-snelson
Valued Contributor II

Thanks @Rosko!

For those Macs which are on older versions of macOS 10.12.x and already have current version of /Applications/Install macOS Sierra.app, we added logic to determine the free space on a Sierra box:

## Determine free space ...
osMinorVersion=$( /usr/bin/sw_vers -productVersion | /usr/bin/cut -d. -f2 )
if [[ "$osMinorVersion" -lt 12 ]]; then
    freeSpace=$( /usr/sbin/diskutil info / | grep "Free Space" | awk '{print $4}' )     
else
    freeSpace=$( /usr/sbin/diskutil info / | grep "Available Space" | awk '{print $4}' )
fi

--
Dan

Rosko
Contributor II
Contributor II

@dan.snelson You beat me to the punch! lol

The next version will have the updated support for running on macOS 10.12, just didn't think it would be needed till 10.13 ;)
I took a little different approach, but the end result is the same...

##Check if free space > 15GB
if [[ $osMinor -ge 12 ]]; then
    freeSpace=$( /usr/sbin/diskutil info / | grep "Available Space" | awk '{print $4}' )
else
    freeSpace=$( /usr/sbin/diskutil info / | grep "Free Space" | awk '{print $4}' )
fi

if [[ ${freeSpace%.*} -ge 15 ]]; then
    spaceStatus="OK"
    /bin/echo "Disk Check: OK - ${freeSpace%.*} Free Space Detected"
else
    spaceStatus="ERROR"
    /bin/echo "Disk Check: ERROR - ${freeSpace%.*} Free Space Detected"
fi

But, I'm curious...are you using the installer to upgrade minor versions versus a combo update or did I miss read that?

VladCabrera
New Contributor III

@Rosko Ran into one with the script and my Mac mini's. it doesn't like the power management query in which fails because it seems to look for only an adapter. These are my only test machine at the moment.

After removing the power check, I was able to run the script but stuck at the preparing banner for 50 minutes. I killed the PID for jamfhelper.

Results. TUSMA03MDKVT007:Shared v781598$ vim MacOSSierra_Pwr.sh TUSMA03MDKVT007:Shared v781598$ ./MacOSSierra_Pwr.sh Disk Check: OK - 476 Free Space Detected
Launching jamfHelper as FullScreen...
Launching startosinstall...
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
TUSMA03MDKVT007:Shared v781598$ Error: could not get authorization...

Rosko
Contributor II
Contributor II

@VladCabrera Thanks for the Update! That was definitely not intended behavior.

I've updated the script on GitHub w/ the following:
- Replaced Final AppleScript Dialog w/ jamfHelper
- Added Output for Policy Logs
- Added Support for macOS 10.12 + for Free Space Check
- Fixed Issue with Power Check Only Applies to Laptops

I've tested this on a MacBook Pro, MacMini and a Mac VM, and all the way back to 10.8 so hopefully that should work for you :)

dan-snelson
Valued Contributor II

@Rosko Nice updates.

Since you're being your usual, helpful self, I added the following snippet to use Parameter 4 to validate which version of the installer is present client-side (i.e., "10.12.3").

(I am looking for the installer in /Applications/)

## Script Parameter
requiredInstallerVersion="$4"         # Required Installer Version

## Check if the available installer is the appropriate version
installerVersion=$( /usr/bin/defaults read /Applications/Install macOS Sierra.app/Contents/SharedSupport/InstallInfo.plist "System Image Info" | /usr/bin/grep version | /usr/bin/awk '{print $3}' | /usr/bin/tr -d '";' )

# Validate a value has been specified for Parameter 4 ...
if [ ! -z "${requiredInstallerVersion}" ]; then

    if [[ "${requiredInstallerVersion}" == "${installerVersion}" ]]; then

        installerVersionCheck="OK"

    else

        installerVersionCheck="ERROR"

    fi

else

    installerVersionCheck="ERROR: Version not specified"
    jssLog "ERROR: Parameter 4 not specified"

    exit 1

fi

--
Dan

VladCabrera
New Contributor III

Still running into issues completing the task. Getting stuck on trying to run startosinstall command.

tma0029avkvtad:Shared Setup$ ./macOS10.12Upgrade.sh Power Check: OK - AC Power Detected
Disk Check: OK - 44GB Free Space Detected
Launching jamfHelper as FullScreen...
Launching startosinstall...
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
Error: could not get authorization...
tma0029avkvtad:Shared Setup$ ps PID TTY TIME CMD 678 ttys000 0:00.01 -bash 934 ttys001 0:00.01 -bash 961 ttys001 0:00.18 /Library/Application Support/JAMF/bin/jamfHelper.app/C
tma0029avkvtad:Shared Setup$

I took the above by ssh to the computer. Manually I gave the script 755 rights, but we have limited the sudo command to particular files and commands. I have to work on getting this script added to the allowed list.

dan-snelson
Valued Contributor II

@VladCabrera For what it's worth, here's the install command I'm using (but the installer is in /Applications):

/Applications/Install macOS Sierra.app/Contents/Resources/startosinstall --applicationpath "/Applications/Install macOS Sierra.app" --volume $1 --rebootdelay 30 --nointeraction

--
Dan

VladCabrera
New Contributor III

@dan.snelson @Rosko When you did your testing was it via policy or manually? I am able to invoke the script manually with sudo ./macOS10.12Upgrade.sh.

dan-snelson
Valued Contributor II

@VladCabrera We're running ours via a Self Service policy.


--
Dan

Rosko
Contributor II
Contributor II

Thanks @dan.snelson I plan to eventually do something similar I think (just need time). Basically will check if there is already the "Install macOS Sierra.app" in the Applications folder and if the version matches use that. Otherwise we'll download (call another policy) to download the latest version we have and use that for the process. Shouldn't take much to do, just time.

@VladCabrera All my testing was done using Self Service (so, basically script is run as root). As you have stated, it appears to be hanging on the startosinstall command. What version of the macOS Sierra installer app file are you trying to use and on what OS version? Also, with the installer on the end-point, can you try running the below command and see if the command itself works?

/path/to/Install macOS Sierra.app/Contents/Resources/startosinstall --volume / --applicationpath /path/to/Install macOS Sierra.app --nointeraction

You can also check out /var/log/install.log to see if there is any other errors there, but running this manually you should see a lot more information.

Dalmatian
Contributor

@TylerC @stevewood

any luck on this error? i got the same error
Error:
Script result: Helper tool creashed...
By using the agreetolicense option, you are agreeing that you have run this tool with the license only option and have read and agreed to the terms.
If you do not agree, press CTRL-C and cancel this process immediately.
No matching processes were found
Error running script: return code was 1.

stevewood
Honored Contributor II

@Dalmatian if you look at my last post, the only time I was able to successfully utilize that method was if I triggered the installation via a Login trigger on the policy. I did not try using Self Service, if I recall.

How are you triggering this? And have you looked at the other methods mentioned? Like Rich's method I posted in the first post I did. I've been using that method since 10.10 with no issues.

Dalmatian
Contributor

@stevewood

I've tried with a mixed trigger. but just changed it to Login only.

and funny thing is, i ran the command line manually in terminal and still got error, and upgrade can't proceed.

any idea?

stevewood
Honored Contributor II

@Dalmatian can you post the line in your script where you are calling the installer? It should be like what is posted above:

/path/to/Install macOS Sierra.app/Contents/Resources/startosinstall --volume / --applicationpath /path/to/Install macOS Sierra.app --nointeraction

I would take that line and try running it from within Terminal to see if it works.

VladCabrera
New Contributor III

cede46960c3b40338ff91ca7dc298e60
running startosinstall manually will ask for my password to confirm I want to continue. Same thing with running Joshua's script sudo ./MacOS10.12upgrade.sh. I put both the script and the installer app in the same folder. The new policy is a command #/bin/sh -v -x /Users/Shared/MacOs10.12upgrade.sh

Execute Command
Command to execute on computers. This command is executed as the "root" user

/bin/sh -v -x /Users/Shared/MacOs10.12upgrade.sh

I put it in this location and remove the script because my understanding is that when it is in the script section the policy will run as the current user.

Rosko
Contributor II
Contributor II

@VladCabrera Is it working for you when running the script that way? I unfortunately haven't seen this issue anywhere else so kinda at a loss of how to suppress that as it should be done via the -nointeraction switch.

I also wanted to clarify that when ever you run a script from the JSS whether in a check-in policy or via Self Service it is run as root when executed.

VladCabrera
New Contributor III

@Rosko When in doubt start from the beginning. That's my quote of the day.

I downloaded the script from GitHub again. This time I didn't open it with TextEdit. My default TextEdit format is .rft. So think my original issues may have been with how TextEdit change file data. Can't confirm but didn't care after working on 2 mac mini's this time around.

My new JAMF policies are: 1. download a copy of the Installer Sierra.app file into /Users/Shared and update inventory. 2. Enable the script as a Self Service policy for the logged on user to run from Self Service

This method has worked great thus far during lab testing. I was comfortable in the results enough to attempt another type of policy in which the policy is not available to the user in Self Service for an upgrade button. The idea is to force the upgrade from 10.10 and below OS. Let say a user loves their maverick machine and doesn't want to upgrade even if its available. As Mr. bad guy I can say your machine is being upgraded anyway.

Rosko
Contributor II
Contributor II

@VladCabrera Awesome! Glad to hear everything is working now. This issues was bothering me, so glad its working now :)

Have a great weekend!
~Josh

rqomsiya
Contributor III

The script uploaded by Josh from JAMF seems to never complete on some of my machines. Here is the output log from the JSS:

[STEP 1 of 5] Executing Policy macOS Sierra Upgrade [STEP 2 of 5] Running script macOS_Sierra_10.12.x_upgrade.sh... Script exit code: 0 Script result: Power Check: OK - AC Power Detected Disk Check: OK - 962GB Free Space Detected Launching jamfHelper as FullScreen... Launching startosinstall... [STEP 3 of 5] [STEP 4 of 5] Inventory will be updated when all queued actions in Self Service are complete. [STEP 5 of 5]

The JAMFHelper screen just stays up, but self-service has finished running the policy. I'm lost as to why its working on some machines but not others. I have not modified the script

rqomsiya
Contributor III

The script uploaded by Josh from JAMF seems to never complete on some of my machines. Here is the output log from the JSS:

[STEP 1 of 5] Executing Policy macOS Sierra Upgrade [STEP 2 of 5] Running script macOS_Sierra_10.12.x_upgrade.sh... Script exit code: 0 Script result: Power Check: OK - AC Power Detected Disk Check: OK - 962GB Free Space Detected Launching jamfHelper as FullScreen... Launching startosinstall... [STEP 3 of 5] [STEP 4 of 5] Inventory will be updated when all queued actions in Self Service are complete. [STEP 5 of 5]

The JAMFHelper screen just stays up, but self-service has finished running the policy. I'm lost as to why its working on some machines but not others. I have not modified the script .

bpavlov
Honored Contributor

rqomsiya
Contributor III

Hi @bpavlov I would go that route except one of our requirements was zero user interaction. As we have FV2 enabled the above workflow would require users to authenticate against FV2 to finish the installation.

I actually was able to get the script working by flushing user and system caches via policy.

Thanks for the feedback though!