anyweb

you should create your image on virtual hardware, it's much more predictable and can be deployed to any hardware you want, your error is this which is a network related problem, more than likely it drops the ip address or doesnt get one at all after sysprep so if you choose to stay with real hardware are you loading any network drivers before the setup windows and configmgr step ?

or just rd /s the sxs folder after .net installs...

try again and capture the log(s) before the reboot

what does your smsts.log file reveal ?

and http://www.niallbrady.com/2012/11/12/how-can-i-sequence-applications-using-app-v-version-5-for-configuration-manager-2012-sp1/

Another year has passed, and another year Microsoft System Center 2012 Service Manager (SCSM) is still not on the Gartner Magic Quadrant for “IT Service Support Management Tools”. Now granted I am referring to the Magic Quadrant dated for August 2012, as seen here: …and we still do not know what is to come for 2013, but as someone who is vested in the System Center space complimented by the fact that customers constantly ask our team about this positioning, I find it absolutely interesting why Microsoft is left off. Not to establish credibility, but more importantly to frame my acute perception on the other vendors, let me also theme the next few talking points around the fact that I have worked for HP (well Peregrine back in the day), BMC Software (well Remedy back in the day), Altiris, LANDesk, Axios Systems and have extensive experience with FrontRange, CA Technologies and ServiceNow. All of these products in their own right are very good, but in comparison to these competitors – come on – SCSM should absolutely be at least an orange blip somewhere on this radar. With all that said, let’s break down what we are really looking at! Here are some raw themed bullet points from the “Market Definition/Description” for the IT Service Support Management Tools Gartner Report: Tighter integration of functions that correlate with the activities of the broader IT support organization Leverage a business view of IT services, allowing to quickly resolve or escalate issues and problems, improving root cause isolation, and provide higher levels of business user satisfaction Using this business view, manage Incidents, problems, changes, releases and request management Enables tools to provide modules that enable business end users to find knowledge to support/resolve their computer related issues So effectively a basic ticketing system, which aligns you with ITIL best-practice and mixed in with some ITSM common sense qualifies you for this quadrant. Fair enough, have to keep it broad to include most likely the 200+ Service Desk vendors to have a fighting chance at being in this mix. Again, as I have worked for other vendors that are on this Magic Quadrant, let me passionately say all qualify and should be part of this conversation. There is no doubt in my mind that every single vendor deserves their recognition, however there is 1 very large, huge, and most important item left out of this Market Definition/Description: Business Process Automation I mean, at the end of the day what are we trying to do here? What every CIO on the planet should be trying to do is leverage a Service Desk solution to measure their business activity, understand operational cost and in an attempt to save the company a lot of money automate as much as humanly possible. Some key examples include: Password Reset Automate New Hire / Termination Processes Hardware / Software Procurement Processes Server Provisioning Access Requests The list goes on… Again, as I have worked for other vendors some of them on this Quadrant have the capabilities to do these as a platform to complement their Service Desk story. There are however a few on this quadrant that don’t even come close, remotely close, and in their attempts to do so just introduce more hassle to their customers then needed. The reality is Microsoft System Center is the only platform that can automate any tactical IT process, all from its own product eco-system, with the ability to reach out of its product eco-system and interact with other enterprise solutions. This is a very strong story, and really wish this reality was strongly interpreted inside of this Magic Quadrant evaluation. The one other startling reality that flat out should put SCSM somewhere on the Gartner Magic Quadrant is in its few years of existence, SCSM has garnered more customers than some of these other vendors combined! That in itself should shake up the perspective. I will leave you with one last thought, coming back to the “raw themed bullet points” from above: Mr. CIO, what would you rather have: A Service Desk solution that can manage a Service Request, giving your team the ability to know when someone is asking for Software? A Service Desk solution that can manage a Service Request, giving your team the ability to know when someone is asking for Software and with the simple introduction of an automated business process have that piece of software automatically be deployed to the requesting customer based upon a business approval? If I were a CIO with 500 software requests annually, and I could automate 80% – 90% of those requests freeing up my team to do much more business aligned strategic initiatives – then my decision would be made for me. Let’s no longer measure a Service Desk solution by feature function any more, but as a business solution that aligns with the simple reality of saving $$$. The key theme we should walk away with is: System Center Service Manager is not a Service Desk solution, it is a gateway into understanding, measuring and automating your business. Disclaimer: The article is from a windows-noob recommends partner.

have a look at the USMT section here

have you installed Windows ADK prior to running setup ?

is this problem only happening after upgrading to CM12SP1 or is this fresh installs ? have you verified that no antivirus solution is blocking creation of these files/folders ?

try adding just two updates, does it work ?

and now it is

if you followed the guide 100% then you would not have this problem, you most likely installed Configuration Manager as the Local administrator account (Administrator) and then later logged on as SMSadmin. as you can logon as Administrator and start the configuration manager console, you can grant the SMSadmin user (or group of configuration manager admins) the Full Administrator rights, thos rights are listed below

haha, that guy looks like the dude from the office

have you seen this post ? http://www.niallbrady.com/2013/05/17/after-selecting-a-task-sequence-in-configuration-manager-2012-sp1-you-receive-threadtoresolveandexecutetasksequence-failed-code0x8007000e-in-smsts-log/ it's not exactly the same issue but similar, please check it and see if any of the advice contained within helps.

i'd suggest you start using a Pause ability in your task sequences when troubleshooting, i guarantee it will help to make problems easier to solve and to identify the issues.

