{"id":1303,"date":"2014-02-19T15:53:39","date_gmt":"2014-02-19T20:53:39","guid":{"rendered":"http:\/\/batchpatch.com\/?p=1303"},"modified":"2017-11-13T15:04:39","modified_gmt":"2017-11-13T20:04:39","slug":"deploy-registry-keys-to-multiple-computers-using-batchpatch","status":"publish","type":"post","link":"https:\/\/batchpatch.com\/deploy-registry-keys-to-multiple-computers-using-batchpatch","title":{"rendered":"Deploy Registry Keys to Multiple Computers Using BatchPatch"},"content":{"rendered":"

A systems administrator frequently needs to update the Windows Registry of every computer on his\/her network. Did you know that you can use BatchPatch to accomplish this task extremely rapidly? BatchPatch provides administrators with a very simple way of getting registry keys to remote computers on a network.<\/p>\n

    \n
  1. Before we do anything please note that if you are going to be deploying a registry key\/value to the HKEY_CURRENT_USER (HKCU) hive of the target computer(s), then you need to make sure that your ‘Remote Execution Context<\/strong><\/em>‘ is set to ‘Elevated token<\/strong>‘ and not ‘SYSTEM<\/strong>‘. If you are deploying a registry key\/value to the HKEY_LOCAL_MACHINE (HKLM) hive of the target computer(s), then your ‘Remote Execution Context<\/strong><\/em>‘ can probably be set to either ‘SYSTEM<\/strong>‘ or ‘Elevated token<\/strong>‘. More details here: ‘Remote Execution Context<\/a>‘<\/li>\n

    <\/p>\n

  2. Create a .reg file for deployment. To do this you simply launch regedit.exe and highlight the key that you want to deploy to your target computers, and then choose File > Export. The registry editor application will create a .reg file for you. If you look at that reg file in a text editor, you’ll see it contains a line for each value in the key that you are creating\/modifying. In the below screenshot you can see a .reg file for a FileZilla configuration that contains a single DWORD value in the HKLM\\SOFTWARE\\FileZilla<\/code> key.
    \n 
    \n    \"FileZilla_RegFile\"<\/a><\/p>\n<\/li>\n
  3. Now that you have your .reg file prepared, highlight the hosts in BatchPatch that you want to deploy it to, and select Actions > Deploy software\/patch\/script\/regkey > Create\/modify deployment<\/b><\/em>
    \n 
    \n    \"Deploy_Registry_Key\"<\/a>\n<\/li>\n
  4. Browse to the location of your .reg file. After you select the file and click OK, you’ll see that BatchPatch displays the Command to execute:<\/em>
    \nregedit.exe \/s \"yourRegFile.reg\"<\/code>
    \n 
    \n    \"Deploy_Registry_Key2\"<\/a>\n<\/li>\n
  5. The last thing you need to do is actually execute the deployment. You can do this by highlighting the hosts you are deploying to, and then select em>Actions > Deploy software\/patch\/script\/regkey > Execute deployment.<\/b><\/em> Upon successful completion of the deployment you should see Exit Code: 0 in the All Messages column.
    \n 
    \n    \"Deployment_Exit_Code_0\"<\/a>\n<\/li>\n<\/ol>\n

    <\/p>\n

    \n


    \nHere’s a video demonstration of registry key deployment with BatchPatch:<\/b><\/p>\n