none
Application works fine from command prompt when testing but does not install through OSD or Software Center? RRS feed

  • Question

  • Hi Everyone,

    I have 'created an Application' in SCCM for the Adobe Acrobat Reader DC program.

    Here is a screen shot of Programs properties -

    The exact 'Installation program' command line is as follows -

    msiexec.exe /i "Adobe Acrobat Reader DC v19.21.20047.354104.msi" /qn /norestart

    The exact 'Uninstall program' command line is as follows -

    msiexec.exe /x {AC76BA86-7AD7-1033-7B44-AC0F074E4100} /qn /norestart

    On the SCCM Server where I have tested this Application - using the command prompt - the Adobe Reader program installs, and uninstalls fine.

    However when I add this Application to a Task Sequence the program will not install, and furthermore it will not install from the Software Center.

    When I attempt to install from Software Center I am presented with the error message shown below -

    The Application has been added to the main Distribution Point.

    Can anybody offer any pointers on why this is not working?

    Any help will be greatly appreciated.

    Kind Regards,

    Davo

    Tuesday, November 19, 2019 10:34 PM

Answers

  • Hi Guys,

    Once again thank you for your time and assistance.

    I was able to fix this issue by shortening the folder / file name.

    Originally it was 101 characters long, and I got it down to 75 characters.

    Regards,

    Davo

    • Marked as answer by Darts75 Thursday, November 21, 2019 3:48 AM
    Thursday, November 21, 2019 3:48 AM

All replies

  • Hi,

    Looks like a boundary/boundary group issue are you sure the client is within a boundary which has a DP connected to it?

    Regards,
    Jörgen


    -- My Enterprise Mobility blog ccmexec.com -- Twitter @ccmexec

    Tuesday, November 19, 2019 10:48 PM
    Moderator
  • > The Application has been added to the main Distribution Point.

    Just because it was added doesn't mean it has been successfully distributed.

    And, as Jorgen pointed out, that doesn't imply that you've configured the correct mapping from the client(s) in question (using boundaries and boundary groups) to that DP.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Tuesday, November 19, 2019 11:37 PM
  • Hi Guys,

    Thanks for your responses.

    I only have one Boundary Group, and one Distribution Point - everything is very basic.

    Is there a log that I can check to try and determine what is going on?

    Regards,

    Davo

    Wednesday, November 20, 2019 12:50 AM
  • What about boundaries?

    Also, as noted, just because you initiated the distribution to your DP doesn't mean it made it there successfully.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Wednesday, November 20, 2019 3:30 AM
  • Hi,

    Application download failures include the following problems:
    1. The client is stuck downloading an application
    2. The client fails to download the application content
    3. The client gets stuck at 0% while downloading the application
    The first thing to check when you experience application download failures is for missing or misconfigured boundaries and boundary groups.
    If the client can't download the application content, make sure it's distributed to a distribution point. To verify this configuration, use the in-console features to monitor content distribution to the distribution points. For more information, see Monitor content you have distributed.
    In addition, we can also try to check the following log files for more clues:
    CAS.log ContentTransferManager.log DataTransferService.log
    We can refer to the following article for more details:

    https://support.microsoft.com/en-us/help/4509382/troubleshooting-application-deployment-in-configuration-manager

    Best regards,
    Larry


    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, November 20, 2019 7:27 AM
  • Hi Guys,

    Once again thank you for your time and assistance.

    I was able to fix this issue by shortening the folder / file name.

    Originally it was 101 characters long, and I got it down to 75 characters.

    Regards,

    Davo

    • Marked as answer by Darts75 Thursday, November 21, 2019 3:48 AM
    Thursday, November 21, 2019 3:48 AM
  • Hi,

    Thank you very much for your feedback!
    Please allow me to write a short summary for this thread, because we believe this will make the thread clearer and more friendly for other people who have similar problems.


    Problem/Requirement:
    ===================
    Application works fine from command prompt when testing but does not install through OSD or Software Center


    Solution:
    ===================
    fix this issue by shortening the folder / file name


    Reference:
    ===================
    The application Name is required and must be fewer than 256 characters.

    https://docs.microsoft.com/en-us/configmgr/apps/deploy-use/create-applications

    Best regards,
    Larry

     

    Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 22, 2019 9:25 AM