PowerShell (Manual)

To deploy the Lockfy Agent manually on a Windows device, make sure you have the following:

1. Administrator access to the device (Local or domain accounts).
2. The Lockfy Agent deployment PowerShell script.

---

Copy the Script

Copy the signed deployment script provided by your organization to the root of the C: drive. In the example shown, the file name is LOCKFY_AGENT_DEPLOYMENT_GPO_SIGNED.ps1.

Start “Windows Powershell”

1. Open the Start menu.
2. Search for Windows PowerShell.
3. Right-click Windows PowerShell and select Run as Administrator.

---

Prepare For Deployment

In the PowerShell window, change to the root of the C: drive:

cd \
c:

Then verify that the script is present:

dir LOCKFY*.*

You should see LOCKFY_AGENT_DEPLOYMENT_GPO_SIGNED.ps1 in the output. If not, return to Copy the Script and confirm that the script was copied to the correct location.

Note

The PowerShell script provided to you is digitally signed.

Note

If you do not have access to the PowerShell script or the required deployment values, contact your Lockfy administrator or the team that completed your Lockfy onboarding.

If required by your environment, allow signed scripts to run:

Set-ExecutionPolicy AllSigned

---

Run the script

Run the deployment script with your tenant-specific values:

If you need to verify or obtain the agent client values first, review Authorization Clients.

Note

Make sure to replace the placeholder text with your appropriate values.

.\LOCKFY_AGENT_DEPLOYMENT_GPO_SIGNED.ps1 -BaseUrl "{baseUrl}" -ClientId "{clientId}" -ClientSecret "{clientSecret}"

Parameter	Description
-BaseUrl	Lockfy API URL for your hosted tenant or on-premises Lockfy server.	Required string
-ClientId	The agent client ID created during setup.	Required string
-ClientSecret	The agent client secret related to the ClientId	Required string
-Silent	Suppress console output.	Optional flag
-NoLog	Do not write a log file.	Optional flag
-Force	Force installation or update even if the local version matches or exceeds the server version.	Optional flag

After the script completes, review the output for success or error details before closing the PowerShell window.

For a domain-wide rollout, use the Group Policy Objects (GPO) guide instead.