I have noticed the slowness also.
Running on VMware ESXi 5.1... Another thing I also experienced after the
SP1 -> R2 upgrade,
I got my ESXi host (the one with SCCM server) crashing with purple
screen when the WinPE started to download the .wim
image for the OS deployment that was targeted on VM that was on the same
host (ESXi server)
that SCCM server was...
Deployment to another host didn't crash the SCCM server's host...
I re-produced this with two different HW, after moving the SCCM server
between hosts, same thing happend every time.
We didn't have this kind of problem with SP1 and I'm not really sure is
this a VMware bug or SCCM bug, haven't tested
with ESXi 5.5 yet.
On 28.10.2013 11:47, Niall Brady wrote:
it seems that others that are seeing
<http://www.windows-noob.com/forums/index.php?/topic/9312-slow-image-deployment-download-since-sccm-2012-r2-upgrade/#entry35196>
this have Vmware back end servers, could this be part of the problem
(only reason I'm saying this is I havn't seen the issue and i'm using
hyperV only) ?
On Mon, Oct 28, 2013 at 10:39 AM, Johns, Damon (DoJ)
<[email protected]
<mailto:[email protected]>> wrote:
Hi Robert,
My configuration prior to the upgrade was Config Mgr 2012 SP1 with
MDT 2012 Update 1 integration enabled – Boot images were MDT WinPE
4.0 generated within the Config Mgr console with Dart v7. OS wim
files etc downloading normally under WinPE. This was running on a
fully patched Server 2008 R2 instance with local minimum SQL 2008
R2 level DB instance.
My PXE enabled DP’s are also running Server 2008 R2. I had one
instance of WDS failing on one of the DP’s after the upgrade,
removing WDS and reinstalling the role corrected the problem.
Upgrade path as follows:
Uninstalled ADK 8.0 via add remove programs
Installed ADK 8.1
Installed MDT 2013 which updated the MDT 2012 Update 1 instance
Installed Config Manager 2012 R2
Re-ran MDT Integration following successful upgrade to R2
Removed existing WinPE 4.0 boot images from distribution points
and left them intact within the console
Created new MDT 2013 generated WinPE 5.0 boot images and
replicated to DPs
Created new MDT 2013 files package in Config Mgr after upgrading
my MDT deployment share
Adjusted Task Sequences etc, etc
I do have the Dart 7.0 components in my MDT WinPE 5.0 boot images
however I don’t believe this is related to the slow downloads
within the PE environment. No other additional components have
been added when creating the WinPE 5.0 boot images and I don’t
have any additional files or pre-exec hook’s built into the boot
images. Just standard MDT generated with the Dart 7.0 component.
OS wim files were captured using MDT 2012 Update 1 (for Win 7) and
MDT 2013 (for Win 8.1) with standard sysprep and capture TS.
Source wim images built and captured using Hyper V on Windows 8
Enterprise.
Hope a fix is found soon!
Cheers
Damon
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]
<mailto:[email protected]>] *On Behalf Of *Robert
Marshall
*Sent:* Monday, 28 October 2013 7:59 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* RE: [mssms] RE: Slow download in 2012 R2 WinPe
From the thread, it seems several have logged with CSS, should be
quick now.
Is there anything “Exotic” about your configuration that stands
right out? Anything done to these OS, there is a variable involved
here, some are seeing the issue and others are not L
Robert
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]] *On Behalf Of *Jason Sandys
*Sent:* 28 October 2013 01:02
*To:* [email protected] <mailto:[email protected]>
*Subject:* [mssms] RE: Slow download in 2012 R2 WinPe
They’ve had a hard time repro-ing this internally but are well
aware of the many folks having the issue and are actively working
to address it. Your best bet is to contact CSS and provide
information about the environment and issue – the more info that
they have, the better they will be able to find the root cause and
provide the fix (whether that be code or configuration).
J
*From:*[email protected]
<mailto:[email protected]>
[mailto:[email protected]] *On Behalf Of *Johns,
Damon (DoJ)
*Sent:* Sunday, October 27, 2013 7:36 PM
*To:* [email protected] <mailto:[email protected]>
*Subject:* [mssms] Slow download in 2012 R2 WinPe
For everyone’s information on this email group:
http://social.technet.microsoft.com/Forums/en-US/4c72ae27-198f-4751-b0d6-340a11b52bd4/insanely-slow-os-download-in-2012-r2-winpe?forum=configmanagerosd
I am also experiencing this issue. Hopefully a hotfix / work
around is released by Microsoft shortly.
When you have 150+ replacements coming up – an extra 15-20 minutes
to download the OS to the disk really blows out your replacement
times. I’ve also noticed that its slow when downloading driver
packages and the MDT 2013 Files package.
Regards,
Damon
------------------------------------------------------------------------
CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or
protected by legal professional privilege, and is intended only
for the person or persons to whom it is addressed. If you are not
such a person, you are warned that any disclosure, copying or
dissemination of the information is unauthorised. If you have
received the transmission in error, please immediately contact
this office by telephone, fax or email, to inform us of the error
and to enable arrangements to be made for the destruction of the
transmission, or its return at our cost. No liability is accepted
for any unauthorised use of the information contained in this
transmission.
------------------------------------------------------------------------
CONFIDENTIALITY NOTICE AND DISCLAIMER
The information in this transmission may be confidential and/or
protected by legal professional privilege, and is intended only
for the person or persons to whom it is addressed. If you are not
such a person, you are warned that any disclosure, copying or
dissemination of the information is unauthorised. If you have
received the transmission in error, please immediately contact
this office by telephone, fax or email, to inform us of the error
and to enable arrangements to be made for the destruction of the
transmission, or its return at our cost. No liability is accepted
for any unauthorised use of the information contained in this
transmission.
