Is that because it doesn't work, or you just don't have a use for the tools? 
How do your desktop techs support boot failures, bitlocker recovery, etc?

Sent from my iPhone

> On Jun 30, 2015, at 7:57 AM, Marable, Mike <[email protected]> wrote:
> 
> Same here.  Just using it for remote access to WinPE as well.
> 
> Mike
> 
> 
> From: <[email protected]> on behalf of "[email protected]" 
> <[email protected]>
> Reply-To: "[email protected]" <[email protected]>
> Date: Tuesday, June 30, 2015 at 7:40 AM
> To: "[email protected]" <[email protected]>
> Subject: RE: [MDT-OSD] trouble injecting Dart Tools into MDT 2013
> 
> Nope, only using DaRT for remote access to WinPE.
>  
> Daniel Ratliff
>  
> From: [email protected] [mailto:[email protected]] 
> On Behalf Of Joe Sestrich
> Sent: Tuesday, June 30, 2015 7:34 AM
> To: [email protected]
> Subject: Re: [MDT-OSD] trouble injecting Dart Tools into MDT 2013
>  
> Anyone? No one uses this?
> 
> 
> Sent from my iPhone
> 
> On Jun 26, 2015, at 8:54 AM, Joe Sestrich <[email protected]> wrote:
> 
> Has anyone successfully got the Dart 8.1 tools injected into MDT 2013 WinPE, 
> so that you get the “Start Recovery Wizard” option, can authenticate to the 
> offline OS and all tools are functional?
>  
> I can get the use Dart Tools button, but anything that requires offline 
> access to the OS is unavailable. SFC, Computer Management, etc, all say “Tool 
> requires a supported offline OS”
>  
> The only way I could get close was replacing the ADK winpe.wim with the 
> boot.wim from an 8.1 source. If I do that, I get the use recovery tools 
> option, and if I click on it, it recognizes both Win7 and Win 8 as supported 
> OSes, but doesn’t offer me any way to authenticate, and the tools are still 
> unavailable.
>  
> Ironically, this worked perfectly in MDT 2010 when you had to inject the 
> files manually. Now that it’s built into the MMC, it doesn’t work. Any 
> suggestions?
>  
> 
> The information transmitted is intended only for the person or entity to 
> which it is addressed
> and may contain CONFIDENTIAL material. If you receive this 
> material/information in error,
> please contact the sender and delete or destroy the material/information.
> **********************************************************
> Electronic Mail is not secure, may not be read every day, and should not be 
> used for urgent or sensitive issues

Reply via email to