Check out how to deploy scripts to your devices through ConfigMgr

At the time of writing this, ConfigMgr 2211 has a bug where you cannot add scripts. So the following screenshots are from CM2203, and I’ll update them when the bug is resolved - Twitter post

Deploying custom scripts in ConfigMgr isn’t necessarily the most difficult thing, but the first time you do something it can maybe be daunting. In this post, we’ll go through how to add and run a custom PowerShell script on your devices using ConfigMgr

Literally a list of ConfigMgr and Intune error codes, as well as how to look up what they mean

Hey all!

This is literally just a post containing a bunch Intune and ConfigMgr error codes that I hope to keep updated over time.

I’ve found it’s not always straight forward finding what an error code means, maybe beacuse it’s undocuemnted, outdated or sometimes you simply just don’t know where to look, and even if you do the results vary, for example:

Check out this cool tool I helped write that tells you what’s wrong with your WSUS configuration and how to fix it

This is a follow up post to the one I wrote for Patch Tuesday MEM Patching Optimizer (Project-Clippy) and talks about my personal experience with this project

To keep things simple, I’ll refer to MEM Patching Optimizer as MEMPO.

I’ve always had an interest in writing code, automation and writing my own apps but I never really had the drive or motiviation to do it until I started working at Patch My PC.

Did you know that there is a maximum number of apps you can publish to Intune? Well you do now!

Hey! This is my first ever blog post, so bear with me!

Earlier this week I was trying to reproduce an issue in my lab and encountered something I’d never seen before in the IntuneManagementExtension.log

When publishing Win32 apps to Intune, I was presented with this error message

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19

Invoke-RestMethod: {
    "error":{
        "code":"BadRequest","message":"{
            \r\n  \"_version\": 3,\r\n  
            \"Message\": \"New apps may not be created at this time. - 
            Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - 
            Activity ID: ca6749a9-93ac-454a-a970-5c8a90978635 - 
            Url: https://fef.msub06.manage.microsoft.com/AppLifecycle_2208/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=5022-07-06\",\r\n  
            \"CustomApiErrorPhrase\": \"\",\r\n  
            \"RetryAfter\": null,\r\n  
            \"ErrorSourceService\": \"\",\r\n  
            \"HttpHeaders\": \"{}\"\r\n
        }",
            "innerError":{"date":"2022-08-30T17:17:03",
            "request-id":"ca6749a9-93ac-454a-a970-5c8a90978635",
            "client-request-id":"ca6749a9-93ac-454a-a970-5c8a90978635"
        }
    }
}

1
2
3
4
5
6
7
8

<ODataError xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/Microsoft.OData.Core">
  <Details i:nil="true"/>
  <ErrorCode>UnsupportedApiVersion</ErrorCode>
  <InnerError i:nil="true"/>
  <InstanceAnnotations/>
  <Message>{ "_version": 3, "Message": "An error has occurred - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: 26749895-af71-41be-b823-1291e0cc91ca - Url: https://fef.msub06.manage.microsoft.com/AppLifecycle_2208/StatelessAppMetadataFEService/deviceAppManagement/mobileApps%28%277a006623-ba17-4471-8027-f71722ed1057%27%29?api-version=5022-07-06%5C%22,%5Cr%5Cn", "CustomApiErrorPhrase": "", "RetryAfter": null, "ErrorSourceService": "", "HttpHeaders": "{}" }</Message>
  <Target i:nil="true"/>
</ODataError>

I had figured that I had just hit a maximum app limit and almost just left it alone, but I curious about what that limit was I hit up the Graph API to get the total number of published apps