Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Get-Help command not showing all the details RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    When I open the Exchange Management Shell on my laptop and do any command like the following:

    help get-mailbox -detailed

    I just get the following result:

    SYNTAX

    DESCRIPTION


    PARAMETERS
        <CommonParameters>
            This cmdlet supports the common parameters: Verbose, Debug,
            ErrorAction, ErrorVariable, WarningAction, WarningVariable,
            OutBuffer and OutVariable. For more information, see
            about_CommonParameters (link of some kind).

    REMARKS
        To see the examples, type: "get-help  -examples".
        For more information, type: "get-help  -detailed".
        For technical information, type: "get-help  -full".

    If I do the same commands from any of my Exchange servers, I get the full details.  I've done this command for years and this is the first time I'm seeing no details.  Any help would be appreciated.

    Thanks,

    Andrew

    • Moved by Bill_Stewart Monday, April 20, 2015 7:16 PM Abandoned
    Monday, November 17, 2014 10:50 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    OK, here's what I think is going on.  I found that I am running PowerShell v3.  Version 3 introduces updatable help, and not all of the help has been created yet and added to the modules.  The information on this situation is found on the Scripting Guy Blog under an article entitled 'Where is PowerShell Updatable Help for Windows Modules?' .  It may be that I just have to use the '-online' switch for the help command in order to get the help contents for now until the updatable help files are fully implemented.  At least that's the idea I get from the Scripting Guy's blog article.

    Andrew

    • Proposed as answer by jrv Tuesday, November 18, 2014 7:50 PM
    • Marked as answer by Just Karl Thursday, April 30, 2015 4:51 PM
    Tuesday, November 18, 2014 7:02 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Maybe Microsoft hasn't updated help on the newer servers???

    Try this:

    From an elevated session only:

    Update-Help -Recurse -Force

    ¯\_(ツ)_/¯

    Monday, November 17, 2014 11:00 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the reply.  Here are the results of those commands.

    [PS] C:\WINDOWS\system32>update-help -Recurse -Force
    update-help : The -Recurse parameter is only available if a source path is specified.

    Then I tried just using -force :

    [PS] C:\WINDOWS\system32>update-help -Force
    update-help : Failed to update Help for the module(s) 'Microsoft.PowerShell.Diagnostics, Microsoft.WSMan.Management'
    with UI culture(s) {en-US} : Unable to retrieve the HelpInfo XML file for UI culture en-US. Make sure the HelpInfoUri
    property in the module manifest is valid or check your network connection and then try the command again.

    So, maybe that isn't the answer.

    Monday, November 17, 2014 11:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    what language are you set for?

    ¯\_(ツ)_/¯

    Monday, November 17, 2014 11:55 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    English as far as I know.  I certainly haven't changed it to another language.  I will just verify and let you know.  I'm assuming that you are referring to the PowerShell language.  Everything is in English, so I assume English is what it's set to.  I will let you know.

    Andrew

    Tuesday, November 18, 2014 6:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    All I can see is that I'm set up for English.

    Andrew

    Tuesday, November 18, 2014 6:20 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    OK, here's what I think is going on.  I found that I am running PowerShell v3.  Version 3 introduces updatable help, and not all of the help has been created yet and added to the modules.  The information on this situation is found on the Scripting Guy Blog under an article entitled 'Where is PowerShell Updatable Help for Windows Modules?' .  It may be that I just have to use the '-online' switch for the help command in order to get the help contents for now until the updatable help files are fully implemented.  At least that's the idea I get from the Scripting Guy's blog article.

    Andrew

    • Proposed as answer by jrv Tuesday, November 18, 2014 7:50 PM
    • Marked as answer by Just Karl Thursday, April 30, 2015 4:51 PM
    Tuesday, November 18, 2014 7:02 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    are you running a beta version?

    v3 has all base module help. We are ow on V4.

    ¯\_(ツ)_/¯

    Tuesday, November 18, 2014 7:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No, I'm not running a beta version that I know of.  Maybe Powershell needs to be re-installed or something.

    Tuesday, November 18, 2014 10:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You can try upgrading to the latest version and see if that helps:

    http://www.microsoft.com/en-us/download/details.aspx?id=40855

    This requires .Net 4.5.

    Don't retire TechNet! - (Don't give up yet - 13,085+ strong and growing)

    Tuesday, November 18, 2014 11:43 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have now tried this, and I still see the same issue.  I'm running out of ideas here.

    Thanks for your reply!

    Andrew

    Wednesday, November 19, 2014 4:06 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You must be connected to the Internet.  You must have download permissions through your firewalls and proxy servers and you must run at an elevated prompt.

    Be sure this subfolder exists: dir \windows\system32\windowspowershell\v1.0\en-us

    and this one:

    dir \windows\syswow64\windowspowershell\v1.0\en-us

    ¯\_(ツ)_/¯

    Wednesday, November 19, 2014 5:24 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the reply!

    I have both of those directories, I am connected to the Internet, and I am able to download from the internet.

    Are you saying I need to run the upgrade install as local admin? 

    Andrew

    Wednesday, November 19, 2014 5:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Do you know what and elevated prompt is?

    ¯\_(ツ)_/¯

    Wednesday, November 19, 2014 6:05 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Right-click on the Exchange Management Shell icon and choose run as administrator.

    Wednesday, November 19, 2014 7:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That is Exchange shell and not PowerShell. run this from PowerShell.

    ¯\_(ツ)_/¯


    • Edited by jrv Wednesday, November 19, 2014 8:48 PM
    Wednesday, November 19, 2014 8:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I understand that, but the question was whether I knew what an elevated prompt was.  When I run the 'update-help' command from the powershell session using an elevated prompt, I get the following output.

    update-help : Failed to update Help for the module(s) 'Microsoft.PowerShell.Diagnostics, Microsoft.WSMan.Management'
    with UI culture(s) {en-US} : Unable to retrieve the HelpInfo XML file for UI culture en-US. Make sure the HelpInfoUri
    property in the module manifest is valid or check your network connection and then try the command again.

    This output is the same in either a PowerShell session or an Exchange Management Shell session both running with elevated permissions.

    If I type the command 'help get-user -detailed' in the PowerShell session, I get what I expect, but in the Exchange Management Shell session I get nothing but the kind of thing that was in my original post.

    Very odd.

    Andrew

    Wednesday, November 19, 2014 11:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    This is likely becasue yuo didn't install PowerShell correctly.

    Be sure yuo installed all of the opre-requistes and have run WIndows uodate and applied all patches.  Somewhere something is missing.

    ¯\_(ツ)_/¯

    Wednesday, November 19, 2014 11:48 PM