Windows 10: I Need Some Powershell Education

Since the days of an Autoexec.Bat and the Config.Sys, I've kept a directory/folder named Utilities for Batch Files and small programs that do not require installation. It's always been on "the path" for obvious reasons. With the coming of CU and Powershell replacing the Command Prompt, I've been learning something about PS. It's been said that anything I can do from the Command Prompt, I can do in PS. Well I must have something wrong. Here's my setup now and none of my Batch Files or "little" programs run in PS:









How do I get the Utilities folder in a path that PS will read?

Thanks for any attention and help.

:)

 

Powershell - Need some help

Hi Everyone,

Currently I am pulling in data and parsing in powershell with a regex expression.

$regex = [regex]
"\b(??:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\.){3}(?:25[0-5]|2[0-4][0-9]|[01]?[0-9][0-9]?)\b"

$ipAddress = $regex.matches($log) |
% { $_.value }

The variable becomes a string. I am looking for a way to convert the ip addresses into objects, that I can pass into a url.

$ipAddress =
$regex.matches($log) |
% { $_.value } | ConvertFrom-StringData
$IPAddress -OutBuffer
$ipAddressURL

This is the output currently shown when I run the $ipAddress variable in powershell. I have looked and googled left and right but I am unsure how to separate these into objects and not string in PS. Can someone help?

118.101.203.252

24.10.216.192

173.252.100.117

173.252.114.114
Thanks!

Third.

 

Windows 10 education key

You should be able to enter the key in Windows 10 Pro and be upgraded to Education. No need to reinstall Windows 10, your apps, files and settings preserved.

Are you sure you want Education though? It has some limitations like Cortana is disabled by default and there might be some missing functions.

Open Start > Settings > Update & security > Activation > change the product key

Enter your Windows 10 Education key then click Next to upgrade.

 

This may or may not help but command prompt is till there. Settings > Personalization > Taskbar > Replace Command prompt with Power shell in the menu when I right click the start button. Set to Off to get the command prompt option.

 

Hey, thanks for the comment. It is appreciated. I understand. I'm just trying to learn the coming changes and adapt to them. I do know "cmd" will still be available to be run from Powershell.

 

I had a feeling you'd say that. *Smile I'm a total powershell noob. *Sad So much so that I switch it back to command prompt out of habit.

 

So you know how I feel. *Huh

 

Tons of tutors on YouTube for PowerShell

 

You appear to have misunderstood what I said earlier. CMD shell is not going away. The only thing that's gone away is the "Open CMD shell" from the file menu of File Explorer. CMD is still in the start menu, and you do not have to run it from within powershell.

The point I was making was that you could click File->Open Windows Powershell and then do many of the common things, or run cmd from within powershell. You can still run a standard cmd console by going to start and typing cmd and a regular cmd prompt will open. You can also pin that to start or taskbar if you want.

In any event, after you add a path to your environment variables, you have to start a new console or powershell window.

 

Ah, I did misunderstand that one. You shouldn't scare old people like that.

Hmmm. That path addition has been in place since right after I first booted this machine up.

Humph! Something else I have to deal with. But I do have to admit it's entertaining and sometimes even a little fun.

 

CWGilley, could you elaborate?

If I have a folder “C:\Utilities” in the path variable with batch and powershell scripts in it, I can specify just the name of the batch or powershell script in a powershell console and it will run. Is this what isn’t working for you?

 

SET PATH=C:\Utility;%PATH% should just work fine ( or using the GUI as you showed)
Another trick is to always have your script go to the working directory, in my view mandatory ( did that also with Batch):
$location = Split-Path ((Get-Variable MyInvocation -Scope 0).Value).MyCommand.Path
Push-Location $location
[Environment]::CurrentDirectory = $location
<scriptcode>
Pop-Location (if you have more lines below, make sure you are where you expect it.)

Calling for scripts or apps, please read PowerShell and external commands done right // blog.edgylogic
That one helped me A LOT!!!

in my view ( and with the Batch experience of an old guy), Batch can do stuff with less code, normal OS things. But with conditions, functions (as we call them Procedures) and working with file-content, apps, Registry and what have you, I believe one has to start PS. So, chapeau for going there. There are indeed tons of info, have fun

 

That's right. None of the C:\Utilities do anything when I try to run them in PS. Here's what I get with $Archive.bat file:

Windows PowerShell
Copyright (C) 2016 Microsoft Corporation. All rights reserved.

PS C:\Users\Clayton> cd\
PS C:\> $Archive
PS C:\>


Even manually taking it to C:\ before the command gets nothing.

gpglang, thanks for the link. I'm headed over there now.

 

Well there’s your problem. The dollar symbol is used to denote a variable in PowerShell.

If you want to run that batch file with that special symbol in it, you’ll need to explicitly tell PowerShell you want to invoke it, so quote it and prepend an ampersand (the call operator).
Code: PS> & '$Archive'[/quote]

 

OK, bad example. Here's the simplest (and oldest) one I have named X.bat

@ECHO Off
CD\
C:
CLS
Exit


And it doesn't work either. Your code example does run. Thanks for that one.

I'm starting to think/understand PS is an environment unto itself. Independent of Windows, CMD, and/or DOS.