anyweb

But my task sequence fails at the ENABLE BITLOCKER stage towards the end of the TS. with what error ?

<![LOG[Failed to save environment to (80070057)]LOG]!><time="09:33:27.333+240" date="08-24-2015" component="TSManager" context="" type="2" thread="292" file="environmentlib.cpp:697"> if it can't store the files on a suitable drive then it will fail, i don't know how you'll store your files somewhere other than x:, you can't store them in x: and the task sequence wants to store them on a drive formatted as NTFS how you move forward with it i dont know,

Yusuf Mehdi Corporate Vice President, Windows and Devices Group, Microsoft Corp just tweeted a top ten fun facts for Windows 10, and here it is 1. More than 75 million devices running Windows 10 – and growing every day. 1/10 2. Windows 10 is running in 192 countries, virtually every country on the planet. 2/10 3. More than 90,000 unique PC or tablet models have upgraded to Windows 10. 3/10 4. Even some devices manufactured in 2007 have upgraded to Windows 10. 4/10 5. More than 122 years of gameplay have streamed from Xbox One to Windows 10 devices. 5/10 6. 10 million achievements unlocked: Microsoft Solitaire Collection, Minecraft: Windows 10 Edition Beta 6/10 7. In response to “tell me a joke”, Cortana has told over half a million jokes since launch. 7/10 8. Windows Store for Windows 10 has seen 6X more app downloads per device than Windows 8. 8/10 9. Over 2,000 organizations vying to win the global partner slot in #UpgradeYourWorld. 9/10 10. Thank you <some twitter users> and all who helped to #UpgradeYourWorld. Do Great Things. 10/10 cheers ! niall

you are missing nic drivers in winpe as is evident by the lack of network sending with winhttp failed; 80072ee7 TSManager 26-8-2015 10:48:03 2684 (0x0A7C) Will retry in 5 second(s) TSManager 26-8-2015 10:48:03 2684 (0x0A7C) Retrying... TSManager 26-8-2015 10:48:09 2684 (0x0A7C) unknown host (gethostbyname failed) TSManager 26-8-2015 10:48:09 2684 (0x0A7C) sending with winhttp failed; 80072ee7 TSManager 26-8-2015 10:48:09 2684 (0x0A7C) it can't capture to an UNC path with no network (ip) add network drivers for the nic to winpe and try again. if you were using a hyperV vm you wouldn't have to worry about this problem.

are you sure that's correct, the date of the log is 11th of august...

or offline servicing as above

