Hi there,

I'm currently working on deploying LabStats via a Task Sequence in SCCM. This Task Sequence isn't a full OS deployment, just one piece of software, preceded by a couple commands to completely delete any pre-existing versions of LabStats. (Long story...) One of the labs I must deploy to isn't cooperating. It's an off-site lab: still part of our domain, but in a completely different location. There are 18 systems total in this collection (in that building), 9 of which are behind their own switch in a single lab. The 9 systems in the building that AREN'T part of this lab deployed the Task Sequence just fine. But these 9 won't work. I've spend a couple hours with one of our network techs as he used Shark to determine if the issue is a disconnect at the network level. He says the data is reaching the systems, it just doesn't seem to be acted upon once it's received. Funny thing is, when I manually re-deploy the Task Sequence using the console extensions we have in our SCCM console it deploys fine. Can anyone point me in the right direction to get this solved? Which client log file(s) should I be looking at to find any possible errors? Does anyone know what the difference between a scheduled deployment and a manual is that might make the difference in this case?

Thanks!

Steve

smsts.log would be the first one to look at, where does it actually stop? If it's just install software, run some commands, you should wrap it to a script and deploy as an application instead of of task sequence. Task sequences are meant to be used with OS deployment, not deploying applications.