SMSTS.log

Windows Upgrade Setup progress: 68%

Could not read Windows Setup progress regkey value 'SetupProgress' at 'HKLM\SYSTEM\Setup\MoSetup\Volatile'. Stopping UI progress. (0x800703fa)

Waiting for Windows Upgrade Setup process to return ...

Scanresult.xml

There is no hard blocking on the system, however the upgrade is still failing with the above error for the upgrade Task sequence step, the same h/w model is upgraded successfully already so its not a h/w issue.

we are kind of going nowhere as no error is logged in the panther folder for further troubleshooting.

Only thing which we could see in the TS may be enabling the below option part of the TS but we want more proof or evidence to convince the teams.

Anyhelp would be grateful.

Kamala kannan.c| Please remember to click “Mark as Answer” or Vote as Helpful if its helpful for you. |Disclaimer: This posting is provided with no warranties and confers no rights

Hi was reading a Microsoft article :https://docs.microsoft.com/en-us/sccm/core/clients/manage/collections/use-maintenance-windows

There are some lines which  confused me can any one clarify what does it actually mean ?

By default, computer restarts caused by a deployment aren't allowed outside of a maintenance window, but you can override the default. Maintenance windows affect only the time when the deployment program runs; applications configured to download and run locally can download content outside of the window.

When a client computer is a member of a device collection that has a maintenance window, a deployment program runs only if the maximum allowed run time doesn't exceed the duration configured for the window. If the program fails to run, an alert is generated and the deployment is rerun during the next scheduled maintenance window that has available time.

There are  other question :

1) If there is any maintenance window start of patching , will it not allow any application/package deployment to run at that time ?Why ?

About a year back I developed a UDI with 40 or so applications and dependencies, at this point I decided to shelve it as I didn't think it was really "enterprise" but more like an old NT Resource Kit Utility, built to serve a purpose but just barely and supported "as best they can". In any case, I am back to considering it and though I haven't changed anything in my environment besides Windows 10 version (now on 1607 build) and SCCM version (now on 1702), it no longer works. instead when run, I get a warning on the Discovery part, which is listed in the log as ("33554432" Text="Critical problems were encountered while processing the Application Master List. The appropriate applications may not be selected."). Someone on one page suggested  the XML was corrupt which I wrestled with before finally creating a new one with a SINGLE item, which produced the same error. I then built a Windows 10 Enterprise 1511 from ISO and installed SCCM and tried to run the TS and it failed with the same error. I'm at a loss for the issue, not that many replies came to those that listed this error in other threads, anyone have an idea here or face this issue and successfully remediate?

Jack

Hello, 

I am trying to PXE boot surface pro 4 and for some reason it does not boot. I get the attached message. It tries to PXE over IP v4, then reaches my correct DP that has PXE and WDS, it finds the correct NBP file SMSBoot\x64\wdsnbp.com (this is specified in DHCP option), it appears to be downloading and NBP file is successfully downloaded. Then without prompting to press Enter key for PXE boot, it moves to IPV6.

I have tried below but no luck

• Upgrade firmware to latest
• disable secure boot
• Removed DHCP option - but this time it doesn't even finds my PXE server
• Verified and made sure MAC address of network adapter is not registered with SCCM DB
• Tried docking station and no luck

I can PXE boot a desktop on same network with no issues. 

Any suggestions would be helpful

SCCM Hierarchy - 1 primary and 1 secondary. 

SCCM = 2012 R2 SP1 CU1

Server = Windows server 2012 R2 Datacenter

Thanks. 

We are working on switching from a custom solution to using CM12 for our windows 7 deployments.

We have working OSD task sequences, and are hammering out things like making sure they work on different hardware platforms, as well as using boot media, and from different locations in the field.

However, I am encountering a ton of difficulty consistently reporting on these. Even on my test system sitting on my desk, the reports are inconsistent. When I reloaded the laptop 4 days ago, the data shows up inv_taskexecutionstatus. However, the execution from yesterday (which was successful) is not in that data.

When I run all status messages from a specific system for the past week, there seems to be a gap where the OSD was actually taking place. The first status message from yesterday is halfway through the task sequence:

Program started for deployment "PRD2017D" ("PRD0002F" - "Lotus Sametime Connect 8.5.2 IFR1").

Command line: "C:\_SMSTaskSequence\Packages\PRD0002F\IBM Lotus Sametime Connect 8.5.2 IFR1.EXE" /Q
Working directory: C:\_SMSTaskSequence\Packages\PRD0002F\
User context: NT AUTHORITY\SYSTEM

