Jump to content


Established Members
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by keilamym

  1. this site will show you how to create the .ISO then use rufus to put the .iso on boot media.. I use USB drives http://www.sccm.ie/configure-sccm-2012/17-create-a-boot-image-for-os-deployment-without-pxe-environment
  2. if this is a reimage, i would try running disport on the machine. that should get rid of the your error message. open a command prompt and run these commands Diskpart Select disk 0 Clean Convert gpt Create partition efi size=200 Assign letter=s Format quick fs=FAT32 Create partition msr size=128 Create partition primary Assign letter=c Format quick fs=NTFS Exit
  3. the media that your using to boot off of doesnt match the boot file associated with that task sequence. if you update the boot media, that message will go away
  4. Applications won't show up in the execmgr check the AppDiscovery.log and AppEnforce.log. id also make sure the workstation meets the app requirements. (OS, Memory, etc)
  5. if the batch file is copying the files, then sccm wont perform any throttling. It's essentially like you copying the files manually. As an alternative, use the file location as a package source and you can have sccm download the files into the local cache then run the command to install from there. In that case the download will be throttled. Does that make sense?
  6. Yes. You can throttle package downloads to clients via client settings. You can throttle the bandwidth setting when sending packages to the DP. Right click on the DP, properties and I think it's the last tab. Sorry but I'm not at my desk right now.
  7. you can have multiple task sequences. The visibility of the task is reliant on the machine seeing the deployment. i would verify the device is either unknown (not in sccm) of in the Deploy Windows 10 collection.
  8. i created an offline package to run USMT outside of SCCM but have never run it in our MDT server. you could probably run it in MDT but creating an association would be an issue. I'll look at it tomorrow.
  9. 2nd question Inside the task sequence, there is an "Join Domain or Workgroup" option where you can have the device join a domain. I have never used it separately from imaging but I don't see why it wouldn't work for what you want to do. I would try to have it perform the backup, restore, then add to the new domain. keep in mind you have to have an account on the new domain so SCCM will have rights to add the device.
  10. 1st question - we have two separate task sequence. 1st at 6pm disable bitlocker restart computer request state store capture user state re-enable bitlocker 2nd at 2am request restore state restore "customize how it's restored" "we have custom .xml files" Lastly, in the Assets and Compliance section, you will see the "User State Migration" section. That is how you associate the FROM computer and the TO computer. Associate the computers / users and let the tasks run
  11. you can run the BDEHDCFG.EXE command to prep the partition for example: BDEHDCFG.EXE -QUIET -TARGET DEFAULT
  12. we use USMT in this way everyday to deploy new devices backup old machine at 6:30pm / restore to new machine 2am do you have a specific question?
  13. i had a very similar issue a while ago. when I removed PXE WDS got removed but when i enabled PXE, it never got reinstalled and the log file continued to say "WDS is not installed" I fixed mine by "removing the PXE check box, waited for the uninstall to complete and rebooted the server", I then installed WDS manually once complete, I then enabled PXE and it started working.
  14. when you update the bootwim, sccm will use the last uploaded file for PXE requests so make sure the one you created / added last, is the one you want to use, and its PXE enabled. also, im assuming you checked the smspxe.log when you say log file right?
  15. the new ADK will come with new boot.wim files. did you enable it to get deployed from a PXE enabled DP?
  16. SCCM 1710 does not fully support Windows 10 18.x.
  17. If all you did was create a new program, you will not need to update the DPs again. Since you attempted to I stall the package already, make sure you select "always rerun" when creating the deployment. (this is for troubleshooting, not when you move to large scale production deloyment) You can check the execmgr.log to see if the matching is trying to run the program. You can also check the ccmcache folder to make sure the correct files have been downloaded. Lastly, if you dont want to do any of those, you can recreate the package and program and start over. (hope this helps..please ignore typos, I'm half sleep)
  18. FYI when using the LIKE command, you need to add the % variable. Here are a couple examples SMS_G_System_SoftwareFile.FileName like "%foo.lnk"- will show all files with foo.lnk SMS_G_System_SoftwareFile.FileName like "%.lnk" - will show all files with .lnk you get the idea
  19. awe sorry.. you mean in software updates. it's not listed in my console and i just checked the Microsoft catalog and didn't see it there either.
  20. YES. https://support.microsoft.com/en-us/help/4054530/microsoft-net-framework-4-7-2-offline-installer-for-windows
  21. It is the same. if you have the right click tools installed, you can use it to force a hardware and software inventory. I believe it forces a full inventory. hardware inventory is rather fast software inventory takes a while as it scans a LOT of files.
  22. technically yes but not just out the box. you'll need to configure IBCM (Internet Based Client Management), Cloud Management Gateway or Intune. IBCM and Cloud Management Gateway both require PKI certificates and I believe Intune requires Azure. Someone can correct me on that one if Im in correct.
  • 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.