Quantcast
Channel: Configuration Manager 2012 - Operating System Deployment forum
Viewing all 9126 articles
Browse latest View live

SCCM 2012 report for specific software product GUID

$
0
0

Hi,

I'm trying to create a report where i need to get product guid based on my input(specific software name). 

Can anyone help me here, I'm new to report creating.


Task Sequence Failed with the Error Code 0x80070002

$
0
0

Hello Im trying to deploy image to several computers over pxe boot but obtains always Task Sequence Failed with the Error Code 0x80070002

I've a log smsts.log


installing app

$
0
0
i got problem in installing app with the code no. 0x70080057

PXE Boot

$
0
0

Hi All,

I'm getting this error when I pxe boot (blue screen)  The windows boot configurtation data (BCD), filefrom the PXE server does not contain a valid operating system entry.  Ensure that the server has boot images installed for this architecture.

Here's whats in the SMSPXE.log   Any Ideas?

Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 1 ID: 63CC689D
 Sec Since Boot: 4 Client IP: 000.000.000.000 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 010.008.044.001
 Addr: 50:7b:9d:68:cc:63:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 3=Request
  Type=50 Requested IP: 010.008.044.082
  Type=55 Param Request List: 0102030405060b0c0d0f10111216171c28292a2b3233363a3b3c42438081828384858687
  Type=57 Max Msg Size: 04ec
  Type=54 Svr id: 010.008.002.042
  Type=97 UUID: 0001c61c3dab53cb11896bef43fe6b424d
  Type=93 Client Arch: Intel x86PC
  Type=94 UNDI: 010201
  Type=60 ClassId: PXEClient:Arch:00000:UNDI:002001 SMSPXE 13/03/2020 1:37:32 PM 3336 (0x0D08)
============> Received from client: SMSPXE 13/03/2020 1:37:32 PM 3336 (0x0D08)
 Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 63CC689D
 Sec Since Boot: 65535 Client IP: 010.008.044.082 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
 Addr: 50:7b:9d:68:cc:63:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 3=Request
  Type=60 ClassId: PXEClient
  Type=97 UUID: 0001c61c3dab53cb11896bef43fe6b424d
  Type=93 Client Arch: Intel x86PC
  Type=55 Param Request List: 03013c8081828384858687 SMSPXE 13/03/2020 1:37:32 PM 3336 (0x0D08)
Prioritizing local MP http://sccm.something.old.au. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Not in SSL. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
RequestMPKeyInformation: Send() failed. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Unsuccessful in getting MP key information. 80004005. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Prioritizing local MP http://sccm.something.old.au. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Not in SSL. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
RequestMPKeyInformation: Send() failed. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Unsuccessful in getting MP key information. 80004005. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE Provider failed to process message.
Element not found. (Error: 80070490; Source: Windows) SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
50:7B:9D:68:CC:63, 3D1CC601-53AB-11CB-896B-EF43FE6B424D: Not serviced. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
============> Received from client: SMSPXE 13/03/2020 1:37:32 PM 3720 (0x0E88)
 Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 63CC689D
 Sec Since Boot: 0 Client IP: 010.008.044.082 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
 Addr: 50:7b:9d:68:cc:63:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 3=Request
  Type=60 ClassId: PXEClient
  Type=97 UUID: 0001c61c3dab53cb11896bef43fe6b424d
  Type=93 Client Arch: Intel x86PC
  Type=250 0d0208000e010001020006ff
  Type=55 Param Request List: 03013c8081828384858687 SMSPXE 13/03/2020 1:37:32 PM 3720 (0x0E88)
Prioritizing local MP http://sccm.something.old.au. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Not in SSL. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
RequestMPKeyInformation: Send() failed. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Unsuccessful in getting MP key information. 80004005. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Prioritizing local MP http://sccm.something.old.au. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Not in SSL. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
RequestMPKeyInformation: Send() failed. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
Unsuccessful in getting MP key information. 80004005. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
PXE Provider failed to process message.
Element not found. (Error: 80070490; Source: Windows) SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
50:7B:9D:68:CC:63, 3D1CC601-53AB-11CB-896B-EF43FE6B424D: Not serviced. SMSPXE 13/03/2020 1:37:32 PM 4920 (0x1338)
============> Received from client: SMSPXE 13/03/2020 1:37:33 PM 3720 (0x0E88)
 Operation: BootRequest (1)  Addr type: 1 Addr Len: 6 Hop Count: 0 ID: 63CC689D
 Sec Since Boot: 0 Client IP: 010.008.044.082 Your IP: 000.000.000.000 Server IP: 000.000.000.000 Relay Agent IP: 000.000.000.000
 Addr: 50:7b:9d:68:cc:63:
 Magic Cookie: 63538263
 Options:
  Type=53 Msg Type: 3=Request
  Type=60 ClassId: PXEClient
  Type=97 UUID: 0001c61c3dab53cb11896bef43fe6b424d
  Type=93 Client Arch: Intel x86PC
  Type=250 0c01010d0208000e010001020006ff
  Type=55 Param Request List: 03013c8081828384858687 SMSPXE 13/03/2020 1:37:33 PM 3720 (0x0E88)
