Installing Redamp.io via GPO

Learn how to install Redamp.io using GPO (Group Policy Object) on all your Windows devices.

Prerequisites

1. Generating credentials for GPO

  1. Log in to Redamp.io as an administrator. (If you are a partner, click on a specific client to open their dashboard and continue to the next step)

  2. Navigate to Devices and click the Import via GPO button in the top right corner.

Redamp.io | Import via GPO
  1. Click the Create new secret button in the top right corner.
Redamp.io | Generate credentials
  1. Configure the following two key values:

Then click the Create button to generate the secret.

Redamp.io | Create new secret
  1. Download the RedampDistribution.ps1 script by clicking the Download script button and copy the generated token.
Redamp.io | Follow instructions
  1. Continue to the next step.

We recommend keeping the token in a file on a share that only domain computers can read. The token then stays out of the Group Policy configuration, and when you renew the token, you only replace the file. The GPO stays the same.

Who gets access and why

You give access to exactly two groups:

Nobody else gets access. Regular users sign in with their own user accounts, which are not members of Domain Computers, so they cannot open the file, even on the same computers.

This step is optional. If you prefer a quicker setup, skip it and enter the token directly with the -Secret parameter in step 4.

Create the folder and the token file

  1. On a file server, open File Explorer and go to the drive where the folder should be, for example C:\.

  2. Turn on file extensions in View -> Show -> File name extensions, so that the file is not saved as token.txt.txt.

  3. Right-click an empty space, select New -> Folder and name it RedampToken.

  4. Open the folder, right-click and select New -> Text Document. Name it token.txt.

  5. Open token.txt, paste the token from step 1 and save the file. The file must contain only the token.

File Explorer | Folder with the token file

Set the folder permissions

  1. Right-click the RedampToken folder and select Properties -> Security -> Advanced.

  2. Click Disable inheritance and select Convert inherited permissions into explicit permissions on this object.

Windows | Disable inheritance
  1. Select every entry in the Permission entries list and click Remove, so that the list is empty.

  2. Click Add -> Select a principal, type Domain Computers, click Check Names and OK. Keep the basic permissions Read & execute, List folder contents and Read, set Applies to to This folder, subfolders and files and click OK.

Windows | Read permission for Domain Computers
  1. Click Add again and add Domain Admins the same way, this time with Full control.

  2. Check that the list contains only Domain Computers (Read & execute) and Domain Admins (Full control), then click Apply and OK.

Windows | Folder permissions

If the GPO also applies to domain controllers, add Domain Controllers with Read & execute as well. Domain controllers are not members of Domain Computers.

Share the folder

  1. Right-click the RedampToken folder and select Properties -> Sharing -> Advanced Sharing....

  2. Select Share this folder and enter RedampToken$ as the Share name. The $ at the end hides the share from network browsing.

Windows | Share name
  1. Click Permissions, select Everyone and click Remove.

  2. Click Add..., add Domain Computers and allow only Read.

Windows | Share permission for Domain Computers
  1. Click Add... again, add Domain Admins and allow Full Control. If you added Domain Controllers to the folder permissions, add it here with Read too.
Windows | Share permission for Domain Admins
  1. Click OK twice. On the Sharing tab, note the Network Path, for example \\DC01\RedampToken$. The full path to the token file is then \\DC01\RedampToken$\token.txt. You will need it in step 4.
Windows | Network path of the share
  1. Click Close.

Optional: verify the setup

If you want to make sure the token is protected, sign in to a domain device as a regular user and enter the full path to the token file in File Explorer. Windows should deny access. This is expected: the devices themselves can still read the file, because they use the computer account.

Continue to the next step.

3. Mapping devices to email via comment attribute

To make sure the Redamp.io application signs in on each device under the intended account after installation, you must set a valid email address from your AD domain in the comment attribute. If the email is not set in this attribute, the application signs in under the first logged-in user from the AD domain, and if that process fails, a default account is assigned.

  1. Open Active Directory Users and Computers, click View, and enable Advanced Features.
Active Directory | Enable Advanced Features
  1. Open the target device account properties and go to the Attribute Editor tab.

  2. Find the comment attribute and set the target email address (for example, test.email@my_domain.com). You can use any email address from your AD domain under which the devices should be signed in.

Active Directory | Comment attribute with email
  1. Verify that all required devices are part of the selected AD group.
Active Directory | Device group
  1. Continue to the next step and configure the GPO deployment.

4. Installing Redamp.io via GPO

  1. Open the Group Policy Management window using the search box or via Server Manager -> Tools -> Group Policy Management.
Redamp.io | Server Manager
  1. Create a new GPO by right-clicking on the Group Policy Objects folder under your domain and selecting New.
Redamp.io | Create new GPO
  1. Enter the GPO name (e.g., Redamp Distribution Script) and click the Ok button.
Redamp.io | GPO Name
  1. Right-click the created GPO and select Edit....
Redamp.io | Edit GPO
  1. Navigate to Computer Configuration -> Policies -> Windows Settings -> Scripts.
Redamp.io | Script location
  1. Then right-click Startup -> Properties.

  2. Go to the PowerShell Scripts tab and click the Show Files... button.

Redamp.io | Add PowerShell script
  1. A shared directory will open; place the RedampDistribution.ps1 script you downloaded from the website.
Redamp.io | Browse shared directory
Redamp.io | Shared directory with script added
  1. You can now close the shared directory. Click the Add... button, then click Browse... and select the RedampDistribution.ps1 script you placed in the previous step.
ParameterDescriptionRequiredExample
-SecretFilePath to the token file on the protected share from step 2 (recommended)Yes, or use -Secret\\DC01\RedampToken$\token.txt
-SecretThe token generated in step 1, entered directlyYes, or use -SecretFileRandom string
Redamp.io | Add script parameters

Both options install and sign in Redamp.io the same way. If devices do not sign in with -SecretFile, for example because the file server is not reachable when the devices start, replace it with -Secret and the token.

  1. Click the Ok button to save changes.

  2. Right-click your organizational unit where you want to distribute Redamp.io and select Link an existing GPO....

Redamp.io | Select organizational unit
  1. Select the GPO you created in the previous steps and click the Ok button.
Redamp.io | Select GPO
  1. To enforce the policy, change the Enforced column to Yes.
Redamp.io | Enforce policy
  1. The PowerShell script will install the Redamp.io application after the Windows device restarts. If Windows Fast Startup is enabled, Shut down does not fully restart the device, so use Restart. On devices where Redamp.io is already installed, the script does nothing and the application keeps itself up to date.

Switching an existing deployment to the protected share

-Secret keeps working, so no change is needed. To switch to the recommended setup:

  1. Download the current RedampDistribution.ps1 in Redamp.io (Devices -> Import via GPO -> Download script) and replace the script in your GPO.

  2. Create the protected share from step 2.

  3. In the GPO script parameters, replace -Secret <token> with -SecretFile \\DC01\RedampToken$\token.txt, using the path of your share.