teamdeploy Wiki & Documentation Rss Feed

Updated Wiki: Documentation

mikedouglas — Sat, 05 Mar 2011 05:46:56 GMT

Team Deploy 2010 Activities

Activity Name	Properties	Description
Install	MSIPathFilename	Path and filename of MSI
	ExtraArgs	Any additional MsiExec arguments
	TargetMachine	Name of target machine
	RemoteExecutePathFilename	Path and filename of PsExec.exe
	OverrideDefaultArgs	Specify args to override /qb! /i
Uninstall	ProductCode	XML Product code for MSI
	TargetMachine	Name of target machine
	RemoteExecutePathFilename	Path and filename of PsExec.exe
KillProcess	ProcessName	Name of process to kill
	TargetMachine	Name of target machine
	KillAppPathFilename	Path and filename of PsKill.exe
	IgnoreExitCode	Flag to specify whether to ignore error messages
Deploy	DeployScript	Path and filename of XML Deployment Script (see below)
	KillAppPathFilename	Path and filename of PsKill.exe
	RemoteExecutePathFilename	Path and filename of PsExec.exe
StartService	ServiceName	Name of service to be started
	TargetMachine	Name of target machine
StopService	ServiceName	Name of service to be stopped
	TargetMachine	Name of target machine
RemoteExecute	TargetMachine	Name of target machine
	RemoteCommand	Command to execute on target machine
	RemoteExecutePathFilename	Path and filename of PsExec.exe
	OptionalParameters	Optional arguments for the command
	WaitForExit	Flag to specify to wait for process to complete

Team Deploy Deployment Script

Node Name	Parent Node	Description
DeploymentScript	Na	Parent node of XML containing the steps and target machines
DeploymentSteps	DeploymentScript	Node contain all of the steps
CleanupPSExec	DeploymentSteps	Removes any PsExec remaining parts
KillProcess	DeploymentSteps	Kills all processes with that same on the target machine
MSI	DeploymentSteps	Contains the information to uninstall and install a MSI
UnistallProductCode	MSI	Uninstalls the application.
UninstallName	MSI	(use either UninstallProductCode or UninstallProduceCode)
MSIPathFie	MSI	Path and filename to MSI for installation
OverrideDefaultArgs	MSI	Replaces default MsiExec arguments /qb! /i
ExtraArgs	MSI	Pass MSI properties such as username
TargetMachines	DeploymentScript	List of Target machines to perform the same actions
TargetMachine	TargetMachines	Uses attribute name to specify the target machine

Sample XML Deployment Script

<?xml version="1.0" encoding="UTF-8"?>
<DeploymentScript>
	<DeploymentSteps>
		<MSI>			       
			<UninstallProductCode>{XE7BF359-F9AD-443B-A0BE-9E256E72A61F}</UninstallProductCode>
			<MSIPathFile>\\testserver\Deployments\WebServiceApp\Temp\WebServiceApp\WebServiceApp.msi</MSIPathFile>
			<OverrideDefaultArgs></OverrideDefaultArgs>
			<ExtraArgs>ENVSERVER=test</ExtraArgs>
		</MSI>
		<MSI>			       
			<UninstallProductCode>{XC3AC33C-7FE5-441F-997C-318D88901D27}</UninstallProductCode>
			<ServiceName>My Service</ServiceName>
			<MSIPathFile>\\testserver\Deployments\ServerApp\Temp\MyService\MyService.msi</MSIPathFile>
			<OverrideDefaultArgs></OverrideDefaultArgs>
			<ExtraArgs>ENVSERVER=test_Server2 USR=mydomain\myuser PWD=abcd</ExtraArgs>
		</MSI>
		<MSI>			       
			<UninstallProductCode>{XE945AE2-246C-465F-952F-B439AC6902AE}</UninstallProductCode>
			<ServiceName>Another Service</ServiceName>
			<MSIPathFile>\\testserver\Deployments\serverApp\Temp\AnotherService\AnotherService.msi</MSIPathFile>
			<OverrideDefaultArgs></OverrideDefaultArgs>
			<ExtraArgs>ENVSERVER=test_server2 USR=mydomain\myuser PWD=abcd</ExtraArgs>
		</MSI>
	</DeploymentSteps>
	<TargetMachines>
		<TargetMachine name="test_server2" />
	</TargetMachines>
</DeploymentScript>

Updated Wiki: Documentation

mikedouglas — Sat, 05 Mar 2011 05:42:46 GMT

Team Deploy 2010 Activities

Activity Name	Properties	Description
Install	MSIPathFilename	Path and filename of MSI
	ExtraArgs	Any additional MsiExec arguments
	TargetMachine	Name of target machine
	RemoteExecutePathFilename	Path and filename of PsExec.exe
	OverrideDefaultArgs	Specify args to override /qb! /i
Uninstall	ProductCode	XML Product code for MSI
	TargetMachine	Name of target machine
	RemoteExecutePathFilename	Path and filename of PsExec.exe
KillProcess	ProcessName	Name of process to kill
	TargetMachine	Name of target machine
	KillAppPathFilename	Path and filename of PsKill.exe
	IgnoreExitCode	Flag to specify whether to ignore error messages
Deploy	DeployScript	Path and filename of XML Deployment Script (see below)
	KillAppPathFilename	Path and filename of PsKill.exe
	RemoteExecutePathFilename	Path and filename of PsExec.exe
StartService	ServiceName	Name of service to be started
	TargetMachine	Name of target machine
StopService	ServiceName	Name of service to be stopped
	TargetMachine	Name of target machine
