none
ccmsetup during LTI causes Dirty Environment error RRS feed

  • Question

  • During my MDT 2013 task sequence, I have a step to install the SCCM 2012 R2 client.  During this task something causes a new deployment to attempt to kick-off, which generates a "Dirty Environment Found" message and ends the task sequence.

    In my searching I found this thread, which appears to be the same issue:

    https://social.technet.microsoft.com/Forums/en-US/4cc1c6a0-8651-4c40-a035-48b47692bb97/ccmsetup-during-lti-causes-dirty-environment?forum=mdt

    The only recommendation out of that thread was to install the SCCM client through other means.  Unfortunately, the SCCM environment is managed by another team and we don't have the option of deploying using the recommended methods (as much as I'd like to).  Are there any other options or modifications I can make to my ccmsetup task sequence to prevent this issue?


    • Edited by JPW.Meta Thursday, June 16, 2016 4:31 PM
    Thursday, June 16, 2016 4:31 PM

All replies

  • Hi

    you can install the SCCM client with a UserExit Script - then the SCCM client is first installed after the MDT task sequence is done running.

    Kind regards
    Per Larsen
    Twitter: @PerLarsen1975 | Blog: osddeployment.wordpress.com
    If this post is helpful please vote it as Helpful or click Mark for answer.

    Thursday, June 16, 2016 6:55 PM