ConfigMgr 2012 R2 Distribution Point IIS no directories created
I have an issue where I removed the DP role from my Primary Site Server, and am unable to re-install it.
Environment Server 2012 R2 all in one system (SQL, SSRS, and ConfigMgr installed locally).
The logs state that BITS isn't installed, but I have removed and reinstalled it several times. I have also changed the "Log On" account to verify that it isn't a permissions thing (I have since reverted the account to the default).
The process of creating the DP role allows for the ContentLib folder to be created on the drive, but the SMS_DP_PKG$, nor for the virtual folder creation in IIS. Please help.
From the logs:
Error
Milestone
PS1 6/1/2014 11:36:31
AM
SCCM.domain.org
SMS_DISTRIBUTION_MANAGER
2344 Failed to create virtual directory on
the defined share or volume on distribution point "["Display=\\SCCM.domain.org\"]MSWNET:["SMS_SITE=PS1"]\\SCCM.domain.org\".
Possible cause: Distribution Manager requires that IIS base components be
installed on the local Configuration Manager Site Server in order to create the
virtual directory. Distribution Manager also requires that IIS Web
Services be installed on the Distribution Point Server that needs to support
Background Intelligent Transfer Service (BITS). Solution: Verify that IIS
base components are installed on the local Configuration Manager Site Server,
and IIS Web Services are installed on the Distribution Point Server.
Hi,
Please check Distmgr.log as Torsten said.
Have you try to reboot the server after confirm all prerequisites has met?
Could you distribute a content to the DP successfully?
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.
Similar Messages
-
SCCM 2012 R2 - Distribution Point untrusted domain - Not acknowledging Network Access Account (FYI)
Hello!
Scenario
Built a single primary site server in one domain with multiple distribution points. All site servers are member of this one site.
The distribution points in the primary site servers' domain function as expected. The distribution point deployed to an untrusted domain does not. The primary site server can see all objects in the domain, publishes successfully, and CCM client on the
DP in the untrusted domain knows its part of the site, knows its AD site (according to locationservices.log). The DP role is installed properly, logs are populating, queries are being made for application lists and updates. nfortuantely authentication
errors indicate that this software can'tbe downloaded.
In essence the DP in the untrusted domain can't pull down content from the primary site server. The role uses BITS to download content from IIS on the primary site server, but the requests each throw a 401 error. Unauthorised. This should be an easy fix.
Create a Network Access Account in the primary site server's domain, assign it to the site (Software Distribution setting), wait for the DP to pick up the setting and watch it retrieve its content. The DP in the untrusted domain is configured as a Pull DP,
implying it has to use a Network Access Account to download content. It knows the content is available and makes every effort to download it.
Problem
The DP in the untrusted domain doesn't know a Network Access Account (NAA) has been defined for the site.
The account does exist, created in the primary site server's domain and assigned to the site. Its not a password issue. IIS has not been set for Anonymous access as this isn't needed - the NAA should provide the credentials it requires to pull down content.
A manual check using the URL of the package confirms the package is accessible from the DP when using the NAA's credentials. I've allowed enough time (i think) for the DP to acknowledge the NAA. For fun the DP role was removed, and the CCM agent removed. Both
were reinstalled. A fresh install didn't detect the NAA.
Solution
After some soul searching and a little frustration, it came down to this: A Pull DP always uses the Network Access Account. If the DP can't find a Network Access account it will fail to pull down content. This is undisputed. Found an article that states
the Pull DP always uses the CCM client configuration to do its dirty work. At that point the CCM client was checked. It had the classic problem of only displaying two Actions - Machine Policy Retrieval & Evaluation Cycle, User policy Retrieval & Evaluation
Cycle. Most components were installed but not enabled. This is fairly common. Looked at the console, found the device, added the Approval column. Turns out it wasn't auto-approved. Reason being that the client is in an untrusted domain and clients in untrusted
domains aren't approved automatically (by default).
In this case something as simple as an Approving the client fixed these issues.
The DataTransferService.log highlights the issue:
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}' ErrorCode=0x80190191]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="1" thread="3136" file="dtsjob.cpp:3501">
<![LOG[CDTSJob::JobError: DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' URL='http://PRIMARYSERVER.A.B.COM:80/SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68'
ProtType=1]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3136" file="dtsjob.cpp:3504">
<![LOG[Authentication required by the proxy, DTS Job ID='{17E0B672-F699-434D-B063-87CC2ACF715C}' BITS Job ID='{38B81ADE-55B5-4BD7-A881-DBFF13943EDE}'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="3" thread="3136" file="dtsjob.cpp:3513">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} in state 'Cancelled'.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.h:166">
<![LOG[DTS job {17E0B672-F699-434D-B063-87CC2ACF715C} BITS job
{38B81ADE-55B5-4BD7-A881-DBFF13943EDE} encountered Access Denied error during download. Will retry using Network Access Account.]LOG]!><time="18:25:54.264+00" date="02-19-2015" component="DataTransferService"
context="" type="2" thread="3136" file="dtsjob.cpp:3652">
<![LOG[DTSJob {8814E9A1-3D26-4089-83CF-3C7D17BCEC6E} cancelled by client.]LOG]!><time="18:25:54.280+00" date="02-19-2015" component="DataTransferService" context="" type="1" thread="3688"
file="dtsjob.cpp:3205">
<![LOG[No network access account info found.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="1"
thread="3136" file="netaccessaccount.cpp:288">
<![LOG[The network access account is not defined.]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context=""
type="1" thread="3136" file="netaccessaccount.cpp:858">
<![LOG[DTSJob {17E0B672-F699-434D-B063-87CC2ACF715C} encountered error setting BITS job to use Network Access Account
(0x00000000).]LOG]!><time="18:25:54.327+00" date="02-19-2015" component="DataTransferService" context="" type="3" thread="3136" file="dtsjob.cpp:1885">
The IIS server logs u_ex150219.log captures the request:
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 2 5 1509 2
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 4
2015-02-19 123.11.12.13 GET /SMS_DP_SMSPKG$/5af1680e-4a14-4dc5-8a60-bda7370e6d68/sccm /windows6.1-kb3021917-x64.cab 80 - 9.10.11.12 Microsoft+BITS/7.7 -
401 1 3221225581 1509 3
2 x Domains: DomainA and DomainX
- Single domain forests
- No trusts between domains/forests
DomainA\PRIMARYSERVER
- Primary Site Server, MP, DP, IIS, all roles
DomainX\DP1
- Distribution Point, IIS, etc
- CCM client installedBased on the above, you are using a PullDP. If so, have you installed the client agent on this system? The client agent is required on PullDPs in untrusted domains so that they can acquire the NAA.
Jason | http://blog.configmgrftw.com | @jasonsandys -
SCCM 2012 - Pull distribution point and target PKI or HTTPS DPs
I have spent several days researching this and so far have found only a single page that even takes a stab at offering a solution.
Problem:
Trying to target an HTTPS DP when creating a pull distribution point in SCCM 2012 R2. The link that I'm referring to that does offer a workaround is here(guess I can't post a link, but it ends with the following, how-to-set-an-https-distribution-point-as-a-source-dp-for-pull-dps)
I have several problems with the proposed solution.
Is a script really the only way to proceed with something that has up till now been a built in feature with the rest of the product.
You have to provision the DP to use a self signed cert initially for it to even work, then supposedly you can add the private key to the DP later.
Does that mean I have to unbind the cert from both the pull and target/source push DP in IIS?
Powershell which would be a logical way to go, doesn't seem to make any head way(Mr. Snover I know you don't oversee configman but please push for more documentation, you've taught me to live and die by get-help. A single example for a command as large
as set-cmdistributionpoint or add-cmdistributionpoint is a shame. Perhaps my update help just didn't finish properly and I'm talking prematurely. If that is the case then I apologize!)
Is there no other solution other than build the DP with a self signed cert then run this VB script and then switch the private key later? I have read through a lot of the pull DP documentation and it makes mention of leveraging the SDK but I haven't seen
anything definitive. I would like to at the very least convert this from VB to powershell(if that script is the only option) and I know how to convert the portions where it's interacting with the site's WMI namespace (smsprovider if I'm not mistaken).
What I don't know how to do, rather don't have the chops for is what comes after. The site control file piece, I see it's also WMI and I could spend the time stepping through the different piece and just might to learn more about SCCM in the lab anyhow. I've
spent the last year getting to know powershell and have spent next to no time with VB. I know enough to recognize what a script is doing.
The environment:
The reason this is important for me is I'm about to start the production build(been all lab up till now) that is going to have just under 300 DPs in the field connected via T1 lines. They were all 07 secondary sites. I was thinking about migrating them using
the migration tool but considering the amount of work its going to take if that link is the ONLY path to target a HTTPS DP then I might as well just spend the time and manually uninstall and reinstall the field DPs. The client count in the field is an average
of 50 machines per site where there are on-prem devices... Total client count is around 25k. The primary site in the datacenter will house the majority of the site roles unless I start running into resource issues, at which time I will begin offloading site
roles to one of two more servers that I have slated for the project. No CAS, no Secondaries. SQL is co-located on the primary.
Ramblings:
I'm sure there are more people out there using PKI, and using pull DPs. How have you managed to target your HTTPS enabled DPs? Security wants this to be a HTTPS only environment, and up until now I have successfully done that. If someone could please point
me in the direction of some more thorough documentation I would be very grateful. I understand that this is a somewhat new feature, but there has to be an easier way. Perhaps powershell can cleanly do it with the set-cmdistribution point...but when I update
help and do showwindow for the command I only get one example and so far haven't found any other stories like mine with the exception of the link I posted in the beginning.
While I'm rambling, Wally there are a lot of us in the community that are going to miss your presence at Microsoft and should you read this I wish you luck with your new position. But that is a whole different topic. Thanks in advance for any links or help
you can provide. -K.R.Yes, this is the only way, from
http://technet.microsoft.com/en-us/library/gg712321.aspx#BKMK_PlanPullDps: "However, you can use the Configuration Manager SDK to specify a source distribution point that is configured for HTTPS. To use a source distribution point that is configured
for HTTPS, the pull-distribution point must be co-located on a computer that runs the Configuration Manager client. "
Does "why" really matter , who cares? It just is. Whether it was an oversight, a coding bug, or an act of God doesn't change anything. Why does there "have to be" an easier way? And what's wrong with using the VBScripts others have
written? A script is a script is a script particularly if you've been given it already. Just because the hammer is pink doesn't mean it can't hammer the nail in.
Jason | http://blog.configmgrftw.com | @jasonsandys -
SCCM 2012 R2 - Distribution Point
Hello,
I have a SCCM environment configured only one server to handle all the Role MP, DP, etc..
SQL Server 2012 is Remotely installed.
I am using Windows server 2012 R2 Standard with installed SCCM 2012 R2.
I am using VMware vSphere 5.1
I want to use SCCM 2012 R2 for PXE boot to deploy Windows 7 Enterprise 32 bit and 64 bit.
But I am unable to install the Windows 7 Enterprise 32 bit and 64 bit through PXE Boot.
When I am trying to install on VM this error message is:
Downloaded WDSNBP from 10.100.1.178
Pending request ID : 31
Message from Administrator:
Configuration Manager is looking for Policy.
Contacting Server 10.100.1.178
PXE Boot aborted. Booting to next device...
PXE-MOF: Existing Intel PXE ROM.
The operating system was not found. Try Disconnecting.......
And 2nd thing when I am selecting Packages in SCCM 2012 R2 Console and right clicking on User State Migration Tool for Windows 8.1 and Selecting Distribute Content and After clicking next when its asking for Specify the Content destination its now showing
any Distribution Point.
Can someone help me please to fix this issue.
Thanks a lot and help/advise much appreciated.Contacting Server 10.100.1.178
PXE Boot aborted. Booting to next device...
This indicates that there's no task sequence deployed to the computer that was PXE booted.
Torsten Meringer | http://www.mssccmfaq.de -
SCCM 2012 R2 Distribution Point Installs but does not send packet.
I installed SCCM 2012 Primary Site on a server and need to create 18 Dps, could create 12 however I am having trouble creating the last 6, the link from headquarters to branch MPLS is a full 256 Kb, it creates the folders and DPs however the server can not
send the first two packages that are Client Package Configuration Manager and Configuration Manager Client Upgrade package only 6 DPS the other 12 I got.
The computer account is in the Administrators group and Admin Domains;
Already checked the WMI with Wbemtest;
I uninstalled and installed the DP again;
Below is the log, changed the name to contoso by issues of customer privacy.
Sleep 928 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:00:07 2528 (0x09E0)
Sleeping for 60 minutes before content cleanup task starts. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:10:52
5772 (0x168C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:12:13 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40 2528 (0x09E0)
Starting package processing thread, thread ID = 0x14F4 (5364) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40
2528 (0x09E0)
Sleep 60 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:40 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.072 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Retrying package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5264 (0x1490)
Thread Handle = 0000000000002330 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5264 (0x1490)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5264 (0x1490)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41 5364 (0x14F4)
DP thread with thread handle 0000000000002330 and thread ID 5264 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Only retrying local DP update for package LAA00003, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
SourceVersion (1) of package LAA00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5364 GMTDATE=qui ago 14 03:15:41.684 2014 ISTR0="Configuration Manager Client Package"
ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:41 5364 (0x14F4)
Failed to process package LAA00003 after 66 retries, will retry 34 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:41
5364 (0x14F4)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:46 2528 (0x09E0)
Starting package processing thread, thread ID = 0x14D0 (5328) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
2528 (0x09E0)
Sleep 1824 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.300 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
Retrying package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5736 (0x1668)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5736 (0x1668)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5736 (0x1668)
Thread Handle = 0000000000002A50 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
DP thread with thread handle 0000000000002A50 and thread ID 5736 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Only retrying local DP update for package LAA00004, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
SourceVersion (1) of package LAA00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:15:47 5328 (0x14D0)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5328 GMTDATE=qui ago 14 03:15:47.910 2014 ISTR0="Configuration Manager Client Upgrade Package"
ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47 5328 (0x14D0)
Failed to process package LAA00004 after 66 retries, will retry 34 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:47
5328 (0x14D0)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:52 2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:15:52 2528 (0x09E0)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:42:18 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 2528 (0x09E0)
Starting package processing thread, thread ID = 0x1394 (5012) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
2528 (0x09E0)
Sleep 60 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:23.524 2014 ISTR0="LAA00003" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5012 (0x1394)
Retrying package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
No action specified for the package LAA00003. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5012 (0x1394)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5112 (0x13F8)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:23 5112 (0x13F8)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
5112 (0x13F8)
Thread Handle = 0000000000001CF0 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23 5012 (0x1394)
DP thread with thread handle 0000000000001CF0 and thread ID 5112 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:23
5012 (0x1394)
Only retrying local DP update for package LAA00003, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
StoredPkgVersion (1) of package LAA00003. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
SourceVersion (1) of package LAA00003. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5012 GMTDATE=qui ago 14 03:46:24.068 2014 ISTR0="Configuration Manager Client Package"
ISTR1="LAA00003" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00003" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:24 5012 (0x1394)
Failed to process package LAA00003 after 67 retries, will retry 33 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:24
5012 (0x1394)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:24
5012 (0x1394)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 2528 (0x09E0)
Starting package processing thread, thread ID = 0x176C (5996) SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:29.592 2014 ISTR0="LAA00004" ISTR1="" ISTR2=""
ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004" SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 5996 (0x176C)
Retrying package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
No action specified for the package LAA00004. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
Start adding package to server ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\... SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 5996 (0x176C)
Will wait for 1 threads to end. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
Attempting to add or update a package on a distribution point. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 4576 (0x11E0)
The distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ is not installed or upgraded yet. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:29 4576 (0x11E0)
Error occurred. Performing error cleanup prior to returning. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
4576 (0x11E0)
Thread Handle = 00000000000025F8 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
DP thread with array index 0 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29 5996 (0x176C)
DP thread with thread handle 00000000000025F8 and thread ID 4576 ended. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:29
5996 (0x176C)
Only retrying local DP update for package LAA00004, no need to replicate package to child sites. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
StoredPkgVersion (1) of package LAA00004. StoredPkgVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
SourceVersion (1) of package LAA00004. SourceVersion in database is 1. SMS_DISTRIBUTION_MANAGER
14/08/2014 00:46:30 5996 (0x176C)
STATMSG: ID=2302 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=5996 GMTDATE=qui ago 14 03:46:30.137 2014 ISTR0="Configuration Manager Client Upgrade Package"
ISTR1="LAA00004" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=400 AVAL0="LAA00004"
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30 5996 (0x176C)
Failed to process package LAA00004 after 67 retries, will retry 33 more times SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30
5996 (0x176C)
Exiting package processing thread. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:30
5996 (0x176C)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:35 2528 (0x09E0)
Sleep 1825 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:46:35 2528 (0x09E0)
Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA. SMS_DISTRIBUTION_MANAGER 14/08/2014
00:59:32 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 5292 (0x14AC)
Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:32 4008 (0x0FA8)
Processing status update for package LAA00003 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32
4008 (0x0FA8)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 2528 (0x09E0)
Sleep 1048 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 2528 (0x09E0)
Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00003, Status 5
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:32 4008 (0x0FA8)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\LH810W5O.STA SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:32 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 2528 (0x09E0)
Sleep 1043 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:37 2528 (0x09E0)
Processing incoming file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39
4008 (0x0FA8)
Processing STA for regular DP ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:39 4008 (0x0FA8)
Processing status update for package LAA00004 SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39
4008 (0x0FA8)
Successfully updated the package server status for ["Display=\\ServerDP2.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP2.contoso\ for package LAA00004, Status 5
SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:39 4008 (0x0FA8)
Successfully delete package status file C:\Program Files\Microsoft Configuration Manager\inboxes\distmgr.box\INCOMING\KAO4TLAM.STA SMS_DISTRIBUTION_MANAGER
14/08/2014 00:59:39 4008 (0x0FA8)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 2528 (0x09E0)
Sleep 1038 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:42 2528 (0x09E0)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 5292 (0x14AC)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 2528 (0x09E0)
Sleep 1033 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 00:59:47 2528 (0x09E0)
Sleeping for 60 minutes before content cleanup task starts. SMS_DISTRIBUTION_MANAGER 14/08/2014 01:10:52
5772 (0x168C)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:28 5292 (0x14AC)
Sleep 30 minutes... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33 5292 (0x14AC)
Found notification for package 'LAA00003' SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Found notification for package 'LAA00004' SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Used 0 out of 10 allowed processing threads. SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33 2528 (0x09E0)
Starting package processing thread, thread ID = 0x388 (904) SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:33
2528 (0x09E0)
Starting package processing thread, thread ID = 0x1678 (5752) SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:34
2528 (0x09E0)
Sleep 3600 seconds... SMS_DISTRIBUTION_MANAGER 14/08/2014 01:11:34 2528 (0x09E0)
STATMSG: ID=2304 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=Server1.contosoSITE=LAA PID=4288 TID=904 GMTDATE=qui ago 14 04
Lucas Simoes MCTSNo (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 13/08/2014 23:57:10
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
13/08/2014 23:57:10 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Created sending thread (Thread ID = 0xBE8) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Created sending thread (Thread ID = 0x3B4) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:11
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:11 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:35 3048 (0x0BE8)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:35 948 (0x03B4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:36.046 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 3048 (0x0BE8)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 3048 (0x0BE8)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:36.484 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 948 (0x03B4)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:36 948 (0x03B4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 3048 (0x0BE8)
PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:45 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 3048 (0x0BE8)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3048 GMTDATE=qui ago 14 03:17:45.880 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45 3048 (0x0BE8)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45
3048 (0x0BE8)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:45
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:45 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 948 (0x03B4)
PullDP Notification failed. Failure count = 28/30, Restart time = 14/08/2014 00:37:52 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 948 (0x03B4)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=948 GMTDATE=qui ago 14 03:17:52.923 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52 948 (0x03B4)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52
948 (0x03B4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:17:52
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:17:52 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:52 4004 (0x0FA4)
Created sending thread (Thread ID = 0x1680) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:52
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:53 4004 (0x0FA4)
Created sending thread (Thread ID = 0x18A4) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:53
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:37:53
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:37:53 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:16 5760 (0x1680)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:17 6308 (0x18A4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:20.098 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 6308 (0x18A4)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:20.111 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 5760 (0x1680)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 6308 (0x18A4)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:20 5760 (0x1680)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 6308 (0x18A4)
PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:43 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 6308 (0x18A4)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=6308 GMTDATE=qui ago 14 03:38:43.622 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43 6308 (0x18A4)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43
6308 (0x18A4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:43
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:43 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 5760 (0x1680)
PullDP Notification failed. Failure count = 29/30, Restart time = 14/08/2014 00:58:50 E. South America Standard Time SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 5760 (0x1680)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=5760 GMTDATE=qui ago 14 03:38:50.708 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50 5760 (0x1680)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50
5760 (0x1680)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:38:50
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:38:50 4004 (0x0FA4)
Found send request with ID: 10068, Package: LAA00003, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Created sending thread (Thread ID = 0xF28) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
Found send request with ID: 10069, Package: LAA00004, Version:1, Priority: 2, Destination: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Created sending thread (Thread ID = 0x11D0) SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:58:50
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:58:50 4004 (0x0FA4)
Pull DP Sending thread starting for Job: 10068, package: LAA00003, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:15 3880 (0x0F28)
Pull DP Sending thread starting for Job: 10069, package: LAA00004, Version: 1, Priority: 2, server: SERVERDP1.CONTOSO, DPPriority: 200 SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:15 4560 (0x11D0)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:16.990 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:16 3880 (0x0F28)
Sending package info bundle LAA00003 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 3880 (0x0F28)
STATMSG: ID=8206 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:17.845 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 4560 (0x11D0)
Sending package info bundle LAA00004 to PullDP. ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\ SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:17 4560 (0x11D0)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
Attempted max retry count. The job would be marked for deletion now. SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
Sent status to the distribution manager for pkg LAA00003, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27 3880 (0x0F28)
STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.291 2014 ISTR0="LAA00003" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 3880 (0x0F28)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=3880 GMTDATE=qui ago 14 03:59:27.305 2014 ISTR0="LAA00003" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00003" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27 3880 (0x0F28)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27
3880 (0x0F28)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:27
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:27 4004 (0x0FA4)
Repairing PullDP, check \\SERVERDP1.CONTOSO\SMS_DP$\sms\logs\pulldp_repair.log SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
Attempted max retry count. The job would be marked for deletion now. SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
Sent status to the distribution manager for pkg LAA00004, version 1, status 5 and distribution point ["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34 4560 (0x11D0)
STATMSG: ID=8207 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.335 2014 ISTR0="LAA00004" ISTR1="SERVERDP1.CONTOSO" ISTR2="" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="SERVERDP1.CONTOSO" SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4560 (0x11D0)
STATMSG: ID=8211 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_PACKAGE_TRANSFER_MANAGER" SYS=Server1.contoso SITE=LAA PID=4288 TID=4560 GMTDATE=qui ago 14 03:59:34.337 2014 ISTR0="LAA00004" ISTR1="1" ISTR2="SERVERDP1.CONTOSO" ISTR3="" ISTR4=""
ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=3 AID0=400 AVAL0="LAA00004" AID1=410 AVAL1="1" AID2=404 AVAL2="["Display=\\ServerDP1.contoso\"]MSWNET:["SMS_SITE=LAA"]\\ServerDP1.contoso\"
SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34 4560 (0x11D0)
Pull DP Sending thread complete SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34
4560 (0x11D0)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 00:59:34
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 00:59:34 4004 (0x0FA4)
No (more) send requests found to process. SMS_PACKAGE_TRANSFER_MANAGER 14/08/2014 01:19:34
4004 (0x0FA4)
Waiting for new/rescheduled send requests, Maximum Sleep Time = 20 minutes SMS_PACKAGE_TRANSFER_MANAGER
14/08/2014 01:19:34 4004 (0x0FA4)
No (more) send requests found to process.
SMS_PACKAGE_TRANSFER_MANAG
Lucas Simoes Rezende MCP, MCTS , ITIL V3 -
SCCM 2012 - Change Distribution Point's Site System Properties Site Code
Hello All,
I'm hoping someone can help me out. Here's what I have and here's what I'm trying to do.
SCCM 2012 R1
Each of our offices has a Windows 7 SP1 Ent PC that is a distribution point for that office's 10-20 machines. A number of these offices and their DPs were setup prior to me setting up a number of Secondary Site Servers. So right now, these DPs' site codes
are the primary site server's. I'd like to change these to one of the Secondary Site Servers.
When I go to the Site System properties of one of these Win7 distribution points, the Site Code is grayed out.
So, the question is, how can I change one of these DPs' site codes?
Thanks in advance to whomever helps!!
BillThat's a strange reason for using Secondary Sites. How many clients are you managing? Have you good WAN links?
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson -
Adding New SCCM 2012 SP1 Distribution Point To Replace Existing Distribution Point
We currently in the process of the doing a site server refresh at all our remote sites. Each remote site currently has a physical 2012 SP1 DP, and will be replaced with a new DP at each location, and will eventually decommission the current one.
What's the best way to introduce a new DP and remove the old one?
Thanks
BernYou can use this method if distributing through the WAN is not an option.
http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx
If you don't care, just add it to SCCM and replicate your content. Modify your boundary once done.
I hope you have a DP Group, if so, just make it member of the group and all your content will be copied. If not, you'll have to go through all your content and add it manually or script the process using PowerShell.
To remove your existing it's simply a matter of removing the "Distribution Point" role on your Server using the SCCM Console. (Administration / Site Configuration /Site Server, select your distribution point, right click Remove)
Benoit Lecours | Blog: System Center Dudes -
Distribution Point IIS Config - Multiple applications using Default Web Site
Hi all,
I've having some problems with a distribution point, when trying to download content I'm getting the following error in the datatransferservices.log:
Error sending DAV request. HTTP code 500, status 'Internal Server Error'
Looking at IIS, I can see that another application (uniflow print server) has published folders under the Default Web Site.
Reading
similar errors it appears it may be to do with ISAPI filters being configured by the other application. Unfortunately these filters are required by the Uniflow application. So, my question is:
Is there any way to change the web site used by the distribution point?
Thanks,
IainNot on a one off basis, no. The web sites are tied to ports which means you would also have to change the port. Both are global changes. The better solution is to not multi-purpose a DP.
Jason | http://blog.configmgrftw.com -
SCCM 2012 sync distribution point WITHOUT actuvating/using the second DP
Hi,
Pls advise howto sync distribution points WITHOUT using the second one (to which is synced).
We only want to activate it after a full sync and in a controllerd manner (to test if it works fully correct).
Note: I removed it in the boundary group, tab references, site system servers for now. It is still active in the Distribution points underneath Administration.
J.
Jan HoedtNo, he's saying that if it's not included in a boundary group (and not enabled for fallback), then no clients will ever find it to be used. Clients locate and use DPs entirely based upon their association with a boundary group and the boundaries within
that boundary group. Thus, if its not part of a boundary group, client won't be able to locate it. Just because its active doesn't mean anything.
Jason | http://blog.configmgrftw.com -
SCCM 2012 SP1 Distribution points not updating
The package that holds my MS updates is not updating on my distribution points ever since I upgraded to SP1. If I remove the package from the distribution points and then add it back it will work fine. This is happening to me every I add updates to this
package. Below is part of the smsdpprov.log file from one of my distro points.
[C90][Thu 02/14/2013 11:03:51]:Content 'f16906f8-d1d4-44df-8cf7-35dd7428893a' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:55]:Content '1ebc4751-063f-46dd-a7ae-096cce3545dc' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:56]:Content 'b2903470-59e0-4d89-a1a5-808b58c9fd4e' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:03:58]:Content 'f058ee07-a66e-4bdf-8a53-7cc30affe333' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:00]:Content '03546ec3-2613-46ce-bf0c-a6064149f2c6' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:03]:Content '7492e432-b69c-478c-8c7b-7c2396302eb4' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:05]:Content '995a1a82-6d7c-4fb6-9e1b-8cfac070b787' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:06]:Content 'a0a2a75d-beab-49ca-96e5-e03afa98dc8f' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:08]:Content '21061204-1d54-4262-bc90-cf5922191940' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:11]:Content 'ce9e07ad-1467-4da5-bf03-8c7013743d34' for package 'ENS00006' has been added to content library successfully
[C90][Thu 02/14/2013 11:04:14]:MoveFile failed for \\?\C:\SCCMContentLib\DataLib\6178f7ae-a640-4e04-a851-abd13239a50f.ENS00006.temp to \\?\C:\SCCMContentLib\DataLib\6178f7ae-a640-4e04-a851-abd13239a50f
[C90][Thu 02/14/2013 11:04:14]:FileRename failed; 0x80070005
[C90][Thu 02/14/2013 11:04:14]:CContentDefinition::Finalize failed; 0x80070005
[C90][Thu 02/14/2013 11:04:14]:Failed to finalize content '6178f7ae-a640-4e04-a851-abd13239a50f' for package 'ENS00006'. Error code: 0X80070005I've got the same issue. When I look at the smsdpprov.log on the distribution point, this is what I see.
[EB0][Thu 10/31/2013 08:39:08]:Content '0a3fe62c-58ce-47c7-b635-e23407515ecb' for package 'ONB0007A' has been added to content library successfully
[EB0][Thu 10/31/2013 08:39:08]:Content '809b4727-78b3-48bd-85ca-f2fdcf668297' for package 'ONB0007A' has been added to content library successfully
[EB0][Thu 10/31/2013 08:39:08]:MoveFile failed for
\\?\E:\SCCMContentLib\DataLib\5263454e-e3de-49e5-a077-48dba0eefe93.ONB0007A.temp to
\\?\E:\SCCMContentLib\DataLib\5263454e-e3de-49e5-a077-48dba0eefe93
[EB0][Thu 10/31/2013 08:39:08]:FileRename failed; 0x800700b7
[EB0][Thu 10/31/2013 08:39:08]:CContentDefinition::Finalize failed; 0x800700b7
[EB0][Thu 10/31/2013 08:39:08]:Failed to finalize content '5263454e-e3de-49e5-a077-48dba0eefe93' for package 'ONB0007A'. Error code: 0X800700B7
If I reboot the DP, then the package gets updated. I'd like to figure out how to make this not happen :) -
SCCM 2012 shared distribution point reassignment - old SCCM 2007 folders/files delete
Ok, I've looked, googled, binged, and cannot find any definitive answer on this, I've even asked a Microsoft Engineer, and I fear they are just as confused as I am, please help!
The scenario: I'm migrating from SCCM 2007 to 2012 and of course have shared DP's, I reassign a shared DP and this is what I expected to happen but did not - all the old .pck files from 2007 (in the SMSPKG folder on the OLD DP) should have been deleted AFTER
the content was converted into the single instance store, they are still there! if they are supposed to be there...why then is it called a SINGLE instance store if there are TWO folders containing compressed source files??? Also, the files in my OLD SMSPKGD$
(extracted source for 2007) are still there as well, even though prior to the reassignment of the DP I changed all of my deployments to download/run locally...what gives?
The end result of me reassigning my DP is the new content is essentially doubling the space taken up on the drive...not cool. Can I delete the content of the legacy folders (either the .pck or the folders in SMSPKGD$)?
TerryHi,
"The folder is used to temporarily store PCK files that get transferred to child or secondary sites. If you don't have any of those, the folder won't ever have anything in it. Even if you do have one of those, it'll still be empty most of the time because
PCK file storage in 2012 is temporary only."
For more information:http://social.technet.microsoft.com/Forums/en-US/2c5e6049-8566-4638-8ba8-3768c74c53f6/smspkg-folder-on-primary-site-server-which-is-not-a-dp?forum=configmanagergeneral
Best Regards,
Joyce
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Distribution point not installing
I'm having some issues with a new Distribution point. This is my first Server 2012 R2 distribution point and after installing the roles and features (I believe are required) the distribution point does not install. I can't see anything on the distribution
point, nor can I see any configuration on the SCCM console. It displays as a site system with a role of Distribution point but distmgr.log does not display any activity except
Successfully modified DP ["Display=\\DP02.Domain.net\"]MSWNET:["SMS_SITE=CTG"]\\DP02.Domain.net\ Drizzle Role to 1 SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:13 5096 (0x13E8)
ConfigureDP SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:13 5096 (0x13E8)
IISPortsList in the SCF is "80,80". SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:13 5096 (0x13E8)
IISSSLPortsList in the SCF is "443,443". SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:13 5096 (0x13E8)
IISWebSiteName in the SCF is "". SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:13 5096 (0x13E8)
IISSSLState in the SCF is 480. SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:13 5096 (0x13E8)
DP registry settings have been successfully updated on SECROWFIL03.sec.ssegroup.net SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:42 5096 (0x13E8)
STATMSG: ID=9501 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=\\MP01.Domain.net SITE=CTG PID=5580 TID=5096 GMTDATE=Wed Aug 13 10:20:42.786 2014 ISTR0="["Display=\\DP02.Domain.net\"]MSWNET:["SMS_SITE=CTG"]\\DP02.Domain.net\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\DP02.Domain.net\"]MSWNET:["SMS_SITE=CTG"]\\DP02.Domain.net\" SMS_DISTRIBUTION_MANAGER 13/08/2014
11:20:42 5096 (0x13E8)
STATMSG: ID=9503 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=\\MP01.Domain.net SITE=CTG PID=5580 TID=5096 GMTDATE=Wed Aug 13 10:20:42.788 2014 ISTR0="["Display=\\DP02.Domain.net\"]MSWNET:["SMS_SITE=CTG"]\\DP02.Domain.net\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\DP02.Domain.net\"]MSWNET:["SMS_SITE=CTG"]\\DP02.Domain.net\" SMS_DISTRIBUTION_MANAGER 13/08/2014
11:20:42 5096 (0x13E8)
ConfigurePXE SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:42 5096 (0x13E8)
Translated server name SECROWFIL03.sec.ssegroup.net to sec.ssegroup.net\SECROWFIL03.sec.ssegroup.net. SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:43 5096 (0x13E8)
CWmi::Connect() failed to connect to
\\DP02.Domain.net\root\SCCMDP. Error = 0x800706BA SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:44 5096 (0x13E8)
STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=\\MP01.Domain.net SITE=CTG PID=5580 TID=5096 GMTDATE=Wed Aug 13 10:20:44.002 2014 ISTR0="["Display=\\DP02.Domain.net\"]MSWNET:["SMS_SITE=CTG"]\\DP02.Domain.net\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\DP02.Domain.net\"]MSWNET:["SMS_SITE=CTG"]\\DP02.Domain.net\" SMS_DISTRIBUTION_MANAGER 13/08/2014
11:20:44 5096 (0x13E8)
Failed to connect to DP WMI provider SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:44 5096 (0x13E8)
CDistributionManager::ConfigurePXE failed; 0x800706ba SMS_DISTRIBUTION_MANAGER 13/08/2014 11:20:44 5096 (0x13E8)
Any Ideas?
If anyone has the list of Operating system requirements for a DP running on Server 2012R2 it would be appreciated also.I've just tried to reach the admin$ from a remote PC and (from the local server) using PSexec and I can read the admin$ directory without any issues so there is access to the remote DP. I haven't yet looked at the firewall logs but only because
the firewall ports are already allowing traffic to our other DP's.
do the firewall rules differ from server 2008, 2012 and 2012R2? (I have previous 2008 and 2012 servers but this is the first R2 server we are setting up as a DP.)
The firewall rules are the same for 2k8 and 2k12.
When you reach the admin$ share are you using Psexec as the system account and not your use account ? (-i -s as Torsten mentionned) ?
Do you have any other firewall maybe between the machine and the site Server ?
Do you have the SCCMContentLib folder created on the DP ? (On the drive specified in the wizard).
Benoit Lecours | Blog: System Center Dudes -
Monitoring and troubleshooting in-place distribution point upgrades
I have a shared SCCM 2007 secondary site server that I'd like to upgrade to a SCCM 2012 Distribution Point. I went to the Administration>Migration>Source Hierarchy>Shared Distribution Points and right clicked and hit Upgrade and then proceeded
through the Upgrade Shared Distribution Point Wizard. Then under Administration>Migration>Distribution Point Upgrades, monitored that status, but even though I left it overnight, the status is still "Upgrade distribution point." I checked under
the Monitoring>Distribution Status>Distribution Point Configuration Status and selected the name of my distribution point and noticed that I'd forgotten to add the Site Server's computer account to the local admin group on my Distribution Point Server.
But even though I've corrected that, the status of the upgrade has not changed and there is nothing of note in resource manager indicating that the process is underway.
Are there any additional logs to monitor the progress of the in-place Distribution Point upgrade? Are there any other troubleshooting steps I can do to determine why the status of the upgrade isn't complete?Hi all
I would like to share my experience with migrating from SCCM 2007 Distribution Points to SCCM 2012. We have in our test environment 39 secondary site systems with the role of distribution points and I wanted to play with the migration feature "Share
Distribution Point" scenario. In the night in which I had prepared the Secondary sites using the migration wizard, 30 of the 39 sites completed in approximately 3 hours with the status "Completed upgrade distribution point". On all distribution
points the same completion date was entered. It seems that a task at specific times in the background check again whether the migration is complete and the status is consolidated. The remaining 9 Distribution Points were then completed almost exactly after
12 hours.
I then inquired about the migrated packages. On the night not a single package came in the status 'Targeted'. After about 12 hours I saw at once that now at least the distribution points were recorded in most packages. The status 'Installed' but got no distribution
point. I then startet at about 10 packages an update distribution job. These then became the status of 'Installed' more than 4 hours later. Then the weekend was between and on Monday morning, no other distribution points were listed as 'Installed'. I checked
local on the distribution point, if all of the packages was converted. This was the case, not only the 10 I have updated. The packages then should be available during deployments, I think. But I have not tested it.
If you have looked at a package converted times more precise, the status of most distribution point is 'Unknown'. I then googled for this situation, and I have found this
article. There seems to be a bug which is currently in a solving process.
For me, there are two solutions for this problem:
1. Waiting for the hotfix and the problem is then solved centrally. By the fact, that we migrate the 340 Secodary Sites in 3 weeks, I don't think that this hotfix will be available.
2. Depending on the number of distribution points and packages it may be helpful if all 'targeted' packages are again updated. In this 'Unknown' status situation I simply do not know if the packages are really available or not.
I found another problem with the Distribution Point migration. Actually with the migration of SCCM 2007 Secondary Site Server to SCCM 2012 remote Distribution Point, an uninstallation of the secondary site server should be performed. We had tested this with
SCCM 2012 RTM and it was working at that time. With the update to SCCM 2012 SP1 here again seems a problem with the migration to be added. In the SCCM 2007 environment, the Secondary Site Server were removed during migration. But not local uninstalled, even
after 3 days.
Conclusion to the Distribution Point in SCCM 2012 SP1 migration:
As always, you just have to have patience until the migration jobs are completed. Certain tasks must then be carried out by hand. In my view, the missing log information is the biggest problem. Without the log information I was blind
during the migration. If you only have a short window for migration and like us, that we need to migrate 340 Secondary Site Server in the production environment, the scenario must be carefully considered. We proof now to not migrate the Secondary Sites with
the Migration Wizzard, but start from the ground up a new installation of Distribution Points followed by the necessary sync packages.
Kind regards Stefan Somogyi -
Script "upgrade shared distribution points"
Hi
We have about 400 SCCM 2007 Secondary Sites and need to migrate them to SCCM 2012 SP1 Distribution Points. As you can image we don't want to click 400 times during migration wizard.
Is there a way to script the upgrade of all shared distribution point? e.g. powershell or SDK (C# or VBScript)
Many, many thanks in advance,
WolfgangTry with "update-help" (see REMARKS)...
I get following short information:
NAME
Start-CMDistributionPointUpgrade
SYNTAX
Start-CMDistributionPointUpgrade -SiteCode <string> -SharedDistributionPoint <IResultObject#SMS_MigrationDP>
-CertificateExpirationTimeUtc <datetime> -AllowPreStaging <bool> [-PublicFqdn <IResultObject#SMS_MigrationDP>]
[-InstallationAccount <IResultObject#SMS_SCI_Reserved>] [-InitiateConnection <bool>] [-InstallInternetServer
<bool>] [-ClientConnectionType <ClientConnectionTypes> {Intranet | Internet | InternetAndIntranet}]
[-EnableAnonymous <bool>] [-MinFreeSpaceMB <int>] [-PrimaryContentLibraryLocation <DriveType> {Automatic | A | B |
C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}]
[-SecondaryContentLibraryLocation <DriveType> {Automatic | A | B | C | D | E | F | G | H | I | J | K | L | M | N |
O | P | Q | R | S | T | U | V | W | X | Y | Z}] [-PrimaryPackageShareLocation <DriveType> {Automatic | A | B | C |
D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}]
[-SecondaryPackageShareLocation <DriveType> {Automatic | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O
| P | Q | R | S | T | U | V | W | X | Y | Z}] [-EnablePxeSupport <bool>] [-AllowRespondIncomingPxeRequest <bool>]
[-EnableUnknownComputerSupport <bool>] [-ComputersUsePxePassword <securestring>] [-UserDeviceAffinity
<UserDeviceAffinityType> {DoNotUse | AllowWithManualApproval | AllowWithAutomaticApproval}]
[-MacAddressForRespondingPxeRequest <string[]>] [-PxeServerResponseDelaySeconds <int>] [-ValidateContentSchedule
<IResultObject#SMS_ST_RecurWeekly>] [-ContentValidationPriority <Priority> {Lowest | Low | Medium | High |
Highest}] [-BoundaryGroup <IResultObject#SMS_BoundaryGroup[]>] [-AllowFallbackForContent <bool>]
[-PathForSavingMigratedPackage <string>] [-WhatIf] [-Confirm] [<CommonParameters>]
Start-CMDistributionPointUpgrade -SiteCode <string> -SharedDistributionPoint <IResultObject#SMS_MigrationDP>
-CertificatePath <string> -AllowPreStaging <bool> [-PublicFqdn <IResultObject#SMS_MigrationDP>]
[-InstallationAccount <IResultObject#SMS_SCI_Reserved>] [-InitiateConnection <bool>] [-InstallInternetServer
<bool>] [-ClientConnectionType <ClientConnectionTypes> {Intranet | Internet | InternetAndIntranet}]
[-EnableAnonymous <bool>] [-CertificatePassword <securestring>] [-ForceWhenDuplicateCertificate <bool>]
[-MinFreeSpaceMB <int>] [-PrimaryContentLibraryLocation <DriveType> {Automatic | A | B | C | D | E | F | G | H | I
| J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}] [-SecondaryContentLibraryLocation
<DriveType> {Automatic | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W
| X | Y | Z}] [-PrimaryPackageShareLocation <DriveType> {Automatic | A | B | C | D | E | F | G | H | I | J | K | L
| M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}] [-SecondaryPackageShareLocation <DriveType> {Automatic |
A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z}]
[-EnablePxeSupport <bool>] [-AllowRespondIncomingPxeRequest <bool>] [-EnableUnknownComputerSupport <bool>]
[-ComputersUsePxePassword <securestring>] [-UserDeviceAffinity <UserDeviceAffinityType> {DoNotUse |
AllowWithManualApproval | AllowWithAutomaticApproval}] [-MacAddressForRespondingPxeRequest <string[]>]
[-PxeServerResponseDelaySeconds <int>] [-ValidateContentSchedule <IResultObject#SMS_ST_RecurWeekly>]
[-ContentValidationPriority <Priority> {Lowest | Low | Medium | High | Highest}] [-BoundaryGroup
<IResultObject#SMS_BoundaryGroup[]>] [-AllowFallbackForContent <bool>] [-PathForSavingMigratedPackage <string>]
[-WhatIf] [-Confirm] [<CommonParameters>]
ALIASES
None
REMARKS
Get-Help cannot find the Help files for this cmdlet on this computer. It is displaying only partial help.
-- To download and install Help files for the module that includes this cmdlet, use Update-Help. -
Failed to resume task sequence / ConfigMgr 2012 SP1 vs. R2
We have two configMgr environment at customers place. A Lab Environment and production Environment. Till July 2014 both environment were at the same Version level (ConfigMgr 2012 SP1).
We create the WIM-Image in LAB to use this WIM in the production. There were no problems till yet. Some months before we updated our
LAB to ConfigMgr 2012 R2 CU2. The Production is still
ConfigMgr 2012 SP1 CU3. Now if we create a new image in our LAB we can't use this Image in Production.
OSD ends after 'Setup Windows and ConfigMgr' step. There is an error:
Can't we use an captured Image from a ConfigMgr 2012 R2 environment in a ConfigMgr 2012 SP1 environment?I am not 100% if this is really supported (even if the versions were equal). I've seen situations where you can still see references to the MP and sitecode of the test environment when having a close look at the logs (although it did not cause real issues).
Torsten Meringer | http://www.mssccmfaq.de
Maybe you are looking for
-
How To turnoff compatibility mode settings in IE 10
Hi, I have Domain and Forest Functional level is 2008 R2. I got a requirement from a project to turnoff IE10 compatibility mode for windows 7. Can anyone help me with an ADMS template which I can import to view settings in GPO. Regards, Deepak
-
How do I remove ROCKETPDF which is spoiling Adobe
Help Please , I apper to inadvertatly got RocketPDF on my PC which is adversly affecting ADOBE, Pplease can someone tell a beginner how to remove it. Its not on the list of Programms unless under an assumed name. Colin McIntyre
-
Mysterious java.sql.SQLException: ORA-00600:
Hi All, I'm running oracle 9.0.2 on windows xp, 512meg mem. No problem accessing the db via isql, no problem with jdbc doing inserts but can't query?! DriverManager.registerDriver((Driver)drvClass.newInstance()); m_con = DriverManager.getConnection(j
-
Why won't my full access NFL app run on my Iphone 4S after OS 6 update?
I ran the update for my Iphone 4S, then discovered that the Verizon NFL app (that I pay extra for) and a coupld of other apps no longer runs on my Verizon 3G network. Stupidly, I did a restore. The only thing that did for me was lose my phone connect
-
I cant change the backround color for my pages poster document, does anybody know how I can do it or if I can for that matter?