Deploying Clients with Intune

Deploying Clients with Intune

The CurrentWare clients can be deployed through Intune using the Application deployment feature. Microsoft Endpoint Manager allows you to quickly push the clients out across your domain. This will save time when deploying as you do not need to install individually on each PC.

Follow these steps:

  1. Log into your Microsoft Endpoint Manager
  2. Go to Apps > All Apps > +Add

  1. Under App Type choose Line-of-business app and use the cwClientSetup.msi
    Note: If you do not have the cwClientSetup.msi for your version, please contact support@currentware.com
  2. Next it will ask for App Information:
    • Name: cwClient
    • Publisher: CurrentWare
    • Command-line arguments: /qn USERPARAMS=”-p Admin -ds MYSERVER -rp Admin -sp Admin”
      • The “MYSERVER” must be changed to your CurrentWare server IP.
        • Switch Explanation:
          • -ds: CurrentWare Server IP Address or Computer Name pointer
          • -rp: Set CurrentWare Client password (to change from the default “Admin” password)
          • -sp: Confirm CurrentWare Client password
    • The rest of boxes are optional.

⚠️IMPORTANT NOTES: This image is for reference only. The command-line arguments should be commands in step #4.
  1. Under “Assignments”, assign the package to be installed to the Devices/Groups/Users that you want to place a CurrentWare client on.
  2. Review and click “Create” to finish the managed app creation.
  3. It may take a couple minutes to upload the client files, and you should start seeing the client rollout progression through the Microsoft Endpoint Manager managed app page.

If you are having issues setting up your managed app, please see the Microsoft Intune documentation here


    • Related Articles

    • Redirect CurrentWare Clients to another CurrentWare Server

      For the redirect feature to work, the PCs must be turned on. PCs that are not online will not retroactively update when turned on at a later time. #1 – Redirect Clients From One Server to Another (Push) This option is mainly for moving existing ...

    • Schedule CurrentWare Server Restart to Troubleshoot Issues

      If you are having issues with CurrentWare, restarting the CurrentWare Server service will ensure stability in communication between the CurrentWare server and clients. We recommend also setting CurrentWare server restart schedule for every 12 hours. ...

    • Adding CurrentWare to your Antivirus’ Exclusion Lists

      Third-party Antivirus and firewall programs can sometimes interfere with the functionality of CurrentWare. If you have any 3rd party antivirus or firewall installed on your client computers, we recommend adding the following CurrentWare files to your ...

    • Terminal Server/VDI/Remote Desktop Services Compatibility

      If you are using Windows-based virtual desktop infrastructure (VDI) or have users in your network remoting into a terminal server or a Remote Desktop service, you can still use CurrentWare to control and track users. CurrentWare applies Internet and ...

    • Use NOIP to setup a Remote DDNS

      No-IP/DDNS (Dynamic Domain Name System) is a service that associates a domain name with a changing IP address. ISPs often assign dynamic IP addresses, which can be problematic for hosting services such as CurrentWare for a remote setup. No-IP/DDNS ...