Jump to content


firstcom

Content is not fully distributing to 2nd DP

Recommended Posts

We are setting up a second DP in our environment.

 

Files are syncing fine. Resources also seem to be syncing fine.

 

However, when we try to deploy from the second DP, it says packages aren't on it. When you sign into ConfigMgr, it agrees. A majority of the content for that DP states, "Waiting for content" under content status, and "Distribution Manager instructed Scheduler to send package XXXXX to child site XX. When you view the content list for the DP, it's also short. Re-distributing doesn't help.

 

Any ideas on why our content isn't fully syncing?

Share this post


Link to post
Share on other sites

when you goto monitoring -> distro point status what does it say for that dp? does it say files uploaded?

 

Can you map to \\dpname\admin$ from your primary server? are you seeing any alerts in your console? what does distmgr.log on your primary site say? any errors?

Share this post


Link to post
Share on other sites

Hi Firstcom,

 

How long has this Distribution Point been "waiting for content"? I believe that a package will attempt to re-send to a DP 100 times before it gives up. Is it possible that the connection between the Primary and DP was down for a few days? Are you sure that there are no firewall issues preventing the packages from sending over? What's the internet link between the Primary and DP? These are just a few questions that may lead you in the right direction.

 

As GiftedWon mentions, the "distmgr.log" should also give you some clues.

Share this post


Link to post
Share on other sites

when you goto monitoring -> distro point status what does it say for that dp? does it say files uploaded?

 

Can you map to \\dpname\admin$ from your primary server? are you seeing any alerts in your console? what does distmgr.log on your primary site say? any errors?

 

Yes, I can see the files and the admin$ folder.

 

The distribution point status just says "In Progress"

 

There are no alerts.

 

For distmgr.log, which primary site are you referring to? We have a "Central" site and then two primary sites that are also DPs.

Share this post


Link to post
Share on other sites

Hi Firstcom,

 

How long has this Distribution Point been "waiting for content"? I believe that a package will attempt to re-send to a DP 100 times before it gives up. Is it possible that the connection between the Primary and DP was down for a few days? Are you sure that there are no firewall issues preventing the packages from sending over? What's the internet link between the Primary and DP? These are just a few questions that may lead you in the right direction.

 

As GiftedWon mentions, the "distmgr.log" should also give you some clues.

 

It's been trying for days/weeks. We even re-configured the DP from scratch. As far as I know we have no firewall rules in place that would prevent the connection.

Share this post


Link to post
Share on other sites

Well, if it's been trying to days/weeks, has there been progress? If you go the Monitoring -> Content Status, and go into the details of the application/package that you're trying to send, it should give you a little more detail.

 

For instance, on a really big package, it will say something like "15% sent." If I check back in an hour, it might be at "25% sent." Are you seeing progress? How big are these applications/packages?

Share this post


Link to post
Share on other sites

Well, if it's been trying to days/weeks, has there been progress? If you go the Monitoring -> Content Status, and go into the details of the application/package that you're trying to send, it should give you a little more detail.

 

For instance, on a really big package, it will say something like "15% sent." If I check back in an hour, it might be at "25% sent." Are you seeing progress? How big are these applications/packages?

 

There is no progress. There's tons of packages and applications of all sizes.

Share this post


Link to post
Share on other sites

It kind of sounds like your distribution point wasn't installed successfully in the first place. What operating system is this DP? Is it fully patched, and has IIS been installed/configured?

 

Also, when you go the Monitoring section, Distribution Point Configuration Status, go to the new DP, and look at the "Details" tab. What do you see there? Particularly the first few lines, you should be able to tell whether the DP installed correctly. (Check out the attached photo.)

post-24460-0-04205100-1412095087_thumb.png

Share this post


Link to post
Share on other sites

It kind of sounds like your distribution point wasn't installed successfully in the first place. What operating system is this DP? Is it fully patched, and has IIS been installed/configured?

 

Also, when you go the Monitoring section, Distribution Point Configuration Status, go to the new DP, and look at the "Details" tab. What do you see there? Particularly the first few lines, you should be able to tell whether the DP installed correctly. (Check out the attached photo.)

 

The DP is running Windows Server 2012. Everything is up-to-date.

 

The recent status for the DP is a mixture of "Waiting for content" and "Content is being redistributed to the distribution point"

 

The oldest line is "Successfully completed the installation or upgrade of the distribution point on computer"

 

There's nothing but green status marks and green up arrows indicating it's wanting/waiting to transfer content.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.