DCV Client bundled for Microsoft Intune

The 14GB file size occurs because the Microsoft Win32 Content Prep Tool (IntuneWinAppUtil.exe) packages everything located in the specified "Source Folder." If your MSI is sitting in your Downloads or Desktop folder, the tool is likely bundling every other file in that directory.

To fix this, use a Clean Folder approach:

1. Isolate the MSI: Create a new, empty folder (e.g., C:\DCV_Build).
2. Move the Installer: Place only the nice_dcv_client_x64.msi into that folder.
3. Run the Tool:
   • Point the Source Folder to your new C:\DCV_Build folder.
   • Point the Setup File to the MSI within that folder.
4. Silent Install: When uploading to Intune, use the standard silent switch: msiexec /i "nice_dcv_client_x64.msi" /qn /norestart

This will keep your .intunewin package close to the original 45MB size, as it will no longer include unrelated local data.

Based on the available AWS documentation, there isn't specific guidance about bundling the DCV Client for Microsoft Intune or troubleshooting the file size inflation issue you're experiencing when using the Microsoft Intune packaging tool.

The documentation does cover AWS integration with Microsoft Intune in other contexts, such as using AWS Private CA Connector for SCEP with Microsoft Intune for certificate management, and managing Amazon WorkSpaces with Intune. However, these don't address the DCV Client packaging scenario you're describing.

The 14GB balloon from a 45MB MSI installer suggests the Intune packaging tool may be capturing dependencies, runtime environments, or temporary files during the conversion process. This is a Microsoft Intune packaging tool behavior rather than an AWS DCV-specific issue.

Since you mentioned that Amazon and Microsoft offer DCV Client in the Enterprise Catalog for Intune (which you don't have access to), that pre-packaged version would be the recommended approach. For your specific packaging challenge, you may need to:

1. Consult Microsoft Intune documentation and support regarding the Win32 Content Prep Tool behavior
2. Review the packaging tool's logs to understand what's being included
3. Consider alternative deployment methods for DCV Client if the Intune packaging continues to be problematic

For DCV-specific deployment questions, I'd recommend reaching out to AWS Support directly, as this appears to be an edge case not covered in the standard documentation.
Sources
Extension architecture - Amazon DCV
https://docs.aws.amazon.com/whitepapers/latest/streamline-workspaces-with-intune/meta-inf/related-resources.html