SCCM 2012: failed to connect to distribution point

Hi folks,
I have an intermittent issue and can't figure out the reason so far.
I have a primary server and multiple distribution points. The primary does not have a DP configured. When I deploy a new distribution point, I have the following messages:
Distribution Manager failed to connect to the distribution point. Check your network and firewall settings.
and
Distribution Manager failed to find or create the defined share or volume on distribution point.
DistMgr.log shows the following:
CWmi::Connect() failed to connect to \\AMB-SCCM-E.domain.name\root\CIMv2. Error = 0x800706BA
STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=BBD-SCCM-E.domain.name SITE=IDC PID=2120 TID=3376 GMTDATE=do jun 28 07:24:17.463 2012 ISTR0="["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\"
ERROR DPConnection::ConnectWMI() - Failed to connect to AMB-SCCM-E.domain.name. error = 0x800706ba
Failed to find a valid drive on the distribution point ["Display=\\AMB-SCCM-E.domain.name\"]MSWNET:["SMS_SITE=IDC"]\\AMB-SCCM-E.domain.name\
Cannot find or create the package share.
Error occurred. Performing error cleanup prior to returning.
However, after a while (couple of hours), it looks like everything is distributed on the DP. But this message keeps on coming back during the course of the day and every time a new DP is deployed.
I checked permissions, IIS, WMI, but I can't find out the cause of this behavior. I have events about WMI (id 5605) but I can connect to the WMI workspace (root\MicrosoftIISv2) with no issues.
Can anyone shed some light on this please? It would be greatly appreciated.
Cheers,
Safdar.

To clarify: it's not enough to tick "Windows Authentication" in Add Roles/Features - it actually has to be enabled in IIS configuration.
There are also suggestions to run mofcomp.exe smsdpprov.mof
Tip of me hat:
http://weikingteh.wordpress.com/2013/12/03/failed-to-install-a-new-distribution-point-error-0x800706ba/

Similar Messages

SCCM 2012 R2 unable to install Distribution Point on Windows 7

We have a SCCM 2012 R2 CU 2, single site. We would like to deploy the distribution point at 1 of the branch but hit with issues.
We tried various workaround. Reinstall IIS, manually install IIS.
We had repair WMI, and test WBEMTEST to the WMI and proof it able to connect, given security permission to everyone. Problem still persist.
The distmgr.log shows
CWmi::Connect() failed to connect to \\["Display=\\dpname\"]MSWNET:["SMS_SITE=sitename"]\\"dpname\\root\default. Error = 0x80070005
GetWMIObject - Failed to connect to root\default on ["Display=\\dpname\"]MSWNET:["SMS_SITE=sitename"]\\dpname\. Error code: 0x80070005
CDistributionManager::SetDpRegistry failed; 0x80070005
Anyone can help?

Hi,
Have you tried to disable firewall? Just for test.
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.

Sccm 2012 Can we migrate a distribution point to a Secondary site

Can we upgrade our SCCM 2012 Distribution point to a Secondary Site? Can anyone advise the process please?

Hi,
Please refer to the link below:
Planning a Content Deployment Migration Strategy in System Center 2012 Configuration Manager
http://technet.microsoft.com/en-us/library/gg712275.aspx
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.

SCCM 2012 R2 with Server 2003 DIstribution Point

Does anyone know if Server 2003 SP2 can be used as a distribution point? I have a fellow co-worker having issues with getting PxE to work.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. ”

That's right. Windows 2003 Server is not supported. Your original question was about Windows Server 2003 SP2.
That is supported for PXE but does not support multicast or PXE booting of EFI.
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

SCCM 2012 R2 Pull DP fails, works on Update Distribution Points

I'm seeing some odd behavior out of a DP, in particular around driver packages. The system is running SCCM 2012 R2. When I create the driver package I deploy it to the DP on the Primary Site Server. That usually happens in a couple of minutes or less.
I then deploy to a remote DP configured for Pull. This generates the log entries below in the PullDP.log. Even waiting hours doesn't seem to help. If I do a Update Distribution Points for the package, it runs successfully. I know
there was something similar fixed in SP1 CU3.
Intializing DP Monitoring Manager... PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting site code PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting DP Cert Type PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Getting this DP NALPath PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Report state message 0x00000004 to MP PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
Report Body: <ReportBody><StateMessage MessageTime="20140322004854.000000+000" SerialNumber="1"><Topic ID="ACC0006D" Type="902" IDType="0"/><State ID="4" Criticality="0"/><UserParameters
Flags="0" Count="3"><Param>ACC0006D</Param><Param>["Display=\\DP.xxxxx.xxx\"]MSWNET:["SMS_SITE=ACC"]\\DP.xxxxx.xxx\</Param><Param>{B187E44B-4BF3-4748-B437-AFF29D679AA3}</Param></UserParameters></StateMessage></ReportBody>
PullDP 3/21/2014 8:48:54 PM 3564 (0x0DEC)
CPullDPResponse::ReportPackageState return value 0x00000000. PullDP 3/21/2014 8:48:55 PM 3564 (0x0DEC)
Start Download package ACC0006D version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
Start Download package ACC00070 version 1 PullDP 3/21/2014 8:48:55 PM 3460 (0x0D84)
ExecuteJob (1-NotStarted) 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Cannot find FileInfo (\\?\E:\SMS_DP$\ACC00070\9A25E477-3C0C-499E-A0C1-65243BDBCBF0.tar), content download failed PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
CPullDPPkgContJob::ExecuteJob() failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
State at failure: NotStarted PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Content job 9A25E477-3C0C-499E-A0C1-65243BDBCBF0 has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Package job has failed for package ACC00070, version 1 PullDP 3/21/2014 8:48:55 PM 2712 (0x0A98)
Bob

We ended up changing the DP back to a standard distribution point. That allowed the driver package to distribute successfully. so as a result I can't access the logs any longer.
I should note for anyone who goes searching for this that we had problems with every one of our driver packages. As I dug into it I found the contents, it looked like for some reason that it wasn't being transferred from the download location into
the final DP distribution location. It almost looked like SCCM was ignoring driver package types. I don't know if its a bug or just something quirky about this environment.
We were hoping to use Pull DP to handle our distributions more effectively, but we've backed off on that because of all the issues we've had with it. I hate say it, but it appears to be another SCCM 2012 feature that sounds like a good idea, but the
implementation leaves a lot to be desired.
Bob

2012 -- 2012 Migration: How to Reassign Distribution Points that Reside on Source Secondary Site Servers to the Target Site

Source hierarchy AAA is at 2012 R2 CU3 and contains a primary site and 14 secondary sites (A01 through A14). The 14 secondary site servers hold the following roles:
Site system
Management Point
State migration point
Site server
Site database server
Component server
Distribution Point
Target hierarchy BBB is also at 2012 R2 CU3 and contains only a primary site. The goal is to "downgrade" the severs at source secondary sites A01 through A14 to distribution points.
AAA was added as a source site. Data gathering was done. A migration job was created an run, and distribution points from the source hierarchy were shared to allow a phased migration of the clients.
We have reach the point where we are ready to reassign distribution points in sites A01 through A14 from AAA to BBB, but none of the shared distribution points are eligible for reassignment. We surmise that since the DP role is not the only role on
these servers (as you can see from the bullet list above), they are ineligible for reassignment. We are unable to remove most of the roles. In fact, the only 2 roles that can be removed are the DP role itself, and the State Migration
Point. If we delete the secondary site, it removes ALL roles...not leaving any behind...including the one we need...DP.
My question is 2-part:
Is our assumption correct? Must a DP role be the only one on the server for a DP to be eligible for reassignment?
Is there any way we can reassign these DPs instead of deleting everything and building them from scratch?
These secondary site servers are in branch offices and host a lot of distributed packages. It would be very inconvenient to have to rebuild the DPs from scratch and redistribute all those packages over the WAN.

Full Disclosure: I have never used this tool myself. I intend to, however the opportunity or time to do so has not yet arisen.
You could use the techniques outlined in CloneDP (https://gallery.technet.microsoft.com/scriptcenter/CloneDP-for-SCCM-2012-SP1-825ce5b1) to create prestage media on each DP and rebuild. That at least would prevent redistributing over the WAN
Ken provides a nice writeup too: http://blogs.technet.com/b/kensmith/archive/2013/08/01/migrating-the-content-library-between-distribution-points-in-sccm-2012-sp1.aspx

SCCM Install fails. cannot connect to SQL server. "the network was not found"

Hi,
I'm installing SCCM 2012. i have a 2 server boxes. 1x sccm and 1x dedicated SQL. sccm installation is stuck @ connecting to DB.
SQL server is 2012 with SP2, static 1433 port used.installation account used is already sysadmin, sccm computer account also added into SQL local admins. ports 1433, 4022, 445 are already FW open in between SCCM box and SQL Box?
error pop up" "the network was not found"
Pls advise.

if MS is really doing good job then such things (scCm on remote sql) should be easy for us with proper docs. Cheers!
The docs are "proper". They give you all the technical details needed. They assume however that you know how to translate the stated requirements, like the ports necessary (as documented at
http://technet.microsoft.com/en-us/library/hh427328.aspx ), into the environment you are working in. They cannot give you a click by click guide because that would only be applicable to
generic lab environments.
Sorry that that may sound a bit harsh, but it is reality. They simply have no idea what customer networking environments actually look like as the possibilities are simply unbounded. They must rely on the implementer being able to take the core technical
requirements and implement them for the uniqueness of the environment they are working in. In most cases, this is generally straight-forward, but there is a great deal of variety in the real-world.
Jason | http://blog.configmgrftw.com | @jasonsandys

SCCM 2007 to SCCM 2012: Failed Packages are reinstalled ??

We're going to migrate SCCM 2007 to SCCM 2012 (side by side).
On SCCM 2007 we have (for example): Advertisement "ADV1" that execute program "Program1" of Package "Package1". (example....)
What happend if a computer "PC1" is migrated to SCCM 2012 when execution result of "ADV1" on SCCM 2007 was failed ??
1) If I migrate only "Package001" and create a new deployment "Deploy1" to launch program "Program1" of Package "Package1 , by default, "PC1" is going to execute "Deploy1". I known it...
2) If I migrate "Package001" and "ADV1".....Will "PC1" execute "ADV1" on SCCM 2012 ???? This is my question
Thanks

Taken directly from Technet, Regards Damon.
Will
advertisements rerun after they are migrated?
No. Clients that you upgrade from Configuration Manager 2007 will not rerun advertisements that you migrate. System Center 2012 Configuration Manager retains the Configuration
Manager 2007 Package ID for packages you migrate and clients that upgrade retain their advertisement history.
https://technet.microsoft.com/en-au/library/gg682088.aspx

SCCM 2012 console cannot connect to the site

Last Friday for some unknown reason my SCCM console stopped connecting to the site. Reboots of both site servers (MP and database) did nothing. The error is the same as this picture: http://1.bp.blogspot.com/-q0A5GonM498/UCDkreFxc9I/AAAAAAAAAQk/67AQ5tGW_d4/s1600/SCCM%2BConsole.JPG.
I went home for the weekend and on Monday I was actually able to connect to the site. It would take about an hour, but finally the console would load, with the correct information from the site. If I clicked on a different area in the console it would take
forever (about 20 minutes), but it would finally change to that view as well. In troubleshooting I followed all the steps in the attached article, except rebuilding the MOFs. (http://schadda.blogspot.com/2012/08/how-to-fix-issues-related-with_7.html)
After finding that none of that helped I installed CU4 hoping that would help. It completed, but with errors in building the four packages (console, x86, x64 and server). Now the console goes back to the original error and won't connect at all, including
from the actual server.
I have checked and there does not appear to be any bottleneck between the two servers. Network is as it was previously and I can still telnet to the SQL port (1433) from the Management Point.
Infrastructure:
2 servers, running Server 2012 R2 - one server is running everything except the SQL services; SQL Services are running on the second server
SCCM is at 2012 R2 level (now at CU4, was at CU3 at start of problem)
Thank you in advance for your help.
Über Random

This is last entry in the SMSProv.log file. It doesn't show any errors and it just terminates at the time the problem began for us.
CExtUserContext::EnterThread : User=AD\10594690 Sid=0x010500000000000515000000B928868EB3F3E2C669287431D2390100 Caching IWbemContextPtr=0000008E59884E30 in Process 0x5e8 (1512)
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
Context: SMSAppName=Configuration Manager Administrator console
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
Context: MachineName=D088180D.ad.uvu.edu SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
Context: UserName=AD\10594690 SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
Context: ObjectLockContext=1ab442e7-3960-4e44-aa80-87384417fb3e
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
Context: ApplicationName=Microsoft.ConfigurationManagement.exe
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
Context: ApplicationVersion=5.0.7958.1000 SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
Context: LocaleID=MS\0x409 SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
Context: __ProviderArchitecture=32 SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
Context: __RequiredArchitecture=0 (Bool) SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
Context: __ClientPreferredLanguages=en-US,en
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
Context: __CorrelationId={A9D1E6D7-5AA5-0002-759D-DFA9A55AD001}
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
Context: __GroupOperationId=770500 SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
Context: __WBEM_CLIENT_AUTHENTICATION_LEVEL=6
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
CExtUserContext : Set ThreadLocaleID OK to: 1033
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
CSspClassManager::PreCallAction, dbname=CM_UV1
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
ExecMethodAsync : SMS_RbacSecuredObject::UserHasPermissions
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
Requested class =SMS_RbacSecuredObject SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
Requested num keys =0 SMS Provider
3/27/2015 1:30:36 PM 12120 (0x2F58)
CExtProviderClassObject::DoExecuteMethod UserHasPermissions
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=1502105136
SMS Provider 3/27/2015 1:30:36 PM
12120 (0x2F58)
Über Random

SCCM 2012 monitoring - Site Status - Reporting Services Point - Status Critical

Hi all,
I have noticed that the Site Status under Monitoring shows Reporting services point as in Critical state though we do not see anything wrong with SCCM as such (at least we haven't been reported any problems thus far). There is nothing in the event viewer
on SQL Server. Just wanted to know how to resolve this issue. Could you help?
When I try to open status messages for Reporting Services (for any days) it does not return anything as if there are no status messages for this role. Also, could you let me know the log file locations/names for Reporting services point?

Here it is... I have replaced server names with a dummy name.
=================
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.588-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.596-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.616-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.641-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.686-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.713-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.715-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:31.716-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.338-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:23:32.339-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.336-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.347-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.357-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.377-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.404-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.451-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.478-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.480-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:32.481-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.160-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:24:33.161-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.159-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.168-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.188-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.237-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.264-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.462-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.539-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.541-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:33.542-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.796-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:25:34.797-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.795-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.804-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.813-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.834-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.859-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.904-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.905-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.940-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.942-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:34.943-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.724-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.725-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:26:35.726-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.723-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.731-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.752-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.776-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.813-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.902-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.954-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.956-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:35.957-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.728-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.729-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:27:36.730-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.727-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.738-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.747-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.769-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.799-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.848-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.875-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:36.878-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.496-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:28:37.497-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.494-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.503-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.512-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.534-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.563-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.610-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.646-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.648-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.653-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:37.654-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.352-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:29:38.353-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.351-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.361-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.370-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.393-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.432-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.484-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.485-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.520-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.522-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.530-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:38.531-60><thread=6072 (0x17B8)>
Next security configuration at [02/09/2014 13:31:30] $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.270-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:30:39.271-60><thread=6072 (0x17B8)>
Timed Out...~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.268-60><thread=6072 (0x17B8)>
Reporting Services URL from Registry [http://SCCMSQLSERVER/ReportServer/ReportService2005.asmx]~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.277-60><thread=6072 (0x17B8)>
Reporting Services is running $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.286-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.308-60><thread=6072 (0x17B8)>
Confirmed version [10.50.4000.0] for the Sql Srs Instance. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.334-60><thread=6072 (0x17B8)>
Retrieved datasource definition from the server. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.380-60><thread=6072 (0x17B8)>
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ConfigMgr_PRI $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.381-60><thread=6072 (0x17B8)>
Loading localization resources from directory [F:\SMS_SRSRP\SrsResources.dll]   $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.421-60><thread=6072 (0x17B8)>
Looking for 'English (United Kingdom)' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.423-60><thread=6072 (0x17B8)>
Looking for 'English' resources $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
Found resources for 'English' $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:39.424-60><thread=6072 (0x17B8)>
Confirmed the configuration of SRS role [ConfigMgr Report Users]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.088-60><thread=6072 (0x17B8)>
Confirmed the configuration of SRS role [ConfigMgr Report Administrators]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.098-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.700-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.736-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.758-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.791-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.815-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.849-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.870-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.906-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.929-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.961-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:40.998-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.033-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.067-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.099-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.127-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.155-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.192-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.221-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.265-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.303-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.326-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.362-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.381-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.413-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Migration]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.432-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.470-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.495-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.529-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.551-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.585-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.609-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.642-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.666-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.700-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.724-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.755-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.778-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.815-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.835-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.867-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.888-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.924-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.952-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:41.985-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.007-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.042-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.073-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.096-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.132-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.156-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.189-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Users]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.209-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.243-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.268-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.298-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.320-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.349-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.367-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.397-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.418-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.458-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.492-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.511-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.542-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.571-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.599-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Asset Intelligence]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.632-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Compliance and Settings Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.656-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Administrative Security]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.689-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Operating System]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.709-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - A Compliance]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.742-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - B Deployment Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.767-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - C Deployment States]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.800-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - D Scan]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.822-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Updates - E Troubleshooting]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.856-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Driver Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.880-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployment Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.911-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Deployments]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.932-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - Progress]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.966-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Task Sequence - References]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:42.988-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/State Migration]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.020-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.045-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Virtual Applications]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.078-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.113-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Package and Program Deployment]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.137-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User - Device Affinity]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.170-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Metering]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.193-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.227-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Migration]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.247-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Device Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.280-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages - Audit]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.306-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Alerts]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.339-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Status]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.361-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Client Push]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.395-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - CD-ROM]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.415-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Disk]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.445-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - General]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.467-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Memory]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.497-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Modem]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.518-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Network Adapter]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.550-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Processor]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.570-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - SCSI]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.602-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Sound Card]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.625-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Hardware - Video Card]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.655-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Client Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.676-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Discovery and Inventory Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.710-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - General]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.731-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Site - Server Information]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.762-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.785-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.821-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Power Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.852-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Wake On LAN]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.878-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.899-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Files]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.933-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software - Companies and Products]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.967-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Users]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:43.994-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Collections]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.027-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Content]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.052-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Out Of Band Management]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.084-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.106-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Status Messages/Status Messages - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.135-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Endpoint Protection/Endpoint Protection - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.153-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Software Distribution - Application Monitoring/Software Distribution - Application Monitoring - Hidden]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.186-60><thread=6072 (0x17B8)>
The security policy for folder [/ConfigMgr_PRI/Network Access Protection] is out of sync. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.209-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Network Access Protection]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.250-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Replication Traffic]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.284-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/Upgrade Assessment]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.304-60><thread=6072 (0x17B8)>
Confirmed the security policy for folder [/ConfigMgr_PRI/User Data and Profiles Health]. $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.338-60><thread=6072 (0x17B8)>
Root Folder exists $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
Successfully checked that the SRS web service is healthy on server SCCMSQLSERVER.DOMAIN~ $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>
~Waiting for changes for 1 minutes $$<SMS_SRS_REPORTING_POINT><09-02-2014 13:31:44.339-60><thread=6072 (0x17B8)>