Prioritizing local MP http://sccm.something.old.au. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
Not in SSL. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
RequestMPKeyInformation: Send() failed. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
Unsuccessful in getting MP key information. 80004005. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
PXE::MP_LookupDevice failed; 0x80070490 SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
Prioritizing local MP http://sccm.something.old.au. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
Not in SSL. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
RequestMPKeyInformation: Send() failed. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
Unsuccessful in getting MP key information. 80004005. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
PXE::MP_InitializeTransport failed; 0x80004005 SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
PXE::MP_ReportStatus failed; 0x80070490 SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
PXE Provider failed to process message.
Element not found. (Error: 80070490; Source: Windows) SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)
50:7B:9D:68:CC:63, 3D1CC601-53AB-11CB-896B-EF43FE6B424D: Not serviced. SMSPXE 13/03/2020 1:37:33 PM 4920 (0x1338)

MDT Task Sequence Variable Problem

$
0
0

Hi, 

I am trying to figure out where and when Task Sequence Variables are processed in MDT.  

I have several that are running from the customsettings.ini and I am trying to add some to the task sequence using "Set Task Sequence Variable"  (See list below).  These are intended to modify the Pre-Deployment Screens and settings on a Task sequence by task sequence basis.

DoCapture=YES
SkipComputerName=YES
ComputerName=DIV-CAPTURE
JoinWorkgroup=WORKGROUP
SkipApplications=YES

Where in the Task Sequence should these be set?

Unable to Deploy Dell Driver Packs

$
0
0

Hi all,

I'm new to SCCM. So far the system is installed and working and I installed the CU1 for 2012R2. I then installed the Dell tools and started importing packages. During the last import, it failed due to lack of disk space (oops). The server has plenty of disk space now, but I can't get it to import the same package that failed. I can click OK all day but it doesn't do anything and no error message. Does anyone know how to get around this?

Windows 10 1903 Display Language not defaulting to Regional langauge

$
0
0

Hello Team, 

Appreciate if someone can help me out of this issue.

Problem : We have different language packs to be applied in customer environment as part of the TS ( SCCM 1906 ver) with WIn10 1903 Enterprise OS, Language packs along with FOD's/LXP's are getting installed perfectly via TS.

I am using Dynamic variables and unattend .xml to set the language settings, everything looks fine but the OS is always defaulting to English as Display language and not the Regional language.

Input/keyboard/regional settings are defaulting to regional except UI( Display ) which is not setting to respective regional language.

Please find below the unattend.xml and TS settings.  End result should be Display UI setting to default Norway but its not happening right now, tried using powershell command which doesn't either set since it sets for user not system.

Please suggest.



Unattend xml

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="oobeSystem">
        <component name="Microsoft-Windows-International-Core" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <InputLocale>%OSDInputlocale%</InputLocale>
            <SystemLocale>%OSDSystemLocale%</SystemLocale>
            <UILanguage>%OSDUILanguage%</UILanguage>
            <UILanguageFallback>%OSDUILanguageFallback%</UILanguageFallback>
            <UserLocale>%OSDUserLocale%</UserLocale>
        </component>
</settings>
     <settings pass="oobeSystem">
          <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
               <OOBE>
                    <HideEULAPage>true</HideEULAPage>
                    <HideOEMRegistrationScreen>true</HideOEMRegistrationScreen>
                    <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                    <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
                    <HideLocalAccountScreen>true</HideLocalAccountScreen>
                    <ProtectYourPC>3</ProtectYourPC>
<SkipUserOOBE>true</SkipUserOOBE>
                    <SkipMachineOOBE>true</SkipMachineOOBE>
               </OOBE>
          </component>
</settings>      
</unattend>

Static IP during OSD_WinPE - Not Working

$
0
0

Hi,

SCCM Ver: 1902

How can I capture the IP Address, SMask, Gateway and DNS from WinPE ? Does Capture Network Settings work in WinPE ? because its failing for me.

