Categories
How-to Microsoft

Free ebook – Windows PowerShell v2: The Administrator Crash Course

Microsoft is adding PowerShell to more and more products, and going forward, the company’s plan is to incorporate PowerShell throughout all of its business products as a baseline administrative layer.

The Administrator Crash Course: Windows PowerShell v2For windows administrators who are new to PowerShell, Microsoft MVP Don Jones offers a new book from Realtime Publishers entitled The Administrator Crash Course: Windows PowerShell v2. Covering the most crucial elements of PowerShell v2, Don has constructed a set of practical tips and practice exercises that will get you up to speed in a matter of weeks. Each course section is designed to be reviewed in under an hour, so it’s a perfect way to quickly learn how to begin using PowerShell v2!

Download this Free ebook Guide to start your learning with PowerShell.

If you’re ready to get started in PowerShell, and have no experience, this is the crash course for you!

Note: You will need to create a profile in Realtime Nexus (The Digital Library for IT Pros) when you click the above link.

Courtesy: Realtime Nexus Windows Administration

You would also be interested in downloading these e-books:

If you are interested in some more Free Books/Magazines –

IT – Software & Development – Ebooks / White Papers from TradePubBrowse through this extensive list of free IT – Software & Development magazines, white papers, downloads and podcasts to find the titles that best match your skills; topics include web development, programming, software design and application software. Simply complete the application form and submit it. All are absolutely free to professionals who qualify. – Browse through the collection here

msigeek has joined hands with TradePub.com to offer you a new, exciting, and entirely free professional resource. Visit us today to browse our selection of complimentary IT-related magazines, white papers, webinars, podcasts, and more across 34 industry sectors. Try it today!

Categories
Community Activities

Bangalore IT Pro User Group (BITPro) UG Meet – 15th May 2010

As most of you are aware, the Bangalore IT Pro User Group (BITPro) does its regular User Group (UG) meets covering various Infrastructure Technologies, predominantly for IT Pros.

This weekend, we have Nitin Gupta (popularly known as gupnit) talking on “Active Directory Management with Quest Active Roles Server” and the Powershell expert Ravikanth talking on the “Powershell 2.0 Remoting Capabilities”.

Do mark your calenders and attend this UG meet at,

  • Dell India R & D center, Bagmane Parin, Bagmane Tech Park, CV Raman Nagar, Bangalore City, India.
  • Saturday, May 15, 2010 from 3:00 PM – 6:00 PM (IST)

Detailed Agenda: 

Time Topics Speaker Name
From To
03.00PM 03.30PM  Registrations
03.30PM 04.30PM  PowerShell 2.0 Remoting – Deep dive Ravikanth C, Dell India

http://www.ravichaganti.com/blog  

04.30PM 04.45PM  Tea Break  
04.45PM 05.45PM  Active Directory Management with Quest Active Roles Server Nitin Gupta, Quest Software

http://www.nitingupta.in/blogs

05.45PM 06.00 PM  Closing Note

 

Do not forget to Register for this offline UG meet before you plan to attend!

You do not need to pay any fees while registration; if you get any dialog which asks for your credit card details.. just cancel it and report immediately!!

Also, check out the past featured Community Activities here!

Categories
General Microsoft

What has changed from PowerShell 1.0 to PowerShell 2.0?

Windows PowerShell is an extensible automation engine from Microsoft, consisting of a command-line shell and associated scripting language. Windows PowerShell is built on top of, and is integrated with, the Microsoft .NET Framework.

powershellAdditionally PowerShell enabled easy access to COM and WMI to provide an environment in which administrators perform administrative tasks on both local and remote Windows systems.

Windows PowerShell 2.0 installs under the System32/WindowsPowerShell/V1.0 folder. PowerShell 2.0 is backward-compatible with PowerShell 1.0. However, the following points should be noted: 

Breaking changes from PowerShell 1.0

  • The value of the PowerShellVersion registry entry in HKLM\SOFTWARE\Microsoft\PowerShell\1\PowerShellEngine is changed to 2.0.
  • New cmdlets and variables have been added. These additions might conflict with variables and functions in profiles and scripts.
  • The -IEQ operator performs a case-insensitive comparison on characters.
  • The Get-Command cmdlet gets functions by default, in addition to getting cmdlets.
  •  Native commands that generate a user interface cannot be piped to the Out-Host cmdlet.
  • The new Begin, Process, End, and Dynamic Param language keywords might conflict with similar words used in scripts and functions. Interpreting these words as language keywords might result in parsing errors.
  • Cmdlet name resolution has changed. In Windows PowerShell 1.0, a runtime error was generated when two Windows PowerShell snap-ins exported cmdlets with the same name. In Windows PowerShell 2.0, the last cmdlet that is added to the session runs when you type the command name. To run a command that does not run by default, qualify the cmdlet name with the name of the snap-in or module in which it originated.
  • A function name followed by ‘-?’ gets the help topic for the function, if one is included in the function.
  • Parameter resolution for Microsoft .NET Framework methods have changed. In Windows PowerShell 1.0, if you called an overloaded .NET method that has more than one best-fit syntax, no error was reported. In Windows PowerShell 2.0, an ambiguity error is reported. In addition, in Windows PowerShell 2.0, the algorithm for choosing the best-fit method has been revised significantly to minimize the number of ambiguities.
  • If you are enumerating a collection in the pipeline and you try to modify the collection in the pipeline, Windows PowerShell throws an exception.

