Jump to content


bloodjun

Established Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bloodjun

  • Rank
    Newbie
  1. This issue arose a few days ago, and I have been struggling ever since. I captured two images from two separate machines. Then, I went through the normal steps of adding the OS's to SCCM. Steps I've done dozens of times. Everything is peachy. I then proceed to distribute the content. Seems to go alright until I get a dreaded red circle. Happens to both. So, I check on the Content Status and it says: "Distribution Manager failed to access the source directory "sharepath." I then check the path. Make sure SCCM (the server's name) has access to it. Everything seems to be perfect. Both the Share and NTFS permissions give SCCM full access. When checking distmgr.log, I get the following: Successfully created RDC signatures for package ATY00088 version 2 SMS_DISTRIBUTION_MANAGER 8/18/2014 4:17:34 PM 8836 (0x2284) \ATY00088.2 could not be located SMS_DISTRIBUTION_MANAGER 8/18/2014 4:17:34 PM 8836 (0x2284) Failed to get RDC signature path for package ATY00088 version 2. Error = 2 SMS_DISTRIBUTION_MANAGER 8/18/2014 4:17:34 PM 8836 (0x2284) SnapshotPackage() failed. Error = 0x80004005 SMS_DISTRIBUTION_MANAGER 8/18/2014 4:17:34 PM 8836 (0x2284) STATMSG: ID=2361 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm.assurity.local SITE=ATY PID=2200 TID=8836 GMTDATE=Mon Aug 18 21:17:34.238 2014 ISTR0="\\sccm\c$\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.ATY00088.wim" ISTR1="WinPE 8.1 x64" ISTR2="ATY00088" ISTR3="30" ISTR4="99" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="ATY00088" SMS_DISTRIBUTION_MANAGER 8/18/2014 4:17:34 PM 8836 (0x2284) CDistributionSrcSQL::UpdateAvailableVersion PackageID=ATY00088, Version=2, Status=2302 SMS_DISTRIBUTION_MANAGER 8/18/2014 4:17:34 PM 8836 (0x2284) STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=sccm.assurity.local SITE=ATY PID=2200 TID=8836 GMTDATE=Mon Aug 18 21:17:34.262 2014 ISTR0="WinPE 8.1 x64" ISTR1="ATY00088" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="ATY00088" SMS_DISTRIBUTION_MANAGER 8/18/2014 4:17:34 PM 8836 (0x2284) Failed to process package ATY00088 after 1 retries, will retry 99 more times SMS_DISTRIBUTION_MANAGER 8/18/2014 4:17:34 PM 8836 (0x2284) TL;DR - Failed to get RDC signature path for package. SnapshotPackage() failed. Error = 0x80004005. I updated certain pieces of content on my Distribution Point (images that used to work) and they will no longer update (red circle.) What did I DO!? SCCM is completely broken for me, and that is not acceptable. Been working on this for 9+ hours today and all out of ideas. If you need any more information, please don't hesitate to ask. Thanks.
  2. Scratch that. I removed/re-added PXE to my configuration. The folders are all now there. However, I still get the same issues. I will talk to the networking team about possibly setting up an IP Helper for me. Thanks for the tip. I'll try to remember to post back here if it helped or not.
  3. Yep, I most definitely did. Alright, so I set up my lab environment again. Then I noticed something about my production server. It doesn't have the SMSBoot folder. I've read forum topics about the folder being empty, but it doesn't appear that my SCCM installation created the folder whatsoever. The Boot folder is there (which is where the DHCP server options point to.) Would you happen to know if it is possible to manually create the SMSBoot folder and copy the files from the Test environment over? I seem to have this issue on a pretty constant basis as I've redone my production server 4 times now.
  4. Thanks for the suggestion, Rocket Man. I'm not sure I understand the logic behind this. I'm not at all saying I don't believe what you're suggesting, I'm just trying to understand. The machine trying to PXE boot is able to get an IP address. Therefore, DHCP is definitely working. However, after it pulls an address, it tries to perform a TFTP download and fails. I assume it is pulling the boot image. There are no errors in any logs regarding the failure, however. Would this still be a DHCP server issue where IP helpers/etc. are required? Thanks again for the response!
  5. 10.1.8.x subnet. Same as the SCCM server.
  6. Alright, I've been having an insane amount of trouble with SCCM for the last few weeks. I am hoping someone can help me. I have combed these message boards and tried so many fixes, but no go. Setup: SCCM 2012 SP1 Server - 10.1.8.12 DHCP Server - On 172.x.x.x network DHCP Options: 66: 10.1.8.12 67: Tried both smsboot\x86\wdsnbp.com and boot\x86\wdsnbp.com (not sure which to use. Many conflicting posts about them. Also, case sensitive?) When I used to F12, I would get Boot File Not Found. That was before I added the DHCP Options. NOW, however, I get: DHCP.. TFTP. PXE-M0F - Exiting Intel Boot Agent Quite instant after it receives the IP. Now, I have ensured the Files are within both the SMSBoot and Boot folders. Plenty of them. 7 in the SMSBoot and 10 in the boot. I have tried uninstalling WDS. I haven't manually configured anything WDS. I let SCCM do everything. When I try PXE-booting with the laptop, NOTHING is added to the SMSPXE log. NOTHING is added to the DISTMGR log. Everything is added to the C: to avoid any storage-related problems. After restarting WDS service, there is no red in either logs. Please, somebody, save me from the demon. My brain is mush.
×
×
  • Create New...