murda Posted March 19, 2009 Report post Posted March 19, 2009 I am getting that messages when I try to capture a SONY VGN BZ11XN. WDS & PXE roles are installed Also imported boot images X64 & X86 Added OS Added drives in the bootimages Made task sequence and I advertised. Anyone know a solution? Quote Share this post Link to post Share on other sites More sharing options...
0 murda Posted March 25, 2009 Report post Posted March 25, 2009 then you need to verify that you have distributed your boot images to both the normal DP and PXE DP I did distribute the DP's. I can acces the share when i am in cmd (winpe). Any suggestion? Should I create new DP's ? Can I do that ? smsts.txt Quote Share this post Link to post Share on other sites More sharing options...
0 anyweb Posted March 25, 2009 Report post Posted March 25, 2009 you have to fix this Failed to connect to "\\Servername.domain.be\SMSPXEIMAGES$\SMSPKG\CRO00001" (1909) then Content location request for CRO00001:11 failed. (Code 0x80040103) find out what package that is (CRO00001:11) and re-distribute it... Quote Share this post Link to post Share on other sites More sharing options...
0 murda Posted March 25, 2009 Report post Posted March 25, 2009 you have to fix this then find out what package that is (CRO00001:11) and re-distribute it... Thats my bootimage X86 and I distribute it towards the 2 DP's. (still no luck) But when I PXE boot I see my comp saying x64 architecture? (could that be the problem? should I use X64 boot file?) EDIT: With X64 boot image I get another error: Failed to download pxe variable file. code (0x000001) I think this issue, not getting an ip in WINPE with the X64 boot image and intel driver: http://social.technet.microsoft.com/Forums...3529b3f/#page:1 http://blogs.technet.com/mcs-ireland-infra...nager-2007.aspx But that is something for friday. EDIT: Imported a new X64 Intel driver into the X64 boot images and I am getting an IP now. But I have the same issue as above. Not able to acces my share :// Quote Share this post Link to post Share on other sites More sharing options...
0 anyweb Posted March 25, 2009 Report post Posted March 25, 2009 post your new smsts.log file and i'll look at it to see whats wrong now cheers anyweb Quote Share this post Link to post Share on other sites More sharing options...
0 murda Posted March 25, 2009 Report post Posted March 25, 2009 post your new smsts.log file and i'll look at it to see whats wrong now cheers anyweb Will post it when I am back at work. So I'll post every log pxe & smsts log. Quote Share this post Link to post Share on other sites More sharing options...
0 murda Posted March 27, 2009 Report post Posted March 27, 2009 client log: smsts.log Quote Share this post Link to post Share on other sites More sharing options...
0 murda Posted March 27, 2009 Report post Posted March 27, 2009 server log: (smsts.log last entry on 25th is done manually by running TSmanager.exe) smsts.log smspxe.log distmgr.log Quote Share this post Link to post Share on other sites More sharing options...
0 anyweb Posted March 27, 2009 Report post Posted March 27, 2009 delete your X86 bootimage package and recreate it, then distribute it, then update the DP's then try again, cheers anyweb Quote Share this post Link to post Share on other sites More sharing options...
0 murda Posted March 27, 2009 Report post Posted March 27, 2009 delete your X86 bootimage package and recreate it, then distribute it, then update the DP's then try again, cheers anyweb I will try your suggestion later.(if this step below doesn't get solved) I am one step forward now. I set the Network acces account as domain account. This let me go one step further in acces rights towards the share. Now I am getting the following error: Task Sequence: Capture "name" has failed with the error code (0x00000032). Here is the log file. smsts.log Quote Share this post Link to post Share on other sites More sharing options...
0 murda Posted March 31, 2009 Report post Posted March 31, 2009 I will try your suggestion later.(if this step below doesn't get solved)I am one step forward now. I set the Network acces account as domain account. This let me go one step further in acces rights towards the share. Now I am getting the following error: Task Sequence: Capture "name" has failed with the error code (0x00000032). Here is the log file. This is my tasksequence but i removed the "Build the reference machine" part. What I am trying to do is capturing a regular pc in the domain using pxe boot. I thought it was possible Maybe that's why i am getting these errors ... I am just trying a regular "Build & Capture" and it is currently formatting disk C and it failed bringing the pc in the domain. Seems a network driver issue. Quote Share this post Link to post Share on other sites More sharing options...
I am getting that messages when I try to capture a SONY VGN BZ11XN.
WDS & PXE roles are installed
Also imported boot images X64 & X86
Added OS
Added drives in the bootimages
Made task sequence and I advertised.
Anyone know a solution?
Share this post
Link to post
Share on other sites