Documentation

How to use CloudGPP to generate and deploy GPP scripts via Intune

Overview

CloudGPP is a free, browser-based tool that generates production-ready PowerShell scripts for deploying Group Policy Preferences (GPP) via Microsoft Intune — without requiring an on-premises Active Directory or Group Policy infrastructure.

Each generator targets a specific GPP type: Registry Keys, Drive Maps, Shortcuts, and Printers. You configure the settings in the UI, click Preview, and get a script ready to paste into Intune.

How it works

All script generation happens in your browser — no data is sent to any server. The generated PowerShell scripts are self-contained and include:

1A standard script header with #Requires -Version 5.1 and error handling.
2Transcript logging written to the Intune Management Extension log folder.
3Individual try/catch blocks per item, so one failure does not abort the rest.
4A Write-Log helper that timestamps every operation.

The workflow in the UI is:

1Add items manually via the form, or import from an existing file (supported for Registry and Shortcuts).
2Click Preview to generate the PowerShell script.
3Copy or Download .ps1 and deploy it in Intune.
Note: The Preview button turns into Update Preview when you modify items after a preview was generated, so you always know whether the displayed script is current.

Registry Keys

Supports all five registry hives (HKLM, HKCU, HKCR, HKU, HKCC) and all standard value types.

TypeInput format
REG_SZPlain string, e.g. C:\Program Files\App
REG_DWORDDecimal integer, e.g. 1
REG_QWORDDecimal integer, e.g. 1234567890
REG_BINARYSpace-separated hex pairs, e.g. 01 00 AB FF
REG_MULTI_SZComma-separated values, e.g. Value1,Value2
REG_EXPAND_SZString with env variables, e.g. %APPDATA%\App

You can import an existing .reg file to pre-populate the list. Use Download .reg File to export the current items back to a .reg file.

Note: Registry scripts run in SYSTEM context by default. Use HKCU only for per-user settings deployed in user context.

Drive Maps

Maps network drives using net use. Each entry requires a drive letter and a UNC path.

Drive letterSingle letter, e.g. H — the colon is added automatically.
UNC path\\server\share format.
ReconnectWhether to make the mapping persistent across reboots.
LabelOptional display name shown in File Explorer (informational comment in script).
ActionCreate maps the drive. Delete removes an existing mapping.
Note: Drive Maps scripts must run in user context. In Intune, set Run this script using the logged-on credentials to Yes.

Shortcuts

Creates or removes .lnk shortcut files using PowerShell's WScript.Shell COM object.

NameFilename of the .lnk file (without extension).
Target pathFull path to the executable or file.
ArgumentsOptional command-line arguments passed to the target.
Start inWorking directory when the shortcut is launched.
Icon pathOptional path to an .ico file or executable containing the icon.
LocationDesktop, Start Menu, All Users Desktop, or All Users Start Menu.

Upload one or more existing .lnk files to automatically extract their target path, working directory, arguments, and icon path.

Printers

Installs or removes network printers using Add-Printer -ConnectionName.

UNC path\\printserver\PrinterName format.
Set as defaultCalls WScript.Network.SetDefaultPrinter after adding.
ActionAdd installs the printer. Remove uninstalls it.
Note: Printer scripts must run in user contextAdd-Printer -ConnectionName requires an active user session. For per-device shared printers installed in SYSTEM context, consider rundll32 printui.dll,PrintUIEntry instead.

Deploying in Intune

All scripts are designed to be deployed as Intune Platform Scripts (Devices → Scripts → Add → Windows 10 and later).

1Download the .ps1 file from the Preview panel.
2In Intune, go to Devices → Scripts and remediations → Platform scripts → Add → Windows 10 and later.
3Upload the script file and configure the execution context:
GeneratorRun as logged-on userEnforce signature check
Registry Keys
No (SYSTEM)
Optional
Drive Maps
Yes (User)
Optional
Shortcuts
Depends on location
Optional
Printers
Yes (User)
Optional
Note: Set Run script in 64-bit PowerShell host to Yes for registry scripts that target 64-bit keys, to avoid WOW64 redirection issues.

Log files

Every generated script writes a timestamped transcript log using PowerShell's Start-Transcript.

SYSTEM context
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\
User context
C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\Users\

Log files are named <ScriptType>_yyyyMMdd_HHmmss.log, for example Registry_20250101_143000.log. Each entry is prefixed with a timestamp and severity level (INFO / ERROR).

Note: These paths match the standard Intune Management Extension log directory, making it easy to collect them via Intune's log collection feature or a monitoring solution that already watches that folder.