Michael Niehaus' Windows and Office deployment ramblings
In MDT 2012 RTW that released back in April, we included support for DaRT 7, making it easy to add the DaRT components to Lite Touch boot images. See http://blogs.technet.com/b/mniehaus/archive/2011/11/28/mdt-2012-new-feature-dart-integration.aspx for more details on that.
With MDT 2012 Update 1 Beta 1, we added support for DaRT 8 Beta, while leaving support for DaRT 7 too. So if you are using Windows AIK, you would use DaRT 7; when you are using Windows ADK, you would use DaRT 8. (In general, DaRT releases are OS-specific, so DaRT 8 is for Windows 8 and DaRT 7 is for Windows 7.)
The basic functionality with DaRT 8 is the same as with DaRT 7: we add all the tools to the boot image, and we automatically run the remote agent so that you can make remote connections into Windows PE using the remote viewer (which is integrated into the MDT monitoring solution). Additional functionality in MDT 2012 Update 1:
See http://windowsteamblog.com/windows/b/springboard/archive/2012/03/28/microsoft-dart-8-beta-q-amp-a.aspx for more information on DaRT 8.
The error C:\Users\ADM-EL~1\AppData\Local\Temp\MDTUpdate.800\Mount\windows\system32\winpeshl.ini' already exists. I finally figured out this error is caused by the winpeshl.ini file still existing in the temp folder. Open a run tool, and type %temp%, and run it to show contents of the temp folder. I bet you will find the winpeshl.ini file inside it. You need to clean the temp folder out, and with using MDT 2012 you need to clean it out on a regular basis because it uses it a lot. If your not sure what can be deleted then use CCleaner, or disk cleaner to clean it. You can also create a batch file from the following commands, and run it to clean the temp folder out:
del /s /q /f %temp%\*
del /s /q /f %windir%\temp\*
Everytime I put DaRT 8 tool.cab files in the tools folder in my deployment share, and then I updated my deployment share I would get the winpeshl.ini exist error. I kept looking in the system32 folder for wineshl.ini, and it wasn't there. Now I know winpeshl.ini was actually in the temp folder, and once I deleted the winpeshl.ini file from the temp folder my deployment share updated fine. I had to regenerate my boot.wim files when I updated my deployment share, but after that DaRT8 worked. I ended up removing DaRT8 because I felt it wasn't safe to have in MDT, and I found no way to secure access to it. DaRT8 has some pretty powerful tools, such as Wipe Disk, Registry Editor, and Locksmith, and the way its accessed in MDT 2012 anyone in our network could boot to it, and use it. I finally created a DaRT 8 file with limited features, and uploaded it to Windows Deployment Service. Now if someone does gain access to DaRT 8 from WDS the Wipe Disk, Registry Editor, Lock Smith, and File Explorer are disabled. I have a full feature DaRT 8 on DVD when I need it. If someone knows a way to secure DaRT 8 in MDT 2012 please let me know.
With the new version Dart 220.127.116.11. Any chance you can create a blog about that using MDT 2013 and ADK 8.1 (WinPe 5.0)?