no, you are not looking in the right place, look at my screenshot, and then yours. hint: assets and compliance.

can you check your client settings, then computer agent, and then install permissions, what is it set to ?

are you sure you are looking in the right part of the console ? have you tried refreshing the view ? i've just rechecked the script on a Configuration Manager 2012 SP1 primary and the collections appeared after I refreshed the console after the script ran.

Introduction Sometimes things don't go as planned, you are deploying an operating system to a computer and the task sequence fails. You can use normal troubleshooting methods such as press F8 and review the smsts.log in CMTrace review a report of the task sequence progress review other OSD related logs review application or package content status or you can take things one step further and add the ability to pause everything in your task sequence (much like debuggers can step through commands on a compiler).The ability to pause a task sequence gives you the power to perform diagnosis during a deployment and also means that you can monitor a step while it's happening (to check how variables are being set/read/or whatever) rather than reviewing the logs after the event (sometimes the logs will roll over and you'll miss the failure altogether). This method uses serviceUI.exe from the Microsoft Deployment Toolkit. You do not need to use MDT or have MDT integrated with Configuration Manager to use this method. Step 1. Prepare a package containing the required files In this guide we'll use ServiceUI.exe from the MDT 2012 Update 1 files package. This file allows us to popup messages and run interactive actions with users while in SYSTEM context. Simply locate the exe (found by default in C:\ProgramFiles\Microsoft Deployment Toolkit\Templates\Distribution\Tools\X86) and copy it into a new folder called Task Sequence Tools. Note: There are two versions of ServiceUI.exe, one is 32 bit (in the X86 folder) and the other is 64 bit (in the X64 folder). The boot image attached to your task sequence will decide which version of ServiceUI.exe you need to use, so if you are using a 32 bit boot image, you must use the X86 version of ServiceUI.exe otherwise you'll get an error when trying to run it. Download pause_ts.vbs.txt and copy it into our Task Sequence Tools folder. Rename the file from pause_ts.vbs.txt to pause_ts.vbs so that our folder looks like this Step 2. Add our package to Configuration Manager In the software library, expand Application Management, Applications, Packages, right click and choose Create Package. fill in some info about the package and set the UNC path of the source of the Task Sequence Tools folder choose Do Not Create a Program and continue through the wizard until completion. Step 3. Distribute our package Locate the package you just created, right click it and choose Distribute Content. click next when the wizard appears add one or more Distribution Points by clicking on Add and selecting Distribution Point and continue that wizard until it is completed. Step 4. Add the Pause Task Sequence step to a task sequence In Operating Systems, browse to Task Sequences and locate a task sequence you want to troubleshoot, and right click on it and choose Edit. in the task sequence editor, locate a section of the task sequence that you want to troubleshoot and click on the drop down menu Add, then select General, and Run Command Line. give the step a suitable name like ##### Pause Task Sequence, the ##### makes the line stand out in a big task sequence which makes it easier to find later (so that you can remove it once you've fixed the problem). Tip: you should place a Pause Task Sequence step directly before and directly after the step (or Group) you want to monitor, and that step should also have the option 'continue on error' selected during troubleshooting. This will mean that the task sequence will pause before and after the section of the task sequence that you are having trouble with, allowing you time to review logs, gather files, determine the issue. and in the command line paste in the following serviceUI.exe -process:TSProgressUI.exe %SYSTEMROOT%\System32\wscript.exe pause_ts.vbs then browse and select our Task Sequence Tools package as in the screenshot below (the screenshot below has two pause steps, this is so that you can check logs before and after the step that is causing you trouble in the task sequence) Step 5. PXE boot a client to test the Pause task sequence step. PXE a virtual machine and select and then start our recently edited task sequence you can either wait until it gets to the pause task sequence step or go away and do some other chores (that's the beauty of this, you can go away and when you come back the task sequence is paused waiting for you to troubleshoot.) When you get back, the task sequence will be paused and you'll see this and that of course means that you can press F8 and do some deep diving (with CMTrace showing smsts.log live) to find out why your step is failing. Once you are ready to continue the task sequence, press ALT/TAB to flick through windows on your virtual machine, click on OK on our pause task sequence step and watch the action live in CMTrace! Summary You can pause a task sequence using a simple script in conjunction with ServiceUI.exe (or by using a script in MDT Files and access that script directly after a Use toolkit Package step). Pausing a task sequence allows you to quickly get real time results and data in a failing task sequence, once you enable this ability in a task sequence you'll never look back ! have fun, cheers niall.

Microsoft have just announced officially the date when Windows 8.1 is coming out and it's October the 18th. so now we know ! if you'd like to start test deploying it then make sure to checkout windows-noob's guide right here. more info > http://blogs.windows.com/windows/b/bloggingwindows/archive/2013/08/14/mark-your-calendars-for-windows-8-1.aspx

well R2 is coming out shortly but I don't think that it will make it into the exams.

post some logs so we can see what is happening.

what do you mean UEFI set to GPT and bios set to MBR ? it's one or the other with deployments, you can't have the bios in legacy mode (mbr) and deploy a UEFI task sequence to it. I'm deploying to SSD's no problem here at all and no need to add any drivers to the boot image (for storage) at what point are you seeing the failure exactly ? have you tried manually diskparting (clean) the hdd before running the ts ?

did you try this method ? it's working 100% here everytime

have you seen this