Jump to content


Jayshaw91

Established Members
  • Content Count

    14
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Jayshaw91

  • Rank
    Member
  1. Complex to me, anyway. We've got two DPGs set up. DPG1 contains all of our existing DPs. It has all software assigned to it. A large portion is set as High Priority packages (don't ask... this is a client and something to fix). Many packages appear to still be replicating. DPG2 is new. We're replacing some of the existing DPs with new hardware/Server 2012. We have only the software we feel is mandatory at each site set to replicate to this DPG. New DPs are not part of DPG1 - only DPG2. We also have bandwidth throttling going on from our Primary Site (where we create all packages) to each other site. We have the DP where we create packages set to 7 outbound connections at a time. I know that packages replicate according to priority. I also know just one package is sent from the central DP to the branch office DPs when bandwidth throttling is turned on. My question/confusion is when will the new DPs in the new DPG start getting software? Does the replication that needs to complete for the DPs in DPG1 need to happen before the new DPs in DPG2 will get anything pushed to them? Is there a way to stop the replication of specific packages in DPG1 if they have not completed?
  2. Did anything change with the permissions to the System Management container?
  3. Try changing the connection to 'fast'. I think that may do the trick. Remember, that setting relates to the speed of the client to the DP - not the speed from the remote site back to the central office. If the local network is 100MB, and the clients and DP are in the same building, that's obviously fast. Make that change and report back if it helps. You may want to recycle the Agent Host after you make that change. Not sure if anything else should be restarted... I'm just learning all of this stuff myself
  4. If I wanted to remove a single server Secondary Site, but leave a DP in the same physical office, how would I do that? What I think I want to do is create a new Distribution Point Group, put the existing server, SS1 in the DPG, create a new Distribution Point, DP2, put DP2 in the DPG, let everything replicate to DP2, then remove SS1 and the Secondary Site itself. Obviously I still need to get clients assigned to the correct Content Server and Site via Boundary Groups, but that won't be a big deal.
  5. This one has been solved. As I asked - and now have answered - file replication was the cause of the problem. Replication from Secondary Sites to the Primary Site was disabled due to bandwidth issues. We've re-enabled replication for all priorities (system info is LOW priority!) and set it to 5%/hr utilization. Keep that in mind, folks: do *not* turn off your file replication *to* your Primary Site! Throttling? Sure, just don't turn it off entirely.
  6. I should add that that Primary Site is SP1, and the Secondary Site where I checked the logs is also SP1. Client I checked has v.7804 of the agent installed.
  7. We've got Primary and Secondary Sites. Clients in the Primary Site all show as active. A large number of clients show as inactive in the Secondary Sites. To troubleshoot, I followed this: http://be.enhansoft.com/post/2013/07/25/Troubleshooting-Inventory-Flow.aspx I checked that the client is talking to the MP in the SS. I see activity in the IIS log. The SS shows it is processing the record (checked the mp-hinv log) and it is putting it in the dataldr inbox, locally. Here is where I am confused. The MP (the only server in the SS) doesn't have a dataldr.log file. First question, should it have that file? For the record, I do see a dataldr.log on the Primary Server. I don't see the MIF being processed there. I don't even know if it should process it. My assumption is that the SS write the info the the database locally, but I am not 100% sure of that. Does file replication have anything to do with this or just the DDRs?
  8. Apparently, this is a pretty wide spread issue: http://anoopcnair.com/2013/10/28/sccm-configmgr-2012-r2-issue-osd-slow/ Here is a TechNet thread discussing it (taken from the link above): http://social.technet.microsoft.com/Forums/en-US/4c72ae27-198f-4751-b0d6-340a11b52bd4/insanely-slow-os-download-in-2012-r2-winpe?forum=configmanagerosd
  9. This should get you started: http://technet.microsoft.com/en-us/library/gg712701.aspx#BKMK_File_based
  10. Peter, thanks for the input. I understand you should keep sites on the same level. I am at a client site and working through quite a few SCCM issues. This is one I just uncovered today. So, does this really pose any sort of environmental issue? We've got numerous issues and I am wondering if this may be the cause of some of them. For starters, a large number of clients are reporting as 'Inactive' and troubleshooting MPs hasn't turned up any issues that I've seen. FYI, I'm planning a total rearchitecture of their SCCM environment, including deploying adding a CAS to the hierarchy as we do have a requirement for two Primary Sites (geographic/political concerns).
  11. Primary Site is on SP1, numerous Secondary Sites still on RTM, some SS's are on SP1. I just noticed the PS has SP1 CU2 installed. None of the SP1 SS's are on CU2 - only the PS. Is this a big deal? I know that you're not supposed to roll out CU2 to your servers until SP1 is installed on all Site Servers, so this worries me a bit.
  12. I've been doing a fair amount of reading on file replication due to the project I am working on. Keep in mind I am a bit of a n00b on SCCM, so I not an expert, but this is what I have gathered. SCCM replication between sites will use up to 5 threads, but no more than three at a time to any one particulate site. So, on the surface, that should answer your question regarding threads used. However... ...if you plan to turn on any sort of file replication throttling or scheduling between sites, you'll only have one thread working for you. Even if you set a rate limit to 100% bandwidth - which one may think is the same as turning off throttling, but isn't - you will only get one thread working on replication. Since I see you have slow links, you very well may throttle traffic. That'll be up to you and your client, of course. Administration -> Hierarchy Configuration -> File Replication will get you in the correct area for setting this. There, you can set replication schedules, rate limits, and even prioritize when certain package can be replicated.
  13. Google turns this up: http://technet.microsoft.com/en-us/library/jj822985.aspx Expand the section that talks about mixed-version hierarchy. You'll see it details how things operate. Nothing like answering your own question...
  14. Hi folks, sorry if this has been posted, but I failed to find anything while searching. As the subject says, we've got clients running the SP1 agent, but they belong to RTM Secondary Sites. I've tried finding information regarding the impact this may have, but I'm coming up blanks. Anyone have any insight in to what issues this may cause, if any? I know you can run RTM agents in SP1 site with no issues, outside of the fact that clients won't be able to use SP1 features. It's this reverse situation that I am concerned with. Thanks!
×
×
  • Create New...