For example, the following commands would work in Windows PowerShell 1.0 but would fail after first pipeline iteration in Windows PowerShell 2.0:
$h = @{Name=”Hello”; Value=”Test”}
$h.keys | foreach-object {$h.remove($_)}

To avoid this error, create a sub-expression for the enumerator by using the $() characters. For example:
$($h.keys) | foreach-object {$h.remove($_)}

Restricted verbs and characters:

If you use the Import-Module  cmdlet to load commands that use unapproved verbs or restricted characters in the command name, you will receive a warning. Use the Get-Verb command to see a list of the approved verbs. Do not use any of the following characters in command names: [ # , ( ) { } [ ] & – / \ $ ^ ; : ” ‘ < > | ? @ ` * ~ % + =

Reserved keywords and parameter names:

Windows PowerShell 2.0 has reserved certain keywords as part of language syntax and some names that can be used as parameters to commands, as follows: 

  • Reserved language keywords: USING, CLASS, DEFINE, and VAR
  • Reserved parameter names: –SelectProperty and –SelectObject

Windows Presentation Foundation (WPF) hardware acceleration:

The graphical elements of Windows PowerShell Integrated Scripting Environment (ISE) might not render correctly if you are using Windows Presentation Foundation (WPF) hardware acceleration. If the graphical elements do not render correctly, disable the WPF hardware acceleration, especially if you are using older video drivers or virtualization software. For more information, see http://go.microsoft.com/fwlink/?LinkId=144711.

Help over remoting might not work:

If a user is calling the get-help Windows PowerShell command over Windows PowerShell remoting from a highly/partially (not fully) localized operating system, the help content will not be displayed. Users will see only the command syntax, but no help content for the command and its parameter. To work around this issue, users should copy a localized help file (whichever one they want to make the default) from the localized folder under c:\windows\system32\WindowsPowerShell\v1.0\<locale> to the application/module base folder. (The default path for Windows PowerShell commands is c:\windows\system32\WindowsPowerShell\v1.0.)

Courtesy: Windows Management Framework Relese Notes – Here

Categories
Microsoft Windows Installer, Application Compatibility and Deployments

Download – Windows Management Framework Release Candidate

The Microsoft Windows Management Framework Release Candidate (RC) build for Windows Vista, Windows Server 2008, Windows XP, and Windows Server 2003 includes the following components:

WinRM 2.0

Windows Remote Management (WinRM) is the Microsoft implementation of WS-Management Protocol, a standard Simple Object Access Protocol (SOAP)-based, firewall-friendly protocol that allows hardware and operating systems from different vendors to interoperate. The WS-Management protocol specification provides a common way for systems to access and exchange management information across an IT infrastructure.

PowerShell 2.0

Microsoft Windows PowerShell is a new command-line shell and scripting language designed for system administration and automation. Built on the .NET Framework, Windows PowerShell enables IT professionals and developers to control and automate the administration of Windows and applications.

BITS 4.0

Background Intelligent Transfer Service (BITS) is a service that transfers files between a client and a server. BITS provides a simple way to reliably and politely transfer files over HTTP or HTTPS. Both downloads and uploads are supported. Unlike other protocols that transfer files in the foreground, BITS transfers files in the background (by default). Background transfers use only idle network bandwidth in an effort to preserve the user’s interactive experience with other network applications, such as Internet Explorer. Foregound (or normal) transfers are also supported

This RC release is available in English, German and Japanese. The final release will be available in a broader set of languages.

Please note that this build is an RC release and should not be deployed on self-host systems as there may be issues with installation/uninstallation and general usability.

Requirements

Microsoft Windows Management Framework is designed for systems that wish to use the new Windows Management features on downlevel platforms. The system must have the following software installed: Windows Vista SP1, Windows Vista SP2, Windows Server 2008, Windows Server 2008 RTM, Windows XP SP3, or Windows Server 2003 SP2

Installation Instructions

The following are the installation instructions for the Windows Management Framework RC release. These steps may change for the final release.
Step 1: Please select the file that matches the architecture on your computer, the version of Windows on your computer, and the components you wish to install:

  • Architecture: x86 or x64
  • Windows Version: Windows Vista, Windows Server 2008, Windows XP, or Windows Server 2003
  • Components: Core (WinRM 2.0 and PowerShell 2.0) or BITS 4.0

Step 2: Copy the appropriate file from the website to your local desktop.
Step 3: Double click the file and launch the installer.
The installation will prompt for a reboot.

Download the framework here ! ! !