SCCM Agent Install \ Deployment query?

Question

Hi All
I have a query regards best practices.  Within our environment we will have a number of Build Environments (all within the same domain), which will involve servers being built, decommissioned and rebuilt for application testing teams.
Query is how best to handle the install\life-cycle of the SCCM Agent with regards to this scenario?
Just looking to see if others have had experience of this type of scenario and best practices \ experiences etc
Any thoughts much appreciated.
Kind Regards
Andrew

Answer 1

Thank you for your replys Jason and Wally,
I guess 'best practice' was the wrong phrase to use in this case.  However across the other System Center applications a number of best practices have become established for a certain scenarios\processes, and I was looking to see if a similar
approach had become established for the scenario outlined.  However on reflection I appreciate SCCM is a product that has enormous flexibility with regards to the variety of environments and the complexity of scenarios it is able to accommodate\handle. Thus
as you say, 'best practices' are not that realistic in general.
With regards to the scenario mentioned, we have 'x' number of development environments which will be provisioned via VMM Service Templates, via SCSM and SCORCH automation.  With the first number of rebuilds the Server names will not be the reused, but
after 'x' number of rebuilds the server names will be cycled\reused.  After further digging\reading I believe a scripted approach would be best, along with a separate method of cleaning out old server names from within SCCM itself.  The main concern
is when a server names get reused, it may still be in the SCCM database, but the new Server (with same name) has a new SID; which I believe would\could introduce issues.
Although I guess, with all that said, the most elegant\simple approach would be to have a clean uninstall of the SCCM agents whenever a development environment is decommissioned?
Kind Regards
Andrew