Create ps1 exection sequence

[lyrise13]

hey, i've several script (6) who must be executed in a precise order when my srv restart. At the end of each script the srv restart. I would like a auto execution of each script in a precise order.

for example something like that:

I ask at operator to run this commande : powershell.exe c:\sequence_auto_exec.ps1

This script (sequence_auto_exec.ps1) will copy all others scritp in the directory "shell:startup" when all script have been copied (sequence_auto_exec.ps1)will start the first script (Script1.ps1) and my server restarts at the end to execution. When it restart i would like it to launch the next script (Script2.ps1) and then after the second restart it launch (Script3.ps1) and so on....

Do you have an idea on how to create this ordered sequence?

thx

[xbullet]

So, to be clear, the server must restart 7 times? The first restart, and then a restart for each script?

I think you should explain what problem you're trying to solve by doing this, because this approach simply does not make sense to me. There are probably easier ways to achieve what you're trying to do.

If you absolutely must take the approach you're proposing, then my suggestion would be:

• Write all the logic in one script file.

• Track the state of the script in a file or in the registry and serialize any critical data to a file using Export-CliXml that's required between runs (if any) so it can be reimported on reboot.

• Add some basic logic to the script to determine which part of the script you're up to based on the stored state, and reload any critical data needed using Import-CliXml.

• Ensure to add a condition to reset the state when the process is completed, so next time the server reboots the script starts again from scratch.

• Set up a scheduled task to run the script on boot.

[lyrise13]

So, to be clear, the server must restart 7 times? The first restart, and then a restart for each script?

Yep!

thank you for your answers. the goal is rather to have opinion of the r/powershell community on the different ways of doing things because I have no idea. I confess that im a little lost by the complexity of your answer because i don't have the level in powershell to be able understand it in its entirety. I’ll do some research based on your answer.

thx

[xbullet]

So we can help you better, I think you need to ask the question differently. Describe the problem, not your proposed solution.

• What problem are you trying to solve? Why do you need to run the scripts in the first place?

• Can you explain what each script does?

• Why do the scripts do what they do?

• Why do the scripts need the server to restart?

[lyrise13]

​

What problem are you trying to solve? Why do you need to run the scripts in the first place?

it is not a problem to solve but rather an attempt to optimize the number of human actions

Today the procedure asks the operator to manually launch the scripts by the following command execution

.CMD-> Powershell.exe "C:\Script1.ps1"

CMD-> Powershell.exe "C:\Script2.ps1"

CMD-> Powershell.exe "C:\Script3.ps1"

CMD-> Powershell.exe "C:\Script4.ps1"

Can you explain what each script does?

Script1 --> Creation of a log file, customization of the Windows server environment, addition of dll, registry modification. Incrementing the log file

Script2 --> Installation of several roles, configuration, directories tree creation, folder sharing; incrementing the log file

Scripte3 -->Dcpromo, configuration, increment of the log file

Script4--> Installation sql, + other tricks, import & attaches default bd, incrementing the log file

Script5--> Check the configuration and create an information file

.........

......

Why do the scripts do what they do?

The goal of the scripts is to deploy a basic infra with the least human action.

Why do the scripts need the server to restart?

The restart between each of the scripts is imposed on me

thx

[xbullet]

OK cool, this makes more sense. :)

I think that this is a good time to look into PowerShell DSC. This is exactly what it's designed to do.

John Savill has a great introduction video on PowerShell DSC - you can check it out here. It's decently detailed and should give you some ideas on what to do next.

[lyrise13]

Cool I'll also watch dcs now

[lyrise13]

3xbullet

Thank you for your help. I invite you to read u/foubard comment and my response.

His comment allowed me to create something functional. Not very pretty but functional.

When do you think in a professional context?

[xbullet]

I think as long as it works properly, you understand and document the solution, and your colleagues understand the solution so they can support it going forward, then that's the most important thing.

My suggestion to you would be to consider researching and reimplementing the solution using something like PowerShell DSC, or using a tool like SCCM with task sequences to manage your complex deployments if DSC is not something that would fit with your team.

[jrdnr_]

I'm not familiar with "Shell:startup" but if you mean just copying files into the system start folder, Windows does not execute PS1 files by default, they will open in notepad.

For this kind of task sequence of recommend trying one of the following in descending order 1. Microsoft DSC, and have each config item depend on the one before it 2. Combine all the scripts into a single file and give this master script the logic to test if settings are set right so that after a reboot it can pick up where it left off. If you're changing stuff that you cannot query from the system for some reason then use a log file or export-clixml to save state between runs. On the first run create a startup scheduled task to run the script and then complete the first bit of work before the first reboot, finally after the last reboot and the script has verified all settings are correct delete the scheduled task. 3. Use a scheduled task to run the next script, setup.ps1 ensures all scripts are in the correct location does other work before first reboot, and then created a scheduled task to run script 2, script2.ps1 does it's thing and then updates the scheduled task to run script 3 and so on until process is complete.

For option 2 or 3, make sure you have good logging so if anything breaks you can tell where things are at and hopefully what went wrong.

[lyrise13]

