Image may be NSFW.
Clik here to view.
We’ve seen this issue come up a couple of times here lately so I wanted to give it a mention here just in case you run into it. The issue is that if you are trying to install a System Center Configuration Manager 2007 (ConfigMgr) Branch Distribution point role on a Distributed File System (DFS) namespace share you will receive errors as this is not a supported configuration:
ERROR: Received BITS settings policy. Client is not provisioned to be a Branch DP. PeerDPAgent 5564 (0x15BC)
Raising event:
[SMS_CodePage(437), SMS_LocaleID(1033)]
instance of PDPBITSConfigDeleted
{
ClientID = "GUID:34605BAD-3DD3-4979-B852-02D0618CFD72";
DateTime = "20120214155012.186000+000";
MachineName = "";
ProcessID = 5192;
SiteCode = "";
ThreadID = 5564;
};
PeerDPAgent 2/14/2012 10:50:12 AM 5564 (0x15BC)
Not processing message (<PDPScheduledMaintenance MessageType='PDPStatusTask'/>) as agent is not acting as BDP PeerDPAgent 9408 (0x24C0)
Not processing message (<PDPPkgProvisioningStatus PackageType='Pending'/>) as agent is not acting as BDP PeerDPAgent 8920 (0x22D8)
Not processing message (<PDPScheduledMaintenance MessageType='PDPStatusTask'/>) as agent is not acting as BDP PeerDPAgent 9748 (0x2614)
Not processing message (<PDPPkgProvisioningStatus PackageType='Pending'/>) as agent is not acting as BDP PeerDPAgent 5280 (0x14A0)
Troubleshooting:
In this case we checked and found that the customer was using a DFS share to host the Branch Distribution Share data. This was done so that the ConfigMgr packages could be updated on the BDP and then be automatically replicated across all the DFS shares in the same namespace so clients could pick it’s package from any of the DFS shares. This is not supported as it can cause issues with the DFS replication engine.
Solution:
As a workaround, you can bypass the DFS share and instead use the local share on the local machine that is mapped to the DFS namespace. A DFS share will always start with the domain name (e.g. \\contoso.com\internals) and by using the local share name instead, we can do a NET SHARE and find the location, and use this local location as the new Branch Distribution Point share path.
More Information
For more information see the following:
About Distribution Points : http://technet.microsoft.com/en-us/library/bb680614.aspx
Arvind Kumar Rana | Senior Support Engineer
Get the latest System Center news on Facebook and Twitter:
Image may be NSFW.
Clik here to view.
Image may be NSFW.
Clik here to view.
App-V Team blog: http://blogs.technet.com/appv/
ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
DPM Team blog: http://blogs.technet.com/dpm/
MED-V Team blog: http://blogs.technet.com/medv/
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/
Operations Manager Team blog: http://blogs.technet.com/momteam/
SCVMM Team blog: http://blogs.technet.com/scvmm
Server App-V Team blog: http://blogs.technet.com/b/serverappv
Service Manager Team blog: http://blogs.technet.com/b/servicemanager
System Center Essentials Team blog: http://blogs.technet.com/b/systemcenteressentials
WSUS Support Team blog: http://blogs.technet.com/sus/
The Forefront Server Protection blog: http://blogs.technet.com/b/fss/
The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Clik here to view.