locked
SCCM Task Sequence Fail to Connect Share Folder on SCCM server RRS feed

  • Question

  • those days we have an task sequence issue- can't connect to share folder on the SCCM server

    Enviroment

    in our network, we have DHCP server, DC server, DNS server. we are trying to bring up an new server to boot from the SCCM server. we have two VLAN in our environment. VLAN 54 and VLAN 200.

    the DHCP/DC/SCCM/DNS are all running on VLAN200

    Issue

    we have those steps in this task sequence

    • Installing OS
    • setup windows and configuration manager
    • connect to an share folder to SCCM(run some sicrpts)
    • run the scripts
    • install the sqlserver 

    1. when the VM running on VLAN 200, no issue on all the task list, we can access the share folder on SCCM server.

    and task sequence run ran success.

    2. but when VM running on VLAN 54, issue came. when the task sequence run into the [Setup Operation System]/[Connect to network folder]. this step can't get the share folder to sccm server.

    then the task sequcne was quit, so we logined to vm have a look.  run the ipconfig/all. no IP address get from DHCP server.

    but when we run the command  ipconfig/renew on this VM, then we can get the IP address from DHCP server.


    we have tried an alternative solution like below.

    add an step ipconfig/renew  before connect to share folder, then the task sequence can connect to share folder, but when the task run into last step- install the SQL from package.

    unfortunately, we came cross another issue.

    Failed to invoke Execution Manager to Install Software for PackageID='GDL00008' ProgramID='Install SQL 2005 Standard SP4' AdvertID='GDL2001F' hr=0x800706ba InstallSoftware 12/10/2013 11:48:17 PM 1012 (0x03F4)

    InstallSoftware failed, hr=0x800706ba InstallSoftware 12/10/2013 11:48:17 PM 1012 (0x03F4)

    Quetions

    so we suspect there may something to do with network, but the network team said there is no issue on their side. so what i can go to research, how can i fiind the root cause or how to confirm it is an network issue. do you guys have any idea on this issue?

    • Edited by Kevin Lan Wednesday, December 11, 2013 10:24 AM
    Tuesday, December 10, 2013 3:08 PM

Answers

  • The error means RPC server unavailable. TS needs to invoke Execution Manager by RPC. This may be caused by the issue of RPC starting. I suggest you check the RPC service availability first. Another try is to add a restart computer step before installing SQL. If still no avail, add a Delay "cmd.exe /c timeout /t 900".

    Regarding the connecting network share issue, seems the network services has not been initializing or ready. Another possibility is the DHCP time out. Check the Event log and this may give you some clues of why the network is not ready or DHCP cannot get IP address. Network Monitor can also be used to monitor the IP helper when the Client try to send DHCP request after reboot.


    Juke Chou

    TechNet Community Support

    • Marked as answer by Kevin Lan Tuesday, February 18, 2014 9:42 AM
    Friday, February 14, 2014 8:24 AM

All replies

  • it does really sound like a networking issue.   Can you do a ipconfig /renew and confirm it isn't getting any IP address from the DHCP server.    Also you may have to check your VM networking to make sure its setup correctly as well.

    J


    • Edited by jwtdrjj01 Tuesday, December 10, 2013 3:20 PM
    Tuesday, December 10, 2013 3:13 PM
  • yes, run the ipconfig/renew can get the IP address, we can sure the VM network setting is fine. so the issue is where we can checking this issue.
    Tuesday, December 10, 2013 3:17 PM
  • There are deployment logs on the client.   Have you enabled command line support in the boot images?

    If so, copy off the client osd logs and check for any network related errors.   If the machine was able to boot from pxe and start the task sequence then its not a network issue.

    x:\windows\temp\smstslog\smsts.log or
    x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log

    http://blogs.msdn.com/b/lxchen/archive/2009/04/03/a-list-of-sccm-log-files.aspx

    Tuesday, December 10, 2013 3:25 PM
  • will check, but if it is not the network  issue , the task sequence can work fine on VLAN 200, which same VALN with SCCM server. i am sure it is the VM didn't get the IP cause it can't connect to share folder.

    • Edited by Kevin Lan Wednesday, December 11, 2013 10:20 AM
    Tuesday, December 10, 2013 11:17 PM
  • The error means RPC server unavailable. TS needs to invoke Execution Manager by RPC. This may be caused by the issue of RPC starting. I suggest you check the RPC service availability first. Another try is to add a restart computer step before installing SQL. If still no avail, add a Delay "cmd.exe /c timeout /t 900".

    Regarding the connecting network share issue, seems the network services has not been initializing or ready. Another possibility is the DHCP time out. Check the Event log and this may give you some clues of why the network is not ready or DHCP cannot get IP address. Network Monitor can also be used to monitor the IP helper when the Client try to send DHCP request after reboot.


    Juke Chou

    TechNet Community Support

    • Marked as answer by Kevin Lan Tuesday, February 18, 2014 9:42 AM
    Friday, February 14, 2014 8:24 AM
  • hi juke, thanks for you great support. i added an - "computer restart" step before install the SQL. it can success complete all the TS steps. appreciate
    • Edited by Kevin Lan Tuesday, February 18, 2014 9:44 AM
    Tuesday, February 18, 2014 9:43 AM