Windows 10 Migration – Management Suite and AppSense

Version 1



    Migrating to Windows 10 is a nightmare for most of the organizations nowadays. Moving to Windows 10 is easy, but the challenge is how to keep the users’ data in place without losing any of their files, documents or even their browser favorites. In this article, we will go through the needed steps to migrate into Windows 10 using both Management Suite and AppSense.


    Needed Applications:


    1. LANDESK Management Suite (2016.3 is used)
    2. AppSense Environment Manager. (10.1 is used)
    3. AppSense DataNow (4.0 is used)


    Note: You will need to have the AppSense agents installed on the client machines prior the migration to store their data and apply the needed policies.

    Note: This has been tested on both Windows 7 and Windows 8 operating systems.


    1- PXE Configuration and Image Capture


    We need to get the base ready before doing the migration job. The first thing is to have our PXE representative installed on one of the machine in the network. The following article will guide you through the needed steps to get this configured:

    How to configure Self Electing PXE services in LDMS 2016.3 or higher


    After ensuring that the PXE representative is configured, you will need to build your own Windows 10 Image and install the needed applications on it. Once you are happy with the image, we can start with capturing the image. The following article will guide you through the needed steps to get this done: (CHECK THE CAPTURE PART ONLY)


    How to Provision Windows 10

    Note: While creating this document, the image capture was done using ImageX.


    2- AppSense Environment Preparation

              2.1- AppSense Environment Manager

    Before applying the migration, we need to ensure that the user’s profiles/data are stored somewhere. To do that, we are going to use AppSense DataNow and Environment Manager.

    DataNow must be configured correctly in the environment in order to sync the files. AppSense Environment Manager will be used to determine the file/folders that need to be synced. Below is a list of the needed configurations for the Environment Manager:


    • Install CCA Agent on all the client machines that you intend to upgrade. This will install the Environment Manager agent as well. It should be configured as below:



    • Configure the Packages that are going to be included with the CCA installation. In this example, we are going to include the Environment Manager agent:



    • Add the computers that you would like to manage (install the agents on). This can be done manually or by using Membership Rules. In this example, we are going to add one machine manually:


    • Once the machine is added, right click on it and select “Install Deployment Agent”. It might take up to 2 minutes to carry out the installation. Once the CCA is installed, the client machine need to be rebooted to complete the installation of the Environment Manager agent. The result should look like below:


    • Now you will need to prepare the polices that need to be applied on the client machine and the personalization settings that you require. Below is an example of the registry settings that need to be configured for DataNow: (This step depends on what you are trying to achieve, this is just a simple example of the folders that we are going to include in the DataNow Sync along with some configurations for the silent deployment of the DataNow agent)



    Note: For more details about these registry values, check the attached DataNow guide.

    Note: The most needed value is the “InLocationSyncFolders”. This is the value where we set the folders that we would like to sync them with DataNow. Below is an example for these values:




    • After configuring the needed polices, Save the configurations in the Management Center. Then open the Management Center, go back to the Packages section and add the configurations under the Environment Manager and submit it.


    Note: For CCA silent installation, you can use a batch file to install the MSI package and push it through LDMS. The following script can be used in the batch file:


    msiexec.exe /qn /i "\\SERVERNAME\SHARE\ClientCommunicationsAgent64.msi" WEB_SITE="http://APPSENSE-SERVERNAME.DOMAIN.COM" GROUP_NAME="DeploymentGroupName"

    Exit /b %errorlevel%

    Note: For more details on how to deploy batch files through LDMS, Check the following article: How to Create and Deploy Batch File Distribution Packages


         2.2- AppSense DataNow


                    Since we got our configurations already applied on the client machines, it is time to get DataNow configured and then deploy its agent. DataNow will need to be connected to the Active Directory and it will require a valid SSL certificate. The SSL certificate can be created internally using Microsoft Certificate Authority (CA). For more details about creating the certificate, refer to the DataNow Configuration Guide attached.

    After ensuring that the SSL certificate has been uploaded to the DataNow server, we need to create a Map Point (Where the files are going to be stored). In this example, UNC share has been configured as shown below:



    With that being set, all we need to do now is to deploy the agent on the client machines. In this example, I have used Management Suite for the deployment and a batch file to pass my parameters. The batch files contain the following:



    Exit /b %errorlevel%

    Note: For more details on how to deploy batch files through LDMS, Check the following article: How to Create and Deploy Batch File Distribution Packages

    3- Image Deployment (OS Provisioning)


                    Here comes the fun part! We need to ensure that the preferred servers are configured correctly, the PXE representative is up and running and that the AppSense Services are healthy. In this stage, we are going to use LDMS 2016.3 to do the provisioning piece where we are moving from Windows 8.1 to Windows 10.

    I have created a simple provisioning template (Can be found attached) where it starts by booting into WinPE, Create Partitions, Deploy the image, Inject unattend file, Join the machine to the domain and install the needed agents. Feel free to add/remove actions to this template as needed. (You might need to add HII deployment in the Post-OS installation phase and System Configuration Phase to install the required drivers) Below is the full sequence of this template:



    So first, we need to have LDMS agent to be installed on the client machine that we are going to migrate. Then we will schedule the task and run it against the needed devices. This process might take up to 30 minutes to complete and then the end users can start using their fresh new installation of Windows 10 with their existing data.

    For more details on how to deploy an image, refer to the following article: (Deploy Image Section)


    How to Provision Windows 10



    Ivanti will likely not support any of the changes / configurations referenced in this document if you implement them. TjDeeD Technology and / or the author of this document is not responsible for any issues that occur due to changes implemented / referenced in this document.