Search the Community

Hi, lurking for a long time, finally have something I'm scratching my head over. I am a newcomer to the world of SCCM so I'm hoping I can blame my inexperience on this. We have worked up a pretty good task sequence that's working well with all our supported models (Elitebooks: 8530p, 6930p, 8440p, 8460p, 8560p, desktops HP 7800 through 8200) The problems we are seeing is that here at our office where we are testing the build process it goes very well, all specified drivers inject w/o a problem and all applications selected via task sequence variables install with no issues. At remote offices we have another experience. Often drivers do no install probably and we have devices that seem to want to not install most of the time. Sometimes applications don't install. Time to stage at our location is about 40 minutes, at remote offices it can be up to 4 hours, often around 2. Our SCCM server is not local to our location, we are setup as a secondary site here as well. There's no differences I can think of, besides our relatively robust connection (40 Mbps, vs. an average of about 3 Mbps across the company) to the clould and our data center (where the SCCM server resides) LAN setups are pretty much the same, though some sites are pretty old, as far as physical infrastructure sites go, but we have some secondary sites that were built out in the last year to the same specs as the office we inhabit that have this problem, one of them with a burstable to 60 Mbps connection.