anyweb

you do not need to integrate MDT 2013 Update 1 for Windows 10 deployments, but it is a benefit. by the way the updated version of this post is here http://www.windows-noob.com/forums/topic/12873-how-can-i-deploy-windows-10-enterprise-x64-with-mdt-2013-update-1-integrated-with-system-center-2012-r2-sp1-configuration-manager/

Microsoft's Live Stream of the Microsoft Windows 10 Devices event will be available at the following location. this event will most likely be used to unveil a whole bunch of exciting new hardware like the Microsoft Surface Pro 4 The starting times are listed below, stay tuned ! San Francisco: 7:00AM / New York: 10:00AM / London: 3:00PM / Berlin 4:00PM / Moscow: 6:00PM / Beijing: 10:00PM / Tokyo: 11:00PM / Sydney 12:00AM (October 7th) Some photos of the live event are shown below: Microsoft To Ship HoloLens Development Kits For $3000 In First Quarter Of 2016 Introducing the Band 2 and the Lumia 950 and finally.......... 12.3 inches in diagonal, 1TB storage, 16GB RAM, wow, the Surface Pro 4 oh and then there's the Surface Book ! You can review the video again by clicking on the link above or read the blog below http://blogs.windows.com/devices/2015/10/06/a-new-era-of-windows-10-devices-from-microsoft/ and you can pre-order the devices from the Microsoft Store here http://www.microsoftstore.com/store/msusa/en_US/pdp/productID.325716000

i'd backup the two captured images on another server (in case someone needs them later) and then remove them, that should free up a bunch of space, when you say there are isos, do you mean an actual ISO file or an extracted file, if both are not in use then you can remove them from the console and then from the sources\osinstaller folder.

I would first start by finding out what's grabbing all the space, my guess is it's the SQL reporting service log file, if so, maybe just shrinking that file will resolve your current problem.

you can absoultely do offline servicing and combine it with in task sequence applied updates, i was only giving one example of how it's beneficial, there are more, such as size of apps (fat apps like Office, SAP, SEP) which take time to download and install, if they are already baked into the image, that can cut some time off of the deployment either way it's a flexible process and no one is telling you that you have to use one method over another, do what works for you ! cheers niall

the benefits are varied but you could think of it like this, imagine you are deploying Windows 7 (yes a lot of people still are), well the WIM file for that doesn't contain all the software updates that have been released in the last few years which means that you either patch it during deployment, or after first login, neither would be a good experience (think of time etc) to mitigate that you can build and capture the image including software updates which will mean the image is relatively stable security wise when being installed, that's just one example of why people use the build and capture method to create reference images. cheers niall

the configmgrsetup.log should give you some clues, it's in the root of C:\ on the site you do the upgrade on, does it reveal anything ?

this tells me you are using the old version of the ccm client, which doesn't work properly with SCCM 2012 R2 SP1 (cu1), so have you updated your infrastructure yet ?

no apps are installing because the ConfigMgr client is failing to install <![LOG[Failed to install SMS Client (0x80004005)]LOG]!><time="12:21:10.160+420" date="10-02-2015" component="OSDSetupHook" context="" type="3" thread="2368" file="basesetuphook.cpp:1517"> so.. what does the ccmsetup.log file tell you ? and as your post is really not inline with this overall topic i'm going to create a new thread (this one.)

you need to look at the smsts.log file to determine what step is failing (and why it's failing)

they should work, ,can you attach your smsts.log so we can see what's failing and why

when you say 'sideload' are you referring to Windows Store apps, or are you just calling it 'sideloading' and they are normal apps/packages ? sideloading is normally the term provided for installing Windows store apps.

I'm very happy to say that I was once again awarded as an Enterprise Client Management MVP this year, that's 6 years in a row :-) Awesome ! thanks to my family for putting up with me blogging, writing, researching all the time and you (the windows-noob.com members) for reading and telling others about the content here and thank you to Microsoft for awarding me this prestigious title, THANKS !!!!!!!!!!!!! cheers niall !

hi Eddy, what are these applications exactly ? are they actual store apps that your company has created or apps available in the Windows store ?

sure look at this post

awesome result, and yes the SP3 won't be able to boot from that boot image as it's x64 can you do me a favor and video the boot sequence up until your error so i can see where it's failing with that error ?

can you show screenshots of what you are seeing (before/after)

I'm not using copyprofile, however have you checked for the file mentioned in the post to see if it's in the C:\Users\Default\AppData\Local\Microsoft\Windows\Shell location after logging in ?

I'm PXE booting the SP3 no problem here, can you share your smspxe.log and a screenshot of the error you see please

to add to Peter's comment, simply upgrade configmgr to CM12 R2 SP1 or later and you'll be able to deploy drivers to Windows 10 in a supported way, anything prior to that version is not supported (but can work),

I havn't tried it specifically but i'd imagine it should work, try it and let us know

what version of Windows 10 media are you using ? i'll do the taskbar post when I get it working the way I want...

Microsoft have made the scripts free to use (MDT) so why can't the customer use them ? re-inventing the wheel seems counterintuative

assuming you are using capture media to do this search for the smsts.log file and attach it here, why are you not building the image using MDT or ConfigMgr build and capture process ?

hmm looks ok, and this is the file that you verified was copied into C:\Windows\Temp before the next bit (importing it...), i.e. did you verify the file is present in C:\Windows\Temp and it's the one above ?