Jump to content


ejuliorod

Established Members
  • Content Count

    6
  • Joined

  • Last visited

Everything posted by ejuliorod

  1. We are using "Install Applications according to a dynamic variable list" to install our apps. This PS script is used at the end of the task sequence to clean out the variables placed in the computer Properties Variables tab. It works fine when running within Windows but cannot get it to run via task sequence when Windows is still in provisioning mode. I am running a command line in the task sequence running with an admin account This is the error in the log: File C:\_SMSTaskSequence\Packages\SA100154\RemoveOSDVariables.ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at http://go.microsoft.com/fwlink/?LinkID=135170. + CategoryInfo : SecurityError: ( [], ParentContainsErrorRecord Exception + FullyQualifiedErrorId : UnauthorizedAccess I use the same account in the task sequence to launch VB scripts. Thanks for your help
  2. I have a PS script that I run with an admin account that does not run during the task sequence. The log file shows access denied. I am using a command line because the Run Powershell task does not let me specify an account to use. (I get access denied with that one also) This is my command line - powershell.exe -file myscript.ps1 set-executionpolicy bypass This script runs just fine if I run it via TS when Windows is up and running, it just does not work during the TS when Windows is in provisioning mode. Any ideas? Thanks
  3. Is there a way I can rename the statestorepath folder and .MIG file to something like the computer name? This is the default path it creates on a capture, this long guid folder and the .Mig file is named USMT.MIG \\StateMigration\SMPSTORED_05ACDFF6$\3B189BD4CC3A4B45A86A5933516F6F13E75A2D5D1AD8B8ED883AEFD5B975BA95\USMT
  4. The Global condition is looking at Active Directory site, other global conditions work fine from the task sequence
×
×
  • Create New...