3 ms·
The bulk because of soap is sort of irrelevant unless you are in a really slow connection where the size of every packet counts. I have more serious griefs aga
by cm2187 8y ago
The bulk because of soap is sort of irrelevant unless you are in a really slow connection where the size of every packet counts.
I have more serious griefs against powershell remoting.
For instance it is set up as a delayed start service which means you often have to wait more than a minute after a VM rebooted before you can log into it.
Windows Update is accessible by remoting through a COM API that doesn’t allow remote connections, so you can’t do the equivalent of a simple apt-get update remotely. There are horrible hacks around it, like setting up a scheduled task to trigger or collect the update and run that task from remoting and collecting the result some random way like reading a text file.
It really feels half baked, barely usable, and an ugly reminder that CLI has been added to windows as an after thought.
[edit] also I believe it is unencrypted by default. You have to enable https, which isn't straightforward. And you can't change the default ports.
- zaat 8y ago> Windows Update is accessible by remoting through a COM API that doesn’t allow remote connections, so you can’t do the equivalent of a simple apt-get update remotely. This isn't even remotely related to PowerShell (no pun intended), it's a security based decision of the windows update API. You can say that it is annoying, stupid and cause of hacks that are much less secure than opening remote operations to the API, and I will agree with you. But it isn't PowerShell business. As as side note If you are using SCCM you can use WMI for windows update. PowerShell is far from being half baked, it is a first class citizen in Windows, all the OS GUI tools today executes operations through PowerShell. Many let you see the commands so you can bypass the gui next time and run the commands yourself. As a matter of fact, many things these days can only be done by the shell, while the GUI only expose limited set of the available API.
- cm2187 8y agoI am not sure what you are trying the achieve by setting the cursor between the update API and powershell. Both are managed by the same group within the same company. The fact is Microsoft delivered an ssh-like scripting capability that cannot do simple things like updating the OS. You can call powershell a wonder, I beg to differ.
- zaat 8y ago> Both are managed by the same group I highly doubt that this is this the case. >The fact is Microsoft delivered an ssh-like scripting capability that cannot do simple things like updating the OS If you measure PowerShell by its ability to perform OS updates then you are correct, it is a failure. But the fact is that this annoyance isn't caused by the shell being half baked but rather it is an API decision of a different, unrelated product. The shell provides great usability in all other aspects - that is, the whole OS and other Microsoft and 3rd party software.
- radicalbyte 8y agoMost of the issues I had with powershell remoting were related to the security model. It's totally integrated into AD. Which is fine if you're in the domain, but a nightmare to manage when you're not. Or if you want to do anything cross-domain (because, you know, you might now want to combine a production and test domain, or have any kind of explicit trust relationship).
- AnIdiotOnTheNet 8y agoAs a fan and frequent user of PowerShell, I'm afraid I have to agree that PS remoting is pretty clunky. I often end up using psexec with cmd instead.
- sametmax 8y agoNot irrelevant: reactivity when typing in a remote shell affects very important features such as completion or resizing.