I have researched 80091007 errors and everything I've read indicates a hash mismatch.  My smsts logs bear no reference to a hash mismatch.  Because my task sequence successfully processes tasks for preparing C:\ I am able to locate smts.log in C:\_SMSTaskSequence\Logs\Smstslog.  I have reviewed the smsts log in X:\ as well and interestingly the file sizes of each are the same between C: and X:.

I have several Dell models and all of them take my image (via the same task sequence) without error, save for the Dell 5290 2in1.  The only variation in the task sequence is the application of driver and bios packages based on a WMI queries for model name.  The task sequence proceeds through all steps prior to the application of the OS.  It downloads my 10GB WIM, it begins 'Applying Operating System' and after about three minutes throws the 0x80091007 error. 

I have tried different network adapters (all USB-C to Ethernet), different switches and cables.  Each time the 5290 2in1 fails while machines next to it running the same OSD task sequence finish without issue.  

I have read some posts which indicate bad RAM can yield a hash error.  The RAM in my problem Dell model is soldered to the board.  On-board diagnostics do not indicate any RAM issues.

I have a shipment of these problem models on the way and no way to image them...

andrew

Kernel DMA Protection is Running..

How can I make it Off.

Kernel DMA Protection is Off..

How can I make turn it ON.

Über Random

I am trying to build a Windows 10 image.   I have a Dell Optiplex 7050 and I downloaded the driver pack for this model and created the driver package within CM2012.   I PXE boot and begin the build.  It runs without error.   But when the build is done I am at the Windows 10 login screen but only Administrator can log in (there is no domain available).  But, the password I entered for Administrator within the Task Sequence does not work.  So I have no way of logging on.   

so I changed the task sequence to "join a workgroup"  Same problem.  Only Administrator can log in and the password I entered in the task sequence for user Administrator does not work.

The name I gave this machine does Not appear anyplace in AD either.   so it must still have the MININT- name.

is there something special  you need to do for Windows 10 work work in a task sequence?   

mqh7

Hi, 

I'm an admin for our SCCM server.  I'm seeing an issue creating Stand-Alone bootable media to use for Win10 imaging.  

Media creation failed with error message: 'The system cannot find the path specified.'Refer to CreateTsMedia.log file to find more details.

When I go look at the CreateTSMedia.log file located here Program Files\Microsoft Configuration Manager\AdminConsole\AdminUILog, the log file shows it hasn't been modified in years.  I tried renaming the log file to see if it would create a new one and it does not.  I can create bootable media just fine but not the stand-alone version with the image and TS dependencies all pre-loaded.  The process gets as far as formatting the USB, labeling it CMBOOT and dropping an SMS folder, autorun.inf, launchmedia.cmd and volumeid.xml file on the USB but that's where it stops.  I cannot troubleshoot any further without the CreateTSMedia log file that it references.  I've tried various models and sizes of thumb drives.

Any thoughts?

SCCM 2012 - build 1610

Thanks,

Ryan

Ryan Plieth

Guys,

Looking for a query (not report) that will prompt for a value when I run it.  Currently using a query such as the one below which finds adobe in add/remove programs.  I want something where it will prompt for the value to find in the add/remove programs.

Any ideas ?

select SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName, SMS_R_System.NetbiosName, SMS_G_System_ADD_REMOVE_PROGRAMS.Version, SMS_R_System.LastLogonUserName, SMS_R_System.IPAddresses from  SMS_R_System inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like "%Adobe%"

Hello,

I'm in need of some technical advice. I just received 15 Hp Probooks 650 G4's that will not reimage using the sccm. I can get the devices to pxe boot, and get the Microsoft Deployment Screen, then I get an error code that reads the following: "Task Sequence: Windows 10 Base Image- 64 Bit has failed with the error code (0x800700A1). For more information, contact your system administrator or helpdesk operator. The computer will automatically restart in 00:14:58. I have talked to HP, their tech suggested running the diskpart, and then trying to image. That didn't work, so they suggested going into the bios and reformatting the hard drive, and then try the reimage. That didn't work either. Any suggestions you have would be greatly appreciated, I know it's only 15 devices, but if the teachers should need their machine re-imaged in the future, I'm unable to do that quickly. The hard drive that came installed in the machine is as follows: Type -NVMe, Model - SK hynix BC501 HFM256GDJTNG-8310A, Firmware version-80002C00, Capacity - 238GB, SMART - enabled, Sector Type - 512, SSD Wear Percentage- 0. Any suggestions or help you can give me on this issue would be awesome. 

Thank you, in advance