SCCM 2012: Failed to insert OSD binaries into the WIM file' error when you create a MDT Task Sequence

Hi,
When I try to import the MDT boot image X86, I get the following error:
Started processing.
Creating boot image.
Copying WIM file.
Mounting WIM file.
WIM file mounted.
Setting Windows PE system root.
Set Windows PE system root.
Set Windows PE scratch space.
Adding standard components.
Adding component: winpe-mdac
Adding extra content from: C:\Users\ADMINI~1.afO\AppData\Local\Temp\3\sfup2yp2.0rt
Unmounting WIM.
Copying WIM to the package source directory.
Creating boot image package.
Error while importing Microsoft Deployment Toolkit Task Sequence.
Failed to insert OSD binaries into the WIM file
Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException: The SMS Provider reported an error. ---> System.Management.ManagementException: Generic failure
   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementObject.Put(PutOptions options)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   --- End of inner exception stack trace ---
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put(ReportProgress progressReport)
   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Put()
   at Microsoft.BDD.Wizards.SCCM_ImportTaskSequenceTask.DoWork(SmsPageData smspageData, Dictionary`2 data)
Note: previous x86 image was deleted some time ago.
Please advise.
J.
Jan Hoedt

This is the error in smsprov.log
*********** WBEM Missing property TransformAnalysisDate    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
************ WBEM Missing property TransformReadiness    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:00    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:10    7856 (0x1EB0)
Image language ID 1033 and en-US    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
ERROR> Error -1073741502 returned to execute the command line: "C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\dism.exe" /Image:"C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount" /Add-Package
/PackagePath:"C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Windows Preinstallation Environment\x86\WinPE_OCs\WinPE-Scripting.cab"    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
Failed to install required components into the boot image C:\windows\TEMP\BootImages\{8AEF81AB-4B11-4AEF-96D3-E90D84D3DA94}\mount    SMS Provider    16/04/2014 15:11:19    7856 (0x1EB0)
*~*~e:\nts_sccm_release\sms\siteserver\sdk_provider\smsprov\sspbootimagepackage.cpp(3766) : Failed to insert OSD binaries into the WIM file~*~*    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
*~*~Failed to insert OSD binaries into the WIM file ~*~*    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
Auditing: User FAC\administrator called an audited method of an instance of class SMS_BootImagePackage.    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
CExtUserContext::LeaveThread : Releasing IWbemContextPtr=9281008    SMS Provider    16/04/2014 15:11:36    7856 (0x1EB0)
Jan Hoedt

"Failed to connect to remote distribution point" on local machine

I have a new System Center 2012 R2 setup. I only have a single server with Configuration Manager, SQL, and Distribution Point all on the same machine.
The Configuration Manager Client Package is failing to load to the distribution point.
Content Status says: "Distribution Manager failed to connect to distribution point
["Display=\\AcadSCCM01.Academic.local\"]MSWNET:["SMS_SITE=900"]\\AcadSCCM01.Academic.local\. Check your network and firewall settings."
The distribution point is on the same machine as config manager, and the firewall is turned off. When I try to redistribute the package it fails again immediately.
I checked distmgr.log and found the following:
Translated server name AcadSCCM01.Academic.local to Academic.local\AcadSCCM01.Academic.local.
SMS_DISTRIBUTION_MANAGER
2/27/2015 5:15:54 PM    3640 (0x0E38)
CWmi::Connect() failed to connect to \\AcadSCCM01.Academic.local\root\MicrosoftIISv2. Error = 0x8004100E
SMS_DISTRIBUTION_MANAGER
2/27/2015 5:15:54 PM    3640 (0x0E38)
STATMSG: ID=2391 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=AcadSCCM01.Academic.local SITE=900 PID=2240 TID=3640 GMTDATE=Fri Feb 27 22:15:54.990 2015 ISTR0="["Display=\\AcadSCCM01.Academic.local\"]MSWNET:["SMS_SITE=900"]\\AcadSCCM01.Academic.local\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\AcadSCCM01.Academic.local\"]MSWNET:["SMS_SITE=900"]\\AcadSCCM01.Academic.local\"
SMS_DISTRIBUTION_MANAGER
2/27/2015 5:15:54 PM    3640 (0x0E38)
ERROR DPConnection::ConnectRemoteIISManagementWMI() - Failed to connect to
AcadSCCM01.Academic.local. error = 0x8004100e
SMS_DISTRIBUTION_MANAGER
2/27/2015 5:15:54 PM    3640 (0x0E38)
STATMSG: ID=2344 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_DISTRIBUTION_MANAGER" SYS=AcadSCCM01.Academic.local SITE=900 PID=2240 TID=3640 GMTDATE=Fri Feb 27 22:15:54.991 2015 ISTR0="["Display=\\AcadSCCM01.Academic.local\"]MSWNET:["SMS_SITE=900"]\\AcadSCCM01.Academic.local\"
ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=1 AID0=404 AVAL0="["Display=\\AcadSCCM01.Academic.local\"]MSWNET:["SMS_SITE=900"]\\AcadSCCM01.Academic.local\"
SMS_DISTRIBUTION_MANAGER
2/27/2015 5:15:54 PM    3640 (0x0E38)

Can you confirm that all the pre-requisites have been installed?
Using the following Powershell:
Get-WindowsFeature –ComputerName AcadSCCM01.Academic.local| Where Installed
And compare against https://technet.microsoft.com/en-us/library/gg682077.aspx

"Enable distribution-point sharing for this source site" did not showing SCCM 2007 DPs as SCCM 2012 content shares for CM12 clients

Hi
We have one central site server and three primary site servers in SCCM 2007 and completed the SCCM 2012 migration as single hierarchy.
During the migration, We have configured SCCM 2007 Central site server as source hierarchy for data gathering process and configured the "Enable distribution-point sharing for this source site" to make SCCM 2007 distribution points
as SCCM 2012 content shares to serve SCCM 2012 migrated clients. Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this
source site" but data gathering process is completing successfully.
Is anyone have idea, why these SCCM 2007 DPs did not appearing as SCCM 2012 content shares under "Shared Distribution Points"
Thanks in Advance
srkr

Now we are facing a problem that one of the primary site server's data gathering process did not gather SCCM 2007 DPs even though we configured "Enable distribution-point sharing for this source
site" but data gathering process is completing successfully.
Earlier all the shared DPs are showing under Shared Distribution Points ? Or since starting itself these DPs are not showing down? Have you checked migmctrl.log for some clue?
Anoop C Nair (My Blog www.AnoopCNair.com)
- Twitter @anoopmannur -
FaceBook Forum For SCCM

Boot an ESX 5.1 VM to my SCCM 2012 (WDS) server?

Hi folks,
I just got my SCCM 2012 server installed, configured a distribution point, published new boot.wim to distribution point.
I am trying to test booting up a 'bare metal' ESXi 5.1 VM to my SCCM 2012 (WDS) server, but fails with attached error.
Configuration Manager is looking for policy.
Anyone have a suggestion?
Thanks, romatlo

Thank you so much for responding! I must admit that this is my first install. :)
I could not find that option, so I deleted/recreated my task sequence, then found it as part of Deploy option.
I deployed the task sequence to unknown computers but I still get that message and will not boot up correctly.
I've pasted last part of my SMSPXE.log in case you see something definitive.
I did not have my WDS server role installed when enabling PXE on my DP, maybe that messed me up.
Thanks again, I may snapshot my VM here and start over on install if there is not a clue.
<![LOG[Client lookup reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification></ClientIDReply>
]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6346">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: device is in the database.]LOG]!><time="22:34:31.229+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:31.273+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: No boot action. Aborted.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: Not serviced.]LOG]!><time="22:34:31.319+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">
<![LOG[Client boot action reply: <ClientIDReply><Identification Unknown="0" ItemKey="16777219" ServerName=""><Machine><ClientID/><NetbiosName/></Machine></Identification><PXEBootAction LastPXEAdvertisementID=""
LastPXEAdvertisementTime="" OfferID="" OfferIDTime="" PkgID="" PackageVersion="" PackagePath="" BootImageID="" Mandatory=""/></ClientIDReply>
]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="libsmsmessaging.cpp:6544">
<![LOG[00:50:56:AD:01:C8, 94F72D42-9BE7-24BB-8BB6-D90C68B8CF33: no advertisements found]LOG]!><time="22:34:33.422+360" date="12-17-2013" component="SMSPXE" context="" type="1" thread="4716" file="database.cpp:483">

SCCM 2012 boundaries

hello all,
i have one sccm 2012 primary server and few distribution points across the several sites, So when i create boundaries using IP address range or Subnets non of the deployments will work, but it will be
fine when i add it using AD sites. now the problem is, some sites are trying to access the primary site when downloading content for the SW deployment and OS deployment,
Today i noticed, when i boot computers using boot media (CD or USB), Task sequence get failed, then i added Primary AD Site into remote distribution points and vice versa it stared to work,
what will be possible root cause for this? overlapping or smthing? plz advice!
cheers
lrok
Lrok

in SCCM 2012, you should have to be very careful for boundary, as well as for boundary group, every boundary should be member of any boundary group, AND in that boundary group, site system should be add a content location. so when you deploy OS or software
on PC then that PC should be download the content from the DP which was added n boundary group/.
Sharad Singh | My blogs: SharadTech | Twitter:
@SinghSharaad | | Please remember to click “Mark as Answer” on the post that helps you.This can be beneficial to other community members reading the thread.

SCCM 2012: failed to connect to distribution point

Similar Messages

Maybe you are looking for