How to suppress VB Script black screen prompt in PXE/Boot Image

Miriyala, Vasu 21 Reputation points
2020-09-29T16:14:13.283+00:00

Hello,

We are executing a VB Script in PXE (from Boot Image) using prestart command, it does its work well, however this throws a black screen during its execution time. We don’t want this prompt to be seen by Helpdesk people during Image. We have tried suppressing it using wscript.exe /cscript.exe //Nologo switch, but no luck.

Appreciate any pointers

Thanks, Vasu

Microsoft Configuration Manager Deployment
Microsoft Configuration Manager Deployment
Microsoft Configuration Manager: An integrated solution for for managing large groups of personal computers and servers.Deployment: The process of delivering, assembling, and maintaining a particular version of a software system at a site.
906 questions
Microsoft Configuration Manager
0 comments No comments
{count} votes

13 answers

Sort by: Most helpful
  1. Jason Sandys 31,161 Reputation points Microsoft Employee
    2020-10-01T14:13:33.473+00:00

    The parameters are incorrect. nologo and b need to be prefixed by two forward slashes:

    wscript.exe //nologo //b dell_rid.vbs

    Have you simply booted into WinPE and launched a command-line to perform testing?

    0 comments No comments

  2. Miriyala, Vasu 21 Reputation points
    2020-10-01T14:32:58.253+00:00

    Hi Jason, this is latest one actually but we tried two forward slash also for NOLOGO and B as well in different sets, still prompt appears. Yes, we load PC into WinPE and Cmd launch for testing

    Just wondering as Prestart is officially supported by Microsoft and most of commands including Microsoft given examples are on VBS... I assume they might have given it a thought for black screen suppress etc :-). We are trying to check Powershell, leaving VBS behind

    0 comments No comments

  3. Jason Sandys 31,161 Reputation points Microsoft Employee
    2020-10-01T14:48:19.163+00:00

    Yes, this is perfectly supported. It's just a command-line.

    Without more testing on my part, I can't explain the behavior here.

    0 comments No comments