locked
Site connectivity and PXE boot errors. RRS feed

  • Question

  • Hi - I wonder if anyone could help. We have system centre 2012r2. Now, before I get going ive not that much experience with sccm so I'm not very familiar with it. To give a bit of background we have a central server (which apparently is working fine) but most if not all the downstream server are not working correctly (my own is not working atall). Initially ive got an old dell e6400 in front of me which is a test machine.

    This is my initial problem but this is really just the end part of the problem. I can see connectivity problems between the source server and my downstream server also looking at my smspxe.log file I'm seeing this....

    Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 10/07/2016 08:09:43 888 (0x0378)

    MAC Ignore List Filename in registry is empty SMSPXE 10/07/2016 08:09:43 888 (0x0378)

    This repeats a few times also.

    In the sccm server I'm seeing a message saying distribution manger failed to connect to the distribution point "check your network and firewall settings" - on that front everything is good, ive got good connectivity, ns lookup is working fine, pings are responding and both network browsers on both the master and the slave server are good ( my server is also a downstream server of WSUS which is working fine.

    So sorry to jump around a bit but if anyone could offer a starting point of where to look id appreciate it - cheers.!

    Thursday, September 15, 2016 8:45 AM

Answers

  • TS is task sequence 

    so once you distribute the TS on DPs, then it will distribute to all packages to DP which are added into TS

    so you dont have to wait for long to wait for TS to get fail then identify the package  then distribute them on dp


    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Wednesday, September 21, 2016 8:50 AM

