none
Dirty environment found on some models but not others RRS feed

  • Question

  • Hello.

    We use MDT 8443 to deploy clients (Windows 10) and servers (Windows Server 2016) and have issues with "Dirty environment found".

    Both clients and servers use UEFI booting. We initiate installations by PXE booting from a WDS server.

    On clients, some models install without a hitch and some consistently present a "Dirty Environment found" dialog, if you answer "No" and let the task sequence continue it finishes successfully.

    On servers, one model (HP ProLiant ML110 Gen9) applies the OS image and reboots, after reboot it boots to PXE. If we boot from WDS again, we get a "Dirty Environment found" dialog", answer "No", the server reboots and boots off internal disks. The installation seems to finish properly, but we get an error from ZTITatoo, "FAILURE ( 9601 ): ERROR - ZTITatoo state restore task should be running in the full OS, aborting" in the summary.

    If we run the same server task sequence on a VMWare virtual server, it finishes successfully without booting from PXE or displaying errors from ZTITatoo.

    Does anyone have an idea what goes wrong when we end up with a dirty environment?

    Thursday, December 22, 2016 11:42 AM

Answers

  • Two things come into mind..

    How is your boot sequence set on the dirt machines? Hard drive first?

    Also, in your task sequence are you properly formatting and partitioning the drives correctly?

    Thursday, December 22, 2016 12:08 PM

All replies

  • Two things come into mind..

    How is your boot sequence set on the dirt machines? Hard drive first?

    Also, in your task sequence are you properly formatting and partitioning the drives correctly?

    Thursday, December 22, 2016 12:08 PM
  • The boot sequence is hard drive first, both on clients and servers.

    On HP ML110 Gen9 the hard drive doesn't seem to be recognised as bootable until after the "Dirty environment found" has been answered "No" and the server reboots a second time.

    I use a "Standard Server Task Sequence" and it works without problems on a VMWare virtual server.

    Thursday, December 22, 2016 12:20 PM
  • Two things come into mind..

    How is your boot sequence set on the dirt machines? Hard drive first?

    Also, in your task sequence are you properly formatting and partitioning the drives correctly?

    You were right, the boot order is messed up during the install. It's OK before install and OK after, but during the installation something goes wrong and the network card has higher boot priority than the hard disk.

    On the server I use setbootorder.exe from HPE Scripting Toolkit to make sure that the hd is first. On clients we use cctk.exe to disable PXE boot in the default boot order.

    Tuesday, January 24, 2017 2:47 PM
  • Hi Daniel,

    I have the same Problem. Have you already solved it ?

    Tuesday, September 19, 2017 5:03 PM