Just updating ts will not create tons of backlogs. There should be something causing issue. What does schdule.log and sender.log says on the primary ? Are these backlogs big on size ? Are there any packages/software updates created/distributed recently ?
//Eswar koneti www.eskonr.com --- Original Message --- From: "Jonathan Dip" <[email protected]> Sent: May 22, 2013 7:58 PM To: [email protected] Cc: [email protected], [email protected] Subject: [mssms] Backlog in schedule.box This is an SCCM 2007 environment. I have a large backlog in the schedule.box on a primary server with 16 secondaries under it, which has caused things to slowly replicate. The user said they just updated the Task sequences. I am seeing tons of messages in the status messages saying user modified package properties for package X. My question is does updating the Task sequence modify all the packages and in return causes a ton of jobs in the schedule.box? Thanks, Jon