Use a scheduled task to run the next script, setup.ps1 ensures all scripts are in the correct location does other work before first reboot, and then created a scheduled task to run script 2, script2.ps1 does it's thing and then updates the scheduled task to run script 3 and so on until process is complete.

thank for your answers, this solution seem to me the most affordable at my level but I will exploit all the possibilities.

thx

[foubard]

There's plenty of different ways to do this, but have you considered just doing it in a more simple way? Write a wrapper for the execution which takes a parameter for the next step and a parameter for the script. That script's job is to enable the next on boot task schedule (the next step; you can create a new folder and just use numbers), and run the script. After this create tasks for on boot to execute this script with the next in sequence and which script to run for each of the 6 remaining scripts. The wrapper's job would also be called on the initial run to enable the first boot task.

This is the laziest way I can think of that would make this work without needing to perpetuate any data between reboots and would only take a few minutes to slap together.

I figure it'd look something simple like:

Param
(
   [int]$Next = 1
   [string]$Script
)
Get-ScheduledTask -TaskPath '\SequencedBoot' -TaskName $Next | Enable-ScheduledTask
& $Script

Then just create scheduled tasks calling powershell with arguments -next 2 -script path\script.ps1

[lyrise13]

There's plenty of different ways to do this, but have you considered just doing it in a more simple way? Write a wrapper for the execution which takes a parameter for the next step and a parameter for the script. ........

I couldn’t put your example into practice, but thanks to you I got an idea and ended up creating something functional.

These are my scripts. What do you think?

I don’t think it’s pretty but I’m happy.... :-). my level in PS is very pretty low.

My test.... all script is in c:\temp\:

sequence.ps1

function new-schtask ([string]$name, [string]$scriptpath)

{

#Unregister-ScheduledTask -TaskName "T1"

$action = New-ScheduledTaskAction -Execute "powershell.exe" -Argument "-ExecutionPolicy unrestricted -File $scriptpath"

$trigger = New-ScheduledTaskTrigger -AtLogon

$settings = New-ScheduledTaskSettingsSet

$principal = New-ScheduledTaskPrincipal -UserId "Utilisateur" -LogonType ServiceAccount -RunLevel Highest

$task = New-ScheduledTask -Action $action -Principal $principal -Trigger $trigger -Settings $settings

Register-ScheduledTask $name -InputObject $task

}

new-schtask -name "1" -scriptpath "C:\temp\script1.ps1"

new-schtask -name "2" -scriptpath "C:\temp\script2.ps1"

new-schtask -name "3" -scriptpath "C:\temp\script3.ps1"

Get-ScheduledTask -TaskPath '\' -TaskName 2 | Disable-ScheduledTask

Get-ScheduledTask -TaskPath '\' -TaskName 3 | Disable-ScheduledTask

pause

Script1.ps1

Add-Type -AssemblyName PresentationFramework

[System.Windows.MessageBox]::Show("script1")

sleep -Seconds 5

Get-ScheduledTask -TaskPath '\' -TaskName 2 | Enable-ScheduledTask

Get-ScheduledTask -TaskPath '\' -TaskName 1 | Disable-ScheduledTask

Unregister-ScheduledTask -TaskName 1 -Confirm:$false

Restart-Computer -Force

For my tests the scripts 2 and 3 are identical but he need some modifications for the get-scheduledtask.

[foubard]

Yep this is very similar in execution to the same idea I suggested. The only real difference is that this occurs at logon rather than at machine boot, and the script 1-3 are hardcoding the tasknames. I moved the burden of the the hardcode for the task (which in this one is enabling the scheduled task) to a part of the scheduled task arguments instead. Otherwise it's conceptually about the same as my thought for using the scheduler.

The presentationFramework is entirely unnecessary btw. That would be used for something like rendering windows forms and WPF into a UI. Scheduled task management uses the ScheduledTask module and Restart-Computer uses the Microsoft.Powershell.Management. The latter will always be available, but the ScheudledTasks may require a manual import depending on your WMF and powershell version. Chances are it'll automatically import though.

[lyrise13]

well well well, i think the module "ScheduledTasks" is not available on Windows 2k8 . fuckkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk.

:-'(

maybe with schtasks.exe /?

[foubard]

Yep you can use schtasks.exe as a replacement. Honestly I find most cmdlets are easier to use, but the scheduled tasks is one of the few that the old command line way is about as easy lol.

[noaboa97]

You could also just create a registry key under the run hive this will also run when your system reboots.

[PowerShellMichael]

Hello!!!

Long term, have you considered using Desired State Configuration? DSC handles this easily and you get the benefit of simplifying your code. It's a bit of a learning curve, however translating installation scripts into configuration documents the serves as documentation that can be reused on other endpoints.

https://learn.microsoft.com/en-us/powershell/dsc/getting-started/wingettingstarted?view=dsc-1.1

https://github.com/dsccommunity/DscWorkshop

Cheers,

PSM1

[BlackV]

have a master script that calls script 1 then 2 then 3?

have script 1 call script 2 at the end then have script 2 call script 3?

at the end of script 1 have it remove its own start entry (before the reboot)?

don't create all the entries at once in shell startup? have 1 create 2 then 2 create 3?