• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 637
  • Last Modified:

group policy to push .exe and registry entry?

I need to push out and install a small third party agent ".exe" file to a small OU test group.  I also need to push a registry entry so that machines can be identified as belonging to the organization.  Once this test is verified, we will need to push to all users one site at a time.  How can I accomplish this in the least painful way using GP?
I'd also like to make sure that a check is done to verify if the exe has already been installed so it will not attempt to install it again.  Thanks in advance!
  • 3
1 Solution
Joseph DalyCommented:
Since you are trying to do this with AD and the file you need to install isnt an MSI you will need to use a computer startup script to perform the actions you want. So below is a simple script that I created to install an exe as a startup script.

Basically what this BAT file does is look in your program files (or other directory) for any folder created during the install. If it find that folder it exits out. If it doest it installs the software and then writes a text file with the computername to a share on a server so you can track it.

As far as your registry key you would just need to regedit to import a registry key silently.
@ echo off
IF EXIST "C:\Program Files\Softwarefolder" GOTO ENDNOW
echo >> \\server\share\tracking\%computername%

Open in new window

Joseph DalyCommented:
In that code you should probably switch line 4 and 5 around that way it doesnt recreate the text file each time. :Endnow should be the last line.
dkrautAuthor Commented:
xxdcmast, quick question regarding your script.  How/where would you apply it within GP or would you simply add this to the users account login script?
Joseph DalyCommented:
What I would do would be to save the script somewhere all the users would have access to it and then refference it as a computer startup script through GPO. You cant really just add it to the user account login script because if they arent administrators on the machine it will fail due to improper permissions.

The good thing about a startup script is that it runs under the system context so it has the proper permissions needed.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now