Are you running this as a package? If so, ConfigMgr runs packages as 32-bit processes so you HKLM\Software change actually went to HKLM\Software\Wow6432Node.
If you are running this on Win 8 or above, there's an easy fix to this, simply add /reg:64 to your reg.exe command-lines. If you are running this on Win 7, you'll have to do something else like changing the command-line for the program to the following (although there are other possibilities): %windir%\sysnative\cmd.exe batchfile.bat This can be problematic though because the sysnative alias only exists on 64-bit systems so if you intended to run this on 32-bit systems, this command-line will fail. J From: [email protected] [mailto:[email protected]] On Behalf Of Heaton, Joseph@Wildlife Sent: Tuesday, January 23, 2018 2:25 PM To: '[email protected]' <[email protected]> Subject: [mssms] Deploying the .NET registry entries So, I created a deployment package, with a batch file containing the 3 reg add commands. I've deployed it to 3 test servers. 2 of the 3 reg keys are created, no problem, but the 3rd, under HKLM\Software, doesn't get created. If I copy the batch file locally, and run it, this key does get created. The account being used to deploy the package is a local admin on every box in my environment. And the oddest part, to me, is that the deployment comes up green, as if all 3 had been created. Has anyone else had this experience? Is there a better way of deploying these reg adds? Joe Heaton Information Technology Operations Branch Data and Technology Division CA Department of Fish and Wildlife 1700 9th Street, 3rd Floor Sacramento, CA 95811 Desk: 916-323-1284
