Wrong Registry path when using Intune to upload powershell script.

%3CLINGO-SUB%20id%3D%22lingo-sub-1512521%22%20slang%3D%22en-US%22%3EWrong%20Registry%20path%20when%20using%20Intune%20to%20upload%20powershell%20script.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1512521%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EI'm%20trying%20to%20execute%20a%20powershell%20script%20through%20intune%20that%20changes%20the%20OEM%20registry%20but%20its%20writing%20to%20the%20wrong%20registry%20path%20on%20my%20machine%20every%20time%20even%20when%20testing%20locally%20it%20works%20successfully%2C%20For%20some%20reason%20this%20command%20%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EREG%20ADD%20%22HKLM%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5COEMInformation%22%20%2Fv%20Manufacturer%20%2Ft%20REG_SZ%20%2Fd%20%22TEST%22%20%2Ff%20is%20editing%20at%20this%20registry%20path%2C%20%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHKEY_LOCAL_MACHINE%5CSOFTWARE%5CWOW6432Node%5CMicrosoft%5CWindows%5CCurrentVersion%5COEMInformation.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EDon't%20understand%20why%20it's%20doing%20that.%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1512521%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EPowerShell%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1512539%22%20slang%3D%22en-US%22%3ERe%3A%20Wrong%20Registry%20path%20when%20using%20Intune%20to%20upload%20powershell%20script.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1512539%22%20slang%3D%22en-US%22%3EIntune%20executes%20Powershell%20script%20by%20default%20in%2032-bit%20context.%20Have%20you%20configured%20the%20Powershell%20script%20to%20run%20in%2064-bit%3F%3C%2FLINGO-BODY%3E
Senior Member

I'm trying to execute a powershell script through intune that changes the OEM registry but its writing to the wrong registry path on my machine every time even when testing locally it works successfully, For some reason this command ,

REG ADD "HKLM\Software\Microsoft\Windows\CurrentVersion\OEMInformation" /v Manufacturer /t REG_SZ /d "TEST" /f is editing at this registry path,

 

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\OEMInformation.

 

Don't understand why it's doing that. 

 

 

1 Reply
Intune executes Powershell script by default in 32-bit context. Have you configured the Powershell script to run in 64-bit?