example i put all this info in the Configure Static IP Network Settings in WinPE, but when all the tasks finish and log into windows the values are not set in the network adapter.

Please help

thanks,





Task sequence: image capture wizard has failed with the error code (0X00004005)

$
0
0

I am trying capture reference image via capture media (SCCM 2012 SP2 create task sequence media - capture media) form windows 10 enterprise X64 but getting below error. please suggest

running action: prepare oprtaing system

running sysprep command

Task sequence: image capture wizard has failed with the error code (0X00004005)

The computer running the Configuration Manager console does not have Read permissions to the share folder, or the share does not exist.

$
0
0

Hi,

I need to remotely (no local sccm module can be installed) create an application and a deployment type via Powershell.
Everything works fine, BUT creating the deployment type, it says it cannot reach the share, but when I execute the commanddirectly on the SCCM-server it works fine (I did a | clip of the command and pasted it into sscm PS on SCCM Server).
So I guess it is a dual hop issue.

Though I tried to run it via a

$PSSessionConfigurationName = "Microsoft.PowerShell32" 
$Existing = Invoke-Command -ComputerName $sccmserver -ScriptBlock { Get-PSSessionConfiguration | Where-Object name -EQ $using:PSSessionConfigurationName} -Credential $AdminCredentials
if (! $Existing)
{ Write-Output "Creating a session to $SCCMServer"
 Invoke-Command -ComputerName $SCCMServer -ScriptBlock { Register-PSSessionConfiguration -Name $using:PSSessionConfigurationName -RunAsCredential $using:Admincredentials -Force } -Credential $AdminCredentials
}

$sb = "MyCorrectCommand to create the deployment type, it works fine on the server = Add-CMDeploymenType ..."
Invoke-Command -ComputerName $SCCMServer -ScriptBlock { Invoke-Expression ($using:sb)  } -ConfigurationName $PSSessionConfigurationName -Credential $AdminCredentials

Please advise
J


Jan Hoedt

Remove additional OS images from install.wim

$
0
0

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.

Enrolling Client Authentication Certificate during Task Sequence

$
0
0

When using PKI certificates, Microsoft recommends using the Auto-enrollment method to enroll the client authentication certificate yet they also state Group Policy is disabled while the Task Sequence is running so obviously the system will not enroll the cert the first time the computer reboots after joining the domain or any other restart steps since that occurs during the TS while GP processing is disabled. That also means the cert will still not be enrolled when the client is installed during the "Setup Windows and ConfigMgr" step therefore the client doesn't really become fully operational until the Task Sequence actually completes and Group Policy processing is enabled which will occur within 90 minutes (GP refresh) after the TS completes. Can someone confirm this is true that auto cert enrollment will not occur until after the TS completes?


Mashing head against wall trying to get Lenovo Thinkpad to load drivers from SCCM correctly

$
0
0

Hi All - 

We're generally a 100% Dell shop..  due to the limited availability attributed to everyone needing a laptop for their remote use, we've had to adapt a bit and procure some Thinkpad laptops..  Everything goes swimmingly until the client performs a final reboot and drivers don't appear to have loaded - we're presented with a login with no ethernet/wifi drivers- and consequently, the client isn't able to be added to the domain as it normally should..  the driver package looks fine, as well as the driver query looking fine (to our knowledge) - Looking through the SMSTS.log there isn't much at all regarding the drivers being added and that's fairly worrisome.

Any thoughts?  I'll be happy to include logs if that would help.

Thanks!

-A

ServiceUI.exe error

$
0
0

Hi!

I'm using the ServiceUI.exe from MDT 2013 to open cmtrace.exe with "x:\windows\temp\smstslog\smsts.log".

The command line is:

ServiceUI.exe -process:tsprogressui.exe cmtrace.exe "x:\windows\temp\smstslog\smsts.log"

I get error code 0xFFFFFFFF and in SMSTS.LOG:

If I run the command in an CMD.EXE (F8 in Windows PE) I got the same error.

SCCM 2012 - Windows 10 task sequence - Application install fail - Timeout = 0 minutes.

$
0
0

Hi there

Working on a Windows 10 POC, using SCCM 2012.

Going well apart from one persistent issue.

Applications will fail to install in the task sequence with an error I haven't before.

Here's part of AppEnforce.log.

------------------------------------------------------------------------------------------------------------------------------------------------

