Run PowerShell proxy server setup script#

Overview#

VOSS provides a script to automate the setup of the Windows PowerShell proxy server for for Microsoft Teams and (optionally) Microsoft Exchange Online.

Note

You can run the script on a new PowerShell proxy server, or use an existing one. A single PowerShell server can be used by multiple tenants, with or without Microsoft Exchange.

Pre-requisites

  • Download the script and associated files from the client portal: https://voss.portalshape.com

    Note

    Release and file versions displayed here may differ, depending on your target release. The script uses the associated files during install.

    Go to: Downloads > VOSS Automate > 24.2 > New Installation > Windows Powershell Proxy

    Modules.zip
OpenSSH-Win64-v9.8.1.0.msi
PowershellProxySetup_24.2.0_v1.0.ps1
dotnet_4_8.exe
powershell_7_4_6.msi

  • You’ll need a Windows server 2019

  • You must have local Administrator privileges on the PowerShell proxy server.

  • Extract Modules.zip.

Execute the script#

This procedure runs the PowershellProxySetup_24.2.0_v1.0.ps1 script.

  1. Transfer the downloaded PowershellProxySetup_24.2.0_v1.0.ps1 script to the Microsoft PowerShell proxy server.

  2. On the Windows server, run the script as an Administrator.

  3. Are you using a currently active service user account, or do you need to create one?

    • Using a currently active service user account. Press Enter to proceed.

    • Creating a new service user account. Fill out the name you want to use for the service user account that will be created, then press Enter to proceed.

    Note

    If you don’t provide a service user account name, the script uses the currently active user account.

  4. Fill out a password for the service user account to be assigned. If you’re using the current service user account, fill out the password for that user.

  5. Press Enter.

  6. Are you using an outbound internet proxy?

    • Yes. Fill out the proxy server IP/FQDN and port in the following format: xxx.xxx.xxx.xxx:yyyy (for example, 192.168.1.1:3128)

    • No. Leave the field blank.

  7. Press Enter.

    The script executes, performing the following steps:

    Note

    This script uses local files to install all required PowerShell modules so that an internet connection won’t be required to execute it. The files must be downloaded from the VOSS client portal and placed in the same folder as the script before executing.

    • Checks that the local admin service account is present

    • Configures the outbound internet proxy

    • Configures WinRM (Windows Remote Management service)

    • Installs/updates .NET framework

    • Installs/updates PowerShell modules

    • Checks that OpenSSH server is enabled and running

    • Checks that the privileged scheduled task is present

    • Checks that debug tools are present

    • Installs PowerShell 7

    Sample output:

    The service account must be in the "Log on as a batch job" local security policy
in order to be allowed to run the scheduled task.
Administrator is not allowed to log on as a batch job. Adding to the policy.
Administrator has been added to the log on as a batch job policy.
Creating VOSS folder and initializing script for scheduled tasks to run.

LastWriteTime : 2024/12/19 12:32:23
Length        : 0
Name          : run_script.ps1

Creating new task RunPowershellScriptWithElevatedPermissions to run as Administrator...
Privileged scheduled task RunPowershellScriptWithElevatedPermissions created and configured.
Creating new task RunPowershellScriptWithElevatedPermissionsPS7 to run as Administrator...
Privileged scheduled task RunPowershellScriptWithElevatedPermissionsPS7 created and configured.
Powershell 7 is not installed, 7.4.6 will be installed.
Enter the name of the Powershell 7 install file which must be located next to this script.
Press Enter to use 'powershell_7_4_6.msi'.:
Installing PowerShell 7.4.6 from local installer...
Checking installation progress...
Installation or reconfiguration of Powershell 7.4.6 completed successfully.
Note that opening a new shell is required for this to take effect.
TLS 1.2 has been enabled.
TLS 1.2 for .NET 4.x has been enabled.
TLS 1.2 for .NET 3.5 has been enabled.
TLS 1.0 has been disabled.
TLS 1.1 has been disabled.
You must restart the Windows Server for the changes to take effect.

  8. Restart the Windows server for the changes to take effect.

  9. After the server has restarted, run the script again to configure MS Exchange.

    On the second run:

    • Choose Exchange

    • Fill out a different user name as service account

    Note

    No further input should be required. However, check the prompts carefully to verify.

Related topics

See Microsoft Quick Start Step 1 in the Core Feature Guide.