none
unable to connect with distribution point RRS feed

  • Question

  • Hello,

    I'm trying to deploy windows 7, I have windows server 2007 with SP2 and sccm 2007 with SP2 R2, I'm trying to configure OSD to deploy windows 7, I create a new TS and advertise it to unknow computer.

    Computer start -> Receive IP from DHCP -> connetting to SCCM Server -> then enter password wizard start -> after entering password, he notify that TS will start in 15 sec, then freezing for 10 sec and give message that un able to connect to distribution point where boot image is located.

    Network drive already added and I could ping sccm server when it fail to connect with distribution point, any one have idea ?

    Regards
    Best Regards --- Abduljalil Abolzahab Technical Specialist - Microsoft Technical Forum: http://Forum.fourtyfivecorp.net
    Tuesday, February 2, 2010 6:18 AM

Answers

  • Ok, first you need to make sure that your boot image has "Command support" enabled. Open your boot image "Properties" > "Windows PE" tab, and check "Enable command support". When you click "OK", boot image will be updated, so you need to wait till the new source version appears on your distribution point.
    Now run your TS again and then failure occurs, press F8. It will open command prompt (note that as long as command prompt is open, TS will not restart your computer).
    The smsts.log is usually located in X:\Windows\Temp\SMSTSLog\ folder.

    I suppose you have network connection, so the easiest way to save this log to decent location is to map a network drive on some temporary share with NET USE Z: \\server\share and then copy X:\Windows\Temp\SMSTSLog\smsts.log to that share.
    • Marked as answer by Eric Zhang CHN Friday, February 26, 2010 3:37 AM
    Tuesday, February 2, 2010 7:36 AM

All replies

  • Did you check smsts.log for exact error message? Does it give you an ID of a package that is inaccessible on a distribution point?
    The most common issue is that some package that is used by TS has a hash mismatch, and you just need to update that package on distribution point(s) once.

    Tuesday, February 2, 2010 6:41 AM
  • when it fail the ID was for boot image, i already update it but still the same issue. 


    Best Regards --- Abduljalil Abolzahab Technical Specialist - Microsoft Technical Forum: http://Forum.fourtyfivecorp.net
    Tuesday, February 2, 2010 7:02 AM
  • Could you paste here the lines from smsts.log that show the failure? The error code may give some clue on a reason.
    Tuesday, February 2, 2010 7:12 AM
  • I didn't found SMSTS.log, maybe it's because TS didn't finish...
    Best Regards --- Abduljalil Abolzahab Technical Specialist - Microsoft Technical Forum: http://Forum.fourtyfivecorp.net
    Tuesday, February 2, 2010 7:26 AM
  • Ok, first you need to make sure that your boot image has "Command support" enabled. Open your boot image "Properties" > "Windows PE" tab, and check "Enable command support". When you click "OK", boot image will be updated, so you need to wait till the new source version appears on your distribution point.
    Now run your TS again and then failure occurs, press F8. It will open command prompt (note that as long as command prompt is open, TS will not restart your computer).
    The smsts.log is usually located in X:\Windows\Temp\SMSTSLog\ folder.

    I suppose you have network connection, so the easiest way to save this log to decent location is to map a network drive on some temporary share with NET USE Z: \\server\share and then copy X:\Windows\Temp\SMSTSLog\smsts.log to that share.
    • Marked as answer by Eric Zhang CHN Friday, February 26, 2010 3:37 AM
    Tuesday, February 2, 2010 7:36 AM