Error: "resolving core server name (%mycoreserver%)" when booting into WinPE

Version 27

    Verified Product Versions

    Endpoint Manager 9.5Endpoint Manager 9.6Endpoint Manager 2016.xEndpoint Manager 2017.xEndpoint Manager 2018.x


    The following error occurs when booting into Windows PE:

    WinPE boot error "resolving core server name (%mycoreserver%)........"



    • This normally occurs when the ALL.REG file within the BOOT.WIM does not contain the Core Server name or it needs to be changed to FQDN.
    • If CORENAME.TXT and ALL.REG get modified manually and a later patch, service pack, or upgrade updates the boot.wim or boot_x64.wim, the CORENAME.TXT and ALL.REG will need to be updated again.




    The following steps will be taken on the core server:


    • Mount the .WIM files that are used to create the Windows PE boot environment
    • Modify the CORENAME.TXT and ALL.REG files that are used to specify the core server name for Windows PE
    • Commit the changes made to the .WIM files so that the boot.wim and boot_x64 .WIM files contain the changes made
    • Update the PXE Representatives with the newly changed .WIM files


    These steps follow:


    1. Create a new directory you will eventually mount your 32-bit .WIM file to.   Example: C:\bootwim
    2. Create a new directory you will eventually mount your 64-bit. WIM file to.   Example: C:\boot_x64wim)
    3. From a command prompt change to the \Program Files (x86)\LANDESK\ManagementSuite\LANDESK\vboot directory.
    4. Type the following command to mount the Boot.wim file:

      This will mount the 32-bit boot.wim file that contains the 32-bit Windows PE environment used with computers booting to a Legacy 32-bit bios.  This means it will open upthe .wim image file and allow access to it through a directory.
      dism /mount-wim /wimfile:boot.wim /index:1 /mountdir:c:\bootwim
    5. Type the following command to mount the boot_x64.wim file:

      This will mount  the 64-bit boot_x64.wim file that contains the 64-bit Windows PE environment used with computers booting to a UEFI bios.  
      dism /mount-wim /wimfile:boot_x64.wim /index:1 /mountdir:c:\boot_x64wim
    6. Change to the Temp subdirectory under C:\bootwim\ you created in Step 1.
    7. Save your changes to the CORENAME.TXT file.
      CORENAME.TXT will simply contain one line with the name of the core server.   This can be changed to FQDN or IP address to suit the needs of your environment.
    8. Change to the WINDOWS\SYSTEM32  subdirectory under c:\bootwim and edit the file ALL.REG in Notepad or another text editor.
    9. Modify the line that says "CoreServer"="[Corename]" and change the core name to FQDN or IP address as suits your needs.
    10. Save your changes to the ALL.reg file.
    11. Copy the cert from the server (ex:6d7g84c9.0) from the server directory (C:\Program Files (x86)\LANDESK\Shared files\cbaroot\certs) to your offline boot.wim diretory (%offlinefolder%\cba8\cbaroot\certs\) be sure to delete the old cert. Note: This step ensures you don't receive mapped drive failures within Provisioning.
    12. Repeat steps 6-9 for the boot_x64.wim

      Now it is necessary to commit the changes made in the C:\bootwim and C:\boot_x64wim directories to save them into the .WIM files.  This is done by using the DISM (Deployment Image Servicing and Management) tool with the switch "/commit-wim" to save the changes to the images we mounted in steps 4 and 5. IMPORTANT: It is absolutely necessary to close all Explorer windows related to the bootwim mount directory before running the unmount commands. Failure to do so will cause your commit to fail due to files still being in use.

    13. Type the following command to unmount the boot.wim and commit (save) the changes:
      dism /unmount-wim /mountdir:c:\bootwim /commit
      This will commit (or save) the changes to the boot.wim made in modifying the CORENAME.TXT and ALL.REG.
    14. Type the following command to unmount the boot_x64.wim and commit (save) the changes:
      dism /unmount-wim /mountdir:c:\boot_x64wim /commit
      This will commit (or save) the changes to the boot_x64.wim made in modifying the CORENAME.TXT and ALL.REG
    15. At this point, the PXE clients will need to download the updated boot wims. If you are running EPM 2016.3 or higher, you will need to wait around 15 minutes for the the wim files to automatically update on the PXE rep.
    16. Once the boot.wims are updated (you can compare the date/time/size of the boot wims on the PXE rep to the updated wims on the core to make sure that they match), re-test the issue and make sure everything is now working.


    If your core server is on version 2016.0 or below (9.5, 9.6 etc) then you will need to manually redeploy the PXE reps. See the steps below for information on that process.


    1. If your core is on 2016.0 or older, it is necessary to re-deploy the PXE representatives, as the .WIM files on the PXE Representatives do not automatically update. When the targeted devices do a network boot they are directed to their PXE representative for their subnet and download the associated .WIM file that will then be their Windows PE environment.  The following steps detail this.
    2. In the LANDESK Management Suite console, go to the Distribution tool group and then go to the OS Deployment tool.
    3. From the OS Deployment tool expand the "All Other Scripts" section.
    4. Right-click "PXE Representative Deployment" and select "Schedule".
    5. The "Scheduled Tasks" tool should open and the newly created task should be highlighted.
    6. Add the PXE representatives to the task and start the task.

      Note: If you already have a PXE Representative Deployment task created, you can just re-use that one to re-push the PXE representative.

      If the BOOT.WIM and BOOT_X64.WIM files were updated by a patch, service pack or upgrade, these steps will need to be done again.