Ok... Thank you ... I will try once again with Niall & ur suggestions Sent from iPhone....sorry for typos
> On 22-Apr-2014, at 10:46 pm, [email protected] wrote: > > Exe based drivers wont work for network or mass storage, those need to be > “real” drivers. > > also you need to suppress the reboots that your driver installs are doing. > > You may have to extract the “bad” drivers. > > Sent from Windows Mail > > From: Niall Brady > Sent: Tuesday, April 22, 2014 12:38 PM > To: [email protected] > > use apply dirver package instead of auto apply drivers, and use WMI to detect > what the hardware is, like here (same process in cm12), as regards the > reboots, what does your smsts.log file tell you about that ? > > a good idea (when troubleshooting failed deployments) is to use a pause in > the task sequence before and after a step you are troubleshooting, detailed > here. That way you can monitor the step live and review the logs without > having to worry about the machine rebooting when you dont want it to... > > >> On Tue, Apr 22, 2014 at 6:10 PM, Hun boy <[email protected]> wrote: >> Am into drivers integration task for my sccm 2007 and 2012... >> I have enabled default step auto apply drivers and do not have any PNP >> drivers in my TS.. All are the exe based drivers and tested manually with >> all my command lines and working fine. >> >> Now the issue is after apply WIM image it should go for auto apply drivers >> and then it's getting into first reboot with preparing your computer for the >> first time then it does 3-4 reboots and later not continuing my TS steps... >> It just sits into default is without any drivers. >> >> So this is because of multiple reboots are happening out side of sccm >> control ...how can we come out of this kind of situations... Any ideas ... >> Pls.. >> >> Sent from iPhone....sorry for typos >> >> >> > > >
