Jump to content


vincelewin

Established Members
  • Posts

    81
  • Joined

  • Last visited

Everything posted by vincelewin

  1. The SMSPXE.log says "Matching Processor Architecture Boot Image (6) not found" I have the two two new boot images available only for distribution from PXE enabled distribution point. I can see in the SMSPXE log it is looking for COR000FD also and if I enable this image for distribution my devices will boot from that Image ID.
  2. Can anyone help me troubleshoot this?
  3. Helppppp!!!!!! Ive got a windows 10 deployment looming and currently I am unable to get drivers on during the unnattended deployment from sccm. Regards Vince
  4. Ok so this morning I have removed the Distribution Point (DP) from the secondary site server left it half an hour and re-installed the role. I got rid of the problematic deployment package (DPG) and added the patches from it to other previously working DPG's. I then added the DP to the DP group and watched it sync all the packages, except one! I still have one package that will not go over but it is a different, previously sync'd package. I have noticed that on the Parent server I can see error 3 in the SMSDBMON, attached and error 8 on the secondary site servers DP DESPOOL log. Anyone have any ideas? smsdbmon.log despool.log
  5. How much space is enough space? Isn't there a setting which configures the amount of usable or free space on a disk?
  6. This is the second time I have re created the package now. Just getting the same errors with each one on this DP. 0x80070002 error code = 2 error code = 8 despool.log
  7. Ok I removed the package from all DPs and deleted the deployment group, then I navigated to the deployment groups folder on the servers virtual hard drive and deleted the contents. Then I re-created the deployment group and navigated to the updates view and viewed the members, then I re-downloaded them all. I have witnessed the files be re-created in the empty original folder and I have now re-deployed to all DPs. It has failed again on the one DP as before. Does anyone else have any ideas I am ready to throw sccm into the canal.
  8. Hi Niall, An ADK error appears yesterday. I just ran the installer and then copied out the boot images. V SMSPXE.log
  9. Do you know why my PXE boot is not working after adding the new PE6(win10) boot images. I have ticked the box "Deploy this boot image from the PXE-enabled distribution point" on the new image and unticked the same on the old images. I have restarted the WDS service and ensured the content is distributed but my client just times out waiting for the PXE boot. Am I missing something?! V
  10. Hi Apexes, I followed your instructions at 08:10 this morning and waited until 09:08 when I re-distributed the content. Ive left it all day and its still showing the message "The content files for COR00129 have not yet arrived from the source site COR.
  11. Niall, Im getting the DISM error 50 during driver install on windows 10 with 2012 R2 SP1 CU2. I was just about to follow Johan's workaround when I saw your post above. After the OS installed and the laptop restarted I was able to use the windows provided Intel I217 driver to initialize the nic and then I chose to install driver for unknown devices giving windows the path to the extracted driver cab on the SCCM server. Every driver successfully installed from the extracted folder. Very confusing. Vince dism.log smsts.log smsts-20160225-203140.log
  12. OK so im getting DISM error 50. Ive already tried to use the WINPE10 boot images but there not booting so now im looking at http://deploymentresearch.com/Research/Post/443/Beyond-unsupported-Deploying-Windows-10-preview-including-drivers-with-ConfigMgr-2012-R2
  13. Fixed. Thanks. I was using the wrong version for the boot image.
  14. Hmm, Its a 32bit boot image installing a 64bit OS. Would I use the 32 or 64bit version? I think I know what you are going to say and I think I know what I have done wrong now. V
  15. Hi all, Third post in as many weeks :s Yesterday I followed this http://blogs.msdn.com/b/beanexpert/archive/2015/08/05/how-to-switch-to-windows-10-adk-on-configmgr-2012-r2-sp1.aspx to extract the Win10 boot images from the ADK10. Ive been having a problem where Windows 10 deployment wont install any drivers so I thought I would try this. The problem I have is my laptop wont PXE boot now. I have distributed the image to my PXE enable secondary site. I have unticked "Deploy this boot image from the PXE-enabled distribution point" on the old x86 boot image I was using and ticked this same tick box on the new x86 WinPE10 image. I have tried this both on the x86 and the x64 images. I have rebooted the Primary and Secondary site servers but I just get the following.
  16. Hi Apexes, Yes I can get other content onto this DP, only yesterday I distributed new win 10 boot images successfully. None of the logs help me. I can see the sender.log says "Finished sending SWD package COR00129 version 2 to site THE" but that was on the 23/02/2016 at 08:22am no mention of that package since. Pkgxfermgr.log just shows multiple waiting for new/rescheduled send requests. Distmgr.log has this as its last entry relating to this package "Exiting package processing thread for package COR00129." on the 23/02/2016 at 08:20am I've attached below. Everything looks fine from the logs. PkgXferMgr.log sender.log distmgr.log
  17. But heres the error from the log I saw. ![LOG[Failed to execute command line 'C_SMSTaskSequencePackagesCOR0012AserviceUI.exe -processTSProgressUI.exe XWINDOWSSystem32wscript.exe pause_ts.vbs' . This version of is not compatible with the version of Windows you're running. Check your computer's system information and then contact the software publisher. (Error 800700D8; Source Windows)]LOG]!time=085230.146+00 date=02-24-2016 component=InstallSoftware context= type=3 thread=1176 file=runcommandline.cpp562
  18. Is it the 401 - Unsuccessful with anonymous credentials error? It is shortly followed by an attempt to use the context credentials. 401 - Unsuccessful with context credentials error?
  19. Ive attached the file here. smsts_win10_PauseFailed.txt
  20. Hi, I think it was giving the error and crashing out because I didnt have "Continue on error" ticked. Now it just flashes up the title and skips past without stopping or display the window.
  21. Hi, ADK 8.1 Build 8.100.26866 WinPE 6.3.9600.16384 is the boot image version. ConfigMgr I think its 5. Vince
  22. Hi Anyweb, I tried this in my windows 10 TS and it throws this error. Failed to run the action ###########Pause Task Sequence. This version is not compatible with the version of windows your running. Check your computer's system information and then contact the software publisher. (Error: 800700D8; source: Windows) Im using the serviceUI.exe from the MDT2012 Update 1 you linked above. Im using a 64 bit boot image and the 64bit version of the serviceui.exe file. Any idea why this isnt working? Regards Vince
  23. A couple more screen shots. These are the drives on the DP that is failing. This shows the size of the package from the Content view under Monitor.
  24. Hi All, I have a strange issue with this package on one DP. The status under monitoring is "The content files for package COR00129 have not yet arrived from the source site site COR. Distribution manager will try again later to distribute the content. It stays like this and never changes. Its been at least 5 days since I first distributed it. I have tried removing it from this DP in the properties of the package and then distributing it again to this DP, I've tried "Redistributing" from the properties and also "Validating" but it just gets to the same message. The distmgr.log shows We are running 2012 R2 SP1 5.00.8239.1000 I have 1 parent site and 6 secondary sites. As you can see the package distributed to 6 of the 7 fine but it wont go onto this last one. I can attach any logs you require please just ask. Any help would be gratefully received. Vince
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.