Trying a new deployment from a new SCCM server and have been getting Windows setup failed code 31. I have captured all the logs and can post them if needed.

In the SMSTSLog I have a few warnings about drivers and a couple other warnings

Unsuccessful in finding a suitable device driver for device 'High Definition Audio Controller'.OSDDriverClient9/6/2016 3:53:41 PM1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'High Definition Audio Controller'.OSDDriverClient9/6/2016 3:53:41 PM1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'USB Mass Storage Device'.OSDDriverClient9/6/2016 3:53:41 PM1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'Microsoft System Management BIOS Driver'.OSDDriverClient9/6/2016 3:53:42 PM1804 (0x070C)
Unsuccessful in finding a suitable device driver for device 'Plug and Play Software Device Enumerator'.OSDDriverClient9/6/2016 3:53:45 PM1804 (0x070C)

And These Errors

Windows setup failed, code 31OSDSetupWindows9/6/2016 3:53:55 PM1368 (0x0558)
Failed to run the action: Setup Windows and ConfigMgr. 
Unspecified error (Error: 80004005; Source: Windows)TSManager9/6/2016 3:53:55 PM1472 (0x05C0)
The group (Execute Task Sequence) ignored action failure and continue execution on the next step following the group.TSManager9/6/2016 3:53:55 PM1472 (0x05C0)
Start executing an instruction. Instruction name: Gather Logs and StateStore on Failure. Instruction pointer: 132TSManager9/6/2016 3:53:55 PM1472 (0x05C0)
Set a global environment variable _SMSTSCurrentActionName=Gather Logs and StateStore on FailureTSManager9/6/2016 3:53:55 PM1472 (0x05C0)
The condition for the group (Gather Logs and StateStore on Failure) is evaluated to be trueTSManager9/6/2016 3:53:55 PM1472 (0x05C0)
The group (Gather Logs and StateStore on Failure) has been successfully startedTSManager9/6/2016 3:53:55 PM1472 (0x05C0)
ZTI deployment failed, Return Code = -2147467259  0x80004005InstallSoftware9/6/2016 3:53:59 PM1480 (0x05C8)
Failed to run the action: Error in the task sequence. 

Unspecified error (Error: 80004005; Source: Windows)TSManager9/6/2016 3:53:59 PM1472 (0x05C0)

Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue executionTSManager9/6/2016 3:53:59 PM1472 (0x05C0)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.
Operation aborted (Error: 80004004; Source: Windows)TSManager9/6/2016 3:53:59 PM1472 (0x05C0)
Failed to run the last action: Error in the task sequence. Execution of task sequence failed.
Unspecified error (Error: 80004005; Source: Windows)TSManager9/6/2016 3:53:59 PM1472 (0x05C0)

We have to build around 60 machines with a bespoke win 10 image for a client who uses them during the summer break. They have their own network on our site (three switches and a DC) that has to be kept physically separate from ours. The current process is to apply the image on our network then manually remove the machines from our domain. We then have to repatch the machines to the other network and manually add the machines back to the other domain at the other side. It's a bit clumsy so I'd like to trim it a bit.

From what I can tell the only reason they join the domain during the OSD is because at the end of the task sequence we use a domain admin account to disable the firewall. If there is a way to do this without using a domain account then that would spare some time. Alternatively if there's a way to remove the machine from the domain once the necessary tasks are complete this would be equally as useful. I suspect this can be done using a script but I'm not someone who has ever written scripts and have picked most of this up as I'm going along so a lot of it is new to me...

Also (and a bit off topic) if there is a way to auto join 60 machines back to the other domain rather than manually visit each computer that would be helpful but I've not even researched that.

Hi All,

I recently took over an SCCM process but was provided with almost no documentation on how everything had been setup.

Currently theres a single task sequence that deploys Windows 7 or windows 10 based on UDI a UDI selection that then decides which .Wim image is used. 

The unfortunate fact is that the Windows 7 build uses a base image for W7 service pack 1 which results in having to do loads of windows updates once it's completed. So I setup a W7 in VMware went about getting it up to date before taking a capture of it. I then took a copy of the existing task sequence and simply slotted my .Wim in place of the previous one. 

Following the task sequence it's able to see and download the Wim but then fails to apply it with the error 0x80070002.

I have checked the below:
Sites network access account is fine
Distribution points I have tried with anonymously access on and off, confirmed HTTP is selected
I have updated all distribution points including MDT custom settings files and MDT toolkit files

Based on the fact the only change I have technically made is the .Wim I think I'm missing something simple but I'm out of ideas on other potential causes of the issue, running the older existing process still works without issue using the same task sequence process. 

