Microsoft

System Center Configuration Manager Feedback

Suggestion box powered by UserVoice

How can we improve Configuration Manager?

More accurate registry Compliance Settings

When creating the Configuration Item (Create Configuration Item Wizard, Settings step) and choosing Registry setting type for the Create Setting window, there are some bizarre registry types mentioned in Data type drop-down box: String, Integer, Date and Time, Floating Point, Version and String Array. Most of these data types are all REG_SZ type. But where is REG_MULTI_SZ? REG_EXPAND_SZ? REG_DWORD? REG_QWORD? REG_BINARY?
There is also possibility to set/check compliance for those registry settings with script, but why the Registry Configuration Item in first place?
These actual registry data types need to be implemented instead of/additionally to currently existing ones.

47 votes
Vote
Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
You have left! (?) (thinking…)
Roman Žuravljov shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
Noted  · 

9 comments

Sign in
(thinking…)
Sign in with: facebook google
Signed in as (Sign out)
Submitting...
  • Zack commented  ·   ·  Flag as inappropriate

    Also please add the ability to change Reg Type with a CI. For example, if you have a registry value of type REG_SZ and you want to change that to a DWORD, it doesn't work. It will show it as compliant.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Please 'REG_SZ' should be labeled 'REG_SZ' and REG_BINARY should be an option

  • Rob Traynere commented  ·   ·  Flag as inappropriate

    I am not sure why this hasn't been implemented yet. The language needs to be clear, and we need remediation for all possible registry entries, not just simple strings and integers.

  • Roman Žuravljov commented  ·   ·  Flag as inappropriate

    Unfortunately Integer does not always reflect bitness. When you you test Registry value for Integer and the value is REG_DWORD, everything is perfect. But if you try to write the non-existent value, the major headache begins - the registry value suddenly becomes REG_QWORD (especially on 64-bit systems) and 32-bit applications do not understand that. The simpliest example is Internet Explorer 32-bit that expects DWORD values and does not see QWORDs. DWORD and QWORD are both integers...

Feedback and Knowledge Base