Using REST API to get / set device variables
Hi, I'm trying to set a couple of variables against a machine name, through using the REST API. These are the variables that are set that you can see in the console if you right click properties on a device and go to the 'Variables' tab. These are handy because they can later be referenced during Task Sequences / OSD. I just can't figure out how to do it with the REST API. I have no issues doing it with the powershell module using the 'New-CMDeviceVariable' command, but my solution i'm building at the moment requires the solution to be done with rest api, not with ps modules... I can connect to REST API using powershell using commands such as the below. This all works fine. $ConfigMgrServerURL = "https://SCCMserver.domain.local" $MachineName = "MachineName1" # Following command is a sample GET request, which works. (Invoke-RestMethod -Method Get -Uri "$ConfigMgrServerURL/AdminService/wmi/SMS_R_System?`$filter=Name eq '$MachineName'" -Credential $Credential) #I can also fetch "Custom Properties" via this command (Invoke-RestMethod -Method Get -Uri "$ConfigMgrServerURL/AdminService/v1.0/Device($ResourceID)/AdminService.GetExtensionData" -Credential $Credential) Now i just can't see where i can go to set a variable on the machine. Does anyone have any ideas ? Thanks!
0 storage consumed on protected devices
Hello! My System Center 2022 DPM console shows that some protected devices take up 0kb of storage. I know its inaccurate because I can recover data from those devices. Any idea as to how to get the accurate storage consumed number to show? I tried running the "Update-DPMProductionServer" command via the DPM management shell and it tells me that it cant convert the value.VMM Module in PowerShell 7
With the latest news in the tech industry, when can we expect to see the System Center PowerShell modules to be supported in PowerShell 7.0? I believe MECM/MEM works in pwsh7 already but VMM doesn't at this point. Requiring a Windows machine to use the VMM module doesn't make a ton of sense.
AdminService add/delete rules in collection
Hi I'm trying to add and delete devices from a collection via AdminService on Configuration manager 2203 from PowerShell. When I try the below command I receive an error Invoke-RestMethod -Method Post -Uri "https://<ServerName>/AdminService/wmi/SMS_Collection('<CollectionID>')/AdminService.AddMembershipRule" -Credential $Credentials -Body "{'collectionRule':{'RuleName':'<DeviceName>'}}" -ContentType "application/json" Error: Invoke-RestMethod : {"error":{"code":"500","message":"An error with description \"Could not get CCollectionRule* from instance\" occurred when performing MethodExecution operation on WMI class: SMS_Collection."}} At line:1 char:1 Error log AdminService.log Management exception caught: Could not get CCollectionRule* from instance System.Management.ManagementException: Not found at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options) at Microsoft.ConfigurationManager.AdminService.ManagementObjectAbstraction.InvokeMethod(String methodName, IManagementBaseObject inParams, InvokeMethodOptions invokeOptions, WindowsIdentity windowsIdentity) I get the same error if I try to delete a device from a collection. Anybody able to help ?? Regards MartinUpdate 2203 for Microsoft Endpoint Configuration Manager current branch is now available
Update 2203 for Microsoft Endpoint Configuration Manager current branch is now available. One of the exciting new features is the content distribution status visualizer. With it you can now monitor content distribution path and status in a graphical format.Update 2111 for Microsoft Endpoint Configuration Manager current branch is now available
Update 2111 for Microsoft Endpoint Configuration Manager current branch is now available. We are excited to announce that two popular pre-release features, orchestration groups and application groups are now full features in this release.Different ways of SCOM Integration with Third Party Applications
Hello, We have a application which needs to be integrated with SCOM. We were using various methods from management group for getting different data. But as per documentation : https://docs.microsoft.com/en-us/dotnet/api/microsoft.enterprisemanagement.managementgroup.getmonitoringperformancedata?view=sc-om-dotnet-2016 GetMonitoringPerformanceData() and some other similar performance API are now obsolete. Now we are exploring alternatives to using this. Can you help with below questions: 1) Should we change the entire data collection mechanism from SCOM SDK to something else or just find a workaround for obsolete api's and wouldn't it break the consistency? 2) What are the possibilities of using SQL Query approach instead of SCOM SDK, and what are performance issues based on this approach? What are the resources where in detail i can get idea about using SQL query approach. Here i can see a mention of using sql as a way https://docs.microsoft.com/en-us/system-center/scom/plan-thirdparty-integration?view=sc-om-2019 3) How can connectors and orchestrators be used here for getting data from SCOM. Where can i get detailed documentation for using this approach? 4) What are possibilites of using REST API approach, as mentioned here https://docs.microsoft.com/en-us/rest/operationsmanager/. But there are no API's for getting events data and similarly many other data. Also response of API does not contain detailed data for example in case of alerts very limited data is given compared to SCOM SDK. Thanks a lot. System-Center-Team NehaGarg RobYork EricStarker Dean_Gross Trevor Seward dloderApplication approval improvements in ConfigMgr 1810
We have added several new improvements to application approvals in Configuration Manager current branch 1810. Machine-based pre-approved requests (SDK only) Re-approve a previously denied application request (SDK only) Email notifications for application approval requests including CMG support to enable approving the application outside of the internal network
