Yes indeed - very handy
Thanx for the run-through. Latency testing on a TCP port is a good one for me
I think you may have got your bandwidth mixed up with your latency when/if you pasted and forgot to edit.
"An example of a PsPing bandwidth test might look like the following:
Psping -l 3072 -n 15000 -h 50 192.168.20.15:25000"
Discussion on:
View:
Show:
Microsoft have had the Portqry available for a while, it is another way to test the availability of a port, e.g.
portqry -n 10.0.2.55 -e 80
will test for port 80 being open on that IP.
You can download it from the Microsoft website.
portqry -n 10.0.2.55 -e 80
will test for port 80 being open on that IP.
You can download it from the Microsoft website.
Why didn't Microsoft make this with a GUI interface? The year is 2012...isn't it time to get away from command line when possible?
This is 2012 and putting a GUI interface in a script/command file/batch is really hard.
Doing the same (and I mean the exact same) thing tomorrow and the next day with a GUI isn't assured.
Invoking a GUI from a scheduled task and providing arguments isn't really an option.
As they told you in kindergarten:"Stop pointing!"
Doing the same (and I mean the exact same) thing tomorrow and the next day with a GUI isn't assured.
Invoking a GUI from a scheduled task and providing arguments isn't really an option.
As they told you in kindergarten:"Stop pointing!"
Michael,
Learning the command line is an invaluable tool that can serve you well if you choose to put in the time to learn it. I would suggest you do so... I heard somewhere that Windows Server 2012 is a GUI optional OS.... 2012 right?
For Servers GUI presents an unnecessary consumption of resources. What are you going to do if you cant lean on the GUI?
http://www.howtogeek.com/111967/how-to-turn-the-gui-off-and-on-in-windows-server-2012/
Learning the command line is an invaluable tool that can serve you well if you choose to put in the time to learn it. I would suggest you do so... I heard somewhere that Windows Server 2012 is a GUI optional OS.... 2012 right?
For Servers GUI presents an unnecessary consumption of resources. What are you going to do if you cant lean on the GUI?
http://www.howtogeek.com/111967/how-to-turn-the-gui-off-and-on-in-windows-server-2012/
The GUI isn't necessary for things like this, besides a quick batch using a command such as this is a lot faster particularly when you're testing several machines at once.
Why indeed? Is this a MS tactic to steer us away from XP quicker? Well in my opinion XP will be here for a few years more, or until bespoke 3rd party developers decide it is time to code properly for Windows 7.
We still use XP Pro in the industry, It still works. Code this for XP please. Thx
We still use XP Pro in the industry, It still works. Code this for XP please. Thx
Microsoft is moving back to a command line focussed environment with tools like PowerShell. Windows Server Core is a hardened version of Windows that runs primarily from the command line. Because I might manage a bunch of computers with similar properties, using a tool like PowerShell is much more efficient than using remote desktop to access the computers one at a time.
Since Windows XP support is ending fairly soon, I would imagine more tools like PSPing/PSTools will not provide new feature support for Windows XP as new things are introduced. I agree that there will be shops running Windows XP for some time, even after support has ended, but those computers will not be able to take advantage of the new and improved tools not only from Microsoft, but from other vendors as well. Administrators of these systems need to be aware of this as they make the choice to continue with an unsupported Operating System.
Since Windows XP support is ending fairly soon, I would imagine more tools like PSPing/PSTools will not provide new feature support for Windows XP as new things are introduced. I agree that there will be shops running Windows XP for some time, even after support has ended, but those computers will not be able to take advantage of the new and improved tools not only from Microsoft, but from other vendors as well. Administrators of these systems need to be aware of this as they make the choice to continue with an unsupported Operating System.
I had to support Win NT 4.0 sp6a up until the bitter end along with still very active Win 9x machines. The reason was due to some legacy applications that required that environment.
Finally in 2007 we upgraded to Vista Business. It was actually the best version of Vista out there, and I was able to setup any legacy applications to run in virtual machines. We used Parallels for the VMs and they ran pretty well. It took a lot of convincing of the upper management to break away from the old technology, and this happened only after a critical machine died and we had no choice but to upgrade.
Finally in 2007 we upgraded to Vista Business. It was actually the best version of Vista out there, and I was able to setup any legacy applications to run in virtual machines. We used Parallels for the VMs and they ran pretty well. It took a lot of convincing of the upper management to break away from the old technology, and this happened only after a critical machine died and we had no choice but to upgrade.
- Keyboard Shortcuts:
- Prev
- Next
- Toggle
