US English (US)
GB English (UK)

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Create ticket
English (US)
US English (US)
GB English (UK)
  • Home

Requirements validation on the PowerSyncPro Server

Script to check all requirements are installed on the PowerSyncPro Server

Written by Neil Langston

Updated at December 13th, 2024

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Getting Started
  • FAQs
  • API Documentation
  • Integrations
  • Migration Agent
  • Directory Synchronisation
  • Remote DC agent
  • Remote Password Sync Agent
+ More

You can easily check all requirements are installed on your PowerSyncPro server by running the script below.

This script gives you the possibility to performing checks for both Directory Synchronisation and orchestrating device migrations using Migration Agent.

Furthermore, if you do not have a firewall enabled, you can also ignore any firewall port detection failures.

High level checks

  • Basic system information: CPUs, RAM, available storage
  • Domain join state
  • Windows Server version
  • SQL Server installed on the local machine (**)
  • SQL Server Management Studio (PowerSyncPro will operate without this, but it is common place to have installed)
  • .NET 8 ASP.NET Core Runtimes
  • Microsoft Visual C++ Redistributable
  • IIS (*)
  • URL Rewrite (*)
  • Microsoft Application Request Routing (*)
  • Checks firewall ports 443, 5000, 5001 are open (***)
  • Active Directory connectivity (port 389, you need to enter FQDN(s)) (***)
  • Connectivity to M365 tenants' generic entry points (***)

 

* Microsoft Application Request Routing & URL Rewrite are only needed if you have your own public HTTPS SSL certificate and will be using a custom URL for your Migration endpoint, like https://migrationagent.company.com

** The script assumes you are deploying all requirements on the same server, if you will be using a SQL instance on a different server, then you can ignore any failure for SQL.

*** These are common ports used and may not directly relate to your implementation.

 

CheckPSPServerPrerequisites.ps1

 

An example output is like this

 

 

 

requirement verification server software

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Requirements for AD to AD password sync
  • SMTP entries do not flow
  • Migration Agent is not starting or registering on a device

Subscribe to Newsletter

Drop your email in the box below to sign up. We promise to keep our updates relevant and useful – and we’ll never share your details.

PowerSyncPro is the ultimate product for easing the pain and frustration during mergers, acquisitions, divestitures, and consolidations.

Terms & Conditions

  • FAQs
  • Privacy Policy
  • Cookies
  • Anti Slavery Notice

PowerSyncPro

  • Case Studies
  • Contact sales
  • Meet the Team
  • EULA

Get Connected

Room 73, Wrest House, Wrest Park, Silsoe, Bedford, England, MK45 4HR
info@powersyncpro.com

Twitter Youtube Linkedin

Knowledge Base Software powered by Helpjuice

Expand