For Lite Touch, it's never a good idea to continue using task sequences created 
with a preview release :)  Those should be recreated with the official release 
to pick up fixes made in the task sequences after the preview release, changes 
the Unattend.xml templates used, etc.

Existing ones from MDT 2013 (RTW) should be fine, but those wouldn't be Windows 
10-related.

For ConfigMgr-integrated task sequences, existing ones continue unaffected 
(since they have their own self-contained "MDT" in the MDT toolkit files 
package).  But don't try to update an existing task sequence to use a new MDT 
toolkit files package from a later release, that's not tested.  If you want to 
use the MDT 2013 Update 1 scripts, you need to create a new MDT-integrated task 
sequence.

Thanks,
-Michael

From: [email protected] [mailto:[email protected]] On 
Behalf Of Marcum, John
Sent: Tuesday, August 18, 2015 11:03 AM
To: [email protected]; [email protected]
Subject: [MDT-OSD] RE: MDT 2013 Update 1

Michael, Is it your recommendation to create all new task sequences when an MDT 
update is released or are you just saying the ones for Windows 10? Just curious.




From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Michael Niehaus
Sent: Tuesday, August 18, 2015 1:45 PM
To: [email protected]<mailto:[email protected]>; 
[email protected]<mailto:[email protected]>
Subject: [mssms] RE: MDT 2013 Update 1

On item #1, did you create a new task sequence for Windows 10 with the MDT 2013 
Update 1 final release?  Can you check the Unattend.xml associated with your 
task sequence to confirm that it contains this entry:

                <RunSynchronousCommand wcm:action="add">
                    <Description>disable async RunOnce</Description>
                    <Order>4</Order>
                    <Path>reg add 
HKLM\Software\Microsoft\Windows\CurrentVersion\Explorer /v AsyncRunOnce /t 
REG_DWORD /d 0 /f</Path>
                </RunSynchronousCommand>

That is necessary to make HideShell work; without that, RunOnce entries run 
asynchronously, so the shell shows up.

For #2, that obviously sounds backwards :)  Was this a BIOS or UEFI system?  
Did you modify the built-in "Format and Partition Disk" step or use the 
default?  And again, did you create a new task sequence or attempt to reuse an 
existing one from a preview release?

For #3, when you say "Sysprep phase" do you mean during specialize or OOBE (new 
image being deployed), or during sysprep itself (preparing image for capture)?  
I suspect you mean specialize or OOBE.  If during specialize/OOBE, could you 
send the setupact.log files from \windows\panther and 
\windows\panther\unattendgc?  If during Sysprep, could you send setupact.log 
from \windows\system32\sysprep\panther?

Thanks,
-Michael

From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of Anjos, Valter Ângelo 
Brites, Vodafone Portugal (External)
Sent: Tuesday, August 18, 2015 9:00 AM
To: [email protected]<mailto:[email protected]>; 
[email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: MDT 2013 Update 1

Hi Folks,

It seems to me that there are a lot of bugs in this version...

Let me just share with you some issues that I've found so far:


-          HideShell doesn't work on Windows 10. It seems that Deployment 
process just ignore it and you are able to see the desktop and interact with 
the system while the deployment process is running;

-          If you create a Standard Client Task Sequence you will notice that 
you are not able to install the OS due to the following error: "there is no 
enough disk space available". It seems that scripts that create disk partitions 
are not ok. You get the recovery partition with most of the disk space and you 
just get a little percentage of disk space on your osdisk partition. 
Anyway..this one is easy to sort out.

-          During the sysprep phase you get an error box without any 
message...not sure yet why is that happening.

I've decided to get back to the old version until I'm able to install something 
on MDT 2013 U1 using the standard client task sequence.

Thank you,

Best Regards,

Valter Anjos
Systems Engineer
Front End Services
Vodafone Portugal
Mobile: +351912104234
Phone: +351210914725
Email: [email protected]<mailto:[email protected]>


Sede: Av. D. João II, Lote 1.04.01, Parque das Nações, 1998-017 Lisboa, Portugal
vodafone.pt <http://www.vodafone.pt/>



This message and any files or documents attached are strictly confidential or 
otherwise legally protected. It is intended only for the individual or entity 
named. If you are not the named addressee or have received this email in error, 
please inform the sender immediately, delete it from your system and do not 
copy or disclose it or its contents or use it for any purpose. Please also note 
that transmission cannot be guaranteed to be secure or error-free.



From: [email protected]<mailto:[email protected]> 
[mailto:[email protected]] On Behalf Of LEROY Mathieu
Sent: 18 de agosto de 2015 16:23
To: [email protected]<mailto:[email protected]>; 
[email protected]<mailto:[email protected]>
Subject: [MDT-OSD] RE: MDT 2013 Update 1

Great news ... but be sure the check this out before upgrading ;
https://keithga.wordpress.com/2015/08/17/mdt-2013-uberbug01-mdac-and-the-fast-machine/
and
http://deploymentresearch.com/Research/Post/504/A-Geeks-Guide-for-upgrading-MDT-2013-to-MDT-2013-Update-1




De : [email protected]<mailto:[email protected]> 
[mailto:[email protected]] De la part de Barnes,Chris
Envoyé : mardi 18 août 2015 16:11
À : [email protected]<mailto:[email protected]>; 
'[email protected]' 
<[email protected]<mailto:[email protected]>>
Objet : [mssms] MDT 2013 Update 1

http://blogs.technet.com/b/msdeployment/archive/2015/08/17/mdt-2013-update-1-now-available.aspx


Chris Barnes
Senior Technical Specialist
Penske Automotive Group
(248) 648-2528 Direct
(248) 767-4415 Mobile

[Penske75new]


________________________________

Penske Automotive Group and its affiliates will never sell or rent your email 
address in violation of applicable law. This email and any files transmitted 
with it are confidential and intended solely for use of the individual or 
entity to whom they are addressed. Please delete all copies if you are not the 
intended recipient.


________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.



Reply via email to