Thats a 'No' then I guess?
I started Vista Provisionin one year ago with no issues.
It's not much different from XP provisioning.
1. change the OS type in template definition
2. use unattend.xml instead of sysprep
3. WAIK instead of ldprep to inject PNP drivers.
4. execute bootsect.exe /NT60 c: to change boot from c:\ntldr to c:\boot
Hi Jary, thanks for the response.
What about the CTOS action, do you have any issues getting the LDProvision agent loaded so that the template can procede beyond sysprep?
I would love to see the template you're using if possible? I know of a few people who have tried this and run into the same problem as me, if I'm doing something stupid it'd be good to see where I'm going wrong...
1 of 1 people found this helpful
I didn't find problem about CTOS. I just insert unattend.xml (generated by WAIK and inserted with the insert script action) into c:\windows\panther folder.
I can't upload the template because it's on a customer server.
You can upload your template and I'll check it for you.
Interesting, I was inserting the unattend.xml file into c:\ or c:\sysprep. I've not tried putting it in the panther folder so that could be it. Thanks for the info, I'll give it a try.
Sorry its taken a while to get back around to this, been pretty busy! It turned out that the problem was with my unattend.xml file. Even though it worked fine with OSD, Provsioning just didn't like it. They can be quite fiddly to create but I found a handy website that spits out a nice generic unattend.xml file for you. More importantly Provisioning likes it! Here's a link for anyone else thats experienced similar issues:
Thanks anyway for the help Jary