+++ Starting Install enforcement for App DT "BGInfo Install" ApplicationDeliveryType - ScopeId_1315AD/DeploymentType_685AD, Revision - 6, ContentPath - C:\Windows\ccmcache\2, Execution Context - AnyAppEnforce23/12/2015 13:19:504032 (0x0FC0)
    A user is not logged on to the system.AppEnforce23/12/2015 13:19:514032 (0x0FC0)
    Performing detection of app deployment type BGInfo Install(ScopeId_1315AD/DeploymentType_685AD, revision 6) for system.AppEnforce23/12/2015 13:19:514032 (0x0FC0)
+++ Application not discovered. [AppDT Id: ScopeId_1315AD/DeploymentType_685AD, Revision: 6]AppEnforce23/12/2015 13:19:514032 (0x0FC0)
    App enforcement environment: 
Context: Machine
Command line: "bginfo.bat"
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\Windows\ccmcache\2
Working directory: AppEnforce23/12/2015 13:19:514032 (0x0FC0)
    Prepared working directory: C:\Windows\ccmcache\2AppEnforce23/12/2015 13:19:514032 (0x0FC0)
    Prepared command line: "C:\Windows\ccmcache\2\bginfo.bat"AppEnforce23/12/2015 13:19:514032 (0x0FC0)
    Executing Command line: "C:\Windows\ccmcache\2\bginfo.bat" with system contextAppEnforce23/12/2015 13:19:514032 (0x0FC0)
    Working directory C:\Windows\ccmcache\2AppEnforce23/12/2015 13:19:514032 (0x0FC0)
    Post install behavior is BasedOnExitCodeAppEnforce23/12/2015 13:19:514032 (0x0FC0)
    Waiting for process 2448 to finish.  Timeout = 0 minutes.AppEnforce23/12/2015 13:19:514032 (0x0FC0)
Exceeded timeout of 0 minutes while waiting for process 2448 to finish.AppEnforce23/12/2015 13:19:514032 (0x0FC0)
WaitForRunningProcess failed.  Error 0x87d00213.AppEnforce23/12/2015 13:19:514032 (0x0FC0)
CScriptHandler::CompleteEnforcement failed with 0x87d00213AppEnforce23/12/2015 13:19:514032 (0x0FC0)
CAppProvider::CompleteEnforcement failed with error 0x87d00213AppEnforce23/12/2015 13:19:514032 (0x0FC0)
++++++ Failed to enforce app. Error 0x87d00213. ++++++AppEnforce23/12/2015 13:19:514032 (0x0FC0)

------------------------------------------------------------------------------------------------------------------------------------------------------

The key part of the log is Waiting for process 2448 to finish.  Timeout = 0 minutes.

This is odd because that app has a Maximum Allowed Runtime of 15 minutes.

Other apps fail with the same error - Timeout = 0 minutes - even though they have a Maximum Allowed Runtime of 60 minutes or more.

Anyone seen this with SCCM 2012 / Windows 10 task sequences?

Merry Christmas

John


Systems do not seem to register with KMS Server

$
0
0

Just recently we have noticed some of our systems will not register will KMS or are registering as Pro even though this an Enterprise version OS.  I have tried to apply the key in the "Apply Windows Settings (See attachment)"

Picture 1 (Can not add until account verified)

Then I have tried adding a step to add the KMS server statically and then plug in the Key as activate.  Still no luck

Picture 2

Systems just do not see to see the KMS server

Picture 3

I have to run these command after the build is complete and then it seems to register

:Static KMS Server cscript //B "%windir%\system32\slmgr.vbs" -skmscmps-vmmgmt03.private.entfederal.com :Add Enteprise Key cscript //B %windir%\system32\slmgr.vbs /ipkNPPR9-FWDCX-D2C8J-H872K-2YT43 :Activate cscript //B %windir%\system32\slmgr.vbs /ato

Picture 4

I am still doing more research, but with a large number of deployments coming up I need to fix this ASAP

Anyone out there have ideas

SCCM PXE not getting IP address

$
0
0

Our organization uses SCCM 2016 connected to two MS Server 2016-based DPs. The first works fine though the other recently (last 30 days or so) stopped communicating with the PXE. We don't know what exactly caused this (perhaps a CU update?). Essentially, when pressing F12 to start PXE, we don't get any IP address.

The process goes as follows:

>>Checking Media Presence......>>Media Present.......>>Start PXE Over IPv4 (MAC address)

In attempt to get it to work, I have restarted the DHCP server and set up a new DP, the problem persists.

Our servers are up-to-date with the latest Microsoft update (which at this point we would not like to revert due to security reasons). What would you guys suggest me do?

Thanks in advance!

WDS Issue: DP: An error occurred while trying to create the directory for the architecture. Error Information: 0x3

$
0
0