RemoteExecute	TargetMachine	Name of target machine
	RemoteCommand	Command to execute on target machine
	RemoteExecutePathFilename	Path and filename of PsExec.exe
	OptionalParameters	Optional arguments for the command
	WaitForExit	Flag to specify to wait for process to complete

Team Deploy Deployment Script

Node Name	Parent Node	Description
DeploymentScript	Na	Parent node of XML containing the steps and target machines
DeploymentSteps	DeploymentScript	Node contain all of the steps
CleanupPSExec	DeploymentSteps	Removes any PsExec remaining parts
KillProcess	DeploymentSteps	Kills all processes with that same on the target machine
MSI	DeploymentSteps	Contains the information to uninstall and install a MSI
UnistallProductCode	MSI	Uninstalls the application.
UninstallName	MSI	(use either UninstallProductCode or UninstallProduceCode)
MSIPathFie	MSI	Path and filename to MSI for installation
OverrideDefaultArgs	MSI	Replaces default MsiExec arguments /qb! /i
ExtraArgs	MSI	Pass MSI properties such as username
TargetMachines	DeploymentScript	List of Target machines to perform the same actions
TargetMachine	TargetMachines	Uses attribute name to specify the target machine

Updated Wiki: Home

mikedouglas — Thu, 27 May 2010 14:16:29 GMT

Project Description
Deploy MSIs from TFS builds using these custom MSBuild tasks. This collection of tasks includes everything you need to deploy cilent apps to multiple PCs and windows services to Servers. Also includes a build notification task for controlling Lava Lamps/Street lights via X10.

Guidance
Installation
Troubleshooting/FAQ
Creating a Team Deploy TFS Build

New Team Deploy 2010 for Team Build 2010 is released.

End to End Team Deploy Configuration Screencast by Ian Ceicys

Team Deplloy MSI! Install Team Deploy using the MSI for easy installation.
Team Deploy 2.x - Current release is designed for Team Foundation Server 2008
Team Deploy 2010 (3.x) - Current release designed for Team Foundation Server 2010

This project contains the following specialized custom MSBuild tasks for deploying MSIs and monitoring your build status.

New CleanupPsExec task - PsExec works great most of the time but can hang at times. This task cleans up PsExec. Contributed by Jeremy Novak.

Install task - installs an MSI on a target machine

Uninstall task - uninstalls MSI on a target machine by product code

