Jump to content


kevlar01

Established Members
  • Posts

    91
  • Joined

  • Last visited

  • Days Won

    1

kevlar01 last won the day on August 23 2018

kevlar01 had the most liked content!

Profile Information

  • Gender
    Male

kevlar01's Achievements

Newbie

Newbie (1/14)

  • One Month Later Rare
  • One Year In Rare
  • Week One Done Rare

Recent Badges

2

Reputation

  1. You could try this Powershell command: Get-PhysicalDisk | Select FriendlyName,MediaType,DeviceID The mediatype should report back with 'SSD' or HDD'. Maybe you can build in a condition in the step to only run if it is an SSD. edit: in this blog somebody created a more extended script: https://www.vacuumbreather.com/index.php/blog/item/72-dynamically-select-ssd-drive-for-os-installation. It is made for MDT but it looks like it should also work for SCCM.
  2. Create a device collection with computers where you want to keep Chrome. You can exclude this collection when you target your uninstallation deployment. The collection with Chrome users can be maintained manually or based on an AD group for instance (computer is member of security group 'ChromeUsers' or something similar)
  3. What happens if you run the script manually on the computer? Can you publish it as available instead of required? What does the script do? Perhaps it cannot run because it needs to kill a process of some other software first?
  4. Yeah it's pretty complicated stuff. I was planning to follow the next blogs, as we are planning to setup HTTPS in our own environment, so I'm curious thanks again.
  5. Thanks for making this. This made PKI a less tough cookie to crack for me
  6. Checked the value in the registry, it does it exist. However, it points to C:\Program Files\Microsoft Configuration Manager\AdminConsole. This directory doesn't exist, so that may be the issue.
  7. The error was the following: Starting script... Import-Module : Cannot bind argument to parameter 'Name' because it is null. Looks like it cannot use or import the Posh CM module or something....
  8. Thanks for this! Note: it worked for me when I started Powershell ISE via the Configuration Manager Console. http://eddiejackson.net/SCCM/sccm_ps_1.png Running the 'regular' Powershell ISE didn't work for me.
  9. Good to hear that you've managed to get it working. Perhaps the image got corrupted due to offline servicing of Windows updates within the image? Something must have touched the image, making it corrupt.
  10. Perhaps there is a neighboring file server where you can put those files? Instead of injecting them back into the iso file.
  11. Possibly it is something particular to this image. You can also try to rebuild the task sequence from scratch to make sure that is the problem. Fortunately there aren't very much steps. However, when I search for the error (0x80070002) in your log, it brings me to this site: https://prajwaldesai.com/task-sequence-failed-error-code-0x80070002/ It states that possibly something is wrong with your NAA (Network Access Account). Perhaps password expired or wrong?
  12. You could try to redistribute the content for the image. Otherwise, you can also try to deploy a standard wim file (the original from the Windows DVD).
  13. Can you try to add the option FSP=fqdn.of.yourserver in the installation properties?
  14. Does the reboot after the 'Setup Windows and ConfigMgr' step go to the default installed OS or back to the boot image? What happens if you disable the reboot step? Can you post a screenshot of the task sequence steps?
  15. You could also check the deployment for errors in the SCCM console. First, get the deployment ID of the deployment: Go to the task sequence (Software Library -> Operating Systems -> Task Sequences) Open the Deployments tab. Make sure the Deployment ID is enabled by rightclicking the columns) Next: Open Monitoring -> System Status -> Status Message Queries Open 'All Status Messages for a Specific Deployment at a Specific Site'. Fill out the Deployment ID, the Sitecode and the period to search (1hr or 6hrs should be OK). Hopefully you can find the error here which is troubling you right now.
×
×
  • Create New...