At the end of the DEP script, if deferred enablement is active, the command FV_DEFERRED_STATUS=$($FDE_SETUP_BINARY status | grep "Deferred" | cut -d ' ' -f6) returns 'active.' while the script is looking for 'active' in the following if statements.
After building a Macbook from factory settings, the command to show filevault status is as follows.
'Deferred enablement appears to be active.'
The command in the script:
Line 828: FV_DEFERRED_STATUS=$($FDE_SETUP_BINARY status | grep "Deferred" | cut -d ' ' -f6)
Returns:
'active.'
I'm not sure if previously it returns 'active' but this is the results I'm seeing on macOS 13.2.1
As a result, at the end of the script, instead of asking users to log out as expected, they are receiving 'Get Started' (Line 850).
- macOS Version 13.2.1
- Jamf Version 10.45.0
- DEP Notify Version 1.1.6
At the end of the DEP script, if deferred enablement is active, the command
FV_DEFERRED_STATUS=$($FDE_SETUP_BINARY status | grep "Deferred" | cut -d ' ' -f6)returns 'active.' while the script is looking for 'active' in the following if statements.After building a Macbook from factory settings, the command to show filevault status is as follows.
'Deferred enablement appears to be active.'
The command in the script:
Line 828:
FV_DEFERRED_STATUS=$($FDE_SETUP_BINARY status | grep "Deferred" | cut -d ' ' -f6)Returns:
'active.'
I'm not sure if previously it returns 'active' but this is the results I'm seeing on macOS 13.2.1
As a result, at the end of the script, instead of asking users to log out as expected, they are receiving 'Get Started' (Line 850).