Skip to content

3.9.3
Compare
Choose a tag to compare
@Micke-K Micke-K released this 11 Dec 08:02
· 20 commits to master since this release
3.9.3
83c845f

New features

  • New tool - Get Assignment Filter usage

    • List all policies and assignments with a Filter defined
      Based on Issue 141
      NOTE: Start the tool from: Views -> Intune Tools -> Intune Filter Usage

  • Batch Export of App Content Encryption Key from Intunewin files
    This script can export encryption keys from existing intunewin files
    Example:
    Export-EncrytionKeys -RootFolder C:\Intune\Packages -ExportFolder C:\Intune\Download
    This will export the encryption key information for each .intunewinfiles under C:\Intune\Packages
    One json file will be created (for each .intunwinfile) in the C:\Intune\Download folder
    File name will be <IntunewinFileBaseName>_<UnencryptedFileSize>.json
    Do NOT rename this file since the script will search for that file when downloading or exporting App content
    The script will not require authentication and it will have no knowledge of apps in Intune
    Filename and unencrypted file size is used as the identifier to match app content in Intune with encryption file
    Important notes:
    Exported and decrypted .intunewin files are not supported to use for import at the moment.
    These files are just the "zip" version of the source and can be unzipped with any zip extraction tool
    The .intunewin file used for import has the "zip" version of the file and an xml with the encryption information +
    additional file information eg. msi properties, file size etc.
    Use the exported unencrypted "zip" version to restore the original files. Re-run the packaging tool if it should be re-used as applications content

    Please report any issues or create a discussion if there are any questions
    Script is located: <RootFolder>\Scripts\Export-EncrytionKeys.ps1

Fixes

  • Export

    • Fixed issue where Assignments were included in export even if 'Export Assignments' was unchecked
      Based on Issue 171

  • Documentation

    • Fixed issue where filter was not documented on some policies
    • Fixed issue with Word Output provider if a policy only had one settings

  • Custom ADMX Files

    • Fixed bug with migrating custom policies between environments. Cache was not cleared when swapping tenants or imported additional ADMX files
    • Fixed documentention issue with Administrative template policies in GCC environment. Name and Category was missing
      Based on Issue 174
    • Custom ADMX based policies was missing properties when swapping tenant
      Based on Issue 124

  • Generic

    • Fixed logging issues when processing objects with a group that was deleted. ID was not reported
    • Generic Batch request function created to support other batch requests eg Groups
Assets 2
Loading