WEBVTT

00:00.450 --> 00:08.310
Many of those shell commands change to a system state or configuration in some way actions might include

00:08.310 --> 00:14.490
restarting a computer modifying service disabled in a user account and so on.

00:14.550 --> 00:23.550
Windows powers shell standards specify that such commands support to parameters what if and confer which

00:23.550 --> 00:31.580
enables you to test and control command execution commands that do support those parameters will list

00:31.640 --> 00:38.940
the parameters in their help files when it is Aronowitz what the parameter x amount will not actually

00:39.200 --> 00:40.130
exist.

00:40.290 --> 00:47.920
Instead it will display messages that indicate what it would have done when it is Aronowitz confirm

00:47.980 --> 00:49.010
parameter.

00:49.070 --> 00:57.430
The command will stop and ask you whether it should continue for each item that is planned to be modified.

00:57.450 --> 01:06.130
For example if you are trying to stop turn services you'll be prompted ten times once for each service.

01:06.150 --> 01:11.610
Each command has an internal third and call to its current form impact.

01:11.670 --> 01:17.630
This is said by the commands developer to low medium or high.

01:17.790 --> 01:26.810
Windows POAs Shell has to build in reference variables so certains that interact with the conform impact

01:27.100 --> 01:35.550
and the confirmation behavior this reference variables are named Dolorosa unconfirmed preference and

01:35.640 --> 01:38.230
dollar sign what if preference.

01:38.280 --> 01:44.460
And when you open a new shell session they are each set to high by default.

01:44.460 --> 01:53.020
You may change them to low or medium for example by Taipan dollar sign confirmed preference equals in

01:53.030 --> 01:54.640
quotes medium.

01:54.660 --> 02:01.470
You should be aware of that changes is fact that the current shell session or the open sessions are

02:01.470 --> 02:08.340
not affected and your change is lost when you close the current session windows PowerShares confirmation

02:08.340 --> 02:10.400
behavior works as follows.

02:10.440 --> 02:14.950
When the command is run Windows Shell checks its internal.

02:14.970 --> 02:15.750
Confirm.

02:15.750 --> 02:17.130
Impact level.

02:17.220 --> 02:25.920
If the level is equal to or higher than the appropriate reference wearable windows Polwarth shell performs

02:25.920 --> 02:28.680
the confirmation action automatically.

02:28.680 --> 02:32.740
For example suppose that a command has to conform.

02:32.850 --> 02:42.750
Impact of medium and uset conform preference still low the command runs this shell will see that its

02:42.990 --> 02:51.520
impact is higher than the reference and will act as if you had used confirm parameter.

02:51.630 --> 02:57.040
This means you will be prompted to continue or to halt the command.

02:57.040 --> 03:05.100
If a command to use an internal conforming bucket of high load command trail all this all to conform

03:05.340 --> 03:12.390
you can override this by specifying does confirm call on Dolor character falls.

03:12.390 --> 03:15.920
So in that case it won't confirm you.

03:15.930 --> 03:17.880
It won't interact with you.