We recently had an issue where machines were not able to PXE boot (I know I should be using IP helpers but are not there yet, on the to do list) Anyway we had option 60 configured on the DHCP and removing that fixed it. However, in the process of trying to figure that out I had removed the boot image and OS images and replaced them. So we get past DHCP and get a WDS error. So I removed PXE and WDS from the DP and added it back then redistributed the boot image and OS but I am getting the error

An error occurred while trying to create the directory for the  architecture.
 
 Error Information: 0x3

in the Event Viewer that makes it seem like the RemoteInstall folder is not being built out right and WDS is saying there is no architecture for the machine we are trying to boot. Any ideas?


Thomas Faherty

1909 Feature Update woes

$
0
0

Hi all,

now that Windwos 10 v 1909 is out, we have started preparing our environment (SCCM Current Branch 1906) to deploy this new version and updating existing clients. 

OSD Task Sequences for new machines with 1909 seem to run pretty smooth (after figuring out some Language Pack annoyances). However, we are facing issues with SCCM Feature Update Task Sequences that bomb out after the base os installation. We are trying to update Windows 1709 and also 1809 versions. This is what we have encountered so far:

The Task Sequence for the OS upgrade starts fine, performs a few expected reboots, then displaying "Windows is working in updates 0%, 15%, ..." When it reaches 100%, this Windows Upgrade step remains at 100% for a long long time and then suddenly shows the Windows login screen. All TS Post Processing steps (i.e. Language Packs, etc.) are skipped.

SMSTS.LOG indicates, that the base OS upgrade seems to have finished without errors:

  • Successfully completed the action (Upgrade Operating System) with the exit win32 code 0

After that we can discover several "Start top compile TS policy" steps, but suddenly the following errors happen:

<![LOG[Failed to initate policy evaluation for namespace 'root\ccm\policy\machine', hr=0x80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="utils.cpp:5007"><![LOG[Error compiling client config policies. code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1577"><![LOG[Task Sequence Manager could not initialize Task Sequence Environment. code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1654"><![LOG[Task sequence execution failed with error code 80041010]LOG]!><time="10:07:10.271-60" date="11-25-2019" component="TSManager" context="" type="3" thread="6284" file="tsmanager.cpp:1305">

After that the Task Sequence stops any further processing without showing any errors. Digging through all other SCCM logs I have found out that at the time time when the error above happens there is the following in CCMEXEC.LOG:

<![LOG[Detected faulty configuration. Repair will be started in 5 minutes.]LOG]!><time="10:07:11.521-60" date="11-25-2019" component="CcmExec" context="" type="3" thread="6560" file="entrypoint.cpp:3079"><![LOG[Entering main message loop.]LOG]!><time="10:07:11.521-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3104"><![LOG[WM_QUIT received in the main message loop.]LOG]!><time="10:12:11.521-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3121"><![LOG[Initiated repair of configuration. Service will now exit.]LOG]!><time="10:12:11.599-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="entrypoint.cpp:3130"><![LOG[Shutting down CCMEXEC...]LOG]!><time="10:12:11.599-60" date="11-25-2019" component="CcmExec" context="" type="1" thread="6560" file="shutdown.cpp:53">

This looks to me, that immediately after the OS upgrade, the system seems to start a repair of the SCCM client (for unknown reason). This repair seems to break the entire Task Sequence. 

have triple-checked countlessly that the SCCM client is healthy before the upgrade but something seems to happen during the 1909 upgrade that makes Windows trying to repair the SCCM client. 

Any thoughts what might go wrong here? 

Thanks in advance

Regards

Udo



WINHTTP_CALLBACK_STATUS_FLAG_invalid_ca

$
0
0

I have a problem with OSD task sequence - just for tests I imported WinPE 10 from our development environment from SCCM 2012 to our production environment. I am able to boot laptop from PXE then after providing password computer restarts automatically. If I press F8 before restart I see smsts.log where I can find an error:

WINHTTP_CALLBACK_STATUS_FLAG_invalid_ca

I already looked at:

https://social.technet.microsoft.com/Forums/en-US/f6eedffe-25a4-48e8-bc9c-e9e30551794f/certificates-and-other-domains?forum=configmanagergeneral

but this is not the same issue as I am not in full Windows OS but in WinPE. I also checked date and time in BIOS - looks ok. I am able to run another OSD task sequence on this laptop from our SCCM (using different WinPE of course).

I am wondering what certificates are used\checked during WinPE phase when contacting with MP ? How to check it?

Our Management Point is set to HTTP - client connections

Viewing all 9126 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>