Jump to content


shineknox

Established Members
  • Posts

    22
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by shineknox

  1. I've built a task sequence to build and capture our reference image; windows 10. I have been successful in the build and capture task sequence. I have a couple of application installations built into the task sequence; MS Office 2016 and Chrome. So far so good. The big issue I see with the process is that there is no suspend task. I was hoping for a suspend task, so I could configure the default profile and maybe be able to use copyprofile with the sysprep task. I need to be able to set up a default profile and leverage copy profile in the build and capture task sequences. Anyone know how to accomplish this or have recommendations on configuring a default profile in the build and capture task sequence?

  2. I've built a task sequence to build and capture our reference image; windows 10. I have been successful in the build and capture task sequence. I have a couple of application installations built into the task sequence; MS Office 2016 and Chrome. So far so good. The big issue I see with the process is that there is no suspend task. I was hoping for a suspend task, so I could configure the default profile and maybe be able to use copyprofile with the sysprep task. I need to be able to set up a default profile and leverage copy profile in the build and capture task sequences. Does anyone know how to accomplish this or have recommendations on configuring a default profile in the build and capture task sequence?

     

    Thanks,

    Shine

     

  3. One thing i can't stand about forums is no one responding back to how they fixed their issue. I hope this helps someone down the road.

     

    I just got off the phone with support and this was their fix as well. They said it's a client side issue with certificates being corrupt.

     

    ERROR:

    Error. Status code 500 returned OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    Received 1231 byte response. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    pReply != NULL, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2391) OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    SMP Root share info response is empty OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005). OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    ExecuteRootShareInfoRequest(sRootShareList), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1717) OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    Request to SMP 'http://myservername.domain.com'failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    Sleeping for 60 seconds before next attempt to locate an SMP. OSDSMPClient 7/25/2016 4:25:28 PM 5656 (0x1618)

    Retry number 2 OSDSMPClient 7/25/2016 4:26:28 PM 5656 (0x1618)

     

    Microsoft's response

    ++ It looks like there is certificate issues while performing the restoration task.

     

    ++ Please run following command under PowerShell (As Admin )

     

    · Remove-Item -Path ‘HKLM:\SOFTWARE\Microsoft\SystemCertificates\SMS\Certificates\*’ -force;

     

    · restart-service ccmexec

     

     

     

    Sunshine

    • Like 1
    • Thanks 1
  4. I created another DP with site migration point enabled and still a no go.

     

    List of errors below:

    SMP Root share info response is empty OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4)
    ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005). OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4)
    ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4)
    ExecuteRestoreRequestToSMP failed (0x80004005). OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4)
    ExecuteRestoreRequest failed (0x80004005). OSDSMPClient 7/25/2016 11:23:10 AM 3524 (0x0DC4)
    Failed to run the action: Request State Store. Unknown error (Error: 00004005; Source: Unknown) TSManager 7/25/2016 11:23:10 AM 3292 (0x0CDC)
    Task Sequence Engine failed! Code: enExecutionFail TSManager 7/25/2016 11:23:10 AM 3292 (0x0CDC)
    The weird thing is that the capture state is working.
    Any help would be greatly appreciated.
    Thanks
    Sunshine
  5. I've hit this wall. I'm able to run the task sequence successfully on a machine, but I'm receiving error "Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.

    If the client is not yet registered, this is expected behavior." on another machine. I've deleted record in SCCM and computer object in Active directory and re-imaged the machine; i'm still receiving the error above. The record in SCCM looks fine. This is aggravating how inconsistent SCCM is; boooooo!!!!!.
    Any help is greatly appreciated.
    Sunshine
  6. I've deleted the computer account in Active Directory and removed the record from SCCM. I re-imaged the machine and new records were created in both Active Directory and SCCM. I'm still receiving the error below when I try to do a machine policy retrieval.

     

    Error:

    Software Distribution site settings (CCM_SoftwareDistributionClientConfig) policy does not yet exist on the client.
    If the client is not yet registered, this is expected behavior. execmgr 7/21/2016 9:36:01 AM 3740 (0x0E9C)
    Can not find client site settings execmgr 7/21/2016 9:36:01 AM 3740 (0x0E9C)

     

    Not really sure what is going on here. The record in SCCM seems to match up with the client.
    Thanks
    Sunshine
  7. I was successful with moving a windows 7 profile to a windows 10 machine, using a different machine. The error seemed to be related to two of my test machines; I have a pool of 8 test machines. Is there pre-checks I can setup to make sure there is no issues with machines client? The bad thing about it is that it reports fine in SCCM, but seems to be an error at the client level not thinking it's registered with SCCM.

     

    Thanks,

    Sunshine Baines

  8. I've ran into a road block with using USMT on SCCM 2012 R2 version 5.00.8239.1000 and build number 8239. I've made the computer associations before running the capture and the capture works. It only fails when I run the restore task sequence. The source is a windows 7 machine and the destination is running windows 10. The whole process fails when restoring to my windows 10 machine. This is a side by side backup and restore. We are running Win 10 ADK on the SCCM server.

     

    Here are some of the errors listed.

     

    SMP Root share info response is empty OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    ClientRequestToSMP::ClientRootShareRequestToSMP failed. error = (0x80004005). OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    ExecuteRootShareInfoRequest(sRootShareList), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1717) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    ClientRequestToSMP::DoRequest failed. error = (0x80004005). OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    Request to SMP 'http://servername_of_DP_MP.domain.com'failed with error (Code 0x80004005). Trying next SMP. OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    FALSE, HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,1657) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    Failed to find an SMP that can serve request after trying 4 attempts. OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    pClientRequestToSMP->Execute(migInfoFromMP.saSMPs), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2866) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    ExecuteRestoreRequestToSMP failed (0x80004005). OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    ExecuteRestoreRequestToSMP(migInfoFromMP), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\smpclient.cpp,2931) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    ExecuteRestoreRequest failed (0x80004005). OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    ExecuteRestoreRequest(), HRESULT=80004005 (e:\qfe\nts\sms\client\osdeployment\osdsmpclient\main.cpp,84) OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    OSDSMPClient finished: 0x00004005 OSDSMPClient 7/20/2016 3:55:14 PM 84 (0x0054)
    Process completed with exit code 16389 TSManager 7/20/2016 3:55:14 PM 5232 (0x1470)
    Thanks,
    Sunshine
  9. I have a process in place to backup machines before doing an operating system deployment; no sysprep is involved with the backup process. I did this using the ZTIbackup.wsf script that comes with MDT. In short, I've integrated MDT 2013 with SCCM 2012 R2. Is there a way to deploy the backed up image (wim) using SCCM with no sysprep? I need to be able to deploy the backed up image back to the machine; Obviously, this will be a worse case scenario.

     

    Thanks in advanced for the input.

     

    shineknox

  10. I'm currently using SCCM 2012 R2 Version 5.00.8239.1000 build 8239. I've been given the task of transitioning over to Windows 10 from Windows 7. Unfortunately this is my first go with SCCM. I would like to deploy a bare-metal windows 10 image via PXE and leverage USMT to pull the profiles from the Windows 7 machine being migrated to windows 10; I do not want to do an in place upgrade. I've went through some how tos that I found in forums because MS has no white papers on the process; this however did not work.

     

    One thing I noticed is that deploy doesn't seem to ah, deploy; really aggravating. I monitored the ccm logs to see if I see any action and it seems to do nothing. I built the task sequence with the wizard and pointed it to the USMT package, but it never seems to kick off.

     

    Maybe I'm missing something and any help would be greatly appreciated.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.