kevlar01

Thanks, I will look in to that !

Thanks for your quick reply Anyweb. Unfortunately the script has no logging of itself. Below is a snippet from the smsts.log of a computer rolled out a while ago (the issue was existing at that time).

Hi, Since a while we have problems with a step during our Windows 10 task sequence. This step is a powershell script which changes the computer description based on a variable which is set during the OSDMenu.hta (a form which pops up in the beginning of the task sequence where the computerdescription is filled out). For whatever reason, this step doesn't work anymore, but in the past this worked fine. The computerdescription isn't too long (more than 15 characters), and the user which is used in this step has sufficient rights. I have also tested it with a domain admin account but it didn't make any difference. We also have a step which sets the computername but this is no issue. The script which is used is the following: I have created a status message query for the task sequence and the error stated says it is an 'Incorrect function' Anyone else which has this problem?

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.

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)

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?

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.

Thanks for making this. This made PKI a less tough cookie to crack for me

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.

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....

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.

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.

Perhaps there is a neighboring file server where you can put those files? Instead of injecting them back into the iso file.

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?

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).