KillProcess task - Kills any process on target machine (usually done before trying to uninstall/install MSI

Deploy task - This is the main task to be called from your TFS Team build type. This will loop through the deployment script and kill any processes necessary, uninstall the previous version, and install the new version. This now deploys in parallel for quicker deployments.

Start Service task - If deploying a windows service, call this to start the service.

Stop Service task - If deploying a windows service, call this to stop the service before uninstalling it.

Device Controller task - Use lava lamps or street lights to show the status of your builds.

Remote Execute task - Execute any executable on the target machines.

New Sample Automated Deployment Windows Service MSI Solution on on MSDN Code Gallery http://code.msdn.microsoft.com/msi - Code and steps to create an automated deployment MSI to use with Team Deploy.

New Team Deploy now includes a command line utility that allows the deploy task to be called from other build tools. This was originally built so Team Deploy could be called from Final Builder from TFS. Here's more information on Final Builder with TFS. http://www.finalbuilder.com/team-foundation-server.aspx

All of these tasks require the installation of PSTools. These tasks utilize several utilities from this free toolset. This must be downloaded separately at this location below
http://technet.microsoft.com/en-us/sysinternals/bb896649.aspx

My Blog: CodeSmartNotHard.com
http://www.codesmartnothard.com

Follow me on Twitter and tweet comments/questions
http://www.twitter.com/mikedouglasdev

Updated Wiki: Home

mikedouglas — Mon, 17 May 2010 05:06:05 GMT

Project Description
Deploy MSIs from TFS builds using these custom MSBuild tasks. This collection of tasks includes everything you need to deploy cilent apps to multiple PCs and windows services to Servers. Also includes a build notification task for controlling Lava Lamps/Street lights via X10.

Guidance
Installation
Troubleshooting/FAQ
Creating a Team Deploy TFS Build

New Beta release of Team Deploy 2010 for Team Build 2010.

End to End Team Deploy Configuration Screencast by Ian Ceicys

Team Deplloy MSI! Install Team Deploy using the MSI for easy installation.
Team Deploy 2.x - Current release is designed for Team Foundation Server 2008
Team Deploy 2010 (3.x) - Beta release designed for Team Foundation Server 2010

This project contains the following specialized custom MSBuild tasks for deploying MSIs and monitoring your build status.

New CleanupPsExec task - PsExec works great most of the time but can hang at times. This task cleans up PsExec. Contributed by Jeremy Novak.

Install task - installs an MSI on a target machine

Uninstall task - uninstalls MSI on a target machine by product code

KillProcess task - Kills any process on target machine (usually done before trying to uninstall/install MSI

Deploy task - This is the main task to be called from your TFS Team build type. This will loop through the deployment script and kill any processes necessary, uninstall the previous version, and install the new version. This now deploys in parallel for quicker deployments.

Start Service task - If deploying a windows service, call this to start the service.

Stop Service task - If deploying a windows service, call this to stop the service before uninstalling it.

Device Controller task - Use lava lamps or street lights to show the status of your builds.

Remote Execute task - Execute any executable on the target machines.

Updated Wiki: Home

mikedouglas — Mon, 28 Sep 2009 17:56:58 GMT

Project Description
Deploy MSIs from TFS builds using these custom MSBuild tasks. This collection of tasks includes everything you need to deploy cilent apps to multiple PCs and windows services to Servers. Also includes a build notification task for controlling Lava Lamps/Street lights via X10.

Guidance
Installation
Troubleshooting/FAQ
Creating a Team Deploy TFS Build

New End to End Team Deploy Configuration Screencast by Ian Ceicys

Team Deplloy MSI! Install Team Deploy using the MSI for easy installation.
Team Deploy 2.x - Current release is designed for Team Foundation Server 2008
Team Deploy 3.x - Future release designed for Team Foundation Server 2010 (Coming soon)

This project contains the following specialized custom MSBuild tasks for deploying MSIs and monitoring your build status.

New CleanupPsExec task - PsExec works great most of the time but can hang at times. This task cleans up PsExec. Contributed by Jeremy Novak.

Install task - installs an MSI on a target machine

Uninstall task - uninstalls MSI on a target machine by product code

KillProcess task - Kills any process on target machine (usually done before trying to uninstall/install MSI

Deploy task - This is the main task to be called from your TFS Team build type. This will loop through the deployment script and kill any processes necessary, uninstall the previous version, and install the new version. This now deploys in parallel for quicker deployments.

Start Service task - If deploying a windows service, call this to start the service.

Stop Service task - If deploying a windows service, call this to stop the service before uninstalling it.

Device Controller task - Use lava lamps or street lights to show the status of your builds.

Remote Execute task - Execute any executable on the target machines.

Updated Wiki: Home

mikedouglas — Sat, 26 Sep 2009 12:52:35 GMT

Project Description
Deploy MSIs from TFS builds using these custom MSBuild tasks. This collection of tasks includes everything you need to deploy cilent apps to multiple PCs and windows services to Servers. Also includes a build notification task for controlling Lava Lamps/Street lights via X10.

Guidance
Installation
Troubleshooting/FAQ
Creating a Team Deploy TFS Build

New End to End Team Deploy Configuration Screencast by Ian Ceicys

Team Deplloy MSI! Install Team Deploy using the MSI for easy installation.
Team Deploy 2.x - Current release is designed for Team Foundation Server 2008
Team Deploy 3.x - Future release designed for Team Foundation Server 2010 (Coming soon)

This project contains the following specialized custom MSBuild tasks for deploying MSIs and monitoring your build status.

New CleanupPsExec task - PsExec works great most of the time but can hang at times. This task cleans up PsExec. Contributed by Jeremy Novak.

Install task - installs an MSI on a target machine

Uninstall task - uninstalls MSI on a target machine by product code

KillProcess task - Kills any process on target machine (usually done before trying to uninstall/install MSI

Deploy task - This is the main task to be called from your TFS Team build type. This will loop through the deployment script and kill any processes necessary, uninstall the previous version, and install the new version. This now deploys in parallel for quicker deployments.

Start Service task - If deploying a windows service, call this to start the service.

Stop Service task - If deploying a windows service, call this to stop the service before uninstalling it.

Device Controller task - Use lava lamps or street lights to show the status of your builds.

Remote Execute task - Execute any executable on the target machines.

Updated Wiki: Troubleshooting

mikedouglas — Sat, 26 Sep 2009 12:51:09 GMT

Troubleshooting Team Deploy

Issues

Team Deploy task completes but the MSI isn't updated on the clients. PSExec locks up.

MSI returns Error code 1603 When trying to install web services or web site with web setup MSI to IIS7 on Windows 2008 Server
Add IIS 6 Metabase Compatibility feature to the Web Server role. More Info

FAQs

Can Team Deploy be used to deploy WCF Services?
A: Yes, if the WCF services are hosted in IIS, then create a web setup MSI. Team Deploy can install these like any other MSI. If it is hosted in a windows service, this can also be deployed by creating a setup MSI.

If I want to deploy different MSIs to each server, how can I do this with the deploy script?
A: Create two Deploy tasks in your build and each one will call a separate deploy script.

Updated Wiki: Home

mikedouglas — Sat, 26 Sep 2009 12:38:23 GMT

Project Description
Deploy MSIs from TFS builds using these custom MSBuild tasks. This collection of tasks includes everything you need to deploy cilent apps to multiple PCs and windows services to Servers. Also includes a build notification task for controlling Lava Lamps/Street lights via X10.

Guidance
Installation
Troubleshooting/FAQ
Creating a Team Deploy TFS Build

New End to End Team Deploy Configuration Screencast by Ian Ceisys

Team Deplloy MSI! Install Team Deploy using the MSI for easy installation.
Team Deploy 2.x - Current release is designed for Team Foundation Server 2008
Team Deploy 3.x - Future release designed for Team Foundation Server 2010 (Coming soon)

This project contains the following specialized custom MSBuild tasks for deploying MSIs and monitoring your build status.

New CleanupPsExec task - PsExec works great most of the time but can hang at times. This task cleans up PsExec. Contributed by Jeremy Novak.

Install task - installs an MSI on a target machine

Uninstall task - uninstalls MSI on a target machine by product code

KillProcess task - Kills any process on target machine (usually done before trying to uninstall/install MSI

Deploy task - This is the main task to be called from your TFS Team build type. This will loop through the deployment script and kill any processes necessary, uninstall the previous version, and install the new version. This now deploys in parallel for quicker deployments.

Start Service task - If deploying a windows service, call this to start the service.

Stop Service task - If deploying a windows service, call this to stop the service before uninstalling it.

Device Controller task - Use lava lamps or street lights to show the status of your builds.

Remote Execute task - Execute any executable on the target machines.

Updated Wiki: Home

mikedouglas — Sun, 23 Aug 2009 04:50:24 GMT

Project Description
Deploy MSIs from TFS builds using these custom MSBuild tasks. This collection of tasks includes everything you need to deploy cilent apps to multiple PCs and windows services to Servers. Also includes a build notification task for controlling Lava Lamps/Street lights via X10.

Guidance
Installation
Troubleshooting
Creating a Team Deploy TFS Build

Team Deplloy MSI! Install Team Deploy using the MSI for easy installation.
Team Deploy 2.x - Current release is designed for Team Foundation Server 2008
Team Deploy 3.x - Future release designed for Team Foundation Server 2010 (Coming soon)

This project contains the following specialized custom MSBuild tasks for deploying MSIs and monitoring your build status.

New CleanupPsExec task - PsExec works great most of the time but can hang at times. This task cleans up PsExec. Contributed by Jeremy Novak.

Install task - installs an MSI on a target machine

Uninstall task - uninstalls MSI on a target machine by product code

KillProcess task - Kills any process on target machine (usually done before trying to uninstall/install MSI

Deploy task - This is the main task to be called from your TFS Team build type. This will loop through the deployment script and kill any processes necessary, uninstall the previous version, and install the new version. This now deploys in parallel for quicker deployments.

Start Service task - If deploying a windows service, call this to start the service.

Stop Service task - If deploying a windows service, call this to stop the service before uninstalling it.

Device Controller task - Use lava lamps or street lights to show the status of your builds.

Remote Execute task - Execute any executable on the target machines.

Updated Wiki: PSExecLocksUp

mikedouglas — Sun, 23 Aug 2009 03:42:52 GMT

Team Deploy task completes but the MSI isn't updated on the clients. PSExec locks up.

Thanks to Ken Johnson for identifying and documenting this issue and Jeremy Novak for creating the CleanupPsExec task to fix this issue!

Our automated build recently stopped remotely installing our services from the build server (buildserver) to the system test application server (targetserver). It was able to stop and restart the service, and it thought it was installing the services, but the install was not actually running.
Here is a sample of one of our command lines: TeamDeploy.exe /CONFIG:EODService.xml
Because the services installed properly when running the MSI from the application server itself, and because TeamDeploy depends on PSTools for remote deployments, I started looking at thePSTools: specifically PSKill and PSExec.
First I verified that pskill was working remotely by opening notepad on the application server and killing it from the build server:
pskill \\targetserver notepad.exe

PsKill v1.03 - local and remote process killer
Copyright (C) 2000 Mark Russinovich
http://www.sysinternals.com

Process notepad.exe killed on targetserver.

Next, I tried to verify that psexec was working properly:

psexec \\targetserver "c:\windows\system32\ipconfig.exe"

PsExec v1.31 - execute processes remotely
Copyright (C) 2001-2002 Mark Russinovich
www.sysinternals.com

Error communicating with PsExec service on targetserver :
No process is on the other end of the pipe.

It returned an error indicating there was no process on the other end of the pipe. This seemed to indicate a problem with psexesvc.
Since psexesvc installs automatically when running psexec, I removed psexesvc from the application server (1):
sc \\targetserver stop psexesvc
SERVICE_NAME: psexesvc
TYPE : 10 WIN32OWNPROCESS
STATE : 3 STOP_PENDING
(STOPPABLE, NOTPAUSABLE, IGNORESSHUTDOWN))
WIN32EXITCODE : 0 (0x0)
SERVICEEXITCODE : 0 (0x0)
CHECKPOINT : 0x2
WAIT_HINT : 0x0

sc \\targetserver delete psexesvc
SC DeleteService SUCCESS

After cleaning up the psexesvc, I verified that psexec was working properly:

psexec \\targetserver ipconfig

PsExec v1.31 - execute processes remotely
Copyright (C) 2001-2002 Mark Russinovich
www.sysinternals.com

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::b5eb:e3
IPv4 Address. . . . . . . . . . . : 10.2.15.171
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 10.2.15.251

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconn
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconn
Connection-specific DNS Suffix . :
ipconfig exited on targetserver with error code 0.

The final test of course was to run TeamDeploy.exe /CONFIG:EODService.xml from the build server, and it successfully installed our service remotely. Our build is back in business!

(1) http://forum.sysinternals.com/forum_posts.asp?TID=3935&PN=1&TPN=2#32755

Updated Wiki: PSExecLocksUp

mikedouglas — Sun, 23 Aug 2009 03:42:10 GMT

Team Deploy task completes but the MSI isn't updated on the clients. PSExec locks up.

Thanks to Ken Johnson for identifying and documenting this issue and Jeremy Novak for creating the CleanupPsExec task to fix this issue!

Our automated build recently stopped remotely installing our services from the build server (buildserver) to the system test application server (targetserver). It was able to stop and restart the service, and it thought it was installing the services, but the install was not actually running.
Here is a sample of one of our command lines: TeamDeploy.exe /CONFIG:EODService.xml
Because the services installed properly when running the MSI from the application server itself, and because TeamDeploy depends on PSTools for remote deployments, I started looking at thePSTools: specifically PSKill and PSExec.
First I verified that pskill was working remotely by opening notepad on the application server and killing it from the build server:
pskill \\targetserver notepad.exe

PsKill v1.03 - local and remote process killer
Copyright (C) 2000 Mark Russinovich
http://www.sysinternals.com

Process notepad.exe killed on targetserver.

Next, I tried to verify that psexec was working properly:

psexec \\targetserver "c:\windows\system32\ipconfig.exe"

PsExec v1.31 - execute processes remotely
Copyright (C) 2001-2002 Mark Russinovich
www.sysinternals.com

Error communicating with PsExec service on targetserver :
No process is on the other end of the pipe.

It returned an error indicating there was no process on the other end of the pipe. This seemed to indicate a problem with psexesvc.
Since psexesvc installs automatically when running psexec, I removed psexesvc from the application server (1):
sc \\targetserver stop psexesvc
SERVICE_NAME: psexesvc
TYPE : 10 WIN32OWNPROCESS
STATE : 3 STOP_PENDING
(STOPPABLE, NOTPAUSABLE, IGNORESSHUTDOWN))
WIN32EXITCODE : 0 (0x0)
SERVICEEXITCODE : 0 (0x0)
CHECKPOINT : 0x2
WAIT_HINT : 0x0

sc \\targetserver delete psexesvc
SC DeleteService SUCCESS

After cleaning up the psexesvc, I verified that psexec was working properly:

psexec \\targetserver ipconfig

PsExec v1.31 - execute processes remotely
Copyright (C) 2001-2002 Mark Russinovich
www.sysinternals.com

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::b5eb:e3
IPv4 Address. . . . . . . . . . . : 10.2.15.171
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 10.2.15.251

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconn
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconn
Connection-specific DNS Suffix . :
ipconfig exited on targetserver with error code 0.

The final test of course was to run TeamDeploy.exe /CONFIG:EODService.xml from the build server, and it successfully installed our service remotely. Our build is back in business!

(1) http://forum.sysinternals.com/forum_posts.asp?TID=3935&PN=1&TPN=2#32755

Updated Wiki: PSExecLocksUp

mikedouglas — Sun, 23 Aug 2009 03:41:23 GMT

asdf

!!Thanks to Ken Johnson for identifying and documenting this issue and Jeremy Novak for creating the CleanupPsExec task to fix this issue!

Our automated build recently stopped remotely installing our services from the build server (buildserver) to the system test application server (targetserver). It was able to stop and restart the service, and it thought it was installing the services, but the install was not actually running.
Here is a sample of one of our command lines: TeamDeploy.exe /CONFIG:EODService.xml
Because the services installed properly when running the MSI from the application server itself, and because TeamDeploy depends on PSTools for remote deployments, I started looking at thePSTools: specifically PSKill and PSExec.
First I verified that pskill was working remotely by opening notepad on the application server and killing it from the build server:
pskill \\targetserver notepad.exe

PsKill v1.03 - local and remote process killer
Copyright (C) 2000 Mark Russinovich
http://www.sysinternals.com

Process notepad.exe killed on targetserver.

Next, I tried to verify that psexec was working properly:

psexec \\targetserver "c:\windows\system32\ipconfig.exe"

PsExec v1.31 - execute processes remotely
Copyright (C) 2001-2002 Mark Russinovich
www.sysinternals.com

Error communicating with PsExec service on targetserver :
No process is on the other end of the pipe.

It returned an error indicating there was no process on the other end of the pipe. This seemed to indicate a problem with psexesvc.
Since psexesvc installs automatically when running psexec, I removed psexesvc from the application server (1):
sc \\targetserver stop psexesvc
SERVICE_NAME: psexesvc
TYPE : 10 WIN32OWNPROCESS
STATE : 3 STOP_PENDING
(STOPPABLE, NOTPAUSABLE, IGNORESSHUTDOWN))
WIN32EXITCODE : 0 (0x0)
SERVICEEXITCODE : 0 (0x0)
CHECKPOINT : 0x2
WAIT_HINT : 0x0

sc \\targetserver delete psexesvc
SC DeleteService SUCCESS

After cleaning up the psexesvc, I verified that psexec was working properly:

psexec \\targetserver ipconfig

PsExec v1.31 - execute processes remotely
Copyright (C) 2001-2002 Mark Russinovich
www.sysinternals.com

Windows IP Configuration

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Link-local IPv6 Address . . . . . : fe80::b5eb:e3
IPv4 Address. . . . . . . . . . . : 10.2.15.171
Subnet Mask . . . . . . . . . . . : 255.255.254.0
Default Gateway . . . . . . . . . : 10.2.15.251

Tunnel adapter Local Area Connection* 8:

Media State . . . . . . . . . . . : Media disconn
Connection-specific DNS Suffix . :

Tunnel adapter Local Area Connection* 9:

Media State . . . . . . . . . . . : Media disconn
Connection-specific DNS Suffix . :
ipconfig exited on targetserver with error code 0.

The final test of course was to run TeamDeploy.exe /CONFIG:EODService.xml from the build server, and it successfully installed our service remotely. Our build is back in business!

(1) http://forum.sysinternals.com/forum_posts.asp?TID=3935&PN=1&TPN=2#32755

Updated Wiki: Troubleshooting

mikedouglas — Sun, 23 Aug 2009 03:29:40 GMT

Troubleshooting Team Deploy

Issues

Team Deploy task completes but the MSI isn't updated on the clients. PSExec locks up.

Updated Wiki: CreateTeamDeployBuild

mikedouglas — Sat, 22 Aug 2009 18:41:14 GMT

Creating a Team Deploy TFS Build

In Team Explorer, create a new build in your Team Project by right clicking on Builds and choosing “New Build Definition”

Give it a name such as “Build and Deploy”

Create a workspace (Cloak other folders in your project that don’t need to be part of the build. This helps the speed up your build because otherwise the server will try to get all source files in the project)

Leave Project File name as is but click on the “Create” button to create a new TFSBuild.proj file.

Next choose the solution you want to build, then the configuration type. I recommend leaving the default.

Choose any options that you want to enable for running tests and/or code analysis. I would recommend leaving these unchecked for now and once you verify everything is working then go back and enable the options you want.

In TFS 2008, you can choose retention policies. This will help prevent builds from filling up your server disk space quickly. I usually choose Keep 7 latest.

the next options are for the Build Defaults. Choose the appropriate build agent. If unsure, just leave the default. Then choose the share where you want to copy the staging files.

The last option is “Trigger”. The "build and deploy" build should be separate from the continuous integration build. I recommend leaving the default “Check-ins do not trigger a new build”.

Finally click “OK” to create the build type.

Creating the build definition will create the TFSBuild.proj that contains the basic options that were selected in the wizard. The following steps will customize the TFSBuild.proj file created. This file is a Xml file based on MSBuild.

To modify the TFSBuild.proj file, located the file under Source Control -> $/YourTeamProject/TeamBuildTypes/Build and Deploy (You can also navigate directly to this file by right clicking on the build definition and choosing "View Configuration Folder".)

Check out and open the TFSBuild.proj file to configure it to use Team Deploy

Find the comment <!—Do not edit this -> and add the following line underneath the one that is already there. It should look something like the screenshot below

<Import Project="$(MSBuildExtensionsPath)\TeamDeploy\TeamDeploy.Tasks.targets" />

Scroll to the bottom of the TFSBuild.proj file to the <PropertyGroup>. Overwrite the Property group with the following (Adjust the paths for your specific environment):

<PropertyGroup>
    <KillAppPathFilename>c:\Program Files\PSTools\pskill2.exe</KillAppPathFilename>
    <RemoteExecutePathFilename>c:\Program Files\PStools\psexec2.exe</RemoteExecutePathFilename>
  </PropertyGroup>

  <!-- Deploy MSI  -->
  <Target Name="AfterEndToEndIteration">
    <CallTarget Condition="'$(IsDesktopBuild)'!='true'" Targets="DeployMSITargetVirtuals" />
  </Target>

  <Target Name="DeployMSITargetVirtuals">
    <Deploy DeployScript="$(SolutionRoot)\..\..\Push Scripts\SampleDeploy.xml"
            KillAppPathFilename="$(KillAppPathFilename)"
            RemoteExecutePathFilename="$(RemoteExecutePathFilename)"
            TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
            BuildUri="$(BuildUri)" />
  </Target>

The copied Xml in the TFSBuild.proj should look something like this

Save and check-in the TFSBuild.proj file

The Deploy task uses a Xml Deploy Script that contains the information of what Msi(s) to deploy, additional tasks such as starting and stopping the service, and specifies the target machines. The following steps walks you through editing this file.

There are a few things to note here.

Team Deploy can
- Kill 0 to many processes
- Deploy/Uninstall 0 to many MSIs
- Deploy MSIs to 0 to many Target Machines

Modify the xml appropriately for your environment. The GUID for the uninstalls are the MSI product codes. If the MSI is done correctly it will uninstall previous versions using the upgrade code, however they are usually unable to remove the same version of the MSI, this is why we have the separate step of uninstall.

The ExtraArgs element contains the SETUPENV variable that is used by the MSI’s custom action to copy the correct environment’s config file to the project’s. The custom action is a simple VBScript that copies the config file (not included with Team Deploy). Below is how the folder layout is. Ignore the “test” folder I added to exclude the other folder in my actual Program Files folder.

For more information on creating the MSI to support Team Deploy and automated deployments
Blog Post Deployments with TFS Part 2: How to create an automated deployment MSI
Sample MSI Solution: Automated Deployment MSI

Updated Wiki: CreateTeamDeployBuild

mikedouglas — Sat, 22 Aug 2009 18:40:40 GMT

Creating a Team Deploy TFS Build

In Team Explorer, create a new build in your Team Project by right clicking on Builds and choosing “New Build Definition”

Give it a name such as “Build and Deploy”

Create a workspace (Cloak other folders in your project that don’t need to be part of the build. This helps the speed up your build because otherwise the server will try to get all source files in the project)

Leave Project File name as is but click on the “Create” button to create a new TFSBuild.proj file.

Next choose the solution you want to build, then the configuration type. I recommend leaving the default.

Choose any options that you want to enable for running tests and/or code analysis. I would recommend leaving these unchecked for now and once you verify everything is working then go back and enable the options you want.

In TFS 2008, you can choose retention policies. This will help prevent builds from filling up your server disk space quickly. I usually choose Keep 7 latest.

the next options are for the Build Defaults. Choose the appropriate build agent. If unsure, just leave the default. Then choose the share where you want to copy the staging files.

The last option is “Trigger”. The "build and deploy" build should be separate from the continuous integration build. I recommend leaving the default “Check-ins do not trigger a new build”.

Finally click “OK” to create the build type.

To modify the TFSBuild.proj file, located the file under Source Control -> $/YourTeamProject/TeamBuildTypes/Build and Deploy (You can also navigate directly to this file by right clicking on the build definition and choosing "View Configuration Folder".)

Check out and open the TFSBuild.proj file to configure it to use Team Deploy

Find the comment <!—Do not edit this -> and add the following line underneath the one that is already there. It should look something like the screenshot below

<Import Project="$(MSBuildExtensionsPath)\TeamDeploy\TeamDeploy.Tasks.targets" />

Scroll to the bottom of the TFSBuild.proj file to the <PropertyGroup>. Overwrite the Property group with the following (Adjust the paths for your specific environment):

<PropertyGroup>
    <KillAppPathFilename>c:\Program Files\PSTools\pskill2.exe</KillAppPathFilename>
    <RemoteExecutePathFilename>c:\Program Files\PStools\psexec2.exe</RemoteExecutePathFilename>
  </PropertyGroup>

  <!-- Deploy MSI  -->
  <Target Name="AfterEndToEndIteration">
    <CallTarget Condition="'$(IsDesktopBuild)'!='true'" Targets="DeployMSITargetVirtuals" />
  </Target>

  <Target Name="DeployMSITargetVirtuals">
    <Deploy DeployScript="$(SolutionRoot)\..\..\Push Scripts\SampleDeploy.xml"
            KillAppPathFilename="$(KillAppPathFilename)"
            RemoteExecutePathFilename="$(RemoteExecutePathFilename)"
            TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
            BuildUri="$(BuildUri)" />
  </Target>

The copied Xml in the TFSBuild.proj should look something like this

Save and check-in the TFSBuild.proj file

Team Deploy can
- Kill 0 to many processes
- Deploy/Uninstall 0 to many MSIs
- Deploy MSIs to 0 to many Target Machines

Modify the xml appropriately for your environment. The GUID for the uninstalls are the MSI product codes. If the MSI is done correctly it will uninstall previous versions using the upgrade code, however they are usually unable to remove the same version of the MSI, this is why we have the separate step of uninstall.

The ExtraArgs element contains the SETUPENV variable that is used by the MSI’s custom action to copy the correct environment’s config file to the project’s. The custom action is a simple VBScript that copies the config file (not included with Team Deploy). Below is how the folder layout is. Ignore the “test” folder I added to exclude the other folder in my actual Program Files folder.

image

For more information on creating the MSI to support Team Deploy and automated deployments
Blog Post Deployments with TFS Part 2: How to create an automated deployment MSI
Sample MSI Solution: Automated Deployment MSI

Updated Wiki: Home

mikedouglas — Sat, 22 Aug 2009 16:44:54 GMT

Project Description
Deploy MSIs from TFS builds using these custom MSBuild tasks. This collection of tasks includes everything you need to deploy cilent apps to multiple PCs and windows services to Servers. Also includes a build notification task for controlling Lava Lamps/Street lights via X10.

Guidance
Installation
Troubleshooting
Creating a Team Deploy TFS Build

Team Deplloy MSI! Install Team Deploy using the MSI for easy installation.
Team Deploy 2.x - Current release is designed for Team Foundation Server 2008
Team Deploy 3.x - Future release designed for Team Foundation Server 2010 (Coming soon)

This project contains the following specialized custom MSBuild tasks for deploying MSIs and monitoring your build status.

Install task - installs an MSI on a target machine

Uninstall task - uninstalls MSI on a target machine by product code

KillProcess task - Kills any process on target machine (usually done before trying to uninstall/install MSI

Deploy task - This is the main task to be called from your TFS Team build type. This will loop through the deployment script and kill any processes necessary, uninstall the previous version, and install the new version. This now deploys in parallel for quicker deployments.

Start Service task - If deploying a windows service, call this to start the service.

Stop Service task - If deploying a windows service, call this to stop the service before uninstalling it.

Device Controller task - Use lava lamps or street lights to show the status of your builds.

Remote Execute task - Execute any executable on the target machines.

Updated Wiki: CreateTeamDeployBuild

mikedouglas — Sat, 22 Aug 2009 16:44:26 GMT

Creating a Team Deploy TFS Build

In Team Explorer, create a new build in your Team Project by right clicking on Builds and choosing “New Build Definition”

Give it a name such as “Build and Deploy”

Create a workspace (Cloak other folders in your project that don’t need to be part of the build. This helps the speed up your build because otherwise the server will try to get all source files in the project)

Leave Project File name as is but click on the “Create” button to create a new TFSBuild.proj file.

Next choose the solution you want to build, then the configuration type. I recommend leaving the default.

Choose any options that you want to enable for running tests and/or code analysis. I would recommend leaving these unchecked for now and once you verify everything is working then go back and enable the options you want.

In TFS 2008, you can choose retention policies. This will help prevent builds from filling up your server disk space quickly. I usually choose Keep 7 latest.

the next options are for the Build Defaults. Choose the appropriate build agent. If unsure, just leave the default. Then choose the share where you want to copy the staging files.

The last option is “Trigger”. The "build and deploy" build should be separate from the continuous integration build. I recommend leaving the default “Check-ins do not trigger a new build”.

Finally click “OK” to create the build type.

To modify the TFSBuild.proj file, located the file under Source Control -> $/YourTeamProject/TeamBuildTypes/Build and Deploy (You can also navigate directly to this file by right clicking on the build definition and choosing "View Configuration Folder".)

Check out and open the TFSBuild.proj file to configure it to use Team Deploy

Find the comment <!—Do not edit this -> and add the following line underneath the one that is already there. It should look something like the screenshot below

<Import Project="$(MSBuildExtensionsPath)\TeamDeploy\TeamDeploy.Tasks.targets" />

Scroll to the bottom of the TFSBuild.proj file to the <PropertyGroup>. Overwrite the Property group with the following (Adjust the paths for your specific environment):

<PropertyGroup>
    <KillAppPathFilename>c:\Program Files\PSTools\pskill2.exe</KillAppPathFilename>
    <RemoteExecutePathFilename>c:\Program Files\PStools\psexec2.exe</RemoteExecutePathFilename>
  </PropertyGroup>

  <!-- Deploy MSI  -->
  <Target Name="AfterEndToEndIteration">
    <CallTarget Condition="'$(IsDesktopBuild)'!='true'" Targets="DeployMSITargetVirtuals" />
  </Target>

  <Target Name="DeployMSITargetVirtuals">
    <Deploy DeployScript="$(SolutionRoot)\..\..\Push Scripts\SampleDeploy.xml"
            KillAppPathFilename="$(KillAppPathFilename)"
            RemoteExecutePathFilename="$(RemoteExecutePathFilename)"
            TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
            BuildUri="$(BuildUri)" />
  </Target>

Updated Wiki: CreateTeamDeployBuild

mikedouglas — Sat, 22 Aug 2009 16:38:26 GMT

Creating a TFS Build using Team Deploy

In Team Explorer, create a new build in your Team Project by right clicking on Builds and choosing “New Build Definition”

Give it a name such as “Build and Deploy”

Create a workspace (Cloak other folders in your project that don’t need to be part of the build. This helps the speed up your build because otherwise the server will try to get all source files in the project)

Leave Project File name as is but click on the “Create” button to create a new TFSBuild.proj file.

Next choose the solution you want to build, then the configuration type. I recommend leaving the default.

Choose any options that you want to enable for running tests and/or code analysis. I would recommend leaving these unchecked for now and once you verify everything is working then go back and enable the options you want.

In TFS 2008, you can choose retention policies. This will help prevent builds from filling up your server disk space quickly. I usually choose Keep 7 latest.

the next options are for the Build Defaults. Choose the appropriate build agent. If unsure, just leave the default. Then choose the share where you want to copy the staging files.

The last option is “Trigger”. The "build and deploy" build should be separate from the continuous integration build. I recommend leaving the default “Check-ins do not trigger a new build”.

Finally click “OK” to create the build type.

To modify the TFSBuild.proj file, located the file under Source Control -> $/YourTeamProject/TeamBuildTypes/Build and Deploy (You can also navigate directly to this file by right clicking on the build definition and choosing "View Configuration Folder".)

Check out and open the TFSBuild.proj file to configure it to use Team Deploy

Find the comment <!—Do not edit this -> and add the following line underneath the one that is already there. It should look something like the screenshot below

<Import Project="$(MSBuildExtensionsPath)\TeamDeploy\TeamDeploy.Tasks.targets" />

Scroll to the bottom of the TFSBuild.proj file to the <PropertyGroup>. Overwrite the Property group with the following (Adjust the paths for your specific environment):

<PropertyGroup>
    <KillAppPathFilename>c:\Program Files\PSTools\pskill2.exe</KillAppPathFilename>
    <RemoteExecutePathFilename>c:\Program Files\PStools\psexec2.exe</RemoteExecutePathFilename>
  </PropertyGroup>

  <!-- Deploy MSI  -->
  <Target Name="AfterEndToEndIteration">
    <CallTarget Condition="'$(IsDesktopBuild)'!='true'" Targets="DeployMSITargetVirtuals" />
  </Target>

  <Target Name="DeployMSITargetVirtuals">
    <Deploy DeployScript="$(SolutionRoot)\..\..\Push Scripts\SampleDeploy.xml"
            KillAppPathFilename="$(KillAppPathFilename)"
            RemoteExecutePathFilename="$(RemoteExecutePathFilename)"
            TeamFoundationServerUrl="$(TeamFoundationServerUrl)"
            BuildUri="$(BuildUri)" />
  </Target>

Updated Wiki: CreateTeamDeployBuild

mikedouglas — Sat, 22 Aug 2009 16:16:30 GMT

Creating a TFS Build using Team Deploy

In Team Explorer, create a new build in your Team Project by right clicking on Builds and choosing “New Build Definition”

Give it a name such as “Build and Deploy”

Create a workspace (Cloak other folders in your project that don’t need to be part of the build. This helps the speed up your build because otherwise the server will try to get all source files in the project)

Leave Project File name as is but click on the “Create” button to create a new TFSBuild.proj file.

Next choose the solution you want to build, then the configuration type. I recommend leaving the default.

Choose any options that you want to enable for running tests and/or code analysis. I would recommend leaving these unchecked for now and once you verify everything is working then go back and enable the options you want.

In TFS 2008, you can choose retention policies. This will help prevent builds from filling up your server disk space quickly. I usually choose Keep 7 latest.

the next options are for the Build Defaults. Choose the appropriate build agent. If unsure, just leave the default. Then choose the share where you want to copy the staging files.

The last option is “Trigger”. The "build and deploy" build should be separate from the continuous integration build. I recommend leaving the default “Check-ins do not trigger a new build”.

Finally click “OK” to create the build type.

To modify the TFSBuild.proj file, located the file under Source Control -> $/YourTeamProject/TeamBuildTypes/Build and Deploy

Check out and open the TFSBuild.proj file to configure it to use Team Deploy

Find the comment <!—Do not edit this -> and add the following line underneath the one that is already there. It should look something like the screenshot below

Updated Wiki: CreateTeamDeployBuild

mikedouglas — Sat, 22 Aug 2009 15:53:34 GMT

Creating a TFS Build using Team Deploy

In Team Explorer, create a new build in your Team Project by right clicking on Builds and choosing “New Build Definition”

Give it a name such as “Build and Deploy”

Create a workspace (Cloak other folders in your project that don’t need to be part of the build. This helps the speed up your build because otherwise the server will try to get all source files in the project)

Leave Project File name as is but click on the “Create” button to create a new TFSBuild.proj file.

Next choose the solution you want to build, then the configuration type. I recommend leaving the default.

Choose any options that you want to enable for running tests and/or code analysis. I would recommend leaving these unchecked for now and once you verify everything is working then go back and enable the options you want.

In TFS 2008, you can choose retention policies. This will help prevent builds from filling up your server disk space quickly. I usually choose Keep 7 latest.

the next options are for the Build Defaults. Choose the appropriate build agent. If unsure, just leave the default. Then choose the share where you want to copy the staging files.

The last option is “Trigger”. The "build and deploy" build should be separate from the continuous integration build. I recommend leaving the default “Check-ins do not trigger a new build”.