Have you considered using MSIX instead of MSI?
152 votesstarted · AdminMark Silvey - ConfigMgr Product Team (Admin, System Center Configuration Manager) responded
First preview of the hub is available in 1807 Technical Preview.
Items in the community hub get downloaded and imported directly into the site server to which your admin console is connected.
Hi David, thank you for the feedback. Can you let us know which version of ConfigMgr you are seeing this issue?
Using the latest, I tested this by just adding spaces before and after the device name, and searched and the device is displayed in the search results. I also tried copying from an SRS report as well as the monitoring deployments node.
Not sure what reports you are copying from, but perhaps there is some non-whitespace control character that is being copied from the report along with the device name which is not being displayed but prevents the device from being matched in the search.
FYI you can push this yourself already using the Configuration Manager client and a Configuration Baseline with a registry setting.
With Greater than operator, what would the remediation do? It is difficult to guess what value the admin would want as the expected value. One greater than the value in the rule? 10 greater?
What value would you suggest?
Actual value could be different on each device. Deployment monitoring shows a summary and count of machines with the given rule being noncompliant. Actual value only makes sense when an individual machine is displayed, and so would need to be added to the "Asset Details" pane and the actual value next to the machine name.
You can do this today if you use the Import Wifi profile. You'd need to first manually create the wifi profile on a Windows machine, then export it to xml. You'd then import that XML using the wifi profile wizard in the admin UI and choose the import option. In your XML you can include the password.
Note, there are security implications with doing this, since the password will be stored in cleartext (as part of the policy XML) in the SCCM database, and potentially as well on clients.
To export from Windows you should be able to use the netsh wlan commands in a cmd prompt.
There is a checkbox we added to use DWORD when remediating (writing the new value) instead of QWORD, so you can control it either way now.
REG_BINARY is still not supported.
FYI, the Integer type is REG_DWORD. REG_MULTI_SZ is String Array.
This already happens today. When a value is non-compliant, the actual and expected values are reported back in the non-compliance report details. These details can be viewed in reports by 'drilling down' from the summary report down into a specific machine where the details are displayed in a linked report.
The detailed report may not scale to showing details for all machines depending on the number of clients. Is this report not very discoverable?
What would be a preferred way to provide this data (which already exists in the system) to the security group or others?