NetCmdlets Beta 2 is now Available.

NetCmdlets Beta 2 is now Available.

  • Comments 10

nsoftware has released Beta 2 of NetCmdlet, a PowerShell snapin which provides Cmdlets for a wide range of protocols.   The following is from their Release Notes:

New In Beta 2

The current release is packed with new features, new functionality, and new Cmdlets for network management and Internet Communications. The following is an short list of some of the new and exciting features we added to this release:

  • Added new Cmdlets to support WebDAV, TFTP, RAS, NNTP and more.
  • Added support for PSCredential objects across all Cmdlets.
  • Improved handling of certificate trust scenarios.
  • Support for simultaneous operations in Cmdlets such as Get-SNMP, Get-HTTP, etc.
  • set-ldap directly supports common tasks such as password changes to a user DN.
  • Direct MIB support in SNMP Cmdlets such get-snmp and set-snmp.
  • Updated documentation and sample Scripts.
  • Enhanced error reporting.
  • ...and much more!

Networking Tools for IT Professionals

The current package contains the following Cmdlets:

  • [get/send]-email : Send HTML emails with file attachments. Retrieve email through POP or IMAP connectivity.
  • [get/send]-trap : Monitor and send SNMP Traps.
  • [get/set]-ftp : FTP file transfer capabilities with advanced proxy and firewall support.
  • [get/set]-ldap : Access Active Directory or OpenLDAP servers through LDAP directory access
  • [get/set]-snmp : Command-line SNMP Management capabilities.  Manage network devices directly from PowerShell.
  • [get/send]-nntp : Command-line newsgroup browsing.  Monitor newsgroup postings and post messages to newgroup servers directly from PowerShell.
  • [send]-syslog : Syslog client for LAN event monitoring.
  • [get/set]-tftp : TFTP file transfer Cmdlet.
  • [convert]-data : Encoding and decoding utilities including Base64, SHA1, MD5, BinHex, and more.
  • [read/write]-zip : Compressions and decompression Cmdlet supporting Zip, Tar, GZip, and Jar.
  • [get/set]-webdav : WebDav client Cmdlet.
  • [get]-http : Web client Cmdlet with advanced proxy and firewall capabilities.
  • [get]-packet : Monitor network interface traffic.
  • [get]-time : Access network time servers and synchronize machine clocks.
  • [get]-rss : RSS client Cmdlet enables retrieval of RSS Syndicated content.
  • [get]-whois : Domain name Whois lookup.
  • [send]-im : Send Jabber(XMPP) Instant messages.
  • [send]-rexec : Remote execution via Rexec
  • [send]-rshell : Remote execution via Rshell
  • [send]-sms : Send SMS(SMPP) instant messages
  • [send]-page : Send alphanumeric pages (SNPP).
  • [send]-ssh : Secure Shell enabled remote access Cmdlet
  • [send]-ping : Network ping capability to monitor device availability.
  • [get]-trace : Traceroute Cmdlet for determining the path of network packets between hosts.
  • [get/set]-ras : Cmdlets for RAS connectivity.

I am particularly excited about the combination of PowerShell and NetCmdlets for producing scripts to manage SNMP devices and/or remote *NIX boxes.  I would love to hear from anyone that is doing that.

You can find out more about NetCmdlets here.

Jeffrey Snover [MSFT]
Windows PowerShell/MMC Architect
Visit the Windows PowerShell Team blog at:    http://blogs.msdn.com/PowerShell
Visit the Windows PowerShell ScriptCenter at:  http://www.microsoft.com/technet/scriptcenter/hubs/msh.mspx

aa

Leave a Comment
  • Please add 2 and 4 and type the answer here:
  • Post
  • Wouldn't this create a naming nightmare if Microsoft decide let's say to add a send-amil cmdlet to PSH in the future. How does PSH solve naming conflicts?

  • Very good blog with netcmdlets examples:

    http://geekswithblogs.net/lance/

  • @Nektar: There shouldn't be too much of a problem with naming in the future.

    Remember that PowerShell 1.0 (known as PS1) will be kept apart from PowerShell 2.0 (PS2 at my guess) so that any PS1 scripts will work with one, while PS2 scripts will work with another.

    So if you imagine you have a PS1 script that uses Send-Email (if you're using that snapin) today, and Microsoft adds Send-Email to PowerShell 2.0 tomorrow  -  you'd have to update your script to use 2.0 anyway. I'd also pretty much assume that snapins for PS1 will not work with PS2. But I would assume PS1 and PS2 will be designed to sit side by side.

    Though Microsoft could do anything by the time 2.0 is out.... ;)

  • So why the choice to bless Jabber with the -im noun?  Shouldn't the transport have been a parameter, or the noun -xmpp?  The IM transport wars have hardly been won, after all:  this is like write-video, and prematurely deciding to limit it to betamax.

  • Ah, I see.. Third-party product.  Still -- they should consider extensibility on that point.

  • You can use: NetCMDLets [link]

  • There is another way!  Novell offers a C# SDK at http://forge.novell.com/modules/xfcontent/downloads.php/ldapcsharp/ldapcsharp/CsharpLDAP-v2.1.9/.  I am working on a solution and I will be blogging about it at my blog.  If there are any questions shoot me an email: flaxcrack at hotmail.com.

  • Microsoft should not make us Admin's rely on third party solutions for simple FTP usage.  If they really want PowerShell to take off... they will concentrate on FTP commands and automation.

  • Hmmm... sergio, you obviously are not well informed here.

    1) A language is a language. A toolkit is a toolkit. While some toolkits are "included", the prototypical language (heard of "C") can't even write to the screen without a library. A language that tries to wrap all functionality for all people would take years to write, legions to support, and

    2) Loading that many cmdlets/types etc would take FAR LONGER to load (kind of like the bloat Windows gains with each feature set).

    You might want network tools, the guy beside me wants SOAP tools and Office Automation, while others desire neither. Better to provide a good basis and allow people to add the toolkits they need - and provide a good framework for developing the toolks

  • I agree and disagree with you donaldo.

    You're right about languages and libraries and frameworks. But Microsoft could provide a basic set of cmdlets, free of charge, with PowerShell. I believe FTP to be a basic tool and at least that should be incorporated.

    Networking/SOAP/Office automation could be left for the 3rd parties.

Page 1 of 1 (10 items)