Webinar: Using PowerShell with Microsoft Online Services

January 26, 2010

Source: Microsoft Online Services Team Blog Join Jenna Lyday (Microsoft Online Services PM responsible for e-mail Migration) on Thursday, 1/28/2010 for the third webinar in our migration series. In this webinar, Jenna will demonstrate how to use Windows PowerShell commands to: - Provision and activate users - Perform a simple migration from Hosted Exchange to Exchange Online - Grant a user Full Mailbox Access permissions on another user's mailbox If you like managing your environment from the command line, or scripting...
no comments

PowerShell Localized Online help

January 24, 2010

Windows PowerShell online help content is now available in Chinese (simplified and traditional), German, Italian, Korean, Portuguese (Brazil), and Russian. Spanish, French, and Japanese are soon to follow. http://technet.microsoft.com/zh-cn/library/bb978526.aspx http://technet.microsoft.com/zh-tw/library/bb978526.aspx http://technet.microsoft.com/de-de/library/bb978526.aspx http://technet.microsoft.com/it-it/library/bb978526.aspx http://technet.microsoft.com/ko-kr/library/bb978526.aspx http://technet.microsoft.com/pt-br/library/bb978526.aspx http://technet.microsoft.com/ru-ru/library/bb978526.aspx
no comments

How to modify email addresses with PowerShell 2.0

January 20, 2010

One of the most asked question across many PowerShell forums, by Exchange administrators, is how to modify email addresses for mailbox users. The most common used code to add new email address in Exchange 2007 is: PS > $mbx = Get-Mailbox shay PS > $mbx.EmailAddresses += “newAddress@domain.com” PS > Set-Mailbox -Identity $mbx –EmailAddresses $mbx.EmailAddresses With Windows PowerShell 2.0 and Exchange 2007 (and above, sorry guys no 2003 ) we can use the Update-List cmdlet to add,remove or replace email addresses in a middle of a pipeline. PS > Get-Mailbox shay | Select-Object -ExpandProperty EmailAddresses | ` ...
22 comments

QuickTip – One-liners to get WinRM port numbers

January 19, 2010

With PowerShell 2.0 the default Windows Remote Management (WinRM) port numbers has changed from 80/443 (HTTP/HTTPS) to 5985/5986. One reason for changing the ports was a collision with internet servers which used the same ports. These ports are configured when you enable remoting in PowerShell 2.0, typically by using the Enable-PSRemoting cmdlet. So, if you need a quick reminder about the port numbers WinRM uses for its listeners… PS > Get-ChildItem WSMan:\localhost\Service\DefaultPorts | Format-Table -AutoSize Name,Value Name  Value ----  ----- ...
no comments

PowerShell ISE on Windows Server 2008 R2

January 18, 2010

As you probably know PowerShell 2.0 is installed by default on Windows 7 and Windows Server 2008 R2.  PowerShell 2.0 shipped with a new feature called Windows PowerShell Integrated Scripting Environment (ISE), A graphical user interface code editor. In PowerShell 2.0 you can launch ISE simply by executing ‘ise’ in the console (built-in Alias) or by clicking on its shortcut(s) in the programs menu. However, on Windows Server 2008 you won’t be able to find it:   If you open PowerShell and type ‘ise’ you’ll get an error: ...
3 comments

Module manifest gotcha

January 14, 2010

Module authors can use a manifest file for their modules (although this is not required). A manifest file is a .psd1 file that contains a hash table. The keys and values in the hash table describe the contents and attributes of the module, define the prerequisites, and determine how the components are processed. How do you know all the hash table keys? You don’t have to. PowerShell can create the file for you with the New-ModuleManifest cmdlet. New-ModuleManifest creates a new module manifest (.psd1) file, populates its values, and saves the manifest file in a specified path. You...
2 comments

Remote Registry PowerShell Module

January 10, 2010

  About two years ago I wrote a Stand alone registry functions library to help managing Windows Registry on local or remote computers. Now that PowerShell 2.0 has released, I’ve taken the time to convert the library to Advanced Functions and now they are part of a PowerShell module. The big improvement in the functions, beside the richness of PowerShell 2.0 features used in the module (support for Common Parameters, Comment Based Help and declaring a function that acts similar to a compiled cmdlet), is that now the functions can be used together in a...
175 comments