There is no indication from the status messages that the OSD task sequence was ever kicked off?  

While the OSD task sequence was running yesterday I was able to see progress using 'Status of a specific task sequence deployment for a specific computer' report, but this morning when I run the report I get no results returned.

We are looking to develop run documentation for multiple build centers that will be deploying 50+ systems each day. It seems incredibly unlikely that a bench technician will be able to remember which task sequence was run on each different computer. The drill down reports do not make the jump from failed task sequences (when they show up) to the step by step results that resulted in a failure?

Finally, it seems like the reports are tied to the resourceID/itemkey - which may or may not change as a result of re-deploying the OS to a system.

Please tell me this is simple and I'm missing something obvious - or at least that how it sends messages and when is documented somewhere?

Will

Figured I would post my findings for others who desire wireless imaging.
"Where there's a will, there's an IT guy to find a way."

After months of hunting and searching for solutions and coming up with nothing, I found a means of Task Sequence deployment over wireless and decided to share with the community. Note that I have yet to discover a means of PXE booting over wireless, but Task Sequence deployment on bootable devices is a good start.  

The first step is export the wireless profile of your choice to an XML and save it for later—WPA2 is what we use for this hidden network. I called my exported profile “wifiprofile.xml”—original, I know.

Next you’ll mount the ISO for Windows 10 1607 (or newer) and extract the sources\image.wim and place it in your directory of choice for DISM work—mine is C:\TEMP and all commands referenced below will follow that convention.

I then create C:\TEMP\MOUNT and C:\TEMP\winre folders.

I have compiled information from various other sources across the internet that I wish I could cite, but here are the commands to execute in order to extract the WinRE.wim file (which supports wireless imaging), inject my wireless profile, then create a boot(able) image from that:

"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Mount-Image /ImageFile:C:\TEMP\install.wim /Index:1 /MountDir:C:\temp\mount

copy /y “C:\TEMP\mount\windows\windows\system32\recovery\winre.wim” C:\TEMP\

attrib -s -h C:\temp\winre.wim

Dism /Mount-Image /ImageFile:c:\temp\winre.wim /Index:1 /MountDir:C:\temp\winre

"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Mount-Image /ImageFile:c:\temp\winre.wim /Index:1 /MountDir:C:\temp\winre

attrib -R c:\temp\winre\windows\system32\winpeshl.ini

copy /y C:\temp\MOUNT\windows\system32\dmcmnutils.dll C:\temp\winre\windows\system32\

copy /y C:\temp\MOUNT\windows\system32\mdmpostprocessevaluator.dll c:\temp\winre\windows\system32\

copy /y C:\temp\MOUNT\windows\system32\mdmregistration.dll c:\temp\winre\windows\system32\

"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Unmount-Image /MountDir:C:\temp\MOUNT /discard

Now you can copy your wifiprofile.xml into the C:\temp\winre\windows\ folder which we will commit in the next few steps. You’ll see why we need to inject the wireless profile into the image—specifically in the Windows directory—In order to call on its variable location throughout the deployment. You will also want to take your system image and mount it in like manner to inject the wifiprofile.xml into its Windows directory. 

Commit the changes:    

"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:c:\temp\winre /Cleanup-Image /StartComponentCleanup /ResetBase"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Unmount-Image /MountDir:C:\TEMP\winre /commit"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Export-Image /SourceImageFile:c:\temp\winre.wim /SourceIndex:1 /DestinationImageFile:c:\temp\winpe-wifi.wim

I know it looks sloppy, but it works. You've just created a WiFi-enabled boot image and successfully loaded the WiFi profile into the %windir% folder. When you're all done you'll have a new "winpe-wifi.wim" that you can then load into SCCM.

Add the new boot image to SCCM but before you distribute it, edit the properties. You'll want to add any additional (wireless) drivers to your image here and configure a prestart command—the most important part!

The prestart command I use is: 

cmd /c net start wlansvc & cmd /c netsh wlan add profile filename=%windir%\wifiprofile.xml & cmd /c netsh wlan connect profile=YOURs ssid=YOURs

The result of the above command is starting the WLAN service, importing the WiFi profile (from our variable location) then connecting to the provided WiFi network.

I then perform a "run command line" step of the above commands in the Task Sequence after every reboot which ensures we stay connected during the whole imaging process. NOTE: This is why your wifiprofile.xml MUST be in both you boot.wim and your image.wim in order to be called upon after WinRE has exited.      

