Connects to AD and populates treeview with available OU's \ Computers, populates listview with items in Packages folder. When you have selected the destination and start the process, PSEXEC will copy the package host EXE to the client machine and run it with the same credentials you used for AD. That EXE in turn launches whatever program on whatever UNC path it contains (hard coded). A folder called "logs" should be created under the UNC path which will tell you if the program completed successfully or failed. This first version offers no settings aside from the config.ini and will probably crash if run outside a domain.

Installation:

1. Unzip to a folder

2. Compile with latest BETA (don't have to)

3. Modify config.ini to reflect your domain, I recommend using User name and Password for testing only

4. Edit plugins individually to reflect their UNC paths and file names, MUST COMPILE EACH ONE

Notes:

-Checking a root OU does not select sub-items, I have not written a routine for this yet.

-This will currently push one item at a time onto one machine at a time (Sequentially), else too many items will spawn on the client machine.

-I have tested this on both machines that are locked and logged off and it ran okay. The included packages will run completely silent aside from the tray icon. I think Office 2003 is the only one that shows a status bar.

-The Active Directory / LDAP functionality was borrowed from the Join Domain tool floating around but is stripped down.

-The settings I use for PSEXEC push the individual package scripts to the clients before running. You could also run from a local share and consolidate the packages and the files together. I personally have the installation source for each plugin strewn about different servers and don't want shares open from my machine.

Share this post

Link to post

Share on other sites

weaponx 8

is it possible to remote query the target before installation to see if a specific package has been installed?

Well there are a couple ways I could implement that.

The first would be to check the admin shares of the remote system to verify that certain files exist, maybe in the Packages config.ini I could put a list of paths to be checked.

An easier way would be to implement the check right into each package. Since the package is executed on the destination machine before any actual installation takes place you could have it check the registry and check if files exist on the destination.

I really like PSEXEC as it makes my job easier but theres no 2 way communication involved. I was working on another version of this program which required a service be installed on every machine (TCP Functions). This works nicely for me though. At my old job we used Symantec ON Technology to deploy everything but it was bloated. My version is quite fast and it simply writes logs to let you know the status of a package.