October, 2013

  • Migrating App-V Packages– "OSD file defines incompatible OS requirements”

    Ran into an interesting issue while trying to migrate some App-V Applications from ConfigMgr 2007 to 2012 SP1. Most of the App-V packages migrated fine, however a few of them reported an error

    “OSD file defines incompatible OS requirements”

    After taking a look at the OSD file, according to this list all of the OS version listed were fine. After some troubleshooting I found that all the failing Applications had multiple OSD files associated. This led me to the solution.

    If you have multiple OSD files as part of an App-V Application, you must have the same OS requirements listed in all of the OSD files. Once we fixed the compatible OS list, the Application migrated successfully. 

  • Supported AV clients for SCEP to automatically remove

    I’ve just spent a frustrating 10 minutes searching bing/google for the list of the supported anti-virus programs that SCEP (System Center Endpoint Protection) can automatically uninstall. So to save my scalp for a future hair pulling, I thought I’d blog the list so I can find it quickly next time. Hopefully bing/google will index this post and save us all some time!


    Automatically remove previously installed antimalware software before Endpoint Protection is installed

    Endpoint Protection uninstalls the following antimalware software only:

    • Symantec AntiVirus Corporate Edition version 10
    • Symantec Endpoint Protection version 11
    • Symantec Endpoint Protection Small Business Edition version 12
    • McAfee VirusScan Enterprise version 8
    • Trend Micro OfficeScan
    • Microsoft Forefront Codename Stirling Beta 2
    • Microsoft Forefront Codename Stirling Beta 3
    • Microsoft Forefront Client Security v1
    • Microsoft Security Essentials v1
    • Microsoft Security Essentials 2010
    • Microsoft Forefront Endpoint Protection 2010
    • Microsoft Security Center Online v1
  • Redistribute Package in Configuration Manager 2012

    One pain point with Configuration Manager 2007, was that when a package failed to distribute content to a distribution point after the retry count was exceeded, it was permanently stuck in a distributing state. There was no easy supported method to redistribute that package to a specific Distribution Point.

    Now in 2012 we have the new option to Redistribute a package.

    Open the properties of any application or package and click on the Content Locations tab.

    From there you can either select a specific Distribution point or a Distribution Point Group. see Figures below

    Application Properties


    Package Properties


    then Click on Redistribute


    Click OK on the Warning and the package will then redistribute the content to that DP or DP Group.