I do use several PowerShell scripts in my task sequence, but they all kick off
after the OS is applied so it's no longer running in WinPE. Where in the task
sequence are your PowerShell scripts running?
The newer ADK supposedly fixes those problems, but i couldn't get it to work it
kept giving me hardware errors. I don't use MDAC so I can't comment on that
issue.
-Joe
Sent from Outlook Mobile
_____________________________
From: Miller, Todd <[email protected]>
Sent: Thursday, February 25, 2016 9:08 AM
Subject: Re: [MDT-OSD] Current recommendation for win 10
To: <[email protected]>
This post by Aaron says that win 10 ask (rtm) has problems with
powershell and MDAC. Both of which I need to use. Are those problems resolved
in some way?
https://blogs.technet.microsoft.com/configmgrteam/2015/11/20/issue-with-the-windows-adk-for-windows-10-version-1511/
On Feb 25, 2016, at 5:51 AM, Joe Krilov < [email protected]> wrote:
I'm just wrapping a Windows 10 project for a client and it
went surprisingly well. I installed SCCM 1511 with MDT 2013 u2. The only
issue I had was needing to roll back to The RTM Windows 10 ADK due to a known
WinPE bug.
I deployed a very large task sequence with over two dozen
applications and also used the UDI wizard in MDT for other optional settings.
The client had lots of hardware including the surface pro 4 and surface book
and things went very smoothly. I used a MDT task sequence and customized it as
needed.
-Joe
Sent from Outlook Mobile
On Wed, Feb 24, 2016 at 8:32 PM -0800, "Miller, Todd"
<[email protected]> wrote:
I'm Looking for some advice among SCCM 2012r2 sp1,
SCCM 1511, or wait a few more weeks...
Id like to get started with building a Windows 10
deployment and I am having trouble figuring out the best course of action.
I am currently deploying windows7 x64, Windows 7 x86,
and Windows xp x86. I am willing to drop support for XP deployment if I have
to, but I still need to maintain SCCM client support for it.
I am using SCCM R2 with cu4 and MDT 2013 integrated.
The last time I investigated everyone was complaining
about lots of things being broken --- Powershell not working, DaRT being
broken, ADK not installing components like MDAC in WinPE correctly, and driver
packages exploding in size so I just decided to sit on the sidelines and let
things settle down.
Then Microsoft announced that Skylake based systems
will lose Windows 7 support in July 2017 so that got my attention. I
need to get moving on Windows 10.
So what is the current thinking? Upgrade SCCM to 1511
and MDT 2013 u2? Upgrade SCCM to 2012r2 sp1 and MDT 2013u1 and hold on to
older Win10 ADK? Hold out for a few more weeks for more bugs to get stomped?
Not sure what to do...
I rely heavily on the MDT database to drive ZTI task
sequences. DaRT, MBAM bit locker is important to me and I have several POSH
based takes steps that need to work. I don't care about MDT standalone, but I
do use the DB and the monitoring service- I just don't build any machines or
images out of there.
I don't want to update to SCCM 1511 to find that that
sticks me with a WinPE 10 version where other things I need are broken. Also
I'd like to maintain client support for XP so I'd rather not take a version of
SCCM that can't manage XP unless I absolutely have to.
Not sure where my next step should be, and I want to
know what is going to break and what is not going to work before I go there.
It seems like there are a lot of people complaining about all kinds of things
not working correctly with regards to Windows 10 releases especially around the
ADK and I can't figure out what problems are fixed and what problems are real
and what problems still exist. Microsoft is not exactly forthcoming on what is
not working so I have to rely on technet forums and the like and that is not
always accurate advice...
Sent from my iPad
Notice: This UI Health Care e-mail (including attachments) is covered
by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is
confidential and may be legally privileged. If you are not the intended
recipient, you are hereby notified that any retention, dissemination,
distribution, or copying of this communication is strictly prohibited. Please
reply to the sender that you have received the message in error, then delete
it. Thank you.
Notice: This UI Health Care e-mail (including attachments) is covered by
the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is confidential
and may be legally privileged. If you are not the intended recipient, you are
hereby notified that any retention, dissemination, distribution, or copying of
this communication is strictly prohibited. Please reply to the sender that you
have received the message in error, then delete it. Thank you.
