This video covers troubleshooting DPM communication to and from a TMG server. In the video we verify that we have connectivity, then we break the communication between the two and walk through the steps needed to be performed on the TMG server in order to allow successful communication once again to the TMG server.
We cover:
We then verify that the communication is successful once again after our changes are applied.
Enjoy!
Shane Brasher | Senior Support Escalation Engineer
The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis
Thanks for your video. Couple of questions:
what kind of ports are behind the dcom II protocol?
Could you please copy and paste the UUIDs into the blogpost? This would be much easier to handle.
thx
Very good video.
Could you please prepare a documentation and publish it so especially the UUIDs are available more easily.
Thanks.
Here are the UUIDs in use. Hopefully it pastes properly
******
MSDPM AC: {C4EBD674-1457-4B79-BE30-B04735AED9D1} {A3B9D3F4-2477-4F95-B2D1-F75B0FDF2A2F}
DPM RA: {DA6AA17A-D61C-4E9C-8CEA-DB25DEA52A95} {2DF31D97-33CC-4966-8FF9-F47C90F7D0F3}
MSDPM: {27F60283-447F-4D5F-AA84-F45D09BD06EF} {8D8C691A-AFE6-4EA3-A6B2-F3E5EF1BD0CA}
DPM LA: {1B308A4A-FFEC-4C85-957C-53AA1DCC696F} {9E6C5356-B180-4295-888C-5A99E505420F}
Shane
The video and tutorial is pretty good but for some reason it doesn't work here. After all the rules created and applied dpm still cannot attach the agent.
wmi and sc tests run fine.
DPM fails with error 31144