none
Provisioning, Assigned Access, and Application Restrictions RRS feed

  • Question

  • Hi,

    Not sure whether this belongs here or not, so sorry if this is the wrong place to ask this.

    So basically I am having a issue where my app is being blocked by company policy.

    We are the app developer and are making it available as an LOB app through our private store.

    I have used the Windows Configuration Designer to create a provisioning package to be applied to the device to lock it down to only apps that we would allow, ours being one of them.

    This has worked when the app is sideloaded, however since we need to deploy updates and have the device update automatically we are putting the app through the private store. This is where the app becomes blocked by company policy.

    I have since tried adding an AppPolicy xml blob in the ApplicationRestrictions part of the configuration designer, using the same app id. However this hasn't worked, part of the problem is that I am unsure what to use as the publisher name either the display name or the publisher guid, but the assigned access still locks down the device according the AssignedAccess.xml even pinning our app to start whilst being unavailable.

    Any help with this will be appreciated, or a point in the right direction to somewhere more appropriate for this question.

    Many thanks.

    Tuesday, May 30, 2017 8:26 AM

Answers

  • So I managed to solve the issue.

    I noticed that product id from https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9P1SGV1LCJ64/applockerdata was different to the product id in the package manifest.

    Once I used that in the Lockdown xml then it worked.

    Wednesday, May 31, 2017 10:36 AM

All replies

  • Hi,

    Your thread is correct, I don’t find something wrong during your provisioning package.

    You need to contact your company system admin, let them don’t block your apps on policies, or add your apps into the image directly.

    One thing please note, the components for creating images have been removed from Windows Configuration Designer, which now provides access to runtime settings only.

    So, I suggest to use Windows System Image Manager, which is used for create unattended Windows Setup answer files, of course, you can also add packages to be installed during Windows Setup.

    For more information please refer to this documentation.

    https://technet.microsoft.com/en-us/library/cc766347(v=ws.10).aspx

    Regards


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

    Wednesday, May 31, 2017 2:05 AM
    Moderator
  • So I managed to solve the issue.

    I noticed that product id from https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9P1SGV1LCJ64/applockerdata was different to the product id in the package manifest.

    Once I used that in the Lockdown xml then it worked.

    Wednesday, May 31, 2017 10:35 AM
  • So I managed to solve the issue.

    I noticed that product id from https://bspmts.mp.microsoft.com/v1/public/catalog/Retail/Products/9P1SGV1LCJ64/applockerdata was different to the product id in the package manifest.

    Once I used that in the Lockdown xml then it worked.

    Wednesday, May 31, 2017 10:36 AM
  • Glad to hear that you solved the issue, thanks for your sharing.

    Please mark your replay to close this case.

    Regards


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

    Thursday, June 8, 2017 7:11 AM
    Moderator