Jump to content

Search the Community

Showing results for tags 'Task Sequences'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
    • Windows 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Official Forum Supporters
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Windows Server General
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Found 10 results

  1. Hi everyone. I'm hoping someone out there can assist. Sorry for the length post but my aim is to provide as much information as possible to eliminate any of the common gotchas. ConfigMgr is 1702 with latest Hotfix I've spent the better part of two weeks trying to figure out why OSD has all of a suddenly stopped working. It seems to have happened around the same we upgraded our last DC from server 2012 to 2016 (swing migration) and raised the domain fictional level from 2012 to 2016. From the many hours spent doing google kung fu, ConfigMrg should not have any issues working in 2016 etc. DNS, DHCP AD are all reporting healthy with the usual couple of things that we can ignore from the BPA (Best Practices Analyzer). How we do OSD: We exclusively image Unknown Computers and have done so for many years (Since 2012 R2). We do not image our machines using deployments to any other collection. We delete the computer from the SCCM DB when we need to re-image. This works well for us in our environment. :-) All Task Sequences are deployed to the Unknown Computer collection. We are using ADK 1703 (the most recent one with all bug fixes) and boot boot x86 and x64 boot images are distributed and enabled but we only use the x64 boot image. The issue: Machines can successfully PXE Boot into WinPE, all machines no matter make, model, physical or virtual) all get an IP address and we can ping the ConfigMrg server without any issues. Once a computer gets into WinPE the screen goes blank and the computer reboots straight away. Actions taken so far: Common gotchas I have checked: Checked the date and time are correct on the client Made sure to delete any unknown computers or any references to the machines I have been using for testing or imaging in general Thinking that it might possibly be a Boot Image/PXE related issue I followed a couple of very detailed guides online and removed the PXE role from the Distributions Points by: Unticking it from each DP, deleting the files in the Windows Temp folder, deleting the RemoteInstall folder, removing the Boot images from DP's, the usual reboots, checking logs, re-enabling the PXE roll on DP's rebuilding the Boot images, deploying the boot images, enabling the both x86 and x64 boot images, making sure that my Task Sequences were referencing the newly created boot images. I then booted a machine up (in this case a test VM) and pressed F8, I ran cmtrace and opened up X:Windows\Temp\SMSTSLog\smsts.log. Then I found this error message: There are no task sequences available to this computer.. Please ensure you have at least one task sequence advertised to this computer. Unspecified error (Error: 80004005; Source: Windows) TSPxe 12/07/2017 12:28:40 PM 1284 (0x0504) So I thought perhaps my Task Sequence deployments themselves might have some issue on the DP's. I tried redeploying the task sequences and creating a brad new Task Sequence to test and I still got the same error. I checked the boundary groups and Active Directory Sites and Services and everything looks fine. I tried initiating a discovery of everything possible. Here is an example screen capture video of the issue we are experiencing: Looking forward to any comments below!
  2. Hi, I have an issue to install an application during OSD task sequences, no problem when i deploy this app. ++++++ Failed to enforce app. Error 0x87d00213. ++++++ AppEnforce 28/02/2018 19:09:59 5440 (0x1540) In program app, "Allow this application to be installed...." is checked. To illustrate this, here the AppEnforce log after OSD, I deployed right after the application, here the result : For information, this app have dependencies : Microsoft Access Database Engine 2010 and Microsoft Office 2010 Primary Interop Assemblies. These prerequisites was installed with no problem. I don't realy undestand, someone already had the same problem ? Thanks
  3. Hi everyone, I wonder if someone could help me. In my corporate environment, we have collections setup for deployments that our Service Desk use to build machines. The idea is that machines are created or added into that Collection, and the Task Sequence is also deployed to the Collection. We have upgraded to SCCM 1702 in recent times and ntoiced that we cannot always import machines to the collection - we get an error code, like 2152205056. I just looked at: So will test that out tomorrow when I am back in the office. The other issue I am having is; when we have existing machines that are in SCCM and show at Active with a tick etc, we cannot always rebuild them. Sometimes we can just start off the boot media and then either proceed or clean the disk first and then reboot/start the Task Sequence. Other times I get the "There are no task sequences available for this computer" message. What are we doing wrong?
  4. I have run into a problem with my Task Sequences. I am running SCCM version 1511 (Console Version: 5.0.8325.1000). I have been deploying Task Sequences for over a year and have been deploying them to the "All Unknown Computers" collection for bare metal installs for just as long. It had been working fine. However, now whenever it gets into the Task Sequence Wizard on the machine, it fails with: "Failed to run Task Sequence. There are no Task Sequences available for this computer." and then it reboots. It pxe boots just fine. Starts the Task Sequence Wizard fine. The wizard states: "Initiating Windows PE" and "Preparing network connections". Then, "Welcome to the Task Sequence Wizard". I enter the SCCM password and immediately receive: "Failed to run Task Sequence. There are no Task Sequences available for this computer." Then, the computer reboots. I have tried both machines that existed in SCCM and machines that were never in SCCM. It appears to be happening on all computers currently. I don't believe any account accesses have changed. I'm not seeing anything that stands out in the smsts.log file. The only changes I can think of making were attempting to create a new client package to speed up the time deployments take, but it didn't work, so I removed that client package. At the same time I also checked: "copy the content in this package to a package share on distribution points" and later when back and unchecked this. The only other thing I changed was installing the older ADK in order to create Capture Media for Windows 10. If anyone has any ideas on how to fix this, I would appreciate the feedback. Thank you!
  5. Hi, So i have recently upgrade to 1511, i believe since then I'm unable to install Task Sequences via Software Center. When i select a TS, for example the TS used to build the machine Software Center displays Downloading then Installing for about 2 minutes, then installed. During this process there are no smsts logs created, but the TSAgent log does display this error message at the end. So far i have created all new TS's, redistributed the Boot image and OS image, checked all the applications can install without being deployed and updated MDT to 2013 update 1. The task sequences do work when booting from PXE. Any Advice would be appreciated. Thanks, Craig.
  6. Hello, dear colleagues. We are using SCCM 2012 version 5.00.8239.1000. We have CAS+5 Primary Servers. Some time ago i have noticed that i can't edit task sequences on Cas and on one of Primary servers. Everything is ok on other 4 servers. When i am trying to edit Task Sequences a have error below. Please help me to resolve this problem. I can provide any more information about this error. Thanks in advance.
  7. Hi! System Center 2012 R2 SP1, a New Task Sequences don't show with PXE deployment :angry: Task Sequence is deployent to the right Groups. Any suggestions how to troubelshoot this ?
  8. Hi there, i'm in desperate need of help regarding a command line issue I am having. I am trying to run a command line that calls on an .exe in program files and also uses an .xml file to configure an installation of BizTalk 2013R2. Method 1 - Task Sequence command line SCCM Task Sequence Command Line: "C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\configuration.exe" /s "C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\BizTalkDomainExport.xml" Method 2 - Task Sequence batch file SCCM Task Sequence Command Line: "C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\ConfigureBIzTalkCMD.bat" Content of batch file runas /profile /user:domain\administrator /password:##### cmd cd "C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\" Configuration.exe /s BizTalkExportConfiguration.xml Both above command lines work fine when manually run on the server and completes a silent configuration of BizTalk 2013R2 - but once it is run through a task sequence it fails. NOTE: The BizTalk installation creates an SQL DB. I have set the account that runs the SCCM task sequence as a sysadmin in SQL. ERRORS (Both logs attached; cmdSCCM.log and batchSCCM.log) Both command line and batch file start with the same errors (below) but have different errors later in the log files. Error getting system isolation info. Code 8027000C Remediation failed. Code 8027000C Remediation failed with error code 8027000C I have attempted to run the above commands and configuraton files through an SCCM package/application with the same results. It can't be this hard to run a command line through SCCM can it? I have run other command lines before with no issue. I am lost, can anyone help? Thank you in advance. batchSCCM.log cmdSCCM.log
  9. Hi ALL, I have the following: 1.SCCM 2012 server = 1 2. MDT Server = 1 I want to use MDT as a back up if SCCM fails to deploy OSD for reasons like packages in TS are failed or something like that nature. I would like to be able to boot machines using SCCM PXE then be able to choose an MDT TS from the menu. Then using the MDT boot file be able to boot and connect to the MDT server share and run the customsettings.ini file that would then perform the zerotouch MDT deployment. I have a MDT zerotouch deployment thats been tested via MDT ts and MDT PXE and it works well however when I try to run it using SCCM via SCCM PXE and using the same MDT boot.wim thats been uploaded to the SCCM server .... it loads the MDT boot wim then craps out without running my customsettings.ini. I have also tried the mdt\sccm integration however I am having some issues running the mdt customsettings.ini within the SCCM ts. Some assistance with this would be greatly appreciated. If you can include specific instructions and screenshots would als be useful.
  10. I have an SCCM 2012 RTM setup that was previously working fine. Now it will not Deploy any task sequences at all giving me the error 0x8007000e. I have read up on this error and it seems to be that there is not enough disk space. 1 TB is not enough? We all got issues then. I know this isnt the problem. I read on technet that it may be because of the updates being too large. I have disabled the updates. Same problems. This happens with any deployment or capture using TS. Even the ones that have worked fine for ages. The only change I have made is installing MDT and uninstalling it makes no difference at all. Attached SMSTS.log: Please help. Its so frustrating because literally last week there were no problems at all.... smsts.txt
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.