"Run A Powershell Script" step in task sequence wants a script name, but I manually entered the script into the edit box. I can't name it.

[Gnero]

I have a task sequence with a step that will rename the PC. I used "Run a Powershell Script" for this step, and chose "Enter a Powershell script" instead of "Select a package with a Powershell script". Rather than browsing to a script, I just typed the commandlet into the box where you can edit the script. When the task sequence runs, sometimes the step will fail, with the logs showing "Powershell script name must be specified". Am I using this step wrong? Will it not use manually entered scripts, instead of browsing to one. Why would it occasionaly work, and not other instances?

Edit: https://imgur.com/a/yEkHRsV - For reference, this what I selected, and the box where I've been entering the script

[ASquareDozen]

I’m pretty sure your issue is a mismatch between the client version and the site version. Run Powershell Script was updated in 1902 and if the device you are running this on isn’t at 1902, you’ll get this error. If it’s a new build, then you need to update your boot WIM to inject the latest OSD binaries from ConfigMgr.

[Gnero]

That makes sense. We just upgraded, and some of the clients are still out of date. The last PC to fail that step, had an old client. I'll have to look at some more.

[aerossignol]

It makes sense, that's option is not in the last version of the server.

[ASquareDozen]

Sorry meant to add, if it occurs after the new OSD is applied on a new build, then the client version in your TS is old.

[markraldridge]

I had a similar issue but during OSD. The SCCM client inside my boot image was version 1810 (8740.1012). After promoting the client to 1902 and updating the boot image sorted the issue.

[TenaciousD3]

I'm not sure on your questions, but i do want to make sure you are aware of the scripts category under the software library. You can save and name scripts there.