WMS Pull / Push Images Failed with Error 105

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #53103
    • Total Post: 3
    • Newbie


    I´m new to WMS and trying to implement it in our company.

    We used devices based on Dell 5470 Mobile with Windows 10 IoT installed, and WMS Server installed on version 1.4 and upgraded to version 2.0.

    Device are enrolled by DHCP Option correctly and devices and apps policies applyed without issues.

    When i try to Push or Pull images, i got the error :
    “userX” initiated ImagePull (url: https://fqdnservername:443/ccm-web/image/pull/Test-Pull, repositoryId: 1, isCaValidationOn: false) on “devicename” at ‎09‎/‎21‎/‎20 ‎7‎:‎29‎:‎15‎ ‎PM (Status: Failed – [ERROR: WMS File Repository Server not found. (error code : 105).][ERROR STAGE: Repository validation.][REASON: Could not connect to repository server.][SOLUTION: Check the network connection/authentication.]| (105))

    The server and the devices are not in the same Vlan, does i need to add other DHCP option to allow PXE like option 66 and 67 like Windows Deployment Service or SCCM ?


    Take care

    • Total Post: 10696
    • Jedi Master
    • ★★★★★★★

    PXE is not needed. The Wyse clients do have their own boot agent pre-installed.

    Is the fqdn resolvable from the client?
    Do you have read/write permission on the folder?
    Do you have enough space on the WMS server?


    • Total Post: 3
    • Newbie


    Thank you for your reply.

    The server is integrated into our domain and the devices are in workgroup.

    Devices manage to resolve the server fqdn when we are logged on connected to the network.

    For read and write rights, could you tell me which rights are necessary and on which files/folders that I can check?

    Regarding the disk space we have enough disk space (1TB).

    Thanks for your help

    • Total Post: 3
    • Newbie


    I have checked the Test-Pull folder created under the staging folder during the execution of the task, and have :

    Creator owner = Special permissions
    System = Full control
    Administrators = Full control
    Users = Read & execute


Viewing 4 posts - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.