All replies

  • Do you mean you have an SCCM primary site, and a distribution point? If so, is the computer account of your SCCM server part of the local admins on the distribution point?

    When you PXE boot like in the above screenshot, what is in the smspxe.log?

    Have you distributed the boot images to your distribution point?

    Is the distribution point enabled for PXE? and how do you image machines, via unknown computer support or by importing the mac address?


    Thursday, September 15, 2016 8:56 AM
  • could you please provide complete log file smspxe

    and confirm if the boot images are available on DP?


    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Thursday, September 15, 2016 9:01 AM
  • I suggest generating an offline boot media to verify the deployment works.

    https://technet.microsoft.com/en-au/library/hh397285.aspx this way you dont have to rely on pxe boot for dpeloyment and can just use USB. 

    It doesn't solve your current problem but at least provides a work around for the time being.

    PXE issues can be difficult to solve due to various reasons.

    Thursday, September 15, 2016 9:02 AM
  • Hi - yes - I am finding that out the hard way....it seems from what I can see from a fault finding perspective would be to start on the source server first??
    Thursday, September 15, 2016 9:49 AM
  • could you please provide complete log file smspxe

    and confirm if the boot images are available on DP?


    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Which smspxe log do you need ? from the source server or the downstream server? or both??
    Thursday, September 15, 2016 10:03 AM
  • I suggest generating an offline boot media to verify the deployment works.

    https://technet.microsoft.com/en-au/library/hh397285.aspx this way you dont have to rely on pxe boot for dpeloyment and can just use USB. 

    It doesn't solve your current problem but at least provides a work around for the time being.

    PXE issues can be difficult to solve due to various reasons.

    Its not a great problem at the moment so I don't necessarily need to boot from it - we do use acronis images at the moment while its not working....not the best solution but while I'm fault finding its ok...better to concentrate on the problem at hand - I will however go looking as its a good thing to be able to know....thanks very much.
    Thursday, September 15, 2016 10:21 AM
  • Created a usb bootable stick (thanks for the link) but it completes with "failed to run task sequence" so, has it failed because I configured the stick incorrectly or, because its cant connect to a task on the server in assuming there are other issues on the server.
    Thursday, September 15, 2016 10:38 AM
  • ...looking at my smspxe.log file I'm seeing this....

    Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 10/07/2016 08:09:43 888 (0x0378)

    MAC Ignore List Filename in registry is empty SMSPXE 10/07/2016 08:09:43 888 (0x0378)

    This repeats a few times also.

    those two lines in smspxe.log are perfectly normal (in almost all scenarios) - it's basically an informational entry, not a warning nor error.

    the smspxe.log on the server which *should* be offering boot services to the client machine, is where you can start.
    here's a new-ish guide: https://support.microsoft.com/en-au/help/10082/troubleshooting-pxe-boot-issues-in-configuration-manager-2012


    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Thursday, September 15, 2016 10:45 AM
  • Hi,

        >>"In the sccm server I'm seeing a message saying distribution manger failed to connect to the distribution point "check your network and firewall settings""

        Have you check the distmgr.log and SMSdpmon.log on your site server for more details? A healthy DP is required for PXE boot.

        Additionally, like others mentioned. You will have to check the following settings:

         1. Both x64/x86 boot images with this option " Deploy this boot image from the PXE service point " enabled.

         2. Both x64/x86 boot images have been distributed to the DP successfully.

         3. Enable PXE on the DP property and tick the "Enable unknown computer support " option. Make sure the WDS role has been installed correctly and the WDS service is running.  

         4. Make sure you have configured the IPhelper (or DHCP options 66,67) correctly if the device are in the subnet/vlan which separated from your PXE-enabled DP server.

         5. SMSPXE.log on your DP server.

        Hope it helps.

    Best regards,

    Jimmy


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 15, 2016 10:54 AM
  • Hi - ok - going through the process...

    1. yes this is selected.

    2. That I cant comment on - not sure if they are or not (as the distribution log is saying its failed)

    3. Yes, both these options are correct.

    4. Not had to have this set before - the server used to work....I might add that the server was rebuilt from scratch and given the same name and ip number (the reason was to upgrade the server from server 2008r2 to 2012r2)

    heres the log....thanks very much for the replies so far...

    I have been trawling the net and this morning ive tried removing the dp (my local site server) remoted in from the master server and then recreating it. This has happened successfully but not got a definitive result yet as I think things are still happening.

    ================= PXE Provider loaded. ===================== SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Machine is running Windows Longhorn. (NTVersion=0X603, ServicePack=0) SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    MAC Ignore List Filename in registry is empty SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Begin validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Completed validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Initializing PXEPerfObject. SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Could not load logging configuration for component ccmperf. Using default values. SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="0" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
     SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    PXE::CBootImageInfo::CBootImageInfo: key= SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Adding PRE00004.8 SMSPXE 15/09/2016 12:50:17 38864 (0x97D0)
    Adding PRE00005.10 SMSPXE 15/09/2016 12:50:18 38864 (0x97D0)
    Found new image PRE00004 SMSPXE 15/09/2016 12:50:32 38864 (0x97D0)
    ADK installation root registry value not found. SMSPXE 15/09/2016 12:50:32 38864 (0x97D0)
    Loaded C:\Windows\system32\wimgapi.dll SMSPXE 15/09/2016 12:50:32 38864 (0x97D0)
    Opening image file E:\RemoteInstall\SMSImages\PRE00004\boot.PRE00004.wim SMSPXE 15/09/2016 12:50:32 38864 (0x97D0)
    Found Image file: E:\RemoteInstall\SMSImages\PRE00004\boot.PRE00004.wim
     PackageID: PRE00004
     ProductName: Microsoft® Windows® Operating System
     Architecture: 0
     Description: Microsoft Windows PE (x86)
     Version: 
     Creator:
     SystemDir: WINDOWS
     SMSPXE 15/09/2016 12:50:32 38864 (0x97D0)
    Closing image file E:\RemoteInstall\SMSImages\PRE00004\boot.PRE00004.wim SMSPXE 15/09/2016 12:50:32 38864 (0x97D0)
    InstallBootFilesForImage failed. 0x80004005 SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\PRE00004\boot.PRE00004.wim.
    The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    Failed adding image E:\RemoteInstall\SMSImages\PRE00004\boot.PRE00004.wim. Will Retry..
    Unspecified error (Error: 80004005; Source: Windows) SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    File E:\RemoteInstall\SMSTemp\2016.09.15.12.50.32.01.{8E8F38A1-F9AD-4D13-A041-334A9FD913D2}.boot.bcd deleted. SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    File E:\RemoteInstall\SMSTemp\2016.09.15.12.50.32.01.{8E8F38A1-F9AD-4D13-A041-334A9FD913D2}.boot.bcd.log deleted. SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    Found new image PRE00005 SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    ADK installation root registry value not found. SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    Loaded C:\Windows\system32\wimgapi.dll SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    Opening image file E:\RemoteInstall\SMSImages\PRE00005\boot.PRE00005.wim SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    Found Image file: E:\RemoteInstall\SMSImages\PRE00005\boot.PRE00005.wim
     PackageID: PRE00005
     ProductName: Microsoft® Windows® Operating System
     Architecture: 9
     Description: Microsoft Windows PE (x64)
     Version: 
     Creator:
     SystemDir: WINDOWS
     SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    Closing image file E:\RemoteInstall\SMSImages\PRE00005\boot.PRE00005.wim SMSPXE 15/09/2016 12:50:36 38864 (0x97D0)
    InstallBootFilesForImage failed. 0x80004005 SMSPXE 15/09/2016 12:50:41 38864 (0x97D0)
    Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\PRE00005\boot.PRE00005.wim.
    The operation completed successfully. (Error: 00000000; Source: Windows) SMSPXE 15/09/2016 12:50:41 38864 (0x97D0)
    Failed adding image E:\RemoteInstall\SMSImages\PRE00005\boot.PRE00005.wim. Will Retry..
    Unspecified error (Error: 80004005; Source: Windows) SMSPXE 15/09/2016 12:50:41 38864 (0x97D0)
    File E:\RemoteInstall\SMSTemp\2016.09.15.12.50.36.02.{D1900E5E-0AF7-48F1-B1CD-C768CF3AC481}.boot.bcd deleted. SMSPXE 15/09/2016 12:50:41 38864 (0x97D0)
    File E:\RemoteInstall\SMSTemp\2016.09.15.12.50.36.02.{D1900E5E-0AF7-48F1-B1CD-C768CF3AC481}.boot.bcd.log deleted. SMSPXE 15/09/2016 12:50:41 38864 (0x97D0)
    Found new image PRE00004 SMSPXE 15/09/2016 12:50:41 36564 (0x8ED4)
    ADK installation root registry value not found. SMSPXE 15/09/2016 12:50:41 36564 (0x8ED4)
    Loaded C:\Windows\system32\wimgapi.dll SMSPXE 15/09/2016 12:50:41 36564 (0x8ED4)
    Opening image file E:\RemoteInstall\SMSImages\PRE00004\boot.PRE00004.wim SMSPXE 15/09/2016 12:50:41 36564 (0x8ED4)
    Found Image file: E:\RemoteInstall\SMSImages\PRE00004\boot.PRE00004.wim
     PackageID: PRE00004
     ProductName: Microsoft® Windows® Operating System
     Architecture: 0
     Description: Microsoft Windows PE (x86)
     Version: 
     Creator:
     SystemDir: WINDOWS
     SMSPXE 15/09/2016 12:50:41 36564 (0x8ED4)
    Closing image file E:\RemoteInstall\SMSImages\PRE00004\boot.PRE00004.wim SMSPXE 15/09/2016 12:50:41 36564 (0x8ED4)
    Begin validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 15/09/2016 12:50:41 38864 (0x97D0)
    Completed validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 15/09/2016 12:50:41 38864 (0x97D0)
    PXE Provider finished loading. SMSPXE 15/09/2016 12:50:41 38864 (0x97D0)
    Cannot read the registry value of MACIgnoreListFile (800703e5) SMSPXE 15/09/2016 12:50:56 26200 (0x6658)
    MAC Ignore List Filename in registry is empty SMSPXE 15/09/2016 12:50:56 26200 (0x6658)
    Found new image PRE00005 SMSPXE 15/09/2016 12:50:56 36564 (0x8ED4)
    ADK installation root registry value not found. SMSPXE 15/09/2016 12:50:56 36564 (0x8ED4)
    Loaded C:\Windows\system32\wimgapi.dll SMSPXE 15/09/2016 12:50:56 36564 (0x8ED4)
    Opening image file E:\RemoteInstall\SMSImages\PRE00005\boot.PRE00005.wim SMSPXE 15/09/2016 12:50:56 36564 (0x8ED4)
    Found Image file: E:\RemoteInstall\SMSImages\PRE00005\boot.PRE00005.wim
     PackageID: PRE00005
     ProductName: Microsoft® Windows® Operating System
     Architecture: 9
     Description: Microsoft Windows PE (x64)
     Version: 
     Creator:
     SystemDir: WINDOWS
     SMSPXE 15/09/2016 12:50:56 36564 (0x8ED4)
    Closing image file E:\RemoteInstall\SMSImages\PRE00005\boot.PRE00005.wim SMSPXE 15/09/2016 12:50:56 36564 (0x8ED4)
    Cannot read the registry value of MACIgnoreListFile (00000000) SMSPXE 15/09/2016 13:30:25 6616 (0x19D8)
    MAC Ignore List Filename in registry is empty SMSPXE 15/09/2016 13:30:25 6616 (0x19D8)

    Thursday, September 15, 2016 12:52 PM
  • from log file I can see boot image is not updated on DP properly.

    Please remove the boot image from DP, wait for complete the activity and make sure boot image is successfully removed from DP, check the distmgr.log file

    then again add boot image  into DP. 

    is you see the same  error then update the boot image (right click on boot image and select update content)


    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Thursday, September 15, 2016 1:31 PM
  • Do I remove the boot image from the source server or using the downstream server (mine locally here) - and should I remove a folder manually from the storage area on my local server ?

    If I remove it from the source server wouldn't I remove it from all other downstream servers at the same time...?

    • Edited by Comfy Thursday, September 15, 2016 1:45 PM
    Thursday, September 15, 2016 1:43 PM
  • Do I remove the boot image from the source server or using the downstream server (mine locally here) - and should I remove a folder manually from the storage area on my local server ?

    NO, you don't need to remove the folder.

    you can go to SCCM console and find the DP which have the issue, go to property and in content tab find the boot image and remove that. 

    then wait for some time to complete the task and once finish, wait for an hour then distribute it to DP again. 


    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    • Proposed as answer by SinghSharad Friday, September 16, 2016 1:38 AM
    Thursday, September 15, 2016 1:47 PM
  • Ok - ill try that next and let you know. Thanks very much for your help so far.
    Thursday, September 15, 2016 2:34 PM
  • Ok - well - its getting better - pxe boot is now kind of working....

    Contacting server: IP number

    TFTP Download: smsboot\x64\abortpxe.com

    PXE Boot aborted. Booting to next device....

    PXE-MOF: exiting intel boot agent.

    so as you can see its getting better....

    Ok- went looking and found that the laptop in question was already known to SCCM - so, ive removed it and ive got a successful pxe boot into the win PE environment but its fails at the task sequence now...says "XXX0001 cannot be located on a distribution point"


    • Edited by Comfy Thursday, September 15, 2016 3:10 PM
    Thursday, September 15, 2016 3:04 PM
  • so as you can see its getting better....

    Ok- went looking and found that the laptop in question was already known to SCCM - so, ive removed it and ive got a successful pxe boot into the win PE environment but its fails at the task sequence now...says "XXX0001 cannot be located on a distribution point"

    earlier, you removed the DP role. So you'll need to check that packages etc have been distributed to this DP, and if needed, re-distribute the desired packages to this DP again.

    Don [doesn't work for MSFT, and they're probably glad about that ;]

    Thursday, September 15, 2016 8:53 PM
  • Ok - well - its getting better - pxe boot is now kind of working....

    Contacting server: IP number

    TFTP Download: smsboot\x64\abortpxe.com

    PXE Boot aborted. Booting to next device....

    PXE-MOF: exiting intel boot agent.

    so as you can see its getting better....

    Ok- went looking and found that the laptop in question was already known to SCCM - so, ive removed it and ive got a successful pxe boot into the win PE environment but its fails at the task sequence now...says "XXX0001 cannot be located on a distribution point"


    Make sure all TS reference packages are available on DP, if not then distribute them on DP. 

    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Friday, September 16, 2016 1:40 AM
  • Ok- I'm working off site today so I don't have physical access to the laptop to be able to test....ill be in working on sunday so ill update you then. Thanks for the reply back.
    Friday, September 16, 2016 9:24 AM
  • Hi - well, I'm not sure whats happened between then and now but ive lost the ability to pxe boot again with the same error. Opening SMSPXE.log doesn't register that anything has actually connected to try to get an ip address...these are the last 4 logs...Begin validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 18/09/2016 06:50:28 18304 (0x4780)
    Completed validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 18/09/2016 06:50:28 18304 (0x4780)
    Begin validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 18/09/2016 07:50:27 30136 (0x75B8)
    Completed validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 18/09/2016 07:50:27 30136 (0x75B8)

    The last error is approx. an hour before I tried to pxeboot...

    I also tried to update the x86 and x84 boot images and the x64 boot image fails with errors.

    Ive tried removing the x64 boot image and adding it in again which has been successful - ive added one network driver back in but for some reason It wont let me add in additional drivers (when I highlight a driver the "ok" box is greyed off).
    • Edited by Comfy Sunday, September 18, 2016 10:00 AM
    Sunday, September 18, 2016 9:00 AM
  • Hi - just to add to this ive since worked out how to reinject the drivers into the boot image which ive done but I'm still stuck with the pxe error "PXE-E53: No boot filename received. So, effectively back where I started.!
    Monday, September 19, 2016 3:22 PM
  • Hi - well, I'm not sure whats happened between then and now but ive lost the ability to pxe boot again with the same error. Opening SMSPXE.log doesn't register that anything has actually connected to try to get an ip address...these are the last 4 logs...Begin validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 18/09/2016 06:50:28 18304 (0x4780)
    Completed validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 18/09/2016 06:50:28 18304 (0x4780)
    Begin validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 18/09/2016 07:50:27 30136 (0x75B8)
    Completed validation of Certificate [Thumbprint 172B9C4070B01DCBE6C6519D25750308AB190A45] issued to '7511459c-8de0-47fe-8bc9-1b7fd8ff0645' SMSPXE 18/09/2016 07:50:27 30136 (0x75B8)

    The last error is approx. an hour before I tried to pxeboot...

    I also tried to update the x86 and x84 boot images and the x64 boot image fails with errors.

    Ive tried removing the x64 boot image and adding it in again which has been successful - ive added one network driver back in but for some reason It wont let me add in additional drivers (when I highlight a driver the "ok" box is greyed off).
    Boot image is not updated successfully. seems some drivers are also not inserted. do you have any antivirus in your site server, if yes then disable that for some time and then again try to add the driver into boot image and update that on DP.

    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Monday, September 19, 2016 3:30 PM
  • don't remove the boot image, do that for update the content, it will update the version of boot image 

    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Monday, September 19, 2016 3:31 PM
  • Well, obviously I did remove it (and put it back on again)....I had already done that by the time you returned my post. I did go through the options of the x86 boot image and match that. How do I know which boot image my test laptop (Latitude e6400) will use?

    I have checked my dhcp server and the laptop is not even requesting an ip from that initially (nothing has changed on the dhcp server) and it is working correctly at the moment.

    For some reason (ive no idea why) the WDS service was off...ive restarted that and can now see this in the smspxe.log....

    So, I think, this tells me the laptop is asking for a package but sccm doesn't know what to give to it...?

    Ok- so editing this and adding to it ive gotten it working again to where I was before...I removed the x64 boot image which in turn removed it from the task sequences so I needed to add them back in to all the images. So I'm back at the point where I was before....

    So, where do I locate PRE00002. I'm guessing this has not been synchronized down to my server from the master....


    • Edited by Comfy Tuesday, September 20, 2016 10:57 AM
    Tuesday, September 20, 2016 7:12 AM
  • Ok - so ive found PRE00002 its called "Configuration Manager Client Package" - it says its "in progress" but if I "view status" I get an asset message saying "You must manually prestage the package PRE00002 on the distribution point before the content will be available....

    Tuesday, September 20, 2016 11:23 AM
  • Sounds like I'm talking to myself but I thought id document what I'm doing for the good of whoever gets into the same problem - I found I had a checkbox ticked in the properties of my local distribution point server in the general tab called "Enable this distribution point for prestaged content" mine was checked the other site servers weren't so, ive removed the checkbox and resynced the above package which has worked. Now ive got a different package error PRE00017 which I'm guessing I need to redistribute now this particular package ive found in "All DP's" so ive right clicked and "update distribution points".

    Tuesday, September 20, 2016 12:18 PM
  • Ok - so ive found PRE00002 its called "Configuration Manager Client Package" - it says its "in progress" but if I "view status" I get an asset message saying "You must manually prestage the package PRE00002 on the distribution point before the content will be available....

    Yes if the package is not available on DP then you would have to do the prestage, that is fast and effective 

    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    • Proposed as answer by SinghSharad Thursday, September 22, 2016 3:38 PM
    Tuesday, September 20, 2016 12:38 PM
  • Sounds like I'm talking to myself but I thought id document what I'm doing for the good of whoever gets into the same problem - I found I had a checkbox ticked in the properties of my local distribution point server in the general tab called "Enable this distribution point for prestaged content" mine was checked the other site servers weren't so, ive removed the checkbox and resynced the above package which has worked. Now ive got a different package error PRE00017 which I'm guessing I need to redistribute now this particular package ive found in "All DP's" so ive right clicked and "update distribution points".

    With the help of task sequence reference you can see how many packages are not available on DP, then you can do the prestage or distribute them on DP.

    one more thing you can do, just distribute the TS on DP, then whatever packages are added into TS, they will be distributed to DP. 


    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Tuesday, September 20, 2016 12:40 PM
  • Hi - getting a bit lost with the acronyms now...! whats the TS?

    Just to add I'm working my way through the list and redistributing the content down to my local server...

    Anything that comes up as failed, if I right click I can then "Redstribute content" - so I'm assuming this just restarts the process. Again I'm only putting this all in just in case anyone else comes across this problem as its quite a confusing bit of software to use, if you've not had much experience with it.
    • Edited by Comfy Wednesday, September 21, 2016 8:05 AM
    Wednesday, September 21, 2016 7:59 AM
  • TS is task sequence 

    so once you distribute the TS on DPs, then it will distribute to all packages to DP which are added into TS

    so you dont have to wait for long to wait for TS to get fail then identify the package  then distribute them on dp


    Sharad Singh | My blogs: SharadTech | Twitter: @SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

    Wednesday, September 21, 2016 8:50 AM
  • Ok - well after manually going through and removing and resyncing all of the packages im up and running. Thanks so much for all of your help. Just to finish this now its actually running is that we have some images on there that were built when the system was installed. We had no prior knowledge of it so the lads that installed it initially helped us. Id now like to start to adjust and update those said images with new apps (ie our ip phone app has been upgraded, the build has ie9 on it - id like to take it to ie 11) and also get all the latest windows updates on there. I strongly suspect ill be posting again but if youve got a few links that would help also.

    Thanks again for all of your help.

    Thursday, September 22, 2016 11:13 AM