Hello folks
I have a customer who has an environment which looks like this in CM2012R2 They have systems from both TEST and PROD in their CM environment and then they place them via Direct Membership into a rebuild collection. They then target a Task Sequence at the collection. The Task Sequence is set to Always ReRun (Yes, I know) The site is configured to Automatically Create new client Records for New Hardware IDs. They observe that when the Task Sequence completes against the TEST system it completes and the system stops. They observe in the TEST collection that an obsolete record exists which they can then delete. In PROD on the other hand that Task Sequence starts again and the system rebuilds! Aside from the discussions that we have had around their process and removing the system, or only re-running on error etc. I am struggling to find out - Whether this variation in functionality is by design or not? If so what the advantages of this would be - What the process is that is different in CM seeing one as new hardware and the other as not Many thanks