press F8 when capturing (that way it won't reboot) then grab the smsts.log file probably in X:\windows\temp\smstslog\

the 80070057 error means so are you using a command incorrectly, i havn't tried what you are trying to do so i cannot offer advice sorry at what point is yours failing, 1,2,3 ?

ccmsetup.log will be in the c:\windows\ccmsetup\logs did you find it ?

hi guys, some of you may have noticed that we had a few issues with the site a couple of weeks ago, but it was all resolved expertly but our web-server admin who works tirelessly to help keep this site running, I decided it would be nice to let you lot know a bit more about him, so here goes: Hi, tell us a little bit about yourself, where you come from and what you work at... (all optional) My name is Peter Upfold. I'm from the South of England and work in a small IT team in education at the moment. I also do a lot of work with New York-based website design and development agency Van Patten Media, with a particular focus on running their servers and “devops” (buzzword #1). 1. What age did you get into computers ? My family got our first computer when I was five years old, and I was instantly hooked! Later on, I got a computer of my own. I then started playing with Linux when I was 13 years old, and eventually the Mac, when the budget allowed. 2. what was your first computer ? The first computer that was my own was an AMD Athlon XP system with 256 MB of RAM. 3. what os did that computer run ? That first computer of mine was running Windows XP (without any service packs), way back when it was brand new and shiny and exciting! 4. what is your favorite computer today and why ? I still like to run many different operating systems, so I keep a “diverse enough” set of hardware to run all that I like. Right now I have a beautiful 27” iMac with the 5K screen as my primary machine, and I also have a custom built Sandy Bridge-based i5 desktop PC that runs Debian 8 (Jessie) and Windows 10 Pro in a dual boot configuration. 5. How did you get into Linux and what do you like about it ? I first got into Linux after buying a boxed copy of SuSE 9.0 Personal in a bricks-and-mortar store! I was always curious about other operating systems, so finding this was really exciting to me. It was very scary doing the partitioning step to set up a dual boot configuration on that first computer of mine — resizing filesystems was a lot more of a delicate operation back then! 6. Would you consider yourself a programmer ? I do quite a bit of programming, and like to keep myself learning whenever I can. I’ve worked extensively with PHP, but I have also spent quite a lot of time with Visual Basic.NET, C#, bash scripting and I have also worked quite a bit with Python, Objective-C and more languages I am probably forgetting. Most recently I have been really getting into doing a lot more with PowerShell in my day job too — it really is wonderful to have some of the automation power previously only found on Unix-like systems on Windows. 7. What advice would you give to anyone wanting to be a web-server admin ? Spin up some virtual machines and start playing! I think that one of the best ways to learn is to give yourself a project — “I want to be able to set up an Nginx web server” — and then do the research, try things out, make mistakes and then fix them. It’s important obviously not to blindly accept that some random person’s configuration on the internet is The Right Way to do it, so keep an open mind and keep learning once it is working. 8. Have you heard about Azure and would you consider it ? if not, why not ? I haven’t been living under a rock. I played with Azure on the free trial that everyone gets, but frankly probably didn’t do as much with it as I could in that time. I really love that Linux is a first-class citizen along with Windows Server on Microsoft’s cloud platform. We work a lot with cloud-based Virtual Private Servers at Van Patten Media, but the biggest issue for us there would be the cost of Azure VMs being much higher than the providers we use. Azure seems best if you can make use of the services that aren’t just full-fat virtual machines, like their Azure Table Storage, and so on. 9. what do you think of all this talk about 'the cloud' ? Cloud computing makes a lot of sense for a lot of things. At the same time, though, I think there are important issues to consider around control and security. Once something is in the cloud, it is not inherently less secure (in fact it might be more so), but we all need to consider carefully how moving things physically off-premises impacts users’ rights to maintain control over their own computers. I don’t, for example, use cloud backup services for all my data unless there’s another layer of encryption protecting the data that only I control. 10. What do you use for load balancing and database clustering? What how-tos do you recommend using? At the moment, the workloads I have been working with have tended not to need heavy-duty solutions of this type — and if you can get away without clustering, you save a lot of headaches! Projects in the past though over on the Linux side of things have used the Varnish HTTP caching server to load balance between several application servers. We use Varnish extensively at Van Patten Media to cache as much as possible in RAM and avoid needing beefier servers wherever we can. 11. How do you manage the updates and configuration for your servers (Chef, Webmin, Puppet)? Would you consider using the PowerShell DSC that integrates into Chef and Puppet for managing Linux boxes? Why or why not? I’ll pretend you didn’t mention Webmin… I have spent a significant amount of time over the last few years working with Puppet to describe the configuration for our Van Patten Media servers, my personal server, servers at my day job and, most recently, the Windows-Noob server itself. I’ve used it exclusively in standalone mode so far, but looking into a proper Puppet master setup is something perhaps to look at soon. The time investment initially is significant: you have to sit down and describe everything about a whole server’s configuration. Not being able to unilaterally make a quick config change without causing yourself future issues can also be annoying. The payoff is enormous, though. No longer are you worried about losing some obscure configuration file that is super important that you forgot about. In a web server world, as long as you have your Puppet manifest, your database backups and your code repository, you can blast away a whole server and absolutely know you can get back to a perfectly accurate known good configuration very quickly. When we need a new VM, we can be up and running and deploying our code within 15 minutes. I’m now able to spin up a new server with any of the configurations I listed above and everything “just works” — including automated backups to remote sources. In my day job, I have used Puppet for our Linux servers as mentioned, but PowerShell DSC looks very exciting if it allows us to do the same for our Windows workloads as well. Another thing to look at, when there is time! —————— Peter Upfold http://peter.upfold.org.uk/ Well that's it, thanks Peter ! We (me especially) all really appreciate the time and effort you spend on this site in the background keeping things running, especially when things go wrong. windows-noob.com says > THANK YOU !!!!

what does your ccmsetup.log file say ?

how did you configure the Deployment of the updates exactly, be specific...

a lot of people have issues with Build and Capture in ConfigMgr and there are lots of advice as to how to resolve it, some suggestions are below Build it using MDT instead Build it using a task sequence like so https://social.technet.microsoft.com/Forums/en-US/a535e509-fc6a-483c-bf24-7e2aa064e5b7/deploying-100-of-available-software-updates-during-a-task-sequence?forum=configmanagerosd Build it using a wsus script instead of the Install software Updates step Offline Servicing method http://www.windows-noob.com/forums/index.php?/topic/4683-using-sccm-2012-rc-in-a-lab-part-12-updating-an-operating-system-image-using-offline-servicing/ and so on..

did you verify this works ? is the task sequence in question deployed as hidden ? oTaskSequence ("SMSTSPreferredAdvertID") = ucase(oSelection.InnerText) what does the smsts.log reveal ?

Introduction In a previous posts I've shown you how you can deploy Windows 8.1 x64 to the Surface Pro 3 with MDT 2013 or Configuration Manager 2012 R2. In this post I'll show you how to automate the deployment of Windows 10 x64 to a Surface Pro 3 from start to finish on a Server 2012 R2 server by using a PowerShell script. The PowerShell script is to be run on your soon-to-be MDT server and it will create everything for you, all you have to do is supply it with an OS (Windows 10 x64) and optionally some apps, drivers or even the Windows ADK 10. Fear not, if you don't have the Surface Pro 3 drivers or Windows ADK 10 then the script will download them for you. Download the script You can download the script here, then unzip it. Setup MDT 2013 Update 1 for Microsoft Surface Pro 3 - August 2015.zip To use the script simply adjust the many variables within to suit your needs, then when you are ready, run it in PowerShell ISE. The script will automatically download and install Windows ADK 10 and MDT 2013 Update 1. In addition, it will install Windows Deployment Services and after configuring the MDT DeploymentShare it will import the boot image into WDS. The boot image will have both the Surface Pro 3 100mb and gigabit network driver pre-installed. If you want to remove with, simply rem out the line in the script. Speaking of drivers, the script will automatically download the latest drivers for Windows 10 for the Surface Pro 3 and import them into the MDT 2013 Update 1 deployment workbench. Once the script is complete you can go ahead and launch the deployment workbench to review what has happened. Here you can see the drivers imported for the Surface Pro 3. and here are the two selection profiles it creates, one for the Surface Pro 3, the other for WinPEx64 (the boot image). If you open the Deploy Windows 10 x64 - Surface Pro 3 task sequence you can see the inject driver step When you PXE boot (UEFI network boot) the Surface Pro 3, the correct x64 boot image containing NIC drivers for the Surface Pro 3 will be downloaded from WDS you get to enter a computer name (you can modify customsettings.ini to change this behaviour) and select your core apps (Office 365) before the LiteTouch OSD kicks off here you can see that Windows 10 x64 is already installed and now MDT is installing Office 365 Professional and after some time installing that, it's done ! Related Posts CM12 in a Lab - How can I deploy Windows 10 Enterprise x64 with MDT 2013 Update 1 integrated with System Center 2012 R2 SP1 Configuration Manager ? CM12 in a Lab - How can I upgrade to System Center 2012 R2 SP1 with MDT 2013 update 1 integrated ? Johan's list of MDT 2013 Update 1 bugs and workarounds - http://deploymentresearch.com/Research/Post/504/A-Geeks-Guide-for-upgrading-MDT-2013-to-MDT-2013-Update-1 Until next time, adios !

yes just be aware that when you deploy the new MDT 2013 update 1 integrated task sequence that the boot wim attached to it (should be winpe 10) will take over as the LIFO rule applies (last in, first out) when it comes to deployed task sequences to a collection therefore to avoid your production machines staging the wrong boot wim, redeploy your production task sequences to the same colleciton, the difference is they have Winpe 5.x attached to them,

<![LOG[successfully completed the action (Setup Windows and Configuration Manager) with the exit win32 code 0]LOG]!><time="12:02:29.657-600" date="08-24-2015" component="TSManager" context="" type="1" thread="800" file="instruction.cxx:846"> probably means the latest logs are in the C:\_SMSTasksequence\Logs or C:\Windows\CCM\LOGS folder, can you check there to see what log file you have as the one above looks ok from first looks

if you are using UEFI network boot then you must remove the DHCP scope options which you may have put in place for Legacy network boot, instead use iphelpers to direct traffic accordingly.

you can reuse the old ones with the old toolkit packages no problem, however if you want to use the new content, then you have to create new task sequences

In a previous post I showed you how you can upgrade System Center 2012 R2 Configuration Manager to System Center 2012 R2 SP1 Configuration Manager with MDT 2013 Update 1 integrated. If you haven't upgrade ConfigMgr yet then I urge you to do so before starting this post. In this post I'll show you how you can deploy a clean build of Windows 10 Enterprise x64 by using the official media from Microsoft in a MDT integrated task sequence in ConfigMgr. Before we can do that however we need to create a bunch of new MDT content by creating a new MDT 2013 Update 1 task sequence and choosing from the available options to create the new MDT Toolkit and MDT Settings packages. In addition, we will create a new MDT 2013 Udpate 1 boot image (x64). Note: I should point out that there were some bugs in the initial release of MDT 2013 Update 1 which were excellently documented by Johan here. However, Microsoft has released a new version of MDT 2013 update 1 (September 15th 2015) as documented here and it should resolve most of those bugs. Step 1. Get the Windows 10 Enterprise x64 media I used the Windows 10 Enterprise x64 media from MSDN available here which i then mounted in Windows File Explorer. After mounting the ISO, copy the contents to somewhere useful like \\server2012\sources\os\os_media\windows 10 x64 Step 2. Add a Windows 10 x64 image To add the operating system do as follows. In the ConfigMgr console, select Software Library, then Operating Systems then Operating System Images. Right click and choose Add Operating System Image. Point it to the install.wim file in the sources folder of the Windows 10 Enterprise x64 media you added in Step 1. \\server2012r2\sources\os\os_Media\Windows 10 x64\sources\install.wim and fill in some details about the image and continue through the wizard until completion. Step 3. Distribute the Windows 10 image to your dps Right click the newly added image, choose Distribute Content, and continue through that wizard. Step 4. Create MDT Task Sequence In order to create our new packages (MDT Toolkit and MDT Settings) we need to go through the Create new mdt task sequence wizard. To start that, in the ConfigMgr console click on Software Library, Operating Systems, Task Sequences, right click and choose Create MDT Task Sequence. Choose Client Task Sequence from the list of available options For task sequence name, use Deploy Windows 10 x64 For Details, enter the domain join details, then enter any Windows settings, and lastly enter a Local administrator password in case you decide to deploy this task sequence later and it fails before joining the domain. For Capture Settings, select This task sequence will never be used to capture an image For Boot Image select the second option, this will allow you to create one of the two architecture MDT boot images, specify a suitable source such as \\sccm\sources\os\MDT\MDT 2013 Update 1\WinPE 10(x64) which will be created later by this wizard. for the Boot Image General Settings use the following values: Name: MDT 2013 Update 1 boot image (x64) Version: 10.0.10240.16384 Comment: WinPE10 select x64 architecture for Components, leave the selection as is (there is a bug related to this) For the Customization step let's point it to some preconfigured Extrafiles, basically in the extrafiles folder we create a folder called Windows and in that folder place a text file called smsts.ini which has the following contents [Logging] LOGLEVEL=0 LOGMAXSIZE=524288000 LOGMAXHISTORY=3 DEBUGLOGGING=1 CCMDEBUGLOGGING=1 this will enable better logging in WinPE as per this blog post. For the MDT Package step, not you have the ability to create the new MDT 2013 Update 1 MDT Toolkit Package, by selecting the Create a New Microsoft Deployment Toolkit Package option. For the Package source option use something like \\sccm\sources\os\mdt\MDT 2013 Update 1\MDT Toolkit for MDT Details use the following settings: Name: MDT Toolkit Version: 2013 Update 1 Language Manufacturer: Microsoft Comments For OS Image, select Specify an existing OS image and browse to the previously added Windows 10 Enterprise x64 image. For Deployment Method you get to choose the type of task sequence interaction will be used, if you want your users to have choices then select the UDI option, otherwise select the Zero Touch option to remove choices from the task sequence. In this guide we will select Perform a Zero Touch Installation OS Deployment with no user interaction. for Client Package, select Specify an existing ConfigMgr client package and browse to the one you wish to use. for USMT Package select the User State Migration Tool for Windows 10 package which we renamed in this post. For Settings Package, we need to create our new MDT 2013 Update 1 settings package, therefore select the second option. You only have to do this once, and that is when you upgrade to a new version of MDT. Select Create a new settings package and fill in the path to be created as shown below something like \\sccm\sources\os\mdt\MDT 2013 Update 1\MDT Settings for Settings Details use the following settings: Name: MDT Settings Version: 2013 Update 1 Language Manufacturer: Microsoft Comments for Sysprep Package, set No sysprep package to use and continue through to the end of the wizard. off it goes creating the Boot Image and after a while you'll get a process completed successfully message (hopefully). close the wizard. Step 5. Distribute the new MDT Toolkit and MDT Settings packages Open the ConfigMgr console, and press F5 or refresh the view to see the newly created packages. Select both of the MDT packages, right click and choose distribute content, continue through that wizard until completion. Step 6. Edit the boot image settings. Browse to Software Library, Operating Systems, Boot images and select the MDT 2013 Update 1 boot image x64. Right click and choose Properties, and select the Data Source tab. Place a checkmark in Deploy this boot image from a PXE enabled distribution point. Next select the Optional Components tab and select the yellow starburst to add any new Optional Components that you want in the boot wim including Database (WinPE-MDAC) which was not included due to a bug. click Apply and answer no to the Distribute content to dp's now question close the wizard when done. Step 7. Distribute the new MDT 2013 Update 1 boot image Browse to Software Library, Operating Systems, Boot images and select the MDT 2013 Update 1 boot image x64. Right click and choose Distribute Content, continue through that wizard until completion. Step 8. Deploy the task sequence Browse to Software Library, Operating Systems, Task Sequences and select the Deploy Windows 10 x64 task sequence. Right click and choose Deploy and use the following settings For the General screen choose a suitable OSD Deploy collection for Deployment Settings make sure it is set to Available and deployed to Only media and PXE continue through the rest of the wizard until completion Note: Once you've deployed the task sequence, you may have to set the Deployment available date back a day otherwise it won't show up due to a bug. This ConfigMgr bug is set to be fixed in CU2. Step 9. PXE boot a VM to experience the changes Now everything is in place for testing a deployment of Windows 10 using an MDT 2013 Update 1 integrated task sequence in Configuration Manager. Simply PXE boot a computer that is a member of the OSD Deploy collection. While PXE booting, you can verify that the WIM file it's pulling down is indeed your newly created MDT 2013 update 1 boot image by looking at the boot image package id. It should match the Image ID column beside your new boot wim if it doesn't then you are probably booting from a different task sequence or there are problems with the content of the MDT boot image. Once the boot image has loaded you'll see the new Microsoft Deployment Toolkit background, and the new Windows PE 10 PXE password prompt and you see the list of Task Sequences, if your's doesn't show up, verify the deployment scheduling date as mentioned above. select the Deploy Windows 10 x64 and click next and off it goes... running Windows Setup And we are done. In a later post i'll guide you through adding drivers to the task sequence, until next time adios. Recommended reading New version of MDT 2013 Update 1 released to squash bugs in the first release - http://www.niallbrady.com/2015/09/15/new-version-of-mdt-2013-update-1-released-to-squash-bugs-in-the-first-release/ http://blogs.technet.com/b/msdeployment/archive/2015/08/25/mdt-2013-update-1-release-notes-and-known-issues.aspx

well has something else changed in your infrastructure ? is the slowness only on the wim download ? any errors in smsts.log ?

was their a client installed on the computer prior to this ? any smscfg.ini or sms certs present ?

are you trying this on very fast SSD disks ? Johan mentioned a bug about this on his blog > http://www.deploymentresearch.com

good questions ! 1. not sure, but i'll seek clarification from the MS Product group 2. I just updated MDT by running the new msi,. then ran the configmgr integration, where it defaults to wanting to remove the extensions, simply change it to add. however, you'll still have to recreate any MDT task sequences, and create new MDT toolkit and MDT settings, MDT boot images packages, I'm doing up a post on that and will hopefully have it live tonite. cheers niall

is ConfigMgr running on a Virtual Machine on your laptop ? what is the 'crash' error message ?