Let’s have look at how to setup a deployment agent for VS 2013 Release Management. I have explained in earlier posts on setting up a Release Management Server and a Release Management Client.
Launch Deployment Agent setup.
Installer will be very quick.
![002 002](http://lh6.ggpht.com/-FrVOXmTMscM/U9_FccC1mII/AAAAAAAACtI/jThhAp7dC9M/002_thumb%25255B7%25255D.png?imgmax=800)
![003 003](http://lh3.ggpht.com/-0M1l5z0dCdw/U9_FeCgD6JI/AAAAAAAACtY/evJkDiDqroY/003_thumb%25255B7%25255D.png?imgmax=800)
Launch to configure.
![004 004](http://lh3.ggpht.com/-tjrtxgBzuTo/U9_FfbfmtSI/AAAAAAAACto/Mb9DnOlQohI/004_thumb%25255B2%25255D.png?imgmax=800)
![005 005](http://lh5.ggpht.com/-kCGwPcO0TDs/U9_Fgyay9OI/AAAAAAAACt4/NNRM3TNzQ9s/005_thumb%25255B1%25255D.png?imgmax=800)
We need an account to set up agent. Let’s add a domain account.
![006 006](http://lh5.ggpht.com/-abi0oZCn2kc/U9_FiR5QUoI/AAAAAAAACuI/h0uzsCQElFk/006_thumb%25255B7%25255D.png?imgmax=800)
![007 007](http://lh4.ggpht.com/-p7_vMwdaA2g/U9_FkNqMVjI/AAAAAAAACuY/BEfUmrOB-E0/007_thumb%25255B1%25255D.png?imgmax=800)
Make sure to add the rmagent account created above to the deployment machine local administrators group.
![012 012](http://lh3.ggpht.com/-FDpmeOikX8Q/U9_Fl1HUZrI/AAAAAAAACuo/hgKfqwCZ6PQ/012_thumb%25255B2%25255D.png?imgmax=800)
![013 013](http://lh6.ggpht.com/-Nns5YnaLePw/U9_FnuAIi_I/AAAAAAAACu4/4kKADfm7aEg/013_thumb%25255B1%25255D.png?imgmax=800)
It is really easy when configuring a Deployment Agent in the same domain as Release Management Server. Use the created domain account as the account for Deployment Agent and provide Release Management Server url to configure. The user running the configuration should have Release Manger role in the server.
![008 008](http://lh3.ggpht.com/-FwLUlHbAT6I/U9_FpOgbI8I/AAAAAAAACvI/uHmQtDwgP1I/008_thumb%25255B1%25255D.png?imgmax=800)
Configuration succeeds.
![009 009](http://lh5.ggpht.com/-SLHmwLzR_Lc/U9_FqbIEV7I/AAAAAAAACvY/Xu_Dw2FECds/009_thumb%25255B1%25255D.png?imgmax=800)
Successful configuration can be verified in services.
![010 010](http://lh6.ggpht.com/-ovIVHGYBDFk/U9_FsInS7FI/AAAAAAAACvo/Vr9Uk82Z8mc/010_thumb%25255B1%25255D.png?imgmax=800)
rmagent account is added as a service account to Release Management Server
![011 011](http://lh5.ggpht.com/-VTaRngCDciI/U9_Ftc0UnYI/AAAAAAAACv4/ndZIrJS2qqw/011_thumb%25255B2%25255D.png?imgmax=800)
Now the Deployment Agent machine can be registered in the Release Management Server.
Adding a deployment agent is easy in the same domain. To add a machine outside of domain follow below steps.
1. Create account rmshadowagent as window user in Release Management Server.
2. Create same account with same password in deployment agent machine, and add the rmshadowagent account to local admin group the deployment agent machine.
3. Add rmshadowagentwith only user name to RM server and make him ReleaseManager and a service user
![014 014](http://lh5.ggpht.com/-kQt_DFSO9J8/U9_FvP-xqKI/AAAAAAAACwI/i0hsjgCFN9o/014_thumb%25255B1%25255D.png?imgmax=800)
4. Log on to deployment agent machine with rmshadowagent user or in deployment agent run the deployment agent configuration as rmshadowagent user (run as different user).
![015 015](http://lh4.ggpht.com/-Qopfigsh5R8/U9_FwXB_R3I/AAAAAAAACwY/ejOdnQqokkY/015_thumb%25255B1%25255D.png?imgmax=800)
![016 016](http://lh4.ggpht.com/-1v4JWAWZmWg/U9_FxhWG4WI/AAAAAAAACwo/LeHu3mhNFTA/016_thumb%25255B1%25255D.png?imgmax=800)
5. In configuration screen provide shadow agent user name (only rmshadowagent ) and password, and Release Management Server url. Release Management Server url can be exposed as https, so that this can be used to configure agent (example – Production machine in client’s environment) fully outside of the Release Management Server network.
Note use of .\rmshadowagent or machine\rmshadowagent will give error "user is not a release manager and service"
![017 017](http://lh3.ggpht.com/-sqIEosYtyzw/U9_Fyw8MPtI/AAAAAAAACw4/wkdtdsbgJcI/017_thumb%25255B1%25255D.png?imgmax=800)
6. After “Apply Settings” and configured successfully, removal of shadow user (rmshadowagent ) release manger role is possible. (if adding new agent with this user again, temporary make him release manager)
Successfully configured agent machine can now be registered in the Release Management Server.
No comments:
Post a Comment