Today, I created a script using Powershell 2 on XP (WMF)



The best way I could find to make it silent was to do the following...



-----------

1.) Create a .bat file that kicks off the Powershell script using the following line...

powershell.exe -WindowStyle Hidden -noprofile -Noninteractive -command "& 'C:\Script.ps1' "



2.) Create a shortcut to the .bat file that opens it minimized.



3.) Next, I entered the path to the shortcut into the HKLM\..\Run Folder of the registry to have it start automatically when a user logs on (I didn't want to put it in startup).

-------------



The problem I run into is (and maybe I'm being nitpicky here). The "script.bat" shows on the Start bar for 20 to 30 seconds when the script is kicked off during system logon and this whole processes of running a shortcut to run a minimized .bat file to run a .ps1 seems like a bit much.

Why do you need to wrap it into a .bat anyways?

I guess that's the way I learned to do it. but I think I see what your getting at. I should just put the powershell.exe line in a custom shortcut or directly into the Registry. I think I read somewhere that I had to use a .bat file for task sceduler and have been doing it ever since. Boy do I feel silly. 8-)