Jump to content


MagnumVP

Established Members
  • Content Count

    93
  • Joined

  • Last visited

  • Days Won

    3

MagnumVP last won the day on October 8 2016

MagnumVP had the most liked content!

Community Reputation

5 Neutral

About MagnumVP

  • Rank
    Advanced Member

Profile Information

  • Gender
    Male
  • Location
    CA, USA
  1. My system currently sits at SCCM 2012 R2 SP1 CU4 on Server 2008 R2. If I want to move to SCCM CB 1903 would it be best to; Upgrade the existing SCCM from 2012 to CB and then migrate to a new server (2008 R2 to 2016)? Add a 1903 CB to the environment and then swing migrate from 2012 to CB (if this is even possible??) Also if anyone can answer this (Googled and Bing....without success). Within out EA agreement I can download System Center Standard/Datacenter 2019. How does this differ from CB? Any recommendations I would greatly appreciate.
  2. SCCM 2012 R2 CU4 ADK 1903 WinPE 1903 I'm booting a Windows 7 upgrade to 10 into WinPE and receive the following error 0x80220014. Everywhere I look I see that it was an issue with ADK 1511 and has been fixed with the Hotfix or sequential ADK. I'm running 1903 and have built and distributed this Boot Image from scratch Boot Image is 10.0.18362.1. It has 6 signed NIC drivers that are built into the image. If I boot this image directly to the PC via PXE (Dell Pressing F12) it works without issues. smsts.log
  3. I'm sure it matters, but I'm running SCCM 2012 R2 SP1 with the latest ADK for 1903. @anyweb is the exact scenario different than normal? What's weird that is different from your "exact scenario" . Is it the "Capture Name" I'm kind of surprised that a wipe and reload is out of the ordinary for a SCCM OS push install.
  4. I have inherited a system where there are 50+ workstations that are running Windows 7 Ultimate OEM 32Bit. I want to push out a Task Sequence that performs the following; Captures the PC Name Reboots the PC Goes into WinPE Installs Windows 10 Enterprise Joins the domain All user docs are redirected to the servers so I do not need to save the users settings I have tried to create numerous tasks sequences but always running into can't upgrade 32-64 bit, OEM license won't allow you to run an upgrade.... I just want to Wipe and Replace but don't want to walk to each workstations. Can someone please assist in pointing me in the correct direction of a guide, Step-By-Step (which this site is great for) or some guidance? Thank You
  5. Wierd Update..... It looks like if I boot using the BIOS (legacy) setting for the PC I only get the 1 task. However, if I boot a PC using UEFI all tasks are there.
  6. We have been using the guides on this site for over 2 years without issues, but for some reason I can't find a guide that helps me through this issue. We have been deploying Win 10 Enterprise 2016 without issues (Add PC and MAC to SCCM, add new computer to group, boot PC to PXE and done....) We want to deploy Win 10 v1803. Here is what I did; Added the OS to SCCM - Distributed Content Copied the OS Task Sequence for 2016, named it 2019 Edited 2019. The only change the OS to Apply to the 2019 Deployed 2019 to the same groups (Unknown Computers and Deploy Windows 10) PC booted into PXE as expected, but is ONLY presented with the 2019 Task. Task 2016 is gone. If I disable the 2019 Task, the computer is rejected and doesn't boot. Is these something that I"m missing? Why if I copy a Task does it no longer show? Is there a "special" guide to have multiple OS task Sequences presented to the PC?
  7. We have been using the guides on this site for over 2 years without issues, but for some reason I can't find a guide that helps me through this issue. We have been deploying Win 10 Enterprise 2016 without issues (Add PC and MAC to SCCM, add new computer to group, boot PC to PXE and done....) We want to deploy Win 10 v1803. Here is what I did; Added the OS to SCCM - Distributed Content Copied the OS Task Sequence for 2016, named it 2019 Edited 2019. The only change the OS to Apply to the 2019 Deployed 2019 to the same groups (Unknown Computers and Deploy Windows 10) PC booted into PXE as expected, but is ONLY presented with the 2019 Task. Task 2016 is gone. If I disable the 2019 Task, the computer is rejected and doesn't boot. Is these something that I"m missing? Why if I copy a Task does it no longer show? Is there a "special" guide to have multiple OS task Sequences presented to the PC?
  8. Where can I find the report/log for the results of a system initiated Full Scan of the client. Is it stored on the client...where? Or can I bring up a report with the scan from System Center? I'm currently using SCCM 2012.
  9. Sometimes these computers will sit for months on end and if it's already joined to the domain it will lose the ability to login "Trust Relationship" issues. If the computer is in the workgroup, how can the computer see the Software Center?
  10. I guess then that is what I will have to do. Thanks Anyone have a generic script to rename a PC, reboot and join a domain? Edit: I found this which may work as a PowerShell command Add-Computer -DomainName MYLAB.Local -ComputerName TARGETCOMPUTER -newname NewTARGETCOMPUTER
  11. Currently (following the Step-by-Step on this site) we deploy new PC's with Windows 10 2016 LTSB by adding the PC to Active Directory and then adding the PC to System Center with the PC's MAC address. Boot the PC, connect to the PXE Server and it does the rest. I have 7 PC's sitting in my office "just in case someone's PC needs to be replaced". Is it possible to image a computer with everything but the name and then during the first boot prompt for a name and add it to the domain? This will allow me to image all 7 PC's now and when one dies I just pick up the PC and go instead of having to image it first and then deliver it.
  12. Now that Microsoft is no longer proving a patch-by-patch Tuesday and is an All-In-One Package, how is that handled within SCCM12? I followed the guide outlined on this site (BEST GUIDE EVER), so do I need to change anything or will the patches stop working until i modify the requirements and criteria? What's everyone else doing with these CU patches?
  13. Thank you for the reply. I was considering the CBB route as well but where do I find it? I only see the LTSB to download in the VLSC.
  14. Are you using Windows 10 LTSB, CB or CBB when deploying new images/computers to new users? More just curious what others are doing.
  15. I have downloaded the Surface Pro 3 and 4 drivers from Microsoft's site https://www.microsoft.com/en-us/download/details.aspx?id=49498. It was able to extract the zip file into \\server\sources\drivers\sourcefiles\SurfacePro4 When I import the drivers and select this root folder it only shows and imports about 12 drivers all System drivers from the System folder. I have verified that the drivers are there, Folders with extracted drivers.
×
×
  • Create New...