New
#140
Ah Dimitri, wouldn't it be easier this way to post it
Instal Speculation Control 1.0.14.ps1
I prefer automation
Ah Dimitri, wouldn't it be easier this way to post it
Instal Speculation Control 1.0.14.ps1
I prefer automation
My dear friend, I do too!
The issue here was that steps 2.1 and 2.2 are mutually exclusive.
It's up to the user to decide if he/she wants to keep the older versions (2.1) or clean install the script by uninstalling any previously installed versions (2.2).
In that case we should have given such a choice to the user, within a script, which is easily doable.
In my post, I just wanted to provide a quick and dirty solution to anyone who just wanted to install the script!
But as I said before, the "customer" (especially the good ones, like Cliff) is always right. If you want it, I can do it.
You're most welcome! Glad it helped you.
And as a side note, you don't need to run the import-module command, in Powershell V4.0 and later, once you save the module in a folder included in the environment variable PSModulePath.
The folder "$env:ProgramFiles\WindowsPowerShell\Modules" is included, so any modules saved in there, are accessible by Powershell, without importing them.
Dimitri it's just I have written so many instructions for members here, and they always say "It didn't work??!!".
And why?
Because they almost always skip a step or think they don't need to a step.
So when possible, I feel it's just best to automate a process, where I can, so I don't have to troubleshoot their failure to follow instructions step for step.