Conundrum - PXE boot fails vs. "reinstall OS from software center" succeeds

Hi All.
I am facing a bit of a conundrum..
In our offices I am seeing some strange behaviour when trying to PXE boot into a TS to reinstall or install OS. 
If I use F12/PXE boot then the deployment fails during OSD.
If I take a client (the same client as I tried pxe booting with) that is fully installed and reinstall OS via software center then the deployment completes. 
Any ideas what could be wrong?
Kindest regards, Martin

Daniel:
Clients are both laptops & desktops.
I "feels" like it's the network that's acting up but I really can't see where. 
PXE boot works.. it's not until it tries to apply the OS... 
whether it's a timeout or what it is I cannot say.. 
Gerry: After all will you be likely to rebuild your entire estate in-situ any time soon?
You know... we are actually On the verge" of upgrading & Streamlining our entire network infrastructure..
But I'd still love to solve the problem.. 
We never had this issue when we only had MDT as deployment tool. 
it's not until sccm came into the picture that this issue has arisen.
Kindest regards, Martin

Similar Messages

  • Software install from software center is failing

    Hi,  We have a application install that is failing when trying to install from software center.  Its a straightforward .msi install.
    Which log file would we look at to see why the application install is failing?
    Thanks
    Thanks Lance

    Hi,
    Please see AppEnforce.log and AppDiscovery.log if the installation already started.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Unable to unistall application from software center

    Hi,
    I am unable to uninstall Chrome from Software Center. When i select Chrome and click uninstall, it doesn't seem to do anything.

    Check logs to get more details about issue
    http://www.scconfigmgr.com/2012/08/15/applications-in-software-center-uninstall-with-removal-failed/
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"Mai Ali | My blog:
    Technical | Twitter:
    Mai Ali

  • How to hide installed application from Software Center 2012

    Hello,
    I would like to ask you whether it is possible in Software Center 2012 to remove the record of program that was installed successfully from application catalog.
    Currently it stays visible in SC as "Available" constantly informing users with popup that there is new software available for installation. This may be disturbing behavior for users.
    Technical specialist in our company would be very glad to know some workaround. Is there some xml file or registry on user computer that could be used to remove such record from Software Center 2012?
    Thank you very much for any advice!

    Hi,
    There is a related setting in Client Setting - Show notifications for new deployments.
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • OSD: pxe boot fails with "failed to get infromation for MP:/"

    Hi,
    We face an issue on pxe boot. It boots into pxe then tries to apply network settings but then reboots.
    Ipconfig is ok, smsts.log says "failed to get information for MP:/oursccmserver.
    Troubleshooting:
    *PXE is working fine when client as well as sccm-server are in same subnet, it fails when in different subnets.
    *Firewall is fully opened, no connections blocked.
    *Ping to sccm-server works fine on dns
    Please advise.
    J.
    smsts.log:
    Missing root CA environment variable from variables file    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Support Unknown Machines: 0    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Custom hook from X:\\TSConfig.INI is     TSPxe    26/03/2014 16:37:11    288 (0x0120)
    No hook is found to be executed before downloading policy    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Authenticator from the environment is empty.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Need to create Authenticator Info using PFX    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Initialized CStringStream object with string: {40AB3050-A926-4BA5-9D17-7423F93CBCD5};2014-03-27T00:37:11Z.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Set media certificate in transport    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Set authenticator in transport    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    CLibSMSMessageWinHttpTransport::Send: URL: oursccmserver.ourcompany.com:80  GET /SMS_MP/.sms_aut?MPKEYINFORMATIONMEDIA    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): WINHTTP_CALLBACK_STATUS_SECURE_FAILURE Encountered    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]                : dwStatusInformationLength is 4
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]                : *lpvStatusInformation is 0x8
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING]            : WINHTTP_CALLBACK_STATUS_FLAG_INVALID_CA is set
        TSPxe    26/03/2014 16:37:11    288 (0x0120)
    [TSMESSAGING] AsyncCallback(): -----------------------------------------------------------------    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    WinHttpReceiveResponse (hRequest, NULL), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,8927)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    failed to receive response with winhttp; 80072f8f    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    m_pHttpTransport->Send (0, 0, pServerReply, nReplySize), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5159)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    MPKeyInformation.RequestMPKeyInformationForMedia(szTrustedRootKey), HRESULT=80072f8f (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,9410)    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Failed to get information for MP: http://oursccmserver.ourcompany.com. 80072f8f.    TSPxe    26/03/2014 16:37:11    288 (0x0120)
    Jan Hoedt

    Hi,
    Have you check Mpcontrol.log on the MP server and Smspxe.log?
    Best Regards,
    Joyce Li
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • PXE boot fails and reboots after loading PE

    I have run into what I think is a unique issue and need some help determining the cause.
    We are in the process of replacing and aging DP/PXE point (2003 R2 SP2) with a new server (2008 STD R2 SP1).  What makes my pxe issue unique is that pxe works without issue on the existing 2003 DP/PXE server.  But on the new 2008 server I run into
    the following issue.
    Environment:  Config Manager 2007 R2, a single primary, multiple DP's and PXE points.
    Issue:  When I attempt to PXE boot a system, I am able to load PE, but shortly after the custom background screen is loaded, the system reboots.  I've searched the internet quite a bit and found lots of potential causes including, bad/missing drivers,
    certificate issues, rights issues, etc.  None of these seem to be the cause.
    My troubleshooting has determined that the client computers are unable to download the variables.dat file.  I just don't know why.
    We're using the same boot images on both servers. 
    I've tried using multiple computer models and VM's. 
    I've opened a command prompt as soon as our background image loads and have verified that the system is pulling a valid IP address.  I am able to map a drive to the PXE server's REMINST share using our sccm net access account and manually copy the .var
    file using xcopy to the appropriate directory on the local virtual drive.   I've also attempted to manually run smstftp.exe by mimicking the command line from the smsts log file.  I'll admit that I'm not sure I have the correct syntax for smstftp. 
    I've tried several variations and all but one result in a short pause and no file copied/created in the X:\sms\data folder.  The one that does produce a result says that the file cannot be found.  I checked for typos and made sure I used the name
    of the newly created .var file.
    I've also tried disabling anti-virus on the server, shutting off the windows firewall on the server, granting everyone read rights to the REMINST share.
    Below is the smstslog file I've been using as a reference.  Per corporate security policy, I have X'd out the IP address of the PXE server.  The log file for the successful pxe boot from the 2003 server shows an exit code of 0 for smstftp.exe, a note
    about successful download of the pxe var file and then it continues through the rest of the boot process.
    -----SMSTS log file from a failed PXE boot on the new 2008 server -----
    <![LOG[LOGGING: Finalize process ID set to 832]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="tslogging.cpp:1489">
    <![LOG[==============================[ TSBootShell.exe ]==============================]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836"
    file="bootshell.cpp:963">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="util.cpp:869">
    <![LOG[Debug shell is enabled]LOG]!><time="16:13:54.440+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:974">
    <![LOG[Waiting for PNP initialization...]LOG]!><time="16:13:54.471+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:59">
    <![LOG[Booted from network (PXE)]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="configpath.cpp:198">
    <![LOG[Found config path X:\sms\data\]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:553">
    <![LOG[Booting from removable media, not restoring bootloaders on hard drive]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:564">
    <![LOG[Executing command line: wpeinit.exe -winpe]LOG]!><time="16:13:54.830+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:767">
    <![LOG[Executing command line: X:\WINDOWS\system32\cmd.exe /k]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:767">
    <![LOG[The command completed successfully.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:850">
    <![LOG[Successfully launched command shell.]LOG]!><time="16:13:57.014+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="836" file="bootshell.cpp:430">
    <![LOG[The command completed successfully.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
    <![LOG[Starting DNS client service.]LOG]!><time="16:14:41.458+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:597">
    <![LOG[Executing command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880"
    file="bootshell.cpp:767">
    <![LOG[The command completed successfully.]LOG]!><time="16:14:41.973+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:850">
    <![LOG[==============================[ TSMBootStrap.exe ]==============================]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932"
    file="tsmbootstrap.cpp:1039">
    <![LOG[Command line: X:\sms\bin\i386\TsmBootstrap.exe /env:WinPE /configpath:X:\sms\data\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932"
    file="tsmbootstrap.cpp:1040">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\1033\TSRES.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="util.cpp:869">
    <![LOG[Succeeded loading resource DLL 'X:\sms\bin\i386\TSRESNLC.DLL']LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="resourceutils.cpp:152">
    <![LOG[Processor Is IA64: 0]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1005">
    <![LOG[PXE Boot with Root = X:\]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="1" thread="1932" file="tsmbootstrap.cpp:921">
    <![LOG[Executing from PXE in WinPE]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstrap.cpp:936">
    <![LOG[Loading TsPxe.dll from X:\sms\bin\i386\TsPxe.dll]LOG]!><time="16:14:41.989+000" date="12-23-2013" component="TSMBootstrap" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1319">
    <![LOG[TsPxe.dll loaded]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tsmbootstraputil.cpp:1329">
    <![LOG[Device has PXE booted]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:122">
    <![LOG[Variable Path: \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
    file="tspxe.cpp:134">
    <![LOG[Variable Key Len: 61]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:141">
    <![LOG[Succesfully added firewall rule for Tftp]LOG]!><time="16:14:42.004+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:123">
    <![LOG[Executing: X:\sms\bin\i386\smstftp.exe -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.004+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tspxe.cpp:177">
    <![LOG[Command line for extension .exe is "%1" %*]LOG]!><time="16:14:42.067+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:229">
    <![LOG[Set command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="commandline.cpp:707">
    <![LOG[Executing command line: "X:\sms\bin\i386\smstftp.exe" -i XXX.XXX.XXX.XXX get \SMSTemp\2013.12.23.16.11.24.0002.{AB0FBE86-1F6C-47D7-919B-A44641035A2E}.boot.var X:\sms\data\variables.dat]LOG]!><time="16:14:42.067+000" date="12-23-2013"
    component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:805">
    <![LOG[Process completed with exit code 1]LOG]!><time="16:15:29.179+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="commandline.cpp:1102">
    <![LOG[Succesfully removed firewall rule for Tftp]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932" file="fwopen.cpp:146">
    <![LOG[uExitCode == 0, HRESULT=80004005 (e:\nts_sms_fre\sms\server\pxe\tspxe\tspxe.cpp,185)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="0" thread="1932"
    file="tspxe.cpp:185">
    <![LOG[Failed to download pxe variable file. Code(0x00000001)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tspxe.cpp:185">
    <![LOG[PxeGetPxeData failed with 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="3" thread="1932" file="tsmbootstraputil.cpp:1419">
    <![LOG[HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1420)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context=""
    type="0" thread="1932" file="tsmbootstraputil.cpp:1420">
    <![LOG[TSMBootstrapUtil::PxeGetPxeData(&bPxeBooted, sVariablesFile, sPxePasswd), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,2236)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tsmediawizardcontrol.cpp:2236">
    <![LOG[oTSMediaWizardControl.Run( sMediaRoot, true, true ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,937)]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe"
    context="" type="0" thread="1932" file="tsmbootstrap.cpp:937">
    <![LOG[Execute( eExecutionEnv, sConfigPath, sTSXMLFile, uBootCount, &uExitCode ), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstrap.cpp,1106)]LOG]!><time="16:15:29.194+000" date="12-23-2013"
    component="TSPxe" context="" type="0" thread="1932" file="tsmbootstrap.cpp:1106">
    <![LOG[Exiting with return code 0x80004005]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSPxe" context="" type="1" thread="1932" file="tsmbootstrap.cpp:1118">
    <![LOG[Execution complete.]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="bootshell.cpp:624">
    <![LOG[Finalizing logging from process 832]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1736">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="16:15:29.194+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1578">
    <![LOG[LOGGING: Setting log directory to "D:\SMSTSLog".]LOG]!><time="16:15:29.491+000" date="12-23-2013" component="TSBootShell" context="" type="1" thread="880" file="tslogging.cpp:1803">
    This has been an extremely frustrating issue and any assistance would be greatly appreciated!

    Thanks for your quick response Jason!  I didn't expect someone to reply so quickly or I would have checked back sooner. 
    I had found the two 'older' posts already, but had not seen the 'newer' one.  Unfortunately that did not give me any new ideas.  But your comment on checking for TFTP availability did.  Here are things I have tried since my original
    post...
    I re-ran most of my tests in case I missed something.  I only found one change.  Even though I double-checked, I must have made a typo when I manually ran the smstftp.exe command, because when I ran it again I received a timeout message instead
    of file not found.
    I had a minor 'thinking outside of the box moment' and decided to PXE boot the new 2008 R2 server itself.  This was successful and I interpreted the success as meaning that the hardware is ok.  Thinking there may be a compatibility issue with
    the hardware and the OS, I tried a few different NIC drivers, settings, registry keys, and even a completely different NIC.  No luck on any of these.
    I decided to build another Server on a VM tovalidate my build process and configuration.  And of course clients in multiple locations were able to PXE boot off this VM.  Too bad I can't use this in production.
    After reading your response Jason, I began to focus on network.  I moved the server to a few different locations so it was utilizing different switches.  No luck.  I noticed in the event viewer for WDS that the server was logging the
    beginning of the boot.var file via TFTP.  This of course was not very surprising.  What was surprising is that the very next entry (informational) noted that the client 'COMPLETED' the download of the boot.var file via TFTP.  I know that completed
    does not mean successful, but it usually implies or is interpreted as successful.  It should have logged a warning or error, or nothing at all because although the process completed, it was not successful.  I re-verified that the file was not downloaded
    to the client and the client log file still shows the same error noted in the logfile from my original post.
    Finally, I installed sniffing software on the server and ran some captures while attempting to PXE boot.  Even though I am not much of a network guy, I quickly discovered two things.  First, I found the section where the client attempts to download
    the boot.var file.  Unfortunately I don't think the local security team will allow me to post the capture, so I'll do my best to describe what I found.  It starts with a single entry where the client calls for the file via TFTP protocol.  This
    is followed by a series of alternating entries (all TFTP) where it looks like the server attempts to send a portion of the file, and the client sends an acknowledgement.  The sending entries all have checksum errors.  The checksum received on
    all packets is 0x0000 and of course should be something else.  There is also a shorter section below this with alternating entries where the server attempts to send ICMP packets and the client responds with TFTP acknowledgements. 
    The ICMP entries are all marked as Destination unreachable (Port Unreachable).
    The second thing I noticed from the network capture is the a few 'Spanning Tree Protocol' entries.  I my search for a solution, I remember reading several posts saying that Spanning Tree can cause this issue.  When I asked, I was assured that
    Spanning Tree was disabled in this environment.  It made sense too, because the 2003 PXE server was functioning properly, and Spanning Tree should affect both 2003 and 2008 servers, right?
    Either way I will bring my findings to the network team and see what they have to say.
    Any additional thoughts or ideas???

  • PXE boot fails

    All
    I have an issue with PXE booting into zenwork imaging. Using zenworks
    V4.0.1 when you boot the pc into zenworks maintence mode, the pc downloads
    from the server until it get to "Uncompressing and laoding zenworks
    imaging, please wait" and then errors with the message "Invalid
    compression format (err2) -System halted.
    I have tried replacing the z:publiczenworksimaging and the pxe folders
    with copies from another server, however I still get the same issue.
    Does anyone know which file is uncompressed or needs replacing/restoring?
    Thanks
    David

    On Mon, 13 Aug 2007 08:22:28 GMT, David wrote:
    > Yes
    > It fails on all pcs - however if you use a boot cd it works ok. It must be
    > what the server is sending down as part of the pxe boot process that is
    > the issue.
    > Thanks
    > David
    hmm I would check sys:\tftp and try the ir7 update
    If you have already compiled drivers or have linux.2 please put them on
    http://forge.novell.com/modules/xfmo...ect/?zfdimgdrv
    Live BootCd and USB Disk from Mike Charles
    http://forge.novell.com/modules/xfmod/project/?imagingx
    eZie http://forge.novell.com/modules/xfmod/project/?ezie
    Marcus Breiden
    If you are asked to email me information please remove the - in my e-mail
    address.
    The content of this mail is my private and personal opinion.
    http://www.didas.de

  • Running Task Sequence from Software Center failed after rebooting to WinPE (0x8022001B)

    Hi all
    I have created a task sequence to refresh client OS to windows 8.1 x64. I ran this task sequence in software center on a windows 7 client, everything went well without any fails.
    But when I ran the same ts again after it refreshed to Windows 8.1, it failed immediately after rebooted to WinPE. It shows a warning with error code 0x8022001B.
    My test environment: SCCM 2012 R2 (Windows Server 2012 R2). Client Device: Lenovo L430
    Any suggestions? Thanks in advance!
    SMSTS.log file shows below:
    <![LOG[Configuring 1 of 3 network adapters]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="netsettings.cpp:186">
    <![LOG[Configuring DHCP]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:417">
    <![LOG[DNS suffix: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:428">
    <![LOG[DNS server search order: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:437">
    <![LOG[DNS registration enabled: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:444">
    <![LOG[Full DNS registration enabled: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:452">
    <![LOG[Permitted IP protocols: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:457">
    <![LOG[Permitted TCP ports: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:461">
    <![LOG[Permitted UDP ports: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:465">
    <![LOG[Tcpip Netbios options: 0]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:474">
    <![LOG[Enable WINS: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:480">
    <![LOG[WINS server(s): ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:489">
    <![LOG[MAC address: a4:17:31:f3:e4:28]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:503">
    <![LOG[Adapter index: 0]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:512">
    <![LOG[Adapter name: WLAN]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:516">
    <![LOG[Getting namespace "Microsoft-Windows-TCPIP" for architecture "amd64"]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="smiinterface.cpp:222">
    <![LOG[Added list item with key value 'a4-17-31-f3-e4-28']LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="smiinterface.cpp:441">
    <![LOG[Configuring 2 of 3 network adapters]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="netsettings.cpp:186">
    <![LOG[Configuring DHCP]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:417">
    <![LOG[DNS suffix: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:428">
    <![LOG[DNS server search order: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:437">
    <![LOG[DNS registration enabled: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:444">
    <![LOG[Full DNS registration enabled: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:452">
    <![LOG[Permitted IP protocols: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:457">
    <![LOG[Permitted TCP ports: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:461">
    <![LOG[Permitted UDP ports: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:465">
    <![LOG[Tcpip Netbios options: 0]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:474">
    <![LOG[Enable WINS: false]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:480">
    <![LOG[WINS server(s): ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:489">
    <![LOG[MAC address: a4:17:31:f3:e4:28]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:503">
    <![LOG[Adapter index: 1]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:512">
    <![LOG[Adapter name: WLAN]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:516">
    <![LOG[spItem->CreateListElement( var, &spChildItem ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\smiinterface.cpp,439)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="smiinterface.cpp:439">
    <![LOG[Failed to create list element with key value 'a4-17-31-f3-e4-28' (0x8022001B)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="3" thread="808" file="smiinterface.cpp:439">
    <![LOG[pSetupPass->addListItem( m_spSettingsEngine, pszNamespace, pszPath, pszKeyValue ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\smiinterface.cpp,1187)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="smiinterface.cpp:1187">
    <![LOG[m_pSMIInterface->addListItem( SetupPassValue[eSetupPass], pszComponentName, pszPath, pszKeyValue ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,738)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="xmlanswerfile.cpp:738">
    <![LOG[AddListItem( eSetupPass, XML::TcpIp::ComponentName, XML::TcpIp::Interfaces::InterfaceElement, sIdentifier ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\xmlanswerfile.cpp,1063)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="xmlanswerfile.cpp:1063">
    <![LOG[m_pImpl->AddAdapterTcpIpSettings( XMLAnswerFileImpl::WindowsPE, adapterInfo ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\winpeanswerfile.cpp,176)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="winpeanswerfile.cpp:176">
    <![LOG[pAnswerFile->AddNetworkAdapter(adapterInfo), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\netadaptersettings.cpp,575)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netadaptersettings.cpp:575">
    <![LOG[Failed to configure adapter 1 (0x8022001B)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="3" thread="808" file="netadaptersettings.cpp:575">
    <![LOG[adapterSettings.Configure( pAnswerFile ), HRESULT=8022001b (e:\nts_sccm_release\sms\framework\osdcore\netsettings.cpp,188)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="netsettings.cpp:188">
    <![LOG[Failed to configure network settings for adapter 2 (0x8022001B)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="3" thread="808" file="netsettings.cpp:188">
    <![LOG[m_pNetSettings->Configure(pAnswerFile), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootstrapsettings.cpp,191)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="bootstrapsettings.cpp:191">
    <![LOG[this->createAnswerFile(sAnswerFilePath), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootstrapsettings.cpp,140)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="bootstrapsettings.cpp:140">
    <![LOG[pSettings->configureAnswerFile(), HRESULT=8022001b (e:\nts_sccm_release\sms\client\tasksequence\bootshell\bootshell.cpp,595)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="bootshell.cpp:595">
    <![LOG[Execution failed with error 8022001B.]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="3" thread="808" file="bootshell.cpp:703">
    <![LOG[hMap != 0, HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentscope.cpp,493)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="environmentscope.cpp:493">
    <![LOG[m_pGlobalScope->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,335)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="environmentlib.cpp:335">
    <![LOG[this->open(), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\environmentlib.cpp,553)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="environmentlib.cpp:553">
    <![LOG[::RegOpenKeyExW (HKEY_LOCAL_MACHINE, sKey.c_str(), 0, KEY_READ, &hSubKey), HRESULT=80070002 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,809)]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="0" thread="808" file="utils.cpp:809">
    <![LOG[RegOpenKeyExW is unsuccessful for Software\Microsoft\SMS\Task Sequence]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="2" thread="808" file="utils.cpp:809">
    <![LOG[GetTsRegValue() is unsuccessful. 0x80070002.]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="2" thread="808" file="utils.cpp:842">
    <![LOG[End program: ]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="bootshell.cpp:725">
    <![LOG[Finalizing logging from process 800]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="tslogging.cpp:1741">
    <![LOG[Finalizing logs to root of first available drive]LOG]!><time="14:10:49.114+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="tslogging.cpp:1583">
    <![LOG[LOGGING: Setting log directory to "E:\SMSTSLog".]LOG]!><time="14:10:49.130+480" date="01-09-2015" component="TSBootShell" context="" type="1" thread="808" file="tslogging.cpp:1808">

    Then it's using a different boot image that doesn't have the NIC driver. The OS that the TS starts out in has no impact on the WinPE environment. Either the driver is there and properly loads or it doesn't -- there is not and cannot be any connection to
    the OS the system was booted into prior to PE booting.
    Thus, the only possibility here is that the boot image does *not* have the NIC driver in it. You need to verify which boot image I being used in both cases.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Getting "Error: 0x80070654" when trying to install SCCM 2012 R2 Console from Software Center

    What I did:
    Created a Package Source share on the Site Server
    Gave the Package Source Share the following Share permissions: SCCM Admins: Full Control, Domain Computers: Full Control, Local Admins: Full Control.
    Copied the "Program Files\Microsoft Configuration Manager\tools\ConsoleSetup" folder to my package source (Since the Package Source is actually on the site server, I just copied the ConsoleSetup folder to it that is on the same drive)
    Created a package and a Standard Program
    Command line: ConsoleSetup.exe 
    I deploy it to my collection
    Run Machine Policy and Reevaluation on my Right Click Tools 
    Go to one of my clients and open up Software Center and click the Install button
    It fails with ""Error: 0x80070654" 
    I open up execmgr.log on the client using CMTrace and I use the error lookup tool and it shows that the 0x80070654 error is "This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer
    package"
    I also see a red highlighted line in the execmgr.log file with the following entry: "Script for Package:PRI00013, Program: SCCM 2012 R2 Management Console failed with exit code 2147944020"
    I can run ConsoleSetup.exe using a command line to the package source. 
    Execmgr.log Contents
    Policy arrived for parent package PRI00013 program SCCM 2012 R2 Management Console
    execmgr 7/31/2014 2:40:48 AM
    3336 (0x0D08)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 6l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:40:48 AM
    3336 (0x0D08)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramOfferReceivedEvent
    AdvertisementId = "PRI2000A";
    ClientID = "GUID:C83A938E-8BD7-4207-A450-11B3FE063DD6";
    DateTime = "20140731094048.938000+000";
    MachineName = "My Computer";
    ProcessID = 1548;
    SiteCode = "PRI";
    ThreadID = 3336;
    execmgr
    7/31/2014 2:40:48 AM 3336 (0x0D08)
    Raising client SDK event for class NULL, instance NULL, actionType 6l, value , user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:40:48 AM
    3568 (0x0DF0)
    Validating chain of dependent programs for package PRI00013 optional program SCCM 2012 R2 Management Console
    execmgr 7/31/2014 2:41:04 AM
    4612 (0x1204)
    Validating package PRI00013 program SCCM 2012 R2 Management Console in the chain. The content request ID is {00000000-0000-0000-0000-000000000000}
    execmgr 7/31/2014 2:41:04 AM
    4612 (0x1204)
    Creating an optional execution request for package PRI00013 program SCCM 2012 R2 Management Console
    execmgr
    7/31/2014 2:41:04 AM 4612 (0x1204)
    Requesting content from CAS for package PRI00013 version 1
    execmgr 7/31/2014 2:41:05 AM
    4612 (0x1204)
    Successfully created a content request handle {CBABEBB0-D019-4421-8B2E-47ABF90A925F} for the package PRI00013 version 1
    execmgr 7/31/2014 2:41:05 AM
    4612 (0x1204)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistWaitingContentEvent
    AdvertisementId = "PRI2000A";
    ClientID = "GUID:C83A938E-8BD7-4207-A450-11B3FE063DD6";
    DateTime = "20140731094105.334000+000";
    MachineName = "My Computer";
    PackageName = "PRI00013";
    PackageVersion = "1";
    ProcessID = 1548;
    ProgramName = "SCCM 2012 R2 Management Console";
    SiteCode = "PRI";
    ThreadID = 4612;
    execmgr
    7/31/2014 2:41:05 AM 4612 (0x1204)
    Successfully raised SoftDistWaitingContentEvent event for program SCCM 2012 R2 Management Console
    execmgr 7/31/2014 2:41:05 AM
    4612 (0x1204)
    Execution Request for advert  package PRI00013 program SCCM 2012 R2 Management Console state change from NotExist to WaitingContent
    execmgr 7/31/2014 2:41:05 AM
    4612 (0x1204)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:05 AM
    4612 (0x1204)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:05 AM
    5072 (0x13D0)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:05 AM
    4260 (0x10A4)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:05 AM
    4756 (0x1294)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:05 AM
    4756 (0x1294)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:05 AM
    5072 (0x13D0)
      Processing [{CBABEBB0-D019-4421-8B2E-47ABF90A925F}, 0]: OnContentAvailable
    execmgr
    7/31/2014 2:41:10 AM 4756 (0x1294)
    [{CBABEBB0-D019-4421-8B2E-47ABF90A925F}]: Content Version 1 is available for advert , pkg: PRI00013, program SCCM 2012 R2 Management Console.
    execmgr 7/31/2014 2:41:10 AM
    4756 (0x1294)
    An existing MTC token was not supplied, using ExecutionRequest's Id as MTC token and this execution request is the owner of resultant MTC task.
    execmgr 7/31/2014 2:41:10 AM
    4756 (0x1294)
    Request a MTC task for execution request of package PRI00013, program SCCM 2012 R2 Management Console with request id: {C9942D47-8A99-4363-AE69-A6F813336239}
    execmgr 7/31/2014 2:41:10 AM
    4756 (0x1294)
    Execution Request for advert  package PRI00013 program SCCM 2012 R2 Management Console state change from WaitingContent to Ready
    execmgr 7/31/2014 2:41:10 AM
    4756 (0x1294)
    MTC task with id {C9942D47-8A99-4363-AE69-A6F813336239}, changed state from 0 to 4
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:10 AM
    4756 (0x1294)
      Processing [{CBABEBB0-D019-4421-8B2E-47ABF90A925F}, 0]: RemoveNotification
    execmgr 7/31/2014 2:41:10 AM
    4756 (0x1294)
    MTC signaled SWD execution request with program id: SCCM 2012 R2 Management Console, package id: PRI00013 for execution.
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Sending ack to MTC for task with id: {C9942D47-8A99-4363-AE69-A6F813336239}
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Executing program ConsoleSetup.exe in Admin context
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Execution Request for advert  package PRI00013 program SCCM 2012 R2 Management Console state change from Ready to NotifyExecution
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Checking content location C:\Windows\ccmcache\eo for use
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Successfully selected content location C:\Windows\ccmcache\eo
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Executing program as a script execmgr
    7/31/2014 2:41:10 AM 4328 (0x10E8)
    Successfully prepared command line "C:\Windows\ccmcache\eo\ConsoleSetup.exe"
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Command line = "C:\Windows\ccmcache\eo\ConsoleSetup.exe", Working Directory = C:\Windows\ccmcache\eo\
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Running "C:\Windows\ccmcache\eo\ConsoleSetup.exe" with 32bitLauncher
    execmgr 7/31/2014 2:41:10 AM
    4328 (0x10E8)
    Created Process for the passed command line
    execmgr 7/31/2014 2:41:11 AM
    4328 (0x10E8)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramStartedEvent
    AdvertisementId = "PRI2000A";
    ClientID = "GUID:C83A938E-8BD7-4207-A450-11B3FE063DD6";
    CommandLine = "\"C:\\Windows\\ccmcache\\eo\\ConsoleSetup.exe\"";
    DateTime = "20140731094111.028000+000";
    MachineName = "My Computer";
    PackageName = "PRI00013";
    ProcessID = 1548;
    ProgramName = "SCCM 2012 R2 Management Console";
    SiteCode = "PRI";
    ThreadID = 4328;
    UserContext = "NT AUTHORITY\\SYSTEM";
    WorkingDirectory = "C:\\Windows\\ccmcache\\eo\\";
    execmgr
    7/31/2014 2:41:11 AM 4328 (0x10E8)
    Raised Program Started Event for Ad:PRI2000A, Package:PRI00013, Program: SCCM 2012 R2 Management Console
    execmgr 7/31/2014 2:41:11 AM
    4328 (0x10E8)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value NULL, user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:11 AM
    4328 (0x10E8)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:11 AM
    4328 (0x10E8)
    MTC task with id {C9942D47-8A99-4363-AE69-A6F813336239}, changed state from 4 to 5
    execmgr 7/31/2014 2:41:11 AM
    4612 (0x1204)
    Program exit code -2147023276 execmgr
    7/31/2014 2:41:11 AM 4756 (0x1294)
    Looking for MIF file to get program status execmgr
    7/31/2014 2:41:11 AM 4756 (0x1294)
    Script for Package:PRI00013, Program: SCCM 2012 R2 Management Console failed with exit code 2147944020
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramErrorEvent
    AdvertisementId = "PRI2000A";
    ClientID = "GUID:C83A938E-8BD7-4207-A450-11B3FE063DD6";
    DateTime = "20140731094111.506000+000";
    ExitCode = "-2147023276";
    MachineName = "My Computer";
    PackageName = "PRI00013";
    ProcessID = 1548;
    ProgramName = "SCCM 2012 R2 Management Console";
    SiteCode = "PRI";
    ThreadID = 4756;
    UserContext = "NT AUTHORITY\\SYSTEM";
    execmgr
    7/31/2014 2:41:11 AM 4756 (0x1294)
    Raised Program Error Event for Ad:PRI2000A, Package:PRI00013, Program: SCCM 2012 R2 Management Console
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    Execution is complete for program SCCM 2012 R2 Management Console. The exit code is -2147023276, the execution status is FailureNonRetry
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    Requesting MTC to delete task with id: {C9942D47-8A99-4363-AE69-A6F813336239}
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    MTC task with id: {C9942D47-8A99-4363-AE69-A6F813336239} deleted successfully.
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 10l, value Result:FALSE, user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    Requesting MTC to delete task with id: {C9942D47-8A99-4363-AE69-A6F813336239}
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    This execution request does not have a corresponding task in MTC.
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    Raising client SDK event for class CCM_Program, instance CCM_Program.PackageID="PRI00013",ProgramID="SCCM 2012 R2 Management Console", actionType 1l, value , user NULL, session 4294967295l, level 0l, verbosity 30l
    execmgr 7/31/2014 2:41:11 AM
    4756 (0x1294)
    CServiceWindowEventHandler::Execute - Received SERVICEWINDOWEVENT : END Event
    execmgr 7/31/2014 5:00:00 AM
    2928 (0x0B70)
    Thanks 

    Cool, mate it is then.
    Yeah it either changed or there is a typo. 
    I re-created everything and I still get that same 0x80070654 error.
    This is really frustrating
    Anyway, here is what I see in the AppEnforce.log:
    +++ Starting Install enforcement for App DT "SCCM 2012 R2 Management Console" ApplicationDeliveryType - ScopeId_DF08DF3D-39F7-4840-B17C-92FCAB02F116/DeploymentType_00b14782-2bc3-4c88-bc19-9d12981bc4ef, Revision - 1, ContentPath - C:\Windows\ccmcache\ev,
    Execution Context - System AppEnforce
    7/31/2014 11:27:30 PM 4256 (0x10A0)
        A user is logged on to the system.
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Performing detection of app deployment type SCCM 2012 R2 Management Console(ScopeId_DF08DF3D-39F7-4840-B17C-92FCAB02F116/DeploymentType_00b14782-2bc3-4c88-bc19-9d12981bc4ef, revision 1) for system.
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
    +++ Application not discovered. [AppDT Id: ScopeId_DF08DF3D-39F7-4840-B17C-92FCAB02F116/DeploymentType_00b14782-2bc3-4c88-bc19-9d12981bc4ef, Revision: 1]
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        App enforcement environment: 
    Context: Machine
    Command line: consolesetup.exe /q TargetDir="%ProgramFiles%\ConfigMgr" EnableSQM=0 DefaultSiteServerName=my.site.server
    Allow user interaction: No
    UI mode: 1
    User token: null
    Session Id: 2
    Content path: C:\Windows\ccmcache\ev
    Working directory:
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Prepared working directory: C:\Windows\ccmcache\ev
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Prepared command line: "C:\Windows\ccmcache\ev\ConsoleSetup.exe" /q TargetDir="C:\Program Files\ConfigMgr" EnableSQM=0 DefaultSiteServerName=my.site.server
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Executing Command line: "C:\Windows\ccmcache\ev\ConsoleSetup.exe" /q TargetDir="C:\Program Files\ConfigMgr" EnableSQM=0 DefaultSiteServerName=my.site.server with user context
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Working directory C:\Windows\ccmcache\ev
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Post install behavior is BasedOnExitCode
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Waiting for process 2792 to finish.  Timeout = 120 minutes.
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Process 2792 terminated with exitcode: 2147944020
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Looking for exit code -2147023276 in exit codes table...
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
        Unmatched exit code (2147944020) is considered an execution failure.
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)
    ++++++ App enforcement completed (0 seconds) for App DT "SCCM 2012 R2 Management Console" [ScopeId_DF08DF3D-39F7-4840-B17C-92FCAB02F116/DeploymentType_00b14782-2bc3-4c88-bc19-9d12981bc4ef], Revision: 1, User SID: ] ++++++
    AppEnforce 7/31/2014 11:27:30 PM
    4256 (0x10A0)

  • Available Software tab is missing from Software Center

    Some users are missing the available software tab in software center. This is software that can manually be installed and is not required. Is there any specific rules for this tab to show or not to show?

    Hi,
    Any updates?
    Please feel free to let us know if you need further assistance.
    Regards.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • LMS 4.2 Applications missing from Software Center

    I have a problem with LMS 4.2.4 Software center on Win2K8.  I have been trying to download device updates and the only product listed in software center has been:
    Inventory Config And Image Management
    It seems like this happened to me before and I opened a TAC case and got the list of products back but I can't seem to locate the case history.  To top it off my LMS support contract is in limbo due to some administrative glitch and I am waiting for my account team to sort it out.  Meanwhile I have just installed some relatively new products (3850, 4500-X) and LMS doesn't seem to recognize these completely.
    The list of apps seems to be stored in the NMSROOT\lib\classpath\com\cisco\nm\xms\psu\conf\tag.properties.  I stumbled accross a tag.pl script in the bin directory that modifies this file.  So I searched in vain for the proper contents for the tag.properties file.  In the end I just issued the following sequence to get common services back:
    cd <NMSROOT>\lib\classpath\com\cisco\nm\xms\psu\conf
    perl D:\Software\CSCOpx\bin\tag.pl tag.properties -a "cmf:Common Services"
    So I am not sure why a perl script to modify the tag.properties file is necessary since it just seems to append the specified product to the end of the file. In any event I then went to
    Admin > System > Software Center > Device Update
    and sure enough CMF appears and I am able to check for and install device updates for it.  However, I still seem to be unable to perform UT collection for the 3850 stack which is what I am really after.  So does anyone know what product I need to add and get updates for in order to get user tracking working?  In other words, what is the output of
    psucli.bat -h?
    Thanks,
    -Jeff

    Hi Jeff,
    looks like tag.prop is corrupted.
    it should have the below content :
    ipm:IPSLA Performance Management
    cmf:Common Services
    lmsportal:LMS Portal
    cvw:CiscoView
    rme:Inventory Config And Image Management
    dfm:Fault Management
    lms:LAN Management Solution
    upm:Device Performance Management
    cm:Network Topology Layer 2 Services and User Tracking
    Is this a new Installed ? if yes share the Installed.log
    if you have good backup ,then try retstoring it.
    Thanks-
    Afroz

  • Clients cant download application from software center [ error : 0x87d00607 ]

    I've got a small SCCM 2012 deployment with about 3 clients , these three clients cant download application available on software center!
    i checked out my boundries and boundries group and they are well configured .
    help plz

    i have just a subnet configuration in my boundary so there's no association against the site in AD
    Houda
    Subnet or IP ranges? Best to configure with IP ranges. 
    http://blog.configmgrftw.com/ip-subnet-boundaries-still-evil/
    Cheers Paul | http://sccmentor.wordpress.com

  • Screen resolution when PXE boot from WDS vs Install Windows 8.1 from USB

    Hi all
    I own a Lenovo ThinkPad T430s, X230 Tablet, and now have my hands on a T440. All three machines have UEFI Secure Boot enabled properly, i.e. Windows boot screen shows Lenovo logo instead of Windows logo.
    However, if I do a PXE boot (using Windows Deployment Services from Windows Server 2012, not R2) and boot to the same boot.wim provided on a Windows 8.1 ISO image, the boot screen resolution turns crap, and the WinPE environment runs in 640x480. Also, as opposed
    to the Lenovo logo showing on the boot screen, the Windows logo shows up instead, indicating it's not doing a secure boot?
    When booting from a USB stick however, using the same Windows 8.1 boot.wim (copied from ISO), the screen resolution in Windows Setup is detected correctly, and the Lenovo logo shows up.
    This occurs on all three machines since MDT was upgraded to MDT 2013 or when I replaced Windows 8 boot.wim with Windows 8.1 boot.wim (as the Windows ADK 8 --> ADK 8.1).
    Is there a fix for this? Do others have the same problem elsewhere?
    Many thanks 

    Hi,
    When boot UEFI-based computer from PXE you should take more into consideration.
    For some computers, you might have to perform additional steps to make sure that Windows is installed in UEFI mode, and not in legacy BIOS-compatibility mode.
    Some computers might support UEFI. However, they do not support a PXE-initiated boot when in UEFI mode.
    How to Create a PXE-Initiated Windows 8 Deployment for UEFI-Based or BIOS-Based Computers in Configuration Manager
    http://technet.microsoft.com/en-us/library/jj938037.aspx
    Especially for “Pre-Deployment Considerations”
    If you still cannot find a way to make it boot from UEFI mode, you should contact with manufacture to confirm if PXE-initiated boot is supported.
    Hope this helps.

  • Formatting the encrypted hard drive or intalling OS again with PXE boot can change TPM owner password file?

    Hello,
    1) I realized that when MBAM bitlocker encryption start both Recovery key and TPM owner password file are send to MBAM server. If we change the computername of the notebook, we can find out Recovery key from MBAM server with the KeyID as we can read it from
    computer screen, but we can not find out TPM owner password file with the existing new computername information from MBAM server, so we have to know old names of all computers but it is impossible. So we have to do decryption and clearing TPM than we
    can again encrypted it with its new name. is it right?
    2) We will going to deploy mbam encryption to our notebooks. But sometimes when a person quit the job his notebook can given to another person or new employee and based to our procedure when a notebook will given to another user it should installed
    OS again with PXE boot. I would to know will it be enough to installing with this method again with a diffrent computer name or should I firstly clear its TPM than install OS with PXE to keep TPM owner password file missing as item 1?
    I hope i can explain what i mean :)
    Regards,
    SibelM

    I would suggest you to first decrypt the laptop and then follow the process:-
    - Clear the TPM
    - Encrypt the type.
    - Check for the encryption behavior.
    Cause I have found on some model that if the OS drive is encrypted, PXE boot fail on that machine even though I also did a direct PXE on an encrypted machine with clearing the TPM.
    TPM ownership password is a hash file that gets generated with a set of algorithm. SO each time when you PXE boot, by clearing the TPM, the TPM hash password for the TPM will change. This has been done for security measures.  
    Gaurav Ranjan

  • Generation 2 vms pxe boot

    Hi All,
    can anyone please confirm if pxe boot works with gen 2 vms in hyperv? I have wds installed in standalone mode. When ever I create new gen 2 vm, it takes ip, downloads some file and it says 
    Station
    IP address is x.x.x.x
    Server
    IP address is x.x.x.x
    NBP filename is boot\x64\wdsmgfw.efi
    NBP
    filesize is 1459552 Bytes
    Downloading
    NBP file...
    PXE-E18: Server response timeout.
    Boot
    Failed. EFI SCSI Device
    Boot
    Failed. EFI Network.
    No
    Operating System was Loaded. Press a key to retry the boot sequence
    I have tried with and without enabling secure boot option. I have wds(standalone mode), MDT and gen 2 vms. Can anyone please guide me how to make gen 2 vms boot over pxe?
    Chaitanya.
    Chaitanya.

    Hi,
    You might need to set DHCP options 60, 66, 67 and 4011:
    60: set the identifier to "PXEClient" (without the quotes) - pop it in all the active (I put it in the inactive scopes as well, for over-zealous safety) DHCP scopes, just in case the request is picked up by another zone/scope (ensure there are
    sufficient IP addresses within the scope[s] - bit of daft point, but it wouldn't be the first time I have seen a PXE boot fail because there aren't any available IPv4 addresses)
    66: set the Boot Server Host Name "<boot_server_name>.<...>.<CN>.<CN>" or by IPv4 address
    67: set the Boot File Name; stop WDS from listening on UDP Port 67 - it will be used by DHCP:: ensure the full path is listed (verify this before running the PXEboot) - Just as side note, I tend to make the folder containing the file read/write - not sure
    it actually does anything, but it frequently makes things a bit "smoother".
    4011: ensure that PXE broadcasts from the clients are routed by WDS properly i.e.: the traffic should go to the appropriate server (DHCP, WDS and possibly BootTP if configured)
    Also, and don't take this wrong way, but check, check and check again that the boot order settings are set in the Hyper-V Manager correctly.  Time and time again I have come up against this one.  Sometimes, for whatever reason, Hyper-v will put
    the defaults back in, so you think you are booting off the network, and will be told as such, but will actually be booting off DVD/CD...
    Create a VM, open the settings and then start the VM; watch the settings in the left hand pane.   If all is well, there will no change, if all is not well, there may be a slight "jump" as the VM starts up.  
    Could be an idea to start DHCP from the command line - if you have access to it and there are no impediments, there isn't (shouldn't be) any problem with ensuring it has started. 
    Hope this helps
    - quick note, I'm not available for a couple of days but hopefully one of the other kind and generous souls on this site will assist you if you run into any problems.
    have a good one! :D
    Cheers
    Andrew
    Oh, just had thought, check that you are utilizing only one IP address per network adapter on the client, DHCP and WDS servers.  There's a conflict between DHCP and RIS - or at least used to be, not sure if it has been fixed/sorted. 
    Cheers! Andrew

Maybe you are looking for