Jump to content


anyweb

Root Admin
  • Posts

    9182
  • Joined

  • Last visited

  • Days Won

    366

Everything posted by anyweb

  1. why windows 8.1 ? the upgrade task sequence was designed for Windows 10 upgrades only so i doubt it would work for Windows 8.1, you could though do a refresh (reinstall) from Windows 7 to Windows 8.1, have you tried that ?
  2. glad to hear it, to summarize Microsoft is aware of the issue and has produced a fix
  3. ok try this method https://blogs.technet.microsoft.com/brandonlinton/2015/07/30/windows-10-adk-boot-image-updates-for-configuration-manager/
  4. that boot image is ADK 10 version 1507, ancient, are you sure you updated ADK ?
  5. update ! Microsoft's product team knows the issue, and is preparing a mitigation.
  6. i'm checking with Microsoft PG about your specific error any chance you could send the logs to me zipped, niall@windows-noob.com
  7. don't forget windows-noob.com's guide here
  8. here :), no i'm kidding, i don't think it's necessarily documented anywhere but it's based on actually having seen the problem in production, what we did to get around it is what I've mentioned above, try it and see does it improve for you
  9. if you are NOT using eval (as in my example) then you need to add this section to the configuration.ini file [SABranchOptions] SAActive=1 CurrentBranch=1
  10. don't use copyprofile it breaks more things than it fixes, to configure the taskbar or start menu you need to decide which is more important as it's one or the other (at least it was when i last tested it), here's how to customize the start menu
  11. well that's up to you to test and verify, you can add pauses that timeout and continue by simply (for example) pinging localhost a certain number of times C:\Windows\System32\ping.exe -n 61 127.0.0.1
  12. It's not supported, so don't bother trying. If you want to deploy Windows 10 then you really need to consider moving to SCCM Current Branch, you can deploy Windows 10 up to version 1511 with SCCM 2012 R2 SP1 but that's it, to deploy any later versions (such as Windows 10 LTSB version 2016) you'll need Configuration Manager Current Branch, version 1606 or later
  13. for the next release of this guide (for SCCM 1702 or whichever release becomes the next baseline), i'll update the code then, thanks and feel free to add your contribs here or elsewhere in windows-noob, that's what it's all about
  14. this might be enough, please test Uninstall-WindowsFeature -Name Windows-Internal-Database -Restart
  15. WID is required, see the screenshot. You can try manually removing it and scripting that yourself but why worry you are not using it, wsus is using SQL for the DB
  16. mystery solved, when generating the XML i add WSUS via the server manager, and as part of that process it automatically adds required features including WID, see here
  17. good point, i see a reference to it in the wsus xml file but it still uses the SQL DB, and in my lab the wid services are not even running are they running on yours ? i'll see what i can find out in my lab...
  18. Introduction Microsoft have yet again released a new update, this time it's System Center Configuration Manager 1703 (Technical Preview). This is a quick post to highlight a detailed video I've just created and uploaded to youtube. The video shows the entire process from start to finish including Initiating the Upgrade Using CMTrace to review log files Checking status in the console Which logfiles to review Where the content is downloaded Determining the package GUID Upgrading the console Tips advice and more. Please take a look and tell me what you think.
  19. i havn't done this but you could add a pause before the step for those older computers to allow them time to get ready for the apply network settings, what error do you get when those old ones fail ?
  20. if you switch back the normal drive is it ok ? could be the drive is not compatible with this hardware and/or it's faulty or lastly it may need drivers (or firmware)
  21. ask dell which usb nic they provide is pxe bootable on that product, start there
  22. by the way if your boot image is 10240 then they are based on the 1507 ADK, which was the first release of Windows 10, if you are on SCCM CB you should be on ADK 1607 at least
  23. do these devices have usb ports, if so maybe you can connect a usb nic and pxe boot off that ? that said you'll need to ask Dell what nic they offer can do that, not all will be supported by the hardware bios for pxe boot, so contact Dell
×
×
  • 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.