Forum Discussion
Registry script is changing 5 of 6 keys
I'm hoping someone can help with this, it's really starting to get on my nerves. There are some registry keys that I needed to change/create on all pc's, so I tried to bundle the changes in a win...
It's the same script, in my post above, but I adjusted the WinTrust key to string instead of Dword. I mentioned the reg file from that link as example, if you imported that you would see that it's a string and not a Dword.
Just test the adjusted powershell script, curious if that will fix it
Just test the adjusted powershell script, curious if that will fix it
Hi Harm,
I have re-deployed the script from intune and it shows as failed on deployment (my detection rules are for the problematic registry key), even though it said the script failed it has updated all but the first registry key the same as before. It's a real mystery.
I have re-deployed the script from intune and it shows as failed on deployment (my detection rules are for the problematic registry key), even though it said the script failed it has updated all but the first registry key the same as before. It's a real mystery.
- No clue yet what it could be, curious about your findings!
- I guess it must be intune changing it back then, if manual changes are staying as they are. I'll do some more digging.
- Wow... Something is monitoring and changing the keys back, a security thing of some sort...
- Hi Harm,
You wouldn't believe it, but I followed your suggestion to export and import the .reg keys and I have exactly the same problem. All keys import apart from the first one.
Strange how it works outside of intune absolutely fine. - So weird, no explanation for it too 😞 You could try to export the correct keys to a .reg file, create a .intunewin package, and use regedit regfile.reg /s and import it like that?
- Also, I tried running the powershell script manually and it populates all of the registry keys. There must be something related to Intune calling the script for that particular reg key.