Using this process, the PC will cache the WinRE boot image while booted in Windows, reboot at the assigned time and connect to WiFi to run the Task Sequence. For devices that won't boot and need imaging from a cold start, I created an ISO of the Task Sequence Media (with just the boot image) with the unattended flag enabled and the same prestart command. Load that ISO onto a thumb drive and staff at remote campuses can boot to the thumb drive and the Task Sequence will being automatically over wireless.

I have tested this on a USB boot and from the desktop. OS upgrades or clean install-task sequences can be performed ether way. I won’t sugar-coat it, the process takes a while depending on the size of the task sequence. My standard deployment with all the bells and whistles takes 6 PCs 10 hours over wireless so ensure your maintenance windows are long enough to accommodate and your networking team isn’t planning any changes that night.

The key to success was using WinRE rather than WinPE as Windows Recover Environment supports wireless imaging for Surface Pro devices to restore from the cloud. The last task sequence step is to remove the wifiprofile.xml from %windir% as itis stored in plain text.

Not sure why Microsoft has made this so difficult but there it is, wireless imaging with SCCM. 

We noticed today that a tech imaging a laptop was pulling the image from a location it should not pull from. It was pulling it across the WAN from our Remote office to our HQ. We are not sure how long this has been happening, we just had complaints from users of network slowness from the remote office it was pulling the image from.

We have a main site at our HQ that we administer SCCM from. Then we have 2 other smaller office that have a setup to assist with OSD and application deployment, but no administration of SCCM.

We recently lost our sccm admin, so we are tying to figure out why it would be pulling an OSD image from some other location other than our HQ.

We have 1 Primary Site - HQ

We have 2 Site System Servers

Hi guys,

We are having some major problems with PXE booting a set of laptops via SCCM 2012. We have been able to successfully deploy the same package to our desktops PCs however. The boot images and task sequences have been set up correctly. The PXE client sends request and gets response from DHCP, and finds the policy. The WIM file is then downloaded successfully and the client switches to the Windows 8 logo as we are using the ADK. At this point nothing happens and it remains stuck like this. There is no spinning wheel and I can't access command prompt to try and find out any problems. I've looked on the SMSPXE logo and SCCM thinks everything is OK.

I have confirmed the problems with booting are not driver issues. I've been able to boot from a fresh windows image file on a separate network. Even with all of the available drivers boot fails. The only thing I can think of is that this site are using Cisco switches - is it possible that they are causing the problem? This seems unlikely to me though as the desktop PCs are using the same switches and settings but have imaged successfully.

Please please please help as we really have no idea what to try next.

Thanks.

JTh

Joel Thornton Windows 7 Ultimate x64, Windows 7 Ultimate x32, Windows XP x32

Hello SCCM Team,

Please is there anyway to pull out an inventory of the list of devices and their various operating system from System Center Configuration Manager.

Thank you in advance  

Hello SCCM Team,

Please is there anyway to pull out an inventory of the list of devices and their various operating system from System Center Configuration Manager.

Thank you in advance  

Hi,

I am having a weird issue recently. Started about 2 weeks ago. When imaging a new computer the computer shows up in Devices twice. One device name shows as Unknown, Active, Client installed, with proper GUID and a Resource ID 167779xx. The other device name is the correct computer name, inactive, client not installed and with no GUID and a Resource ID 20971527xx. 

This seems caused client on the newly imaged computer not receiving the correct client settings. Current workaround is to manually delete these Unknown active devices in SCCM. The next time that computer checks in it register with correct information. 

Any idea what could be the cause of this issue and is there some kind log(s) I can look for clue?

Thank you,

Henry

Hi

I have Updates SCCM server to 1903 and the hotfix KB45117869.

We have also update MDT to 8456,

We have problem to deploy Windows 10 1809, get error 0x80040154 in TS. 

and the logs file appear like that.

XXXXXX

