Search the Community

Hello. We currently have an OSD Task Sequence for deploying Windows 10 Enterprise 1709 to our client machines. This works quite well for existing PCs which are known to AD and SCCM. We have a mixed environment, where we have multiple departments which require their own set of applications. Again, this works well for existing machines. The issue in which I'm being faced with at the moment, is when we introduce new clients to the environment. Due to the design of SCCM with AD System Discovery, new devices are not discovered as there is no DNS entry for those devices. I have done the following - Pre-staged computer accounts on Active Directory. Created computer objects within SCCM with the Name and MAC address of the new devices. Added new objects to the OSD Device Collection for OSD. The problem here is that some Device Collections which have Collection Variables attached, rely on Active Directory OU membership rules. As these machines haven't yet been discovered as such, they don't become members of these collections until the OSD process has finished the installation of the ConfigMgr Client has completed. Once that has completed, the machines then fall into the correct collections, but the Install Applications step within the Task Sequence doesn't complete as the collection variables haven't yet been evaluated. I was wondering if anybody else here has experienced this and maybe have a solution/work around? Would there be any Powershell scripts which could be used to force a re-evaluation on collection variables prior to the Install Applications step? Cheers, Richard

Morning all, I’ve been looking at an issue for the last couple of days that has me somewhat confused. I know there have been other posts regarding this but I’ve not yet seen a definitive reason behind it… We have a small number of systems in the environment that have two physical drives for example a 75GB and a 300GB drive, meaning the preferred setup would be: Disk 0 (75GB) 200 MB: System reserved 50GB: OSDisk 24GB: Data Partition Disk 1 (300GB) 300GB: Extra Can someone please explain why in Win PE these disk randomly swap between Disk 0 and Disk 1?? I need to ensure that in a system refresh scenario these desktops only ever have W7 Enterprise installed to Disk 0 (in the example above) thus leaving Disk 1 alone. We are using the OSPart task sequence variable at the apply OS Phase so I am going to try to use the following script that I believe Niall had a hand in creating in order to target the current partition that has Windows installed: <job id="GetDriveletter"> <script language="VBScript" src="..\ZTIUtility.vbs"/> <script language="VBScript"> dim driveSearch Set objFSO = CreateObject("Scripting.FileSystemObject") Set colDrives = objFSO.Drives For Each objDrive in colDrives driveSearch = objDrive.DriveLetter & ":\\Windows\\explorer.exe" strComputer = "." Set objWMIService = GetObject("winmgmts:" _ & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") Set colFiles = _ objWMIService.ExecQuery("Select * From CIM_DataFile Where Name = '" & driveSearch & "'") If colFiles.Count < 1 Then Else oEnvironment.Item("OSPART") = objDrive.DriveLetter & ":" End If Next </script> </job> I would still very much like some insight as to why the Disk numbers change at what seems to be random intervals….is it a hardware issue i.e. symptom of using SATA drives, or that OSD prefers the larger drive.... Thanks. Rich.

Guys Been building Windows 10 1709 for about a year all fine... We are starting to build 1809 and all works except the TS/Naming now seems to ignore the Collection Variable 'OSDComputerName' I have both 1709 and 1809 images, both building from the same 'All Unknown Computers' collection, the 1709 works the 1809 does not. the 1809 uses a copy of the TS from 1709 with just the WIM changed. Any ideas? thanks

Hi all, I was trying to deploy a Task sequence, which I Copied from standard T.S. and made little change and trying to test it before using. This T.S. is to make BIOS system to UEFI system in boot (Dell system) and then install OS. But when I try to implement this its throwing an error code "0x80004005". I am pasting my SMSTS log file. Please help me. Log: please see the attachment.

Hi I have a couple of questions regarding using language packs in a reference image in MDT. We want to deploy Swedish OS to all our users and I was advised to do this using English OS media with corresponding language pack (Windows 10 1803) instead of using localized media. It appears to have installed the language pack correctly in the reference image but the display language of the OS before the capture is in English (I have a suspend action in the task sequence). My question is what is the best way to set the display language automatically to Swedish once the LP is installed by the task sequence? Some other concerns regarding patching and updating the client once it has been deployed: We will be deploying the REF-image using OSD in SCCM 1802 and use SUP/ADR rules to patch the clients, I assume the patches we download for Windows 10 will need to be in English since the base OS is English? Are there any other considerations we need to make? What are the implications of using SCCM/Servicing for Windows 10 when updating a client with a LP, say 1709 to 1803? I know that the version of the language pack must match the release version of Windows but is there anything else? I would really appreciate if someone has some experience of this and could give me some feedback. Regards Emile

Hi all, I have an unusual problem in that my employer is purchasing old Supermicro blade servers. They don't support SAS and as such I'm using large SATA drives and I'm pretty sure these are BIOS only as I didn't see anything in BIOS setup that looked like I could enable a UEFI boot mode (they are over 7 years old and cheap.) Currently, I've run down to 3TB and above and my 2016 installations are failing as SCCM is forcing initialization to GPT to use the 3TB capacity. I need these to be MBR and 2TB for Windows to successfully be deployed. The trouble is, I can't locate where the diskpart.exe and diskpartscript.txt are being run during the installation. I'm guessing it's buried in a VBS script in the OSDDiskpart step but I haven't acquired the skills yet to get down to the granular level of tweaking. So far I've tried enabling: Set Diskpart BIOS compatibility in both locations where it's greyed out. Disabling all three Format and Partition Disk (UEFI) and tried flipping the Disk Type drop-down option in each UEFI format step to MBR from GPT, but for some reason that didn't work. but the disk still gets initialized to GPT. If I knew where the initialization step was taking place I could just add a WMI query that ignores Supermicro X8DTT-H or something similar. Another possible solution would be to insert my own Diskpart script that converts it back to MBR right before it's failing. Here's part of my log: And here are the details of what's happening in Stdout: Diskpart.exe STDOUT: Microsoft DiskPart version 10.0.14393.0 Copyright (C) 1999-2013 Microsoft Corporation. On computer: MININT-7SO7UHO Volume ### Ltr Label Fs Type Size Status Info ---------- --- ----------- ----- ---------- ------- --------- -------- Volume 0 C NTFS Partition 2047 GB Healthy Disk 0 is now the selected disk. DiskPart succeeded in cleaning the disk. Disk is uninitialized, initializing it to GPT. DiskPart succeeded in creating the specified partition. DiskPart successfully assigned the drive letter or mount point. The selected disk is not a fixed MBR disk. The ACTIVE command can only be used on fixed MBR disks. Thanks for any help! I'm just finding that the MDT task schedule is a bit blackboxed and I can't seem to find where this lives.

OSD Run Command Line: One Liners Please find attached a set of usefull SCCM OSD Task Sequence "Run Command Line" One-Liners Show Task Sequence Name in SCCM Status Messages: cmd.exe /C "echo %_SMSTSPackageName%" Format Disk 0 for Staging (Remove Bitlocker before downloading first Package) cmd.exe /c "(echo select disk 0&& echo.clean&& echo.list disk&& echo.list volume) > .\diskpart.txt && diskpart.exe /s .\diskpart.txt" Adjust OSDDiskIndex (Max two disks) (Useful if a device has two disk and either one can/should be the C drive. Work in combination with the step "Format and Partition Disk" and overwrites the "Disk Number" value) cmd.exe /V /C "(set /a osdID=1-%OSDDiskIndex% > null&& tsenv.exe "OSDDiskIndex=!osdID!")" Set Drive Offline/Online by variable (see: Bitlocker Pre-Provision multi Disk) cmd.exe /c "(echo select disk %OSDDiskIndex%&& echo.offline disk&& echo.list disk) > .\diskpart.txt && diskpart.exe /s .\diskpart.txt" cmd.exe /c "(echo select disk %OSDDiskIndex%&& echo.online disk&& echo.list disk) > .\diskpart.txt && diskpart.exe /s .\diskpart.txt" Fix Drive Letter of mounted devices (Best used in combination with conditions) cmd.exe /V /C "FOR /F %V IN ('mountvol.exe D: /L') DO (mountvol.exe D: /D & mountvol.exe F: %V)" (Checks if devices has one disk and device with drive letter D is an USB Drive --> Map USB from D to F Drive Letter) (Checks if devices has one disk and device with drive letter D is an CDRomDrive --> Map CDRom from D to E Drive Letter) Forcefully halt the task sequence (The file does not exist and therefor generates an error, best/only to use with conditions) Enables Task Sequence Powershell special return codes StopTaskSequenceWithError.exe The step before is a "Run PowerShell Script" step and may return "SomeRandomPs1ReturnCode". But the step does not support defining return codes. To overcome this issue change the powershell script or set "Continue on Error" and create this step afterwards. If you like this collection and have some other useful commands by your own please share them in a "reply to this Topic"

Background (Using SCCM CBB 1802, MDT & Deployment share on a physical computer, and the image is Windows 10 LTSB 1607) Two part question: I am capturing my Windows 10 image using MDT. The MDT TS installs Windows, then checks and installs windows updates, next it installs office 2016 - run windows updates again - sysprep and capture. - Entire TS runs without a hitch. Then that image is imported into SCCM, then being deployed to new computers. Once completed with OSD (which shows no errors), I receive the following issue when attempting to check for updates: Windows Update failed to check for updates with error 0x8024500C. Error 5/8/2018 2:06:54 PM WindowsUpdateClient 25 Windows Update Agent What could be causing this? Is it a result of running the WIndows update steps during my MDT process? Thanks

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

We have trouble using PXE in our environment. Our setup: SCCM 2016 management point in remote datacentre (running on Windows Server 2016) SCCM 2016 distribution point + OSD in local serverroom (running on Windows Server 2016). On this server, 2 network cards are configured. One is connected to the domain, the other is connected to a seperate 'installation LAN'. We also configured DHCP on this server with a binding only to the 'installation LAN NIC'. We also configured DHCP options 60, 66 and 67. On this local server, we installed Hyper-V to run a virtual machine which we can use to create a clean Build and Capture using OSD. However, we cannot boot this virtual machine into PXE. It doesn't seem to get an IP address from DHCP. If we boot up a laptop to the installation LAN, then there is no issue booting up in to WinPE. We've tried several things: Change WDS settings; (set PXE response to respond to all computers / Configured DHCP options / Authorized server in to DHCP / let DHCP give out the multicast address) Changed DHCP options (removed option 60 (PXEClient) / Configured DHCP option to also use BOOTP) Configured different virtual switches in Hyper-V (Internal / external / private), configured RRAS to create a shared NIC, disabled DCHP guard, disabled 'Protected Network' Added computer manually in to SCCM using MAC address. We are running out of options. If I boot up a VM on the laptop using Hyper-V, I don't have any issues. However, we would like to use Hyper-V on the server itself to create images because it is a central and permanent solution. Any suggestions? Many thanks in advance.

Hello, We are planning a Win10 migration in the next few months, we have about 1300 endpoints. The management team wants to split the migration on 2 weenkends. Here is our SCCM infrastructure Architecure : 1 Site server \MP 7 DPs with SMP role (one for each location on different timezones) 1 SUP server. My question is, would you think that we should scale up our architecture? what changes you may want to make to adjust to the migration? Thanks,

Dear Experts, I Would like to get some inputs from you Please. My Data Center is located in 2 Regions. This data center is supplying the services (Windows Server, Network., etc) At Present we are planning to perform SCCM CB Implementation with High Availability for SCCM Client Roles. In fact not for SQL (Due to Commercial items) Single Standalone Primary Site is fair enough for the environment. However, We would like to reduce the usage of SQL Server, and make the Client facing roles with HA. Hence your inputs would be helpful for us Data Center Region A: Server 1 - SCCM Site Server - A Primary Site with Roles (Component Server, Site Server, Site System, Reporting Service Point, Other Non Client Facing Roles) Server 2 - SCCM Site System - Client Facing Roles (Management Point, Software Update Point/WSUS, Distribution Point (With WDS/PXE OSD Capabilties) Data Center Region B: Server 3 - SCCM Site System - Client Facing Roles (Management Point, Software Update Point/WSUS, Distribution Point (WithOut WDS/PXE OSD Capabilties) So all Client facing role, will be working with HA Option. However, PXE Boot for OSD will work only with SERVER 2 from WDS (Which respond to the Client during the OS Imaging) - To make this happen I need to mention the IP Details of WDS Server (Server 2 from Region A) in the DHCP Scope. Am I correct? The reason, I do not preferred to give the SERVER 3 (From Region B)as WDS Role with PXE, which we do not need to give the multiple entries with DHCP Scope (Option 66, 67) for OSD Please suggest, if this is looks good for an organization. The Ultimate goal is to reduce the SQL CPU Utilization.

Is it safe to import drivers for a newly acquired model while an osd task sequence might be running? I say might be running because our company is a global one and imaging of machines can be going on without my knowledge. Should I wait for our change management window to import new drivers for use in the OSD or is it safe to do so during business hours?

I have created a Windows 10 MDT task sequence in SCCM and am using the ztisetbackground.wsf script STEP_01 STEP_-2 etc My problem is that once Configuration Manager is loaded and the system reboots the screen goes black and stays on the "Setup is preparing your computer for first use." Is there a way to hide this screen during OSD so that my ztisetbackground.wsf script steps appear?

Dear Experts, My Sincere thanks for your extended support and great mentorship with System Center Products I am trying to Perform the Build and Capture and Unable to do getting an error Very Shortly - We are planning to upgrade the Environment from SCCM 2012 SP2 to SCCM CB 1702 (Upgrade) and also Windows 7 SP1 to Windows 10 V1702 To perform the Windows 10 Deployment, trying to perform the Capture Image Wizard with limited sequence, but getting an error while installing SCCM Agent. Please do the needful. Console :SCCM 2012 SP2 Target OS : Windows 10 V1607 LTSB Earlier, tried with Windows 10 V1511, which also failed to install SCCM Agent and do not find the Site Code. Any advice pls. SMSTSLog.txt

Encountering the following error message after a successful PXE boot using UEFI enabled ESXi and a Virtual Machine. I am not sure where to look to find the answer to resolving this. It never loads into my boot image. Any help is appreciated.

I'm seeing some weird behaviour when building a new Dell Latitude 7490. Boot List Option is set to UEFI and I've tried this with SATA Operation mode in both AHCI and RAID On. I PXE boot the laptop and start my OSD TS which sets some more BIOS settings (disable UEFI Network Stack, disable Legacy Option ROMs and enable Secure Boot). It then formats the disk with GPT partitions (700MB FAT32 Primary with TSUEFIDrive variable and 100% of remaining space NTFS Primary) and reboots. The laptop goes through POST, displaying the Dell splash screen and then just powers off as if there are no boot options available. If I start the laptop again, it'll keep doing the same thing until I either press F12 and select the HDD (and M.2 SATA SSD) to boot from or simply just enter and exit the BIOS. If I do either of those, WinPE loads and the TS continues as normal. I've tried various workarounds including setting "cctk.exe bootorder --bootlisttype=uefi --sequence=hdd --enabledevice=hdd" and different combinations of BIOS settings but I can't get past this problem. When the laptop was first built, the BIOS was upgraded from 1.1.6 to 1.2.6 as part of the task sequence (I don't remember if I encountered the above problem that first time) but I'm not able to downgrade to any of the previous versions. *EDIT - Forgot to mention that 1.2.6 is no longer available on Dell's website with no mention of why.* Any ideas? Could this be a bug with the BIOS firmware? Thanks in advance!

Hello, Is there a way to deploy Skype for Business Basic (O365 Click-to-Run) during an Operating System Deployment task sequence? I'm able to deploy O365 Pro Plus with OSD. But if I include Skype in the configuration xml file, the application will not install. I broke Skype out into its own package with its own configuration xml and it still won't install during OSD. Can anyone provide some pointers on how to get this done, please?

Hi guys, After developing my OSD process for my work and creating all my WIMs, the IT manager decided that it would be better for us to install the SCCM client and cache into a secondary partition in a hidden folder. Reason for this is we use DeepFreeze and the cache/config is getting wiped at thaw time and is causing problems with Windows Updates. I understand why, but it's creating quite a difficulty to implement. After a few hours of investigation I thought I had a solution. In the "Format and Partition Disk" step of the TS I have a 60GB Primary partition (SCCM Partition) created with no drive letter assigned, then the remaining disk space used for OSDisk. I did this because it was assigning C to the SCCM partition and wanted to install the OS to it. I thought if I used a diskpart command utilizing a txt file to assign M (the letter we settled on) to partition 1 of disk 0 (which is what diskpart told me it was) before the "Setup Windows and Configuration Manager" step, there would be an M drive for SCCM to install to, as per the installation properties I set, namely: smscachesize=40960 smscachedir="M:\SCCM\cache" ccminstalldir="M:\SCCM\client" I am getting no failures in the TS, and in fact nothing in the log files shows any failure except the normal ones you'll see regularly. The diskpart step is completing properly according to the smsts.log file. However, for some reason once the system finishes imaging there is no M drive, SCCM isn't installed and as a result none of the UDI-chosen software is installed either. There is no CCM folder anywhere to be found. The partition is visible in Disk Management, but has no drive letter assigned and if I assign it M there is no data in it. I'm really surprised that the step to install the client finishes without error and clearly didn't work. Thing is, I can't get a log file after that point to check because, once again, the SCCM files are nowhere to be found. I know I could do this by completely redoing the WIM I based everything off of, but that would take several days of work, and I'm about to leave on vacation for a week. Below are screencaps of the steps in question and a copy of the simply diskpart.txt file I'm using. Help please! diskpart.txt

We are having a very difficult time locating any posts, forum topics, or ms bulletins in regards to the attached distmgr.log file. If anybody of you knowledgeable helpful users on the forum can assist in ANY way, please feel free to offer any suggestions. We currently are unable to distribute any new data, sync dp's, etc... We have performed a site reset. We have removed MP role. We have removed and replaced the mentioned file. Kind of at a loss. Short of rebuilding the main site server, I'm not too sure as to our next step. Any assistance would be greatly appreciated. Thank you in advance for your time and assistance. distmgr.log mpcontrol.log

Hello, Hope you can help me here, I have a customer running 1702 CB and in applications fail to install due to the following errors Here's a snippet of the smsts.log: <![LOG[Passed in version 2 for ScopeId_0F54416B-2F58-42FE-81D2-D6016500A009/RequiredApplication_068aceb6-300e-46e7-91e7-9a34f4257f85]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="DCMAgent" context="" type="1" thread="3596" file="cisdkclass.cpp:2408"> <![LOG[spCIStateStore->GetCIState( pszAppPolicyId, csPolicyRevision, (sUserSID.length()>0) ? sUserSID.c_str() : 0, &spPolicyState, 1), HRESULT=87d00215 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2432)]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="DCMAgent" context="" type="0" thread="3596" file="cisdkclass.cpp:2432"> <![LOG[CAppMgmtSDK::GetEvaluationState - ScopeId_0F54416B-2F58-42FE-81D2-D6016500A009/RequiredApplication_068aceb6-300e-46e7-91e7-9a34f4257f85.2 Not found in CI state store. Marking CIs state as EvaluationFailed]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="DCMAgent" context="" type="1" thread="3596" file="cisdkclass.cpp:2438"> <![LOG[NotifyProgress received: 16 (Application failed to evaluate )]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="3596" file="installapplication.cpp:662"> <![LOG[GetAppMgmtSDKInterface successful]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="3596" file="installapplication.cpp:165"> <![LOG[CAppMgmtSDK::GetEvaluationState ScopeId_0F54416B-2F58-42FE-81D2-D6016500A009/RequiredApplication_068aceb6-300e-46e7-91e7-9a34f4257f85]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="DCMAgent" context="" type="1" thread="3596" file="cisdkclass.cpp:2390"> <![LOG[Passed in version 2 for ScopeId_0F54416B-2F58-42FE-81D2-D6016500A009/RequiredApplication_068aceb6-300e-46e7-91e7-9a34f4257f85]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="DCMAgent" context="" type="1" thread="3596" file="cisdkclass.cpp:2408"> <![LOG[spCIStateStore->GetCIState( pszAppPolicyId, csPolicyRevision, (sUserSID.length()>0) ? sUserSID.c_str() : 0, &spPolicyState, 1), HRESULT=87d00215 (e:\nts_sccm_release\sms\dcm\sdk\cisdkclass.cpp,2432)]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="DCMAgent" context="" type="0" thread="3596" file="cisdkclass.cpp:2432"> <![LOG[CAppMgmtSDK::GetEvaluationState - ScopeId_0F54416B-2F58-42FE-81D2-D6016500A009/RequiredApplication_068aceb6-300e-46e7-91e7-9a34f4257f85.2 Not found in CI state store. Marking CIs state as EvaluationFailed]LOG]!><time="08:01:31.216+300" date="11-14-2017" component="DCMAgent" context="" type="1" thread="3596" file="cisdkclass.cpp:2438"> <![LOG[Waiting for job status notification...]LOG]!><time="08:06:31.221+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="installapplication.cpp:1290"> <![LOG[Retrying: 1 attempt]LOG]!><time="08:06:31.221+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="installapplication.cpp:1315"> <![LOG[Waiting for job status notification...]LOG]!><time="08:11:31.227+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="installapplication.cpp:1290"> <![LOG[Retrying: 2 attempt]LOG]!><time="08:11:31.242+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="installapplication.cpp:1315"> <![LOG[Waiting for job status notification...]LOG]!><time="08:16:31.248+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="installapplication.cpp:1290"> <![LOG[Retrying: 3 attempt]LOG]!><time="08:16:31.248+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="installapplication.cpp:1315"> <![LOG[nRetryVal != 0, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1327)]LOG]!><time="08:16:31.248+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="installapplication.cpp:1327"> <![LOG[Exhausted retry attempts. Giving up. ]LOG]!><time="08:16:31.248+300" date="11-14-2017" component="InstallApplication" context="" type="3" thread="2404" file="installapplication.cpp:1327"> <![LOG[WaitforJobCompletion(spAppMgmtSDK, m_guidPolicyEvalJobID, ulPolicyEvalTimeout, nPolicyEvalRetryAttempts), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1090)]LOG]!><time="08:16:31.248+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="installapplication.cpp:1090"> <![LOG[Step 2 out of 7 complete]LOG]!><time="08:16:31.248+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="daprogress.cpp:226"> <![LOG[Install application action failed: 'Adobe_Reader-DC_15.007.20033_002T'. Error Code 0x80004005]LOG]!><time="08:16:31.263+300" date="11-14-2017" component="InstallApplication" context="" type="3" thread="2404" file="installapplication.cpp:914"> <![LOG[Sending error status message]LOG]!><time="08:16:31.263+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="installapplication.cpp:918"> <![LOG[ Setting URL = http://GP-SCCMSQL-P1.CXG.CO.UK, Ports = 80,443, CRL = false]LOG]!><time="08:16:31.263+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="utils.cpp:6614"> <![LOG[ Setting Server Certificates.]LOG]!><time="08:16:31.263+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="utils.cpp:6642"> <![LOG[ Setting Authenticator.]LOG]!><time="08:16:31.263+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="utils.cpp:6649"> <![LOG[Set authenticator in transport]LOG]!><time="08:16:31.263+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="libsmsmessaging.cpp:7980"> <![LOG[ Setting Media Certificate.]LOG]!><time="08:16:31.263+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="utils.cpp:6666"> <![LOG[Sending StatusMessage]LOG]!><time="08:16:31.279+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="libsmsmessaging.cpp:4112"> <![LOG[Setting message signatures.]LOG]!><time="08:16:31.294+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="libsmsmessaging.cpp:1381"> <![LOG[Setting the authenticator.]LOG]!><time="08:16:31.294+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="libsmsmessaging.cpp:1411"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: GP-SCCMSQL-P1.CXG.CO.UK:80 CCM_POST /ccm_system/request]LOG]!><time="08:16:31.294+300" date="11-14-2017" component="InstallApplication" context="" type="1" thread="2404" file="libsmsmessaging.cpp:8856"> <![LOG[Request was successful.]LOG]!><time="08:16:31.310+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="libsmsmessaging.cpp:9191"> <![LOG[Install application action cannot continue. ContinueOnErrorFlag is set to false.]LOG]!><time="08:16:31.310+300" date="11-14-2017" component="InstallApplication" context="" type="3" thread="2404" file="installapplication.cpp:933"> <![LOG[hrInstallation, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,934)]LOG]!><time="08:16:31.310+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="installapplication.cpp:934"> <![LOG[pInstall->InstallApplications(saAppNames, sContinueOnError), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\main.cpp,282)]LOG]!><time="08:16:31.310+300" date="11-14-2017" component="InstallApplication" context="" type="0" thread="2404" file="main.cpp:282"> <![LOG[Install Static Applications failed, hr=0x80004005]LOG]!><time="08:16:31.310+300" date="11-14-2017" component="InstallApplication" context="" type="3" thread="2404" file="main.cpp:282"> <![LOG[Process completed with exit code 2147500037]LOG]!><time="08:16:31.326+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="commandline.cpp:1124"> <![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="08:16:31.326+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="instruction.cxx:814"> <![LOG[Failed to run the action: Install Application. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="08:16:31.326+300" date="11-14-2017" component="TSManager" context="" type="3" thread="2172" file="instruction.cxx:921"> <![LOG[MP server http://GP-SCCMSQL-P1.CXG.CO.UK. Ports 80,443. CRL=false.]LOG]!><time="08:16:31.326+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="utils.cpp:6321"> <![LOG[Setting authenticator]LOG]!><time="08:16:31.326+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="utils.cpp:6343"> <![LOG[Set authenticator in transport]LOG]!><time="08:16:31.326+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="libsmsmessaging.cpp:7980"> <![LOG[Sending StatusMessage]LOG]!><time="08:16:31.357+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="libsmsmessaging.cpp:4112"> <![LOG[Setting message signatures.]LOG]!><time="08:16:31.357+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="libsmsmessaging.cpp:1381"> <![LOG[Setting the authenticator.]LOG]!><time="08:16:31.357+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="libsmsmessaging.cpp:1411"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: GP-SCCMSQL-P1.CXG.CO.UK:80 CCM_POST /ccm_system/request]LOG]!><time="08:16:31.357+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="libsmsmessaging.cpp:8856"> <![LOG[Request was successful.]LOG]!><time="08:16:31.372+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="libsmsmessaging.cpp:9191"> <![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2147467259]LOG]!><time="08:16:31.372+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="executionenv.cxx:662"> <![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="08:16:31.372+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="executionenv.cxx:662"> <![LOG[Clear local default environment]LOG]!><time="08:16:31.372+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="executionenv.cxx:801"> <![LOG[Let the parent group (Install Applications) decides whether to continue execution]LOG]!><time="08:16:31.388+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="instruction.cxx:1033"> <![LOG[Let the parent group (Setup Operating System) decide whether to continue execution]LOG]!><time="08:16:31.388+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="instruction.cxx:258"> <![LOG[The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed. Operation aborted (Error: 80004004; Source: Windows)]LOG]!><time="08:16:31.388+300" date="11-14-2017" component="TSManager" context="" type="3" thread="2172" file="instruction.cxx:221"> <![LOG[Failed to run the last action: Install Application. Execution of task sequence failed. Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="08:16:31.388+300" date="11-14-2017" component="TSManager" context="" type="3" thread="2172" file="engine.cxx:249"> <![LOG[MP server http://GP-SCCMSQL-P1.CXG.CO.UK. Ports 80,443. CRL=false.]LOG]!><time="08:16:31.388+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="utils.cpp:6321"> <![LOG[Setting authenticator]LOG]!><time="08:16:31.388+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="utils.cpp:6343"> <![LOG[Set authenticator in transport]LOG]!><time="08:16:31.388+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="libsmsmessaging.cpp:7980"> <![LOG[Sending StatusMessage]LOG]!><time="08:16:31.404+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="libsmsmessaging.cpp:4112"> <![LOG[Setting message signatures.]LOG]!><time="08:16:31.404+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="libsmsmessaging.cpp:1381"> <![LOG[Setting the authenticator.]LOG]!><time="08:16:31.404+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="libsmsmessaging.cpp:1411"> <![LOG[CLibSMSMessageWinHttpTransport::Send: URL: GP-SCCMSQL-P1.CXG.CO.UK:80 CCM_POST /ccm_system/request]LOG]!><time="08:16:31.404+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="libsmsmessaging.cpp:8856"> <![LOG[Request was successful.]LOG]!><time="08:16:31.435+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="libsmsmessaging.cpp:9191"> <![LOG[Execution::enExecutionFail != m_eExecutionResult, HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmanager\tsmanager.cpp,1271)]LOG]!><time="08:31:44.024+300" date="11-14-2017" component="TSManager" context="" type="0" thread="2172" file="tsmanager.cpp:1271"> <![LOG[Task Sequence Engine failed! Code: enExecutionFail]LOG]!><time="08:31:44.024+300" date="11-14-2017" component="TSManager" context="" type="3" thread="2172" file="tsmanager.cpp:1271"> <![LOG[****************************************************************************]LOG]!><time="08:31:44.024+300" date="11-14-2017" component="TSManager" context="" type="1" thread="2172" file="tsmanager.cpp:1299"> <![LOG[Task sequence execution failed with error code 80004005]LOG]!><time="08:31:44.024+300" date="11-14-2017" component="TSManager" context="" type="3" thread="2172" file="tsmanager.cpp:1300"> I've attached the entire logs folder, I've tried removing all of the install application steps from the task sequence and re-adding following this article to no avail: http://www.vansurksum.com/configmgr-2012-caveat-with-application-revisions-when-used-in-a-task-sequence/ Appears to be mostly random, but on one particular device it fails every time. Thanks in advance Logs.zip

Hi All, Recently we started experiencing issues with our OSD process creating an "Unknown" computer object with the PC's MAC address as soon as the first "Next" button is clicked at the Welcome to the Task Sequence Wizard screen causing the built to present the "There are not task sequences available for this computer" error. We advertise our task sequences ONLY to the x86/x64 unknown computer objects, so as soon as this object is created in the database the TS availability fails. We are running SCCM 1706 (5.00.8540.1500). Object Properties: Agent Name: "Heartbeat Discovery" Client: NO Client Type: Computer Decommissioned: No MAC Addresses: "A4:4C:C8:0A:C0:2C" Name: Unknown NetBIOS Name: Unknown Resource Type: System Unknown Computer: 1 Attached is the SMSts.log file for review. Any help is greatly appreciated! Matt smsts.log

Hey Guys / Niall - I'm in a bind and need some suggestions, please... I'm currently in the middle of rebuilding our OSD task sequence from scratch to resolve a few issues. It's TS is fairly lengthy as it's MDT integrated and uses the UDI Wizard for customization of the build. One of the most used UDI features is the ability to select Applications & packages not installed by default for automated installation during the build. This has worked great in the past with Applications and Packages. The issue is that many of our applications are installed via task sequence & some are pretty lengthy. They are built as such due to their complexity and ability to support multiple locations (different steps are executed depending on the system's location), scenarios (Install, Repair, Upgrade), etc. It would be easy enough to copy / paste these steps into a folder in the OSD TS and have them tied to a UDI variable - but - when attempting to do so have found that it makes the task sequence too large and I get memory / handle errors when trying to save it. As a workaround, I did adjust specific settings in WMI on the Primary server as described here to the settings shown below (quadrupled values for first 3) plus the server is only using 27% of 16gb of RAM, but that didn't help. So - what is the most reliable way to install a task sequence during OSD (if any) I know that the latest version of SCCM includes this ability, but we are on 2012 R2 SP1 CU4 for the next 2 months. The only way I can think of is to pre-advertise the TS to collections OSD is advertised to then create and Application which executes a PowerShell script that initiates the desired TS similar to this post. I've used it before for the App Catalog, but it hasn't been that consistent and I haven't tried it with OSD yet. Surely, there's another workaround for this or way to safely be able to add more steps to OSD's TS. I'd appreciate any suggestions - Thank You!

SCCM 1706 Is it possible to generate report or query for an deleted task sequence OS Deployment?

Hello, I`m trying to recreate my customsettings.ini file in order to Join and provide a computer name during OSD, i`m wondering if it`s possible to achieve it based on the "constraints" that we have : 1-Diffrent OUs for each type of computer and locations: Desktop and Laptop 2-Diffrent defaultgateway for floor in each location. 3-Diffrent naming convention for each location and diffrent computer type. Thanks,