header1   header
header
header Register : : Login header
header
connector   connector
menuleft menuright
submenu   submenu
left
Exchange CMDLETS
Last Post 09 Feb 2012 01:25 AM by BostjanK-SI. 11 Replies.
Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
BobdeeUser is Offline
Basic Member
Basic Member
Posts:130
Avatar

--
10 Aug 2010 02:07 AM
    Hi,

    Can anyone point me in the right direction of getting exchange cmdlets that allow me to create and modify mailboxes?

    Thanks in advance

    Robbie.
    RajithaUser is Offline
    New Member
    New Member
    Posts:9
    Avatar

    --
    10 Aug 2010 02:49 AM
    You can use the help command to get any cmdlets

    Get-Help New-Mailbox
    Get-Help Set-Mailbox
    RajithaUser is Offline
    New Member
    New Member
    Posts:9
    Avatar

    --
    10 Aug 2010 03:14 AM
    You must have Exchange Management Shell installed to use the cmdlets. If you are only looking for the cmdlets you can see them in the Exchange help file.
    BobdeeUser is Offline
    Basic Member
    Basic Member
    Posts:130
    Avatar

    --
    10 Aug 2010 03:16 AM
    I don't actually have the cmdlets installed, so was wondering where I can get them?

    I've had a good old look on the web, but the only thing I can find really is the Exchange Management Tools. Is this the only option? I mean, can I not just install the appropriate libraries?

    Robbie.
    BobdeeUser is Offline
    Basic Member
    Basic Member
    Posts:130
    Avatar

    --
    10 Aug 2010 03:29 AM
    Ok, thanks.
    Marco ShawUser is Offline
    Veteran Member
    Veteran Member
    Posts:1684
    Avatar

    --
    10 Aug 2010 07:10 PM
    You can get the "EMS" by installing the Exchange Admin Tools. You'll be able to use the Exchange install media and I believe you can even download the admin tools online. You need the appropriate access permissions.

    Are you using PowerShell v1 or v2? If the client and server are using v2, you may be able to use PowerShell remoting, which is basically built-in with Exchange 2010.
    BobdeeUser is Offline
    Basic Member
    Basic Member
    Posts:130
    Avatar

    --
    06 Jan 2012 11:03 AM
    Hi Marco - sorry for only replying now.

    We are using an earlier exchange domain, so completely non-powershell.  I'm only posting in case any other folks are having the same troubles.

    Basically, only 2010 (I think) at the moment is PS compliant and trying to use powershell on the older versions will not work, unless you upgrade your entire exchange, which will not happen in most circumstances.

    In my case on this thread, I used powershell to create the users and VB to create their mailboxes...

    It's unfortunate that Microsoft has cut PS off from earlier versions.  But money talks I guess!
    mcmaniglesUser is Offline
    New Member
    New Member
    Posts:18
    Avatar

    --
    06 Jan 2012 12:05 PM
    Exchange 2007 fully supports powershell as well as 2010, but you are correct that exchange 2003 does not.
    Karl MitschkeUser is Offline
    Basic Member
    Basic Member
    Posts:457
    Avatar

    --
    06 Jan 2012 12:12 PM
    You can use PowerGUI and the Exchange 2003 PowerPack:
    http://powergui.org/kbcategory.jspa...egoryID=47

    Karl
    http://unlockpowershell.wordpress.com
    Co-Author, Windows PowerShell 2.0 Bible
    -join("6B61726C6D69747363686B65406D742E6E6574"-split"(?<=\G.{2})",19|%{[char][int]"0x$_"})
    newuserUser is Offline
    New Member
    New Member
    Posts:14
    Avatar

    --
    08 Feb 2012 12:34 PM
    in response to the question :- Are you using PowerShell v1 or v2? If the client and server are using v2, you may be able to use PowerShell remoting, which is basically built-in with Exchange 20

    How to find out if the server is using v2?
    Marco ShawUser is Offline
    Veteran Member
    Veteran Member
    Posts:1684
    Avatar

    --
    08 Feb 2012 01:56 PM
    From a PowerShell window, type "$psversiontable".

    That will only work on v2, so if you see output, you're running v2.

    You may want to start this thread over: You've sort of "hickjacked" the thread, and I don't know what you're really looking for...
    BostjanK-SIUser is Offline
    New Member
    New Member
    Posts:11
    Avatar

    --
    09 Feb 2012 01:25 AM
    You can also get version with

    get-host

    and you will see version you have
    ------------------
    Name : ConsoleHost
    Version : 2.0
    InstanceId : aa8bd451-85d8-4538-9f29-61147e6a0b1c
    UI : System.Management.Automation.Internal.Host.InternalHostUserI
    nterface
    CurrentCulture : sl-SI
    CurrentUICulture : en-US
    PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
    IsRunspacePushed : False
    Runspace : System.Management.Automation.Runspaces.LocalRunspace
    You are not authorized to post a reply.


    Active Forums 4.3
    right
    footer   footer
    footer Sponsored by Quest Software • SAPIEN Technologies • Compellent • Microsoft Windows Server 2008 R2 footer
    footer   footer