jceddlemon

Since we migrated our driver packages to SCCM 2012, they have been behaving strangley. If I update the driver package, or send the drivers to a new DP, they will begin to copy, then the drivers will delete out of the package, and then the package will try to copy again. It actually takes a couple of days on average, but the drivers ultimately copy to the DP and show up as 100% on the package status. They will just keep deleting themselves and re-distributing over and over again until they successfully copy. My concern is that this is not feasible once we go live in SCCM 2012 - I need to be able to update drivers alot faster than 2-3 days. Something seems to be stopping the copy, then starting the copy again. I never saw this in 2007 - the packages always copied fine. Also, the size doesn't matter - small packages perform the same. I've looked at the logs and status reports, but I don't see any errors or issues that dictate this behavior. Any help would be very helpful. Thanks, Josh

Since we migrated our driver packages to SCCM 2012, they have been behaving strangley. If I update the driver package, or send the drivers to a new DP, they will begin to copy, then the drivers will delete out of the package, and then the package will try to copy again. It actually takes a couple of days on average, but the drivers ultimately copy to the DP and show up as 100% on the package status. They will just keep deleting themselves and re-distributing over and over again until they successfully copy. My concern is that this is not feasible once we go live in SCCM 2012 - I need to be able to update drivers alot faster than 2-3 days. Something seems to be stopping the copy, then starting the copy again. I never saw this in 2007 - the packages always copied fine. Also, the size doesn't matter - small packages perform the same. I've looked at the logs and status reports, but I don't see any errors or issues that dictate this behavior. Any help would be very helpful. Thanks, Josh