Menu
Is there any potential issues with using the powershell but executing all the traditional commands associated with the old Windows command shell? I am also concerned that batch files written in the old style remain unaffected.
It makes complete sense that Microsoft will have thought of all of this; however, I just need to be cautious as we are running old style scripts in a production environment. I don't want to worry that powershell might pose any issues.
We are scheduling jobs (running batch files) via Windows Task Scheduler. I assume these jobs will be just fine whether the files are run as though submitted via the Powershell.
450
It is not only an interface but also a scripting language that is used to carry out administrative tasks more easily. Most of the commands executed on cmd can be run on PowerShell as well.
Yes, kind of. Powershell sometimes use different syntax for the commands, so if you have specific commands you often use in CMD, you might want to do a quick search for those first. Most commands are the same though.
PowerShell 7.0 marks a move a to . NET Core 3.1, enabling significantly more backwards compatibility with existing Windows PowerShell modules. This includes many modules on Windows that require GUI functionality like Out-GridView and Show-Command , as well as many role management modules that ship as part of Windows.
No it is not completely backwards compatible. You can however run a cmd session within powershell then get compatibility. If you are running a batch file as a scheduled task, then the batch file would be processed in a cmd session and not powershell anyway so they shouldn't have an issue.
121
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