InstallSoftware 28.10.2019 14:22:08 1152 (0x0480)
Microsoft Deployment Toolkit version: 6.3.8456.1000 InstallSoftware 28.10.2019 14:22:08 1152 (0x0480)
The task sequencer log is located at X:\WINDOWS\TEMP\SMSTSLog\SMSTS.LOG.  For task sequence failures, please consult this log. InstallSoftware 28.10.2019 14:22:08 1152 (0x0480)
ZTI deployment failed, Return Code = -2147221164  0x80040154 InstallSoftware 28.10.2019 14:22:08 1152 (0x0480)
Unable to create WebService class InstallSoftware 28.10.2019 14:22:08 1152 (0x0480)
Command line is being logged ('OSDDoNotLogCommand' is not set to 'True') InstallSoftware 28.10.2019 14:22:08 1152 (0x0480)
Command line cscript "C:\_SMSTaskSequence\WDPackage\scripts\ztierrormsg.wsf" returned 2147746132 InstallSoftware 28.10.2019 14:22:08 1152 (0x0480)
Process completed with exit code 2147746132 TSManager 28.10.2019 14:22:08 1756 (0x06DC)
!--------------------------------------------------------------------------------------------! TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Failed to run the action: Error in the task sequence. Error -2147221164 TSManager 28.10.2019 14:22:08 1756 (0x06DC)
MP server http://XXXXXXXXX. Ports 80,443. CRL=false. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Setting authenticator TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Sending StatusMessage TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Setting the authenticator. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: XXXXXXXXX:80  CCM_POST /ccm_system/request TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Not in SSL. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Request was successful. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Set a global environment variable _SMSTSLastActionRetCode=-2147221164 TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Set a global environment variable _SMSTSLastActionName=Error in the task sequence TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Set a global environment variable _SMSTSLastActionSucceeded=false TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Clear local default environment TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Let the parent group (Gather Logs and StateStore on Failure) decides whether to continue execution TSManager 28.10.2019 14:22:08 1756 (0x06DC)
The execution of the group (Gather Logs and StateStore on Failure) has failed and the execution has been aborted. An action failed.Error 0x80004004 TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Failed to run the last action: Error in the task sequence. Result -2147221164. Execution of task sequence failed. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
MP server http://XXXXXXXXX. Ports 80,443. CRL=false. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Setting authenticator TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Sending StatusMessage TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Setting the authenticator. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
CLibSMSMessageWinHttpTransport::Send: WinHttpOpenRequest - URL: XXXXXXXXX:80  CCM_POST /ccm_system/request TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Not in SSL. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Request was successful. TSManager 28.10.2019 14:22:08 1756 (0x06DC)
Executing command line: X:\WINDOWS\system32\cmd.exe /k TSBootShell 28.10.2019 14:22:24 84 (0x0054)
The command completed successfully. TSBootShell 28.10.2019 14:22:24 84 (0x0054)
Successfully launched command shell. TSBootShell 28.10.2019 14:22:24 84 (0x0054)

How will I do to procced that ?

----- S-O-K-O-B-A-N -----

I have created an OSD task sequence to migrate from WIndows XP to Windows 7. The Task Sequence works great from the software install and from a DVD, but I need to create a USB stick.

When I go to Create Task Sequence Media -> Stand-alone media and select "USB flash drive" as a radio button the drop down does not have my USB drive.

I tried to create a DVD ISO and export it to the USB stick but when I run it I get: "an error occurred while starting the task sequence" 0x80004005

My USB stick is seen fine in Windows.

does anyone know why my USB stick is not seen?

Also:

I have rebooted and uninstalled/re-installed Configuration Manager console

J Gruber

Having issue during build and capture ts.

I want the build .wim -image to have some info what to do next after the sysprep, basicly turn off hibernation and also some tweaking on one special file (modify permissions for users with cacls.exe).

I've added a step that echoes these couple of commands to %windir%\setup\scripts\setupcomplete.cmd which then should run after the sysprep, however the file is overwritten everytime during the install task sequence of the wim. It always contains only "%windir%\system32\osdsetuphook.exe /execute" and nothing more... I'm guessing SCCM OSD is doing this.

Is there any way to do some customization to the build image itself that does the magics after it's deployed? I don't want to use the install sequence itself and I'd also like to avoid unattened.xml...

Any registry paths that could be used? anything?

I am needing to upgrade machines from Windows 10 1803 / 1809 to Windows 10 1903. 

I have Microsoft 365 E3 plan.

All of the machines have their OEM keys. I am using the Windows 10 Pro KMS key for the upgrade operating system step in the SCCM Task Sequence. I am trying to apply the OEM key at the end of the task sequence, without luck.

SCCM version is 1902.

Hi,

I'm looking for how to documentation or step by step procedures to migrate from a windows 2012 R2 running Sccm Current Branch 1902 to a brand new server 2016 which will be running current branch 1906. I don't want to do an in place upgrade please.

Any help would be very appreciated.

Thank you