locked
Branch DP setup after pulldp.msi installs takes hours RRS feed

  • Question

  • I've noticed on the last dozen of these I've setup that the time from when I see

    "started process msiexec.exe /quiet /I d:\SMS_DP$\sms\bin\pulldp.msi /log D:\SMS_DP$\sms\logs\pulldp_install.log"

    to when I see...

    "CreateSignatureShare, connecting to DP"

    can be HOURS..  at worst I've seen some take 12 hours.  One here in the US with very good connectivity took 3 and a half hours on a Saturday - while one in Brazil on Friday was installed and operational in an hour.

    Any thoughts?  I don't see any errors.

    CM12 R2 CU4.  Single Primary (US), (4) secondary sites (UK, EMEA, Asia).  About 120 branch DP's now.  All the Pull DP's pull from a different DP, not the primary site server itself.. so it should not be because the sender is busy.. then again they wouldn't use the sender anyway..

    I will be applying R2 SP1 when it's available on volume license site.. 

    Tuesday, May 19, 2015 7:50 PM

All replies

  • You could use process monitor or Netmon/Wireshark to see what's going on behind the scenes.

    Torsten Meringer | http://www.mssccmfaq.de

    Tuesday, May 19, 2015 8:19 PM
  • Yes, I've used process monitor and I see the install finish.. then nothing happens.  I havn't bothered with WireShark for this issue.. I may have to do that for the next one.
    Tuesday, May 19, 2015 9:01 PM