Jump to content


Search the Community

Showing results for tags 'distribution point'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 54 results

  1. Hi all, Background We’re running SCCM 2012 R2 CU1. It’s a single primary site with a physical Site Server, six virtual distribution points, and a physical SQL cluster. Our physical site server hosts, among other things, the distribution point role and has a 600GB drive for packages and the content library. It’s in a distribution point group with the six other DPs and customers distribute content to that group rather than to the DPs individually. Question Recently we started getting close to the hard 600GB limit on our primary site server, so we started thinking through our options. Buy more drives? Can’t, we’re maxed out. Buy bigger drives? We can, but how big should we get and is that the best option for us? It seems like the best option would be to remove the DP role from our physical site server and just let that role live on the virtual servers with drives that can be grown easily. Our thoughts were to Perform our maintenance in the off-hours and apply a maintenance window to keep people from doingthings. Pull the physical site server from the DP group Remove the DP role from the physical site server Lift the maintenance window so people can do things again Does that plan seem sufficient? Are there any gotchas to look out for? How does this affect any active or ongoing deployments that may be out there? If a computer is stuck waiting for content from our physical site server, how can we tell it to move on to the next available DP? All the documentation out there says how to remove the role, which isn't hard, but doesn't really go into any detail. So either it's very easy and we're over complicating things or you're just not supposed to do it. Thanks in advance for your help and thoughts!
  2. Recently a new drive was installed on my remote SCCM 2007 distribution point. This new drive (F:) was larger and had more space on it than my previous drive designated to be used for my packages (D:). After distributing and updating a few packages, I realized (too late) that these files were being copied to drive "F:". I tried to reverse this process by creating a "NO_SMS_ON_DRIVE.SMS" file on drive "F:", but apparently this is not how this works. I now have these issues: The SMSPKGD$ share no longer exists In the database packages that have not been added or updated since the new drive was added still point to SMSPKGD$ for this DP and now do not work Packages that existed before the new drive was added that have been updated since the new drive installation now have package files on both "D:" and "F:" and will not install on clients properly. I believe this is because the SMSSIG$ directory on the original drive "D:" still holds the package signatures for these packages and there is not a matching package signature in the new SMSSIG$ directory on "F:". I would like to be able to do the following (if possible): Change the drive that SCCM uses on this distribution point server from "F:" to "D:" Prevent the "F:" drive from being used for SCCM packages Copy the packages and signatures from "F:" back to "D:" Update the database pointers for these packages on this DP to "SMSPKGD$" instead of "SMSPKGF$" Perform these steps without having to purge the files from this DP. I believe this last point is the biggest sticking point as this DP is remote and it would take a large amount of bandwidth and time to re-copy these packages back to this DP. It also seems silly to have to remove and re-copy files over the WAN that are already on that server to begin with. Any guidance or assistance that leads me to be able to fix this "in-place" would be a godsend and a huge time saver.
  3. Hello, Im facing this log entries in DISTMGR.log file. Package 'PAK0002D' is found in active queue, will try it later Package 'PAK0002E' is found in active queue, will try it later Sleep 3600 seconds... Though these packages are not listed in Configmgr packages, i have searched individually in console also in WMI by using WMI query but there is no entry for this package file. But DistMgr.log file continuously prompt these logs. I have attached snapshot for furthure reference.
  4. Hello All, My team lead wants to know from which DP client is downloading the package. As we are going to deploy DP on windows 7 computer in our site which is composed of approx 100 clients.
  5. On my site distribution points, I am having an issue with after installing them that the SMS_MULTICAST_SERVICE_POINT comes up as critical under component status. This is because the mutli cast is not being installed for some reason. In teh status Message Details, i recieve this message, "Site Component Manager failed to install this component, because the Microsoft Installer File for this component (mcs.msi) could not install." in the mcsMSI.log.LastError I see these messages: Property(S): System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61 = C:\Windows\system32\ Property(S): SMSCACHEDIR = Default Property(S): SMSCACHEFLAGS = Default Property(S): DISABLESITEOPT = Default Property(S): DISABLECACHEOPT = Default Property(S): SMSCACHESIZE = 5120 Property(S): SmsShellNotify_ActionText = Notifies the shell for the file-association icon changes. Property(S): CcmInstallMCS = D:\SMS_CCM\ 0 Property(S): WDS_ActionData = WDS Property(S): WDS_UnregisterActionData = WDS_UNINST Property(S): SmsMCSDetectDowngrade_ErrorMessage = A newer version of the SCCM Multicast Service Point is already installed Property(S): ARPSYSTEMCOMPONENT = 1 Property(S): ARPNOREMOVE = 1 Property(S): ARPNOMODIFY = 1 Property(S): MCSENABLELOGGING_Default = TRUE Property(S): MCSLOGLEVEL_Default = 0 Property(S): MCSLOGMAXSIZE_Default = 2000000 Property(S): MCSLOGMAXHISTORY_Default = 1 In the MCSSetup.log I see this: <05/12/14 15:14:16> ======== Completed Installation of Pre Reqs for Role SMSMCS ======== <05/12/14 15:14:16> Installing the SMSMCS <05/12/14 15:14:16> Machine is running Windows Operating System or later. (NTVersion=0X601, ServicePack=1) <05/12/14 15:14:16> IIS Service is installed. <05/12/14 15:14:16> Created the DP mutex key for WDS. <05/12/14 15:14:16> Created the DP mutex value for WDS. <05/12/14 15:14:16> Machine is running Windows Server. (NTVersion=0X601, ServicePack=1) <05/12/14 15:14:16> WDS is INSTALLED <05/12/14 15:14:16> WDS Service is installed. <05/12/14 15:14:16> No versions of SMSMCS are installed. Installing new SMSMCS. <05/12/14 15:14:16> Enabling MSI logging. mcs.msi will log to D:\SMS\logs\mcsMSI.log <05/12/14 15:14:16> Installing D:\SMS\bin\x64\mcs.msi CCMINSTALLDIR="D:\SMS_CCM" CCMSERVERDATAROOT="D:\SMS" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 MCSENABLELOGGING=TRUE MCSLOGLEVEL=1 MCSLOGMAXSIZE=1000000 MCSLOGMAXHISTORY=1 <05/12/14 15:14:27> mcs.msi exited with return code: 1603 <05/12/14 15:14:27> Backing up D:\SMS\logs\mcsMSI.log to D:\SMS\logs\mcsMSI.log.LastError <05/12/14 15:14:27> Fatal MSI Error - mcs.msi could not be installed. <05/12/14 15:14:27> ~MCSRoleSetup(). <05/12/14 15:14:27> Stopping wdsserver service <05/12/14 15:14:32> Starting wdsserver service <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging\@GLOBAL <05/12/14 15:14:32> RegOpenKeyEx failed (2) for: Software\Microsoft\CCM\Logging\McsIsapi <05/12/14 15:14:32> RegOpenKeyEx failed for Software\Microsoft\CCM\Logging\@GLOBAL <05/12/14 15:14:32> RegWriteDWord failed. 80070002. <05/12/14 15:14:32> ReleaseDpMutexForWDS: Deleting the DP mutex key for WDS. <05/12/14 15:14:32> ~MCSRoleSetup() - 00000000 <05/12/14 15:14:32> ~RoleSetup(). Any hep with this is greatly appreciated
  6. Hi all, In all our company uses 8 distribution point and the majority are 2008 R2 domain controllers. About two days ago I have done an inplace upgrade on one server to 2012 R2. The upgrade went mostly without a hitch except for the SCCM DP. The error that I was getting was "access denied" or something along those lines when the site server was attempting to distribute content. So I have tried a lot of things so far to the point where I decided to remove the distribution point and start over. No Joy... I am getting an error on the distribution point in the SCCM console stating "Failed to verify the disk drive". when looking further into the distmgr.log, nothing makes sense to me. please see the below log. ~Sleep 60 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:35.310-600><thread=5576 (0x15C8)> ~Sleep 60 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:44.178-600><thread=5576 (0x15C8)> Upgrading DP with ID 18. Thread 0x1e1c. Used 1 threads out of 5. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.248-600><thread=5868 (0x16EC)> ~Processing 18.INS $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.253-600><thread=7708 (0x1E1C)> ~DPID 18 - NAL Path ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\ , ServerName = [sERVER NAME HERE], DPDrive = E:, IsMulticast = 0, PXE = 0, RemoveWDS = 0 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.263-600><thread=7708 (0x1E1C)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.255-600><thread=5868 (0x16EC)> ~Created policy provider trigger for ID 18 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:20:59.308-600><thread=5860 (0x16E4)> DPConnection::Connect: For [sERVER NAME HERE], logged-on as rondo\sccmpush~ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:02.712-600><thread=7708 (0x1E1C)> Found notification for package 'RDO00002' $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.263-600><thread=5576 (0x15C8)> Found notification for package 'RDO00003' $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.268-600><thread=5576 (0x15C8)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.302-600><thread=5868 (0x16EC)> ~Package Thread Limit: 3 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.310-600><thread=5576 (0x15C8)> ~Per package Thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.315-600><thread=5576 (0x15C8)> ~Retry interval: 30 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.320-600><thread=5576 (0x15C8)> ~DP upgrade thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.325-600><thread=5576 (0x15C8)> ~DP upgrade retry interval: 20 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.330-600><thread=5576 (0x15C8)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.360-600><thread=5576 (0x15C8)> Failed to find a valid drive on the distribution point ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.541-600><thread=7708 (0x1E1C)> ~Starting package processing thread, thread ID = 0x88 (136) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:04.919-600><thread=5576 (0x15C8)> DPConnection::Disconnect: For [sERVER NAME HERE], reverted to SYSTEM context~ $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.131-600><thread=7708 (0x1E1C)> user(NT AUTHORITY\SYSTEM) runing application(SMS_DISTRIBUTION_MANAGER) from machine ([sITE SERVER NAME HERE]) is submitting SDK changes from site(RDO) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.348-600><thread=7708 (0x1E1C)> ~Starting package processing thread, thread ID = 0x2B78 (11128) $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.426-600><thread=5576 (0x15C8)> ~Sleep 3600 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.434-600><thread=5576 (0x15C8)> STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00003" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=11128 (0x2B78)> ~Retrying package RDO00003 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.450-600><thread=11128 (0x2B78)> No action specified for the package RDO00003. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=11128 (0x2B78)> STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:05.440 2014 ISTR0="RDO00002" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.440-600><thread=136 (0x88)> ~Retrying package RDO00002 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.469-600><thread=136 (0x88)> No action specified for the package RDO00002. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.476-600><thread=136 (0x88)> Start adding package to server ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.494-600><thread=136 (0x88)> Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=136 (0x88)> Thread Handle = 00000000000035C0 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.507-600><thread=136 (0x88)> Start adding package to server ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.473-600><thread=11128 (0x2B78)> Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.501-600><thread=9852 (0x267C)> The distribution point ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\ is not installed or upgraded yet. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.538-600><thread=9852 (0x267C)> Error occurred. Performing error cleanup prior to returning. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.546-600><thread=9852 (0x267C)> ~Failed to install DP files on the remote DP. Error code = 15 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.455-600><thread=7708 (0x1E1C)> ~Drive E: is not valid. Error = 15 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.566-600><thread=7708 (0x1E1C)> STATMSG: ID=2360 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=7708 GMTDATE=Thu May 01 12:21:05.573 2014 ISTR0="["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\" ISTR1="[sERVER NAME HERE]" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.573-600><thread=7708 (0x1E1C)> ~Will try again after 20 mins ... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.582-600><thread=7708 (0x1E1C)> Will wait for 1 threads to end. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=11128 (0x2B78)> Thread Handle = 00000000000029C8 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.612-600><thread=11128 (0x2B78)> Attempting to add or update a package on a distribution point. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:05.522-600><thread=10028 (0x272C)> DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.124-600><thread=136 (0x88)> DP thread with thread handle 00000000000035C0 and thread ID 9852 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.131-600><thread=136 (0x88)> The distribution point ["Display=\\[sERVER NAME HERE]\"]MSWNET:["SMS_SITE=RDO"]\\[sERVER NAME HERE]\ is not installed or upgraded yet. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.136-600><thread=10028 (0x272C)> Error occurred. Performing error cleanup prior to returning. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.164-600><thread=10028 (0x272C)> DP thread with array index 0 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.198-600><thread=11128 (0x2B78)> DP thread with thread handle 00000000000029C8 and thread ID 10028 ended. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.205-600><thread=11128 (0x2B78)> ~Package RDO00002 does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.645-600><thread=136 (0x88)> The package and/or program properties for package RDO00002 have not changed, need to determine which site(s) need updated package info. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.653-600><thread=136 (0x88)> ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00002, Version=3, Status=2301 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.659-600><thread=136 (0x88)> ~StoredPkgVersion (3) of package RDO00002. StoredPkgVersion in database is 3. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.687-600><thread=136 (0x88)> ~SourceVersion (3) of package RDO00002. SourceVersion in database is 3. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.694-600><thread=136 (0x88)> STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=136 GMTDATE=Thu May 01 12:21:06.700 2014 ISTR0="Configuration Manager Client Package" ISTR1="RDO00002" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00002" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.700-600><thread=136 (0x88)> ~Failed to process package RDO00002 after 33 retries, will retry 67 more times $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.711-600><thread=136 (0x88)> ~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.720-600><thread=136 (0x88)> ~Package RDO00003 does not have a preferred sender. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.721-600><thread=11128 (0x2B78)> The package and/or program properties for package RDO00003 have not changed, need to determine which site(s) need updated package info. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.749-600><thread=11128 (0x2B78)> ~CDistributionSrcSQL::UpdateAvailableVersion PackageID=RDO00003, Version=1, Status=2301 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.757-600><thread=11128 (0x2B78)> ~StoredPkgVersion (1) of package RDO00003. StoredPkgVersion in database is 1. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.784-600><thread=11128 (0x2B78)> ~SourceVersion (1) of package RDO00003. SourceVersion in database is 1. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.790-600><thread=11128 (0x2B78)> STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=[sITE SERVER NAME HERE] SITE=RDO PID=3112 TID=11128 GMTDATE=Thu May 01 12:21:06.797 2014 ISTR0="Configuration Manager Client Upgrade Package" ISTR1="RDO00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="RDO00003" $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.797-600><thread=11128 (0x2B78)> ~Failed to process package RDO00003 after 33 retries, will retry 67 more times $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.806-600><thread=11128 (0x2B78)> ~Exiting package processing thread. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:06.814-600><thread=11128 (0x2B78)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:09.311-600><thread=5868 (0x16EC)> ~Package Thread Limit: 3 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.463-600><thread=5576 (0x15C8)> ~Per package Thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.469-600><thread=5576 (0x15C8)> ~Retry interval: 30 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.476-600><thread=5576 (0x15C8)> ~DP upgrade thread Limit: 5 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.482-600><thread=5576 (0x15C8)> ~DP upgrade retry interval: 20 $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.488-600><thread=5576 (0x15C8)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.509-600><thread=5576 (0x15C8)> ~Sleep 1826 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:10.517-600><thread=5576 (0x15C8)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:14.320-600><thread=5868 (0x16EC)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.544-600><thread=5576 (0x15C8)> ~Sleep 1821 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:15.553-600><thread=5576 (0x15C8)> Sleep 20 minutes... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:19.332-600><thread=5868 (0x16EC)> ~Used 0 out of 3 allowed processing threads. $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.581-600><thread=5576 (0x15C8)> ~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.589-600><thread=5576 (0x15C8)> ~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.732-600><thread=5576 (0x15C8)> ~Sleep 1816 seconds... $$<SMS_DISTRIBUTION_MANAGER><05-01-2014 22:21:20.872-600><thread=5576 (0x15C8)> So I have two questions, How can I fix this and how do I prevent it from happening to the remainder? Thank you all in advance. Daniel.
  7. Hi, I have 1 site thats running SCCM 2007 with IP ranged boundaries and a site with SCCM 2012 running on same IP ranged boundaries. The problem is that the SCCM 2012 site automatically creates boundary groups and boundaries of the old SCCM, pointing the clients to the wrong distribution points. Is there any fix for this, to avoid clients being pointed to the wrong DPs. I have tried setting deny read in AD, on the System Management container, for both SCCM server objects, but they are still created.
  8. Experiencing an extremely frustrating problem. ENVIRONMENT: 1 Primary Site Server / DP (Main Office) 40 DP's (Remote School Locations) - Hosted on a file server VM - Contains 3 partitions: C: (System), E: (Data), I: (PKG share) OS: Server 2008 R2 (Primary Site Server and File Servers / DP's) SCCM Version: SCCM 2012 R2 We recently upgrade to SCCM 2012 R2. I have confirmed that this has not caused the problem I am about to describe. The only other change that has occurred recently is that we configured all of our DP's at each of our 40 sites to be pull distribution points. While this seems to be working fine we are now seeing a whole bunch of 0 Byte alpha numeric folders with a 0 Byte amd64 subfolder. These folders seem to attach to the E: drive on all of our File server distribution points....for the life of me I cannot figure out why and this occurred as soon as we switched to pull distribution points. While this does not seem to be having an erroneous effect on our environment, it is annoying and somewhat disconcerting as I have not been able to ascertain what is causing it. Any SCCM admins out their ever encountered this? Thanks
  9. Hello everyone, I got handed our SCCM enviornment until we get a new guy to fill in and have been trying to keep things in running order, but had some trouble as of lately. I am getting 1000s of error 2302 and 2348 events everyday and am trying to fix them, below is one example: In this case I tried the following troubleshooting steps: Locate the package, SSS000B7, it is an older version of Java, I right click on it, update distribution points, at the prompt that asks me to conform update distribution points I click yes. No dice. Possible cause: Distribution manager does not have access to either the package source directory or the distribution point. Solution: Verify that distribution manager can access the package source directory/distribution point. I have tracked down the folder that it is part of and made sure that the server (computer object) has full control under NTFS permissions. Possible cause: The package source directory contains files with long file names and the total length of the path exceeds the maximum length supported by the operating system. Solution: Reduce the number of folders defined for the package, shorten the filename, or consider bundling the files using a compression utility. The full path even down to the file.exe or .msi in other cases is under 256 characters long and in most instances under 100 characters long. Possible cause: There is not enough disk space available on the site server computer or the distribution point. Solution: Verify that there is enough free disk space available on the site server computer and on the distribution point. Both the primary site and the distribution point have plenty of disk space (in excess of 100GB). I have tried changing the UNC path to the local path on the server as suggested here: http://social.technet.microsoft.com/Forums/en-US/87d35966-9f12-455e-854f-d3d07760acb3/having-dp-issues-event-2302?forum=configmgrsum, however I noticed that when I tried to set it to the local path on the server instead of UNC it reverts back. I removed the program in this instance and recreated it, unfortunately it produced same result where it reverts back to the UNC path instead of the local path. The packages I have created lately have no issue they point to the local path. I saw someone else on this forum previously getting event 2302, http://www.windows-noob.com/forums/index.php?/topic/2423-sms-distribution-manager-failed-to-process-package/?hl=2302 and tried to turn off bits last night to see if this would help alleviate this issue, however it didn't. Has anyone run into this before, if so can you shed some light on how to fix it?
  10. I have most of my data for my packages, applications, drivers, etc stored on my Primary SCCM server. My question is: Is that necessary? I know I can pull data from other places, but can I delete the content from my SCCM 'deploy' share after I have distributed it? A lot of my packages are referring to a UNC \\SCCMServer\Deploy\Software\AppName When I distribute that software do I have to keep those source files there?
  11. I have set up a distribution point for a primary site. Remarkably I didn't have to fuss too much to get PXE to work. What I'm seeing now though, is an unknown client will PXE fine from the distribution point location which is in the proper boundary group, but then it will the image.wim in the task sequence across the WAN rather than locally. I have WDS up and running on the DP and have distributed successfully (from sccm primary to DP) everything included in the task sequence other than the image.wim for the task. I get "failed to distribute content" under Distribution status, but see nothing failing in distmgr.log, but I also never see it actually adding the package to the DP, just the primary site location. This is a snip from the most recent attempt in distmgr.log which has been queued for about 4 days, but doesn't succeed. Found notification for package 'CCM00055' SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:27 AM 6236 (0x185C) Used 0 out of 5 allowed processing threads. SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:27 AM 6236 (0x185C) Starting package processing thread, thread ID = 0x1154 (4436) SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:27 AM 6236 (0x185C) Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:27 AM 6236 (0x185C) STATMSG: ID=2300 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCM12.mydomain.com SITE=CCM PID=4068 TID=4436 GMTDATE=Mon Apr 07 17:13:27.909 2014 ISTR0="Elitebook 840 G1" ISTR1="CCM00055" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CCM00055" SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:27 AM 4436 (0x1154) No action specified for the package CCM00055. SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:27 AM 4436 (0x1154) Start validating package CCM00055 on server ["Display=\\goldendp.mydomain.com\"]MSWNET:["SMS_SITE=CCM"]\\goldendp.mydomain.com\... SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:27 AM 4436 (0x1154) DP health monitoring task has been started successfully to verify package 'CCM00055'. SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:28 AM 4436 (0x1154) Package CCM00055 does not have a preferred sender. SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:29 AM 4436 (0x1154) The package and/or program properties for package CCM00055 have not changed, need to determine which site(s) need updated package info. SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:29 AM 4436 (0x1154) CDistributionSrcSQL::UpdateAvailableVersion PackageID=CCM00055, Version=2, Status=2301 SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:29 AM 4436 (0x1154) StoredPkgVersion (2) of package CCM00055. StoredPkgVersion in database is 2. SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:29 AM 4436 (0x1154) SourceVersion (2) of package CCM00055. SourceVersion in database is 2. SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:29 AM 4436 (0x1154) STATMSG: ID=2301 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=SCCM12.mydomain.com SITE=CCM PID=4068 TID=4436 GMTDATE=Mon Apr 07 17:13:29.764 2014 ISTR0="Elitebook 840 G1" ISTR1="CCM00055" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="CCM00055" SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:29 AM 4436 (0x1154) Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 4/7/2014 11:13:29 AM 4436 (0x1154) I have a volume on the DP dedicated for WDS which includes the following directories: RemoteInstall, SCCMContentLib, SMS, SMS_DP$, SMSSIG$ and a SOURCES folder which I robocopy'd relevant folders and files needed for OSD at the DP location from the primary site server. I set all permissions the same on both sets of folders; the ones on the primary site and the DP site. I'm wondering if I have the task sequence wrong? I thought the OSD TS was supposed to use content closest to the client, but do I have to build a new TS to point to DP content - SOURCES folder on DP - or should the content from the SOURCES folder be in a different location on the DP i.e. RemoteInstall folder or something? The imaging task actually succeeds, much to my amazment, but as you can imagine, I don't want that running over the WAN. Thanks in advance for any input,
  12. Hi, All I am new to Administering SCCM 2012. I have followed the instructions on this forum carefully and it have helped me. I created a TS and for some reason I delete it. But when I created the New Task Sequence it will not allowed me to re-distribute the content to the old DP where the previous one was. I went to the Technet site and it says that. Important If the task sequence that you selected references content that is already distributed to a specific distribution point, that distribution point is not listed by the wizard. http://technet.microsoft.com/en-us/library/hh273490.aspx This is because when I resend or deploy the job to the laptop I keep getting this error " The Task Sequence cannot be run because the program files associated with "CHM00008"cannot be found on the distribution Point". But I know is on the DP. I have updated it and redistribute it. I can browse to it. And help to show me how to re-distribute the TS to the DP will be highly appreciated. Thanks KKA SMSPXE.log
  13. Installation of the DP went fine. The logs show that everything worked fine. The SCCM folders were created. The DP server shows up in the console. Trying to distribute content to the new DP fails with the following errors: ERROR DPConnection::ConnectWMI() - Failed to connect to Office-DP.domain.com. error = 0x800706ba Cannot establish connection to ["Display=\\Office-DP.domain.com\"]MSWNET:["SMS_SITE=TSM"]\\Office-DP.domain.com\. Error = 53 Failed to make a network connection to \\Office-DP.domain.com\ADMIN$ (0x35) CWmi::Connect() failed to connect to \\Office-DP.domain.com\root\MicrosoftIISv2. Error = 0x800706BA The Site server is local admin on the machine. From the site server I can open \\Office-DP\Admin$ , and D$ (SCCM drive) and create folders and copy data. From the link below, I thought maybe the WMI namespace for SCCMPD was not created on the DP, so I ran mofcomp.exe smsdpprov.mof to create it http://silentcrash.com/2013/09/error-0x800706ba-when-trying-to-install-new-distribution-point-in-sccm-2012-sp1/ What am I missing? Thinking it was a problem with this location, I setup another DP in a different location and am having the same issue with it. I think I must be missing a step somewhere, but can't for the life of me think what it might be. Thank you, LT.Son
  14. Hi all, A while ago we had to shut down WDS on all of our DP's due to a task being sent out to the wrong machines. When we started WDS up again, one of our DP's would not start the WDS service. I ended up removing the role and content from the DP and the DP's site server from SCCM and starting from scratch. Now when I try to OSD a machine in that building it fails with the following error: Windows Boot Manager Windows failed to start. <bla bla bla> File: \Boot\BCD Status 0xc000000f Info: An error occurred while attemptint to read the boot configuration data. If I take the machine to another building, it images fine. Imaging also worked fine before restarting WDS. When I look at the SMSPXE.log of the DP during a netboot, I see the following (I have attached the full log as well): [010.013.010.001:4011] Recv From:[010.013.130.191:68] Len:283 1635e70 MAC=08:2E:5F:22:7D:F1 SMBIOS GUID=97035800-4440-11E1-0000-082E5F227DF1 > Received DHCP Request Set media certificate in transport Set authenticator in transport Set authenticator in transport failed to receive response with winhttp; 80072ee2 Failed to get information for MP: http://CM.mydomain.com. 80072ee2. PXE::DB_InitializeTransport failed; 0x80004005 PXE::DB_LookupDevice failed; 0x80004005 Set media certificate in transport Set authenticator in transport Set authenticator in transport failed to receive response with winhttp; 80072ee2 Will retry in 5 second(s) Retrying... failed to receive response with winhttp; 80072ee2 <snip> End of retries failed to send the request Failed to send status message (80072ee2) Failed to send the status message PXE::DB_ReportStatus failed; 0x80072ee2 PXE Provider failed to process message. Unspecified error (Error: 80004005; Source: Windows) failed to receive response with winhttp; 80072efe End of retries failed to send the request PXE::DB_LookupDevice failed; 0x80072efe Also possibly related but when I check the content library with ContentLibraryExplorer.exe all of the regular content checks out except for MSC00001 and MSC00002 (The configuration manager client package) which show as "(PENDING)" Thanks in advance for any help you can give! Edit: This is SCCM2012, no SP1, no R2. SMSPXE-error.log
  15. Hi all, I'm new at SCCM topic and try to install Configuration Manager 2012 SP 1 in a lab environment. Since a few day I have now the problem that in my configuration (I used niall's "System Center 2012 Configuration Manager Guides" as template) no Distribution Point is available. I've installed one SCCM Server as Primary site. This Server has the Site System Role "Distribution Point" assigned. In Administration | Overview | Site Configuration | Servers and Site System Roles I can verify that my Server have this System role But when I open the category "Distribution Points" in Administration | Overview there is just the message "No items found." I tried to remove the System role DP and reassign it - no difference. I also read the logfiles distmgr.log and ConfigMgrSetup.log but I did not find any hint. What can I do? thx for any help, ideas and hints! Best Regards and Merry Christmas Joey
  16. Hey Guys, This is more than likley going to be one of those super simple moments where I have missed something so apologies in advance. We have 1 Primary site and several remote DP's connected by slow links. The remote DP's are only DP's. While the Primary site houses everything else. I.e SUP, MP, SCEP etc.. WHAT IS OCCURING. All clients no matter where they are are going back to primary site flooding the wan links. WHAT IS CONFIGURED The SUP site is configured with ADR's and the Software update Packages are deployed to all remote DP's. Status of each remote DP is healthy. When looking at the WUAhandler.log file I see every bit of traffic going back to the primary site for Software updates and all SCEP updates going to the internet. This is occuring during the the OSD process and after as well. Basically the questions I have is: Should all updates be coming from the local DP assuming all my boundaries are set correclty? If so what would you suggest double checking in the config? Thank you all in advance for your suggestions.
  17. Hi, We have a small office in Stockholm and remote offices in Singapore and London. We have maybe 300 users and max 500 workstations. There are Riverbed appliances to optimize WAN speed to both locations. Now we are in the process of setting up SCCM environments in S and L so we can PXE boot machines and deploy software quicker etc. I'm thinking about setting up remote DPs in both S and L, that seems like the best solution. Do you guys have any better suggestions? What should I do about boundaries and boundary/dp groups? Is there anything I should think about before going ahead with this? I will be travelling to S in a few weeks time and have about a week to get this and some other stuff done. Thanks.
  18. In my SCCM 2012 config, I have 3x distribution points that are no longer active and I need to remove them from the config. I've read that I need to remove the roles before deletion but the Component Server and Site System have "Remove Role" greyed out. I can't find the solution to this on Google but it must be fairly straight forward (must be). If need be I can switch the old DP servers back on. Any ideas greatly appreciated, thanks.
  19. Hi, I have to modify a distribution point value with powershell script. The value is PrestageAllowed who locate in wmi class SMS_SCI_SYSRESUSE like screenshot http://imageshack.us/photo/my-images/27/sanstitrewi.png/ Thanks fz
  20. Hi, I have SCCM 2012 environment with multiple DP's. I need to identify which DP is used for deploying packages to the clients. Can we get this information in reports or any log files? This will ensure that correct DP is being used for the entire collections. Regards
  21. Three dist points. One of the three generates an error for Itunes. The error is essentially where Itunes trys to start up and wants to find its installer but what it is referencing is the path to where the install process would have put it during the install (c:\SMSTaskSequence\Packages\*assigned_package_ID\). If you click cancel on the error Itunes DOES WORK FINE. I have updated the dist point a few time, and "refreshed" it too. The file being installed (itunes64.msi) matches hash on a dist point that does work. Is there a way to disable a dist point (not delete it) to force the machine's in the problem dist points area to go to a different dist point. Other suggestions?
  22. Sometimes when I create a package for deployment and get it all setup and ready and then deploy it for advertisement the reporting mechanism shows "No matching records could be found." This stays like this no matter what I do, updating distribution point. Destroy package and create entirely from new again the whole process including advertisement. The only thing that ever fixes this is to copy the contents of the folder and create a new folder and then paste the contents in there. Then create the package and advertisement all over again. Why does this happen and is there anyway to stop this from occurring? I have SCCM 2007R2 and trying to get this to work as we aren't moving to SCCM 2012 till SP1 is released. Thanks,
  23. Hi, I am having a very strange error crop up while testing the deploy and capture of a boot OS via a task sequence. The error occurs on x86 or x64, on VM's or physical clients. SCCM 2012 is installed per the fantastic tutorial here and this error is appearing on part 7. When deploying the boot image to the target pc, the PE environment loads and immediately resets the client pc with this error: Failed to run task sequence - An error occurred while retrieving policy for this computer (0x80004005) After some searching around I found and tried these: Link 1: Permissions & Link 2: Certificates Unfortunately, neither helped. I have granted sufficient permissions to client systems to access the boot.wim image and the only certificate available is loaded into SCCM and is unblocked. Its difficult to be 100% sure re the certificates issue, as that link is to a 2007 SCCM structure and I think that Admin.\Security\Certificates would be the corresponding location in 2012. At this point I have reinstalled the distribution point, setup new boot images for both x86 & x64, created new tasks and sent them out to the clients and still ... nothing. Clients are still restarting immediately after the PE loads. I have tried to look at the smsts.log on the clients, but they are listed as empty, so cannot. The smspxe.log file reports business as usual with no unusual\error based behaviour. Any ideas anyone or anyWeb? At this point I am at my wits end, but need to continue regardless... Cheers & Thanks
  24. Now that I've got my PXE working I'm running into the error of: Failed to run task sequence because the program files cannot be located on a distribution point. In the documentation for RC2 it states to enable the "Copy content to a share on distribution points" but then after that it's vague on where it means when it says "Note: once you have enabled the setting above your Deployment distribution settings gets a new drop down menu choice, access content directly from a distribution point when needed by the running task sequence" Where can I find this and what exactly needs to be done here Disregard, I figured it out.
  25. Hi! I have installed SCCM 2012 and it have worked fine and I have also installed two Distribution point and they also works fine but when I try to install my third DP I receive errors and it will not work. I have installed the DP on Windows 2008 R2 servers and enabled PXE and I have followed your instruction in “Setting up a DP on a Windows 7 box” but enabled PXE. The only different settings are that the previous servers are in the same time zone as the SCCM 2012 site server and the one that are failing are in a different time zone as the main system. I receive the following error on the remote DP server "sccm2012-server.txt". And on the main SCCM server I receive the following message in document "sccm2012-Distribution-Point.txt". What might I have missed? I have reinstalled the system and enabled it again with the same result. Is there some issue with DP and diffrent time zone? Best regards Mattias sccm2012-Distribution-Point.txt sccm2012-server.txt
×
×
  • Create New...