Not much successful has happened so far today, Vista keeps blue screening, BDD builds aren’t working so I’m rebulding the server and will put BDD back up and go again.
Just for completeness, when I managed to get past the blue screen it was only to get the disk booting again which managed to tell me that the build was complete with the following errors:
- Unable to get WinNT ADSI provider: (-2147221020)
- ERROR – ZTITatoo state restore task should be running in the full OS, aborting
- ZTIERROR – Non-zero return code by ZTITatoo, rc = 1 (this one twice)
This morning was taken up with chasing how to update the security updates in SMS. I didn’t get anything to work for this, but Dave’s managed to coerce SMS into displaying some new updates.
I’ve been doing the same thing and having the same combination of errors…
), but when I saw that you had overcome the same problem I have been strugling with I was overcome with a strange sensation of hope…
What can be done to overcome this? I hope you don’t mind me asking you for help (I usualy don’t bug strangers on the internet
Thank you for any assistance that you may provide.
Response #1 on my blog! Thanks Chris!
I’ve been a bit slack with updating what’s been happening, but off the top of my head I removed all the drivers from the build and it went through ok. I’d give that a run first.
I’ve ended up looking for updated drivers for our Dell machines rather than using the existing ones and that seems to be coming along.
I’ve the same problem with ZTITatoo, tried to folow instructions on this page http://blogs.technet.com/msdeployment/, but it didn’t work.
I’ll try to capture image without drivers…
Hmm, not sure what to say here. I didn’t change ZTITatoo at all and didn’t capture an image as such. The work we’ve done is still in the Lite Touch stage and we’re still basing all deployment work off the original wim file on the disk.
Post logs if you like.