Unable to Stage Package on Branch DP

I recently installed a Branch DP in one of our Remote offices.  All of the packages were pre-staged according to http://technet.microsoft.com/en-us/library/bb681046(printer).aspx  All of the packages have reported into the site as installed on the DP except for one.  

The one Package that is left is showing as Install Pending.  I am unable to gather anything usable from the logs. Some of them show that the Package is there but for whatever reason it does not want to report back.  The Source files for the Package are shared on the server.  I have tried re-copying the files and manually creating the share with the appropriate permissions. I have also tried removing the package from the Branch DP and resending it from the main office.  Still no Luck.

I would like to get this resolved without having to recreate the entire package for all offices.
MeridianBioAsked:
Who is Participating?
 
Adam LeinssConnect With a Mentor Senior Desktop EngineerCommented:
Did you try running the Branch Distribution Point Maintenance Task from the BDP itself?  You should be able to do this over RDP.  For my own network, it can take up to 45 to send a status back even if the package is there.
0
 
Adam LeinssSenior Desktop EngineerCommented:
45 minutes*
0
 
TarekIsmailCommented:
make sure the package setting was not configured with :
Make this package available on protected distribution points when requested by clients inside the protected boundaries.

0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
JonLambertConnect With a Mentor Commented:
I agree, run a BDP Maitenance Cycle on the DP, then post the PeerDPAgent.log file from the client (along with the Package Id of the Package you are having problems staging).  Also, ensure in the package souce that their are no hidden files, as this can mess with Hash checks.
0
 
KezziCommented:
Have you tried updating the package rather than resending it?
I have a method I use when packages are stuck in that state and it requires editing the SQL database using SQL editor.  

here is an article that may help you with that
http://nikifoster.blogspot.com/2009/12/troubleshooting-packages-that-just-wont.html
0
 
MeridianBioAuthor Commented:
I just wanted to thank everyone who responded to this issue.  Here is the final resolution for it...   The IP address of the server had changed and was not within the a boundary containing a standard DP therefore the packages could not be resolved to a Host or Source Location.  I have changed the boundary for the new server and added the Standard DP to it.  Now the BDP is processing packages normally.

Thanks Again

MeridianBio
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.