Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Very Important information:

With CapaInstaller 6.2 the CapaInstaller Windows Agents are built on .NET Framework 4.6 (Default in Windows 10) and .NET Framework 3.5 - if you have windows computers in your environment etc. Windows 7 without 4.6 installed you must wait with this upgrade until you have upgraded all computers.

If .NET Framework 4.6 is installed, you can continue.

Security update, Features and bug fixes - 2021

OS Deployment

 Security

A security flaw has been found in the OS Deployment service, where it was possible with the proper knowledge to download files from the server hosting the OS Deployment Service.

 Windows 11 and Server 2022

The new versions of Windows 11 and Windows Server 2022 has been added to the OS Deployment.

Support for the new ADK for Windows 11 has been tested

 Promote

When promoting packages the dialog has been changed so the CapaInstaller Console can be used while promoting

Configuration Management

 Promote

When promoting packages the dialog has been changed so the CapaInstaller Console can be used while promoting

Management Portal and Self Service Portal

  • Management Portal must be upgraded after CapaInstaller has been updated.

    • Uninstall the old version and install the new version. (Setup is located in “CMP share” \Resources\Management Portal).

  • SelfServicePortal must be upgraded after CapaInstaller has been updated.

    • Uninstall the old version and install the new version. (Setup is located in “CMP share” \Resources\Self Service Portal).

Known Issues

  • In some cases, the CapaInstaller Installation Wizard fails when it updates the database - please contact support if you see this problem.

  • In some cases, the MDM service fails to start after the update. Checking cimdm.log shows an error: " MDM Service failed to obtain a correct CapaOne configuration from the backend service."

    • To fix this, go to System Administration → Software Accounts → CapaOne

    • Right-click on CapaOne and select Properties

    • Copy the token,  then delete the token and click OK

    • Right-click again on CapaOne, then select Properties and paste the token. Click OK.

    • Check that MDM service starts

  • In some cases, the OS Deployment Service stopped working with PXE boot after update - the solution was to reboot the server

  Discontinuation 

  • As announced in earlier release notes, the CapaInstaller Agent will move to .net 4.6 framework.

  • Discontinued support for Windows Server 2008 

  • Discontinued support for Windows XP

  Downloading and Upgrading to CapaInstaller 6.2

  • See this site for download of CapaInstaller 6.2

  • See this site for how to update to CapaInstaller 6.2

 Support

Get Access to support from the portal


  • No labels