anyweb

first things first, did you read the release notes to verify that that is not a bug ?

you can keep the old SUG for reporting purposes as you see fit (to check for compliance etc.) and then delete them when you feel it's ok to do so.

perhaps you need to be using MDT 2013 preview from here http://blogs.technet.com/b/configmgrteam/archive/2013/06/26/microsoft-deployment-toolkit-2013-preview-now-available.aspx i havn't tried it yet though, I assume the above is for your LAB use, as you should not be installing R2 preview in production.

what version of MDT are you using and what version of ADK is installed (and what version of R2 ?)

I'm very happy to say that I just got an email from Microsoft notifying me that i've been re-awarded the MVP title for Configuration Manager (Enterprise Client Management) for 2013, and here it is ! thanks a million Microsoft for giving me the honor of having this award for another year (my fourth !) and thanks to my family for supporting me with all this, and thanks to all of the loyal members of windows-noob.com and niallbrady.com who keep me on my toes ! cheers niall

its not mandatory but the MDT boot images do allow you additional functionality out of the box so i would definetly recommend using them

you didn't attach anything however I saw the same results as you using MDT 2012 in Configuration Manager 2012, I think it's a bug (from memory) i'll see if I can find any reference to that

great stuff and welcome

interestingly it says so have you dealt with certs ? are you running in https mode ? if you search for the mac address of the client do you see anything related to it's pxe boot attempt

I agree with Peter plus I'd add that you should not do the following 2)clean sccm client with "ccmclean" 3) repair WMI is the correct way to uninstall the client

i've just done a build and capture of windows 7x64 with 145 updates and it went fine....slow but fine i would try with windows 8 only that windows 8.1 is out....

ok can you post your smspxe.log file from the server hosting the pxe enabled dp

it's referring to volume D:\ and you are looking in C:\ so which is it, c or d ?

Today Microsoft took the wraps off its holiday hardware lineup, unveiling two new tablets, and a number of new and updated accessories. It’s a lot of information to process, so let’s go through each piece in order. I spent time in Redmond last week with the new hardware, and the team behind the Surface project itself. Hands on notes regarding the Surface 2 and Surface Pro 2 will be published following this piece, along with an extensive interview with Brian Hall, current general manager of the Surface effort, and Panos Panay, corporate vice president at Microsoft and chief of Surface. For now, you need an overview of what’s new. We’ll get granular shortly. Here’s the once-over. Surface 2 The Surface 2 is the second generation of the Surface RT, though its name doesn’t take after its ancestor. In its most basic formulation, the Surface 2 is quite similar to its predecessor: It is an ARM-based tablet that supports attachable keyboards, and is built to make Windows 8(.1) sing. That aside, Microsoft has made across-the-board improvements to the product itself. Battery life has been bettered by 25%. A new processor (the NVIDIA Tegra 4 chip) has improved speed and graphical performance. The kickstand now includes a second, deeper angle that makes using the device on your lap far simpler. It has a new look, with a silver magnesium case that resists fingerprints, and is sturdier. It has improved cameras to better support low light settings, helping you Skype with folks in darker rooms. And, it’s cheaper, starting off at $449 – Surface RT headed into the market for $499. If you think that Windows 8.1 matures the Windows 8 platform sufficiently for daily use, and that the Windows Store has become populated enough with applications in its year of life, the Surface 2 could be a device that you enjoy. Certainly, the hardware has has improved greatly since its first generation. The question becomes how well Windows 8.1 can take advantage of those upgrades. Frankly, the Surface 2 is a very good-looking device, and one that I would feel great using at a cafe if I ever worked in such desultory locales. In that vein, its success is quite tied to that of Windows 8.1: The better Windows 8.1, the more the Surface 2′s upgrades can shine through. The Surface 2 (again, in my very limited hands-on time) proved a capable device. I can see students loving it, for example. Surface Pro 2 If the upgrades to the Surface 2 were broad and various, the changes to the Surface Pro 2 are targeted and vertical: It’s all about battery life, baby. According to Microsoft – and more on this later – it received constant feedback that business customers were interested in the Surface Pro, but could not bear its underperforming battery life. The company is frank that its first generation Pro lacked in that department. So, instead of changing the device externally a single mote, Microsoft rejiggered the guts of the unit into what it calls the Surface Pro 2, which will have around 60% better battery life, a figure that it claims can skew higher in certain use cases. The Surface Pro 2 has been bumped up to the Haswell generation of Intel chips, can contain up to 8 gigabytes of low-power DDR RAM, and a SSD that can reach the half-terabyte mark. It also receives the new kickstand position, which Microsoft is proud of, mostly because it works. The Surface Pro 2 looks like its predecessor, is the same size and weight, but lasts longer, and goes harder and faster if you kit it properly. It starts at the same price point as its forefather: $899. read the rest via > http://techcrunch.com/2013/09/23/meet-microsofts-surface-2-surface-pro-2-new-touch-type-covers-and-more/

have you tried removing and recreating the deployments ?

if it fails while in WinPE: x:\windows\temp\smstslog\smsts.log if it fails while in windows: c:\windows\ccm\logs\smstslog\smsts.log and c:\windows\ccmsetup\ccmsetup.log

you need the client side smsts.log file, and ccmsetup.log file from the client, place a pause in the task sequence to help troubleshoot it

windowsupdate.log should tell you which update is forcing a restart, task sequences don't like being forced to restart take a look at this post to see how you can get 'all' the updates in one task sequence

you need to see what updates are Required on that computer, check the windowsupdate.log for details

yep, here's the important bit and that is scheduled for GA (General Availability) October 18th

how does your setup windows and configmgr step look ? as the computer is in a workgroup you need to specify SMSMP=fqdn.of.your.mp for it to find the software updates and secondly do any of the updates force the computer to restart, if so remove them from your Software update group

if this is a normal task sequence and you are making minor edits to it then theres no need to redistribute anything other than a package/application that you change. so what type of task sequence is this and what change have you made ?

completely automated with Configuration Manager 2012 ?

have you tried setting HideOEMRegistrationScreen to true ?

try last one month.... if you want updates released in the LAST MONTH timeframe.