I can supply any of the logs if it's beneficial. 

Hi guys,

I've been struggling with this for a while now and I need help from the community.

I'm not able to deploy an image to a virtual machine i've setup for testing.

there should be enough memory for winpe to function.

winpe loads on the machine and the sccm background appears but it restarts after it tries to configure the network connection.

I dont think it's a network drive issue because I can ping the server and i can map a network share.

I dont think it's a storage driver issue because i was able to run diskpart in winpe and format the disk and winpe could see the newly create c: storage.

the error messege in the logs state: PxeGetPxeData failed with 0x80070005

<![LOG[LOGGING: Finalize process ID set to 968]LOG]!><time="02:18:34.753+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="972" file="tslogging.cpp:1864">
<![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="02:18:34.753+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="972" file="bootshell.cpp:1206">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="02:18:34.753+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="972" file="util.cpp:972">
<![LOG[Debug shell is enabled]LOG]!><time="02:18:34.753+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="972" file="bootshell.cpp:1217">
<![LOG[Waiting for PNP initialization...]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:69">
<![LOG[RAM Disk Boot Path: NET(0)\SMSIMAGES\C0100013\BOOT.C0100013.WIM]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="configpath.cpp:322">
<![LOG[Booted from network (PXE)]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="configpath.cpp:337">
<![LOG[Network(PXE) path: X:\sms\data\]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="configpath.cpp:339">
<![LOG[Found config path X:\sms\data\]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:656">
<![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:721">
<![LOG[X:\sms\data\WinPE does not exist.]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:738">
<![LOG[X:\_SmsTsWinPE\WinPE does not exist.]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:752">
<![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="02:18:34.800+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:1011">
<![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="02:18:35.878+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="972" file="bootshell.cpp:1011">
<![LOG[The command completed successfully.]LOG]!><time="02:18:35.878+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="972" file="bootshell.cpp:1093">
<![LOG[Successfully launched command shell.]LOG]!><time="02:18:35.878+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="972" file="bootshell.cpp:444">
<![LOG[The command completed successfully.]LOG]!><time="02:18:40.237+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:1093">
<![LOG[Setting offline Windows drive and OS root directory to TS envirtonment.]LOG]!><time="02:18:40.237+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:806">
<![LOG[  Processing volume C:\ ]LOG]!><time="02:18:40.237+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:549">
<![LOG[pOs != NULL, HRESULT=80070490 (e:\nts_sccm_release\sms\framework\osdcore\offlineos.cpp,89)]LOG]!><time="02:18:40.456+480" date="05-21-2018" component="TSBootShell" context="" type="0" thread="1008" file="offlineos.cpp:89">
<![LOG[Unable to find a Windows system root at C:\]LOG]!><time="02:18:40.456+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="offlineos.cpp:89">
<![LOG[  Processing volume D:\ ]LOG]!><time="02:18:40.456+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:549">
<![LOG[  Volume D:\ is not a local hard drive.]LOG]!><time="02:18:40.456+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:552">
<![LOG[  Processing volume X:\ ]LOG]!><time="02:18:40.456+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:549">
<![LOG[  Volume X:\ is not a local hard drive.]LOG]!><time="02:18:40.456+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:552">
<![LOG[_OSDDetectedWinDrive='', _OSDDetectedWinDir='']LOG]!><time="02:18:40.456+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:603">
<![LOG[Starting DNS client service.]LOG]!><time="02:18:40.456+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:817">
<![LOG[Executing command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="02:18:40.972+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:1011">
<![LOG[The command completed successfully.]LOG]!><time="02:18:40.972+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:1093">
<![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="02:18:41.050+480" date="05-21-2018" component="TSMBootstrap" context="" type="1" thread="1328" file="tsmbootstrap.cpp:1197">
<![LOG[Command line: X:\sms\bin\x64\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="02:18:41.050+480" date="05-21-2018" component="TSMBootstrap" context="" type="0" thread="1328" file="tsmbootstrap.cpp:1198">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL']LOG]!><time="02:18:41.050+480" date="05-21-2018" component="TSMBootstrap" context="" type="1" thread="1328" file="util.cpp:972">
<![LOG[Succeeded loading resource DLL 'X:\sms\bin\x64\TSRESNLC.DLL']LOG]!><time="02:18:41.050+480" date="05-21-2018" component="TSMBootstrap" context="" type="1" thread="1328" file="resourceutils.cpp:169">
<![LOG[Current OS version is 10.0.16299.0]LOG]!><time="02:18:41.128+480" date="05-21-2018" component="TSMBootstrap" context="" type="1" thread="1328" file="util.cpp:3463">
<![LOG[Adding SMS bin folder "X:\sms\bin\x64" to the system environment PATH]LOG]!><time="02:18:41.128+480" date="05-21-2018" component="TSMBootstrap" context="" type="0" thread="1328" file="tsmbootstrap.cpp:995">
<![LOG[PXE Boot with Root = X:\]LOG]!><time="02:18:41.128+480" date="05-21-2018" component="TSMBootstrap" context="" type="1" thread="1328" file="tsmbootstrap.cpp:1094">
<![LOG[Executing from PXE in WinPE]LOG]!><time="02:18:41.128+480" date="05-21-2018" component="TSMBootstrap" context="" type="1" thread="1328" file="tsmbootstrap.cpp:1109">
<![LOG[Loading TsPxe.dll from X:\sms\bin\x64\TsPxe.dll]LOG]!><time="02:18:41.128+480" date="05-21-2018" component="TSMBootstrap" context="" type="0" thread="1328" file="tsmbootstraputil.cpp:1422">
<![LOG[TsPxe.dll loaded]LOG]!><time="02:18:41.128+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="tsmbootstraputil.cpp:1432">
<![LOG[Device has PXE booted]LOG]!><time="02:18:41.128+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="tspxe.cpp:122">
<![LOG[Variable Path: \SMSTemp\2018.05.21.09.33.11.0004.{B2C28EAE-3B51-4461-8ED2-BAC22D3B8378}.boot.var]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="tspxe.cpp:134">
<![LOG[shService.null() == false, HRESULT=80070005 (e:\nts_sccm_release\sms\server\pxe\tspxe\fwopen.cpp,40)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="fwopen.cpp:40">
<![LOG[PxeStartFirewallService(), HRESULT=80070005 (e:\nts_sccm_release\sms\server\pxe\tspxe\fwopen.cpp,92)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="fwopen.cpp:92">
<![LOG[PxeCreateFwTftpRule(sTftpExe.c_str()), HRESULT=80070005 (e:\nts_sccm_release\sms\server\pxe\tspxe\tspxe.cpp,165)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="tspxe.cpp:165">
<![LOG[PxeGetPxeData failed with 0x80070005]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="3" thread="1328" file="tsmbootstraputil.cpp:1517">
<![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80070005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1518)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="tsmbootstraputil.cpp:1518">
<![LOG[TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80070005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2692)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="tsmediawizardcontrol.cpp:2692">
<![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, sTSLaunchMode ), HRESULT=80070005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1110)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="tsmbootstrap.cpp:1110">
<![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80070005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1258)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="tsmbootstrap.cpp:1258">
<![LOG[Exiting with return code 0x80070005]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="1" thread="1328" file="tsmbootstrap.cpp:1270">
<![LOG[hMap != 0, HRESULT=80070002 (e:\cm1702_rtm\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\cm1702_rtm\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\cm1702_rtm\sms\framework\tscore\environmentlib.cpp,561)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSPxe" context="" type="0" thread="1328" file="environmentlib.cpp:561">
<![LOG[Execution complete.]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:844">
<![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="0" thread="1008" file="environmentscope.cpp:493">
<![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="0" thread="1008" file="environmentlib.cpp:335">
<![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,561)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="0" thread="1008" file="environmentlib.cpp:561">
<![LOG[::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,831)]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="0" thread="1008" file="utils.cpp:831">
<![LOG[RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="2" thread="1008" file="utils.cpp:831">
<![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="2" thread="1008" file="utils.cpp:864">
<![LOG[End program: ]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="bootshell.cpp:876">
<![LOG[Finalizing logging from process 968]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="tslogging.cpp:2110">
<![LOG[Finalizing logs to root of first available drive]LOG]!><time="02:18:41.143+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="tslogging.cpp:1952">
<![LOG[Successfully finalized logs to C:\SMSTSLog]LOG]!><time="02:18:41.393+480" date="05-21-2018" component="TSBootShell" context="" type="1" thread="1008" file="tslogging.cpp:2009">
<![LOG[Cleaning up task sequencing logging configuration.]LOG]!><time="02:18:41.393+480" date="05-21-2018" component="TSBootShell" context="" type="0" thread="1008" file="tslogging.cpp:907">
<![LOG[TS::Environment::SharedEnvironment.isInitialized() == true, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\tslogging.cpp,694)]LOG]!><time="02:18:41.409+480" date="05-21-2018" component="TSBootShell" context="" type="0" thread="1008" file="tslogging.cpp:694">
<![LOG[TS environment is not initialized]LOG]!><time="02:18:41.409+480" date="05-21-2018" component="TSBootShell" context="" type="3" thread="1008" file="tslogging.cpp:694">

............................................................................................................................

I checked my Network Access Account and it all seems fine; I added another account for good measure

I checked the PXE settings and they also seem in order

I confirmed that the packages im using are distributed to the DP

I used the default task sequence that sccm supplied.

The windows Kits version is : 10.1.16299.15

SCCM version: 5.00.8498.1000

Build number: 8498

The installation was not upgraded from a previous version.

any help here will be appreciated.

Hi, 

Today i am getting stuck in a issue that my i have few WMI query conditions to detect Machine type (Like Laptop or Desktop) in Apply network settings step in my task sequence. This task sequence is working globally but in one location its not evaluating that conditions to detect machine types and due to which that step is getting skip. 

I have tried to re update the task sequence (means remove and re-add the same step and apply) but still not working at that location. 

Please help is someone aware about this issue. 

Hi all,

I am having this weird issue that even Microsoft Support is having hard time to figure it out. Wondering if anyone come across this before. Here is the issue.

When deploying OS to an Unknown computer right after it PXE booted into Windows PE there will be an "Unknown" device gets registered in the Configuration Manager. From what I know Unknown should only show up when Task Sequence failed. Please correct me if I am wrong.

Checking the SMSTS log before selecting the Task Sequence I found something interesting. For an unknown computer deployment theSupport Unknown Machines: value should be 1 but it's 0but interestingly it still continues on and Using unknown machine GUID: be9cb138-8c4b-482a-9826-d25daf834c91. 

If select the task sequence it runs like there is no issue but just end up with computer registered as Unknown. 

I think Unknown Machine support is broken or something is there any log related to unknown computer support or a way to repair the support? So when OSD on unknown computer the Support Unknown Machines: 1

Thanks,

Henry T

We recently determined that we need to reimage a large number of our workstations. The reimaging task sequence appears to work fine until this appears on the screen at the end of the TS:

If someone is around to click Skip for now within the time limit set for TS execution, the TS completes successfully. If no one is around, the TS times-out and fails.  The machine cannot connect to the Internet because our proxy is configured by user-based group policy. The machine can connect to our internal network.  I am looking for a clue as to why this screen appears and how I can bypass it. I was thinking it is due to activation, but we have a KMS server on the internal network.

TIA

Hey

Quick (and hopefully easy) question - I've imported the Operating System I care about (Windows Server 2012R2) into SCCM and it is listed under the Operating System Images section. It came with all 4 editions of 2012R2 however (Standard, Core, Datacenter, Datacenter Core). I only care about 1 of these in my enterprise.

Is there a way to remove the other 3 Images/Editions so that only 1 remains? 

It would save me a bit of time every month I update the .wim with offline updates. As it stands now it patches all 4 images when only 1 is needed. I'd like to only patch the version I care about.

I see no option to remove the image in particular, just the whole OS image which contains the 4 separate editions.

Hello.

I've created a standalone media with the TS that we usually run for installing Windows 10 v1803 and applications.
Running fine two hardware model perfectly fine using USB, given error on 3rd model machine.
Using network deployment running this TS works perfectly, without returning any errors.

Installing from the USB though, returns errors in the smsts.log on specific model machine.

Failed to run the action: Install Cisco WebEx Desktop App User cancelled installation. (Error: 80070642; Source: Windows)
Install Software failed, hr=0x80070642

I did not cancel the installation/unplug the USB.

Please suggest

Sarfraz B

Having trouble getting this thing to PXE boot to WinPE - 

So this new Dell Laptop has the TB docking station and when I PXE choosing IPV4, it runs through to the download of the .WIM and then dies. 

I bought another usb-c to ethernet to see if that woudl help and no change.

I have made some changes to BIOS - Legacy boot, ACHI on SATA...

Can't figure out the magic ombo. I have read the currenlty published blogs, tech references about DELL's

I am trying to get this system to boot to PXE choose an Image and deploy without adding any DELL drivers to my Boot image. I am willing to try to create media from SCCM to boot from a USB...

Ideas?

I am wanting to deploy Windows 10 Enterprise to a Microsoft Surface Pro Latest Version and wondered where I could locate the SCCM driver package for this deployment. I have located the drivers for Surface Pro 3 and 4 to import as driver packages but cannot locate for the latest Surface.  The only thing I am finding is an MSI.

https://www.microsoft.com/surface/en-us/support/install-update-activate/download-drivers-and-firmware-for-surface?os=windows-10&=undefined

Does anyone know if latest Surface Pro drivers are available for OSD through SCCM?