FileWave 13.1 TCC Payload Separation (Historical)

Description

This

Apple'spage records a FileWave 13.1 profile migration. For current configuration steps, use Create TCC payloadPrivacy wasPolicy Control Payloads.

Change introduced in FileWave 1313.1

and

FileWave controls13.0 thestored PrivacymacOS sectionTCC ofprivacy thesettings inside a single Security & Privacy Preference.  Since it was controlling the Security & Privacy tab, it was included in one single Security & Privacy Payload, when creating the Fileset.  This, however, reduces flexibility of Privacy Payload distribution.payload. FileWave 13.1 hasseparated addressedTCC this.settings from the General, FileVault, and Firewall settings so administrators could deploy privacy controls independently and use more than one TCC payload.

Information

Legacy Profile Editor layout

The screenshots below show the two payloads in the FileWave 13.1 separates the Privacy TCC payload from the Security & Privacy Preference in our Profile Editor, providing two Security & Privacy PayloadsEditor.

Security & Privacy - iOS and macOS (10.7+) 

IncludingThis thelegacy tabs:payload contained General (macOS only),and FileVault (settings for macOS only),plus Firewall and Privacy settings.

Security & Privacy - macOS (10.14+)

OnlyThis includesseparate legacy payload contained the additional TCC Payload from within Privacy

Upgrading to FileWave 13.1

For any existing payloads, created in 13.0.x, that includedmacOS TCC Privacy Payloads,and duringConsent Control settings.

Historical 13.0 to 13.1 migration

to

When a FileWave 13.1+0.x profile containing TCC settings was migrated to 13.1, the Profile will be converted andprofile will now showdisplayed both Security & Privacy Payloads.payloads. It is highlyThe recommended thatmigration twowas separateto Profiles are created instead;create one containingprofile thefor General, FileVaultFileVault, and Firewall settings and the other containing the Privacy TCC Payload.

With a separate profile for TCC Privacyprivacy Payload,settings.

it

Separating isTCC thensettings possiblealso allowed administrators to deliverdeploy multiple Privacyprivacy Payloads,payloads providing greater granular control.independently.