anyweb

sorry but with the current zero day reported and linked to Adobe products I won't be clicking on the pdf, can you post your screenshots instead here

try re-deploying whatever task sequence it is to a collection, the last task sequence deployed will contain the boot wim that all successive task sequences on that collection will use for first boot (and then they'll stage their respective boot wim)

does this post help you ?

press f8 at the 'empty grey sccm screen' then do cmtrace X:\Windows\Temp\SMSTSLOG\smsts.log and tell us what errors are reported in that log.

does it fail after the boot to WinPE or while still in windows ? if it's while in WinPE then have you verified that it actually has an ip address and can ping the fqdn of the management point in winpe ?

yes i'm aware of the F11 trick, however make a change in your Configuration Manager console on the distribution point properties, does it still work after that ?

if you want to build and capture windows 7 X64 then you need a 64 bit boot wim, for deploying either OS (unless UEFI) you can use an x86 boot wim.

look here http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/

yes of course, do it. How you decide to install the client later is all part of your overall plan.Have you seen the guides here yet ?

are the clients at CU1 level also ?

hi dennis have you seem the CM12 BitLocker Frontend HTA task sequence, it's mainly targetted at bitlocker users but has multi language capability built in as well, im port the task sequence from the zip and take a look at how the task sequence works, maybe it will help you

that is your package source(s) and yes you would definitely need to keep them, any time the package is updated (changed) it will want to read from the data source

windows Store apps (from the store) must be sideloaded. if you are creating your own windows 8 apps then have you seen this post ? http://www.windows-noob.com/forums/index.php?/topic/9430-how-can-i-create-windows-81-applications-and-then-deploy-them-with-system-center-2012-r2-configuration-manager/

why are you running the hta using serviceui, I normally 'call' the hta via the task sequence

have you looked at your application pool settings for the webservice ?

just install teamviewer and Allow Remote control, then drop me a mail with the username/password needed to access it, and let's agree on a time that works for both of us niall@windows-noob.com

What linux distro is it ? have you seen Johan's post on deploying Linux with MDT, that would be the first place to start.

yeah it does. and it will be logged. you just have to find the log. if you can do teamviewer i can remote in and take a look

apologies for the delay your post got missed in all the others, however now I have and nothing stands out in the logs you provided which probably means you are taking them from the wrong location, sometimes the 'actual' error may be in another smsts.log file to find it try doing this on the root of each drive letter dir /s smsts*.log start on drive letter X: (i'm guessing that's where the failure logs are) post any logs you find here and i'll take another look

Once you enable a PXE enabled distribution point in Configuration Manager, then it is in control of PXE deployments and will deliver any task sequences you have deployed within Configuration Manager, that means any TS's you have deployed via MDT standalone will not be seen as only one PXE server can respond at a time. It is trivial though to use both, just disable/stop the WDS service on the PXE server you want to disable, the other will answer the clients call. to understand MDT integration with Configuration Manager do take a look at the guides below, it should get you started.. CM12 in a lab - Part 16. Integrating MDT 2012 RC1 with Configuration Manager 2012 CM12 in a lab - Part 17. Using MDT 2012 RC1 with Configuration Manager 2012 CM12 in a lab - Part 18. Deploying a UDI Client Task Sequence

yup, I was waiting for this... R2 CU1 fixes this, have any of you upgraded to R2 CU1 yet and tried creating media on those 'fixed disks' devices ?, the fix is listed below:-

can you post your smsts.log file so we can see the failure ?

this should be fixed with the latest definition updates (ending with .64), have you tried it ?

the easiest way to do a refresh scenario is with this task sequence, you don't even have to think as it's done the hard work for you, try it and see ! don't be put off by the bitlocker stuff, you don't have to use it if you don't want to. CM12 in a Lab - The CM12 BitLocker FrontEnd HTA - video CM12 in a Lab - The CM12 BitLocker FrontEnd HTA

if you have local access to the box use a pause command as detailed here http://www.windows-noob.com/forums/index.php?/topic/8846-how-can-i-pause-a-task-sequence-in-system-center-2012-configuration-manager/ if you are not local you can even remote to the machine using VNC by getting a remote user to allow the connection as detailed here http://www.windows-noob.com/forums/index.php?/topic/2781-how-can-i-make-troubleshooting-failed-deployments-easier/