The term 'Get-MessageTrackingLog' is not recognized as the name of a cmdlet












0















I'm using powershell, I just use Get-MessageTrackingLog after login/Authentication



$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri “https://outlook.office365.com/powershell-liveid/” -Credential $UserCredential -Authentication Basic -AllowRedirection/ .


But I'm getting the following error:




Get-MessageTrackingLog not recognized as the name of a cmdlet




I want to search all emails in a mail box.










share|improve this question

























  • You should share more of your script I think, and when looking on online documentation, I found that this command only applies to: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - This cmdlet is available only in on-premises Exchange. Are you in one of this cases?

    – Mikitori
    Dec 28 '18 at 16:17











  • @Mikitori I am using Office 365, I don't know how to set on-premises.

    – Rajesh Kumar
    Dec 28 '18 at 18:13
















0















I'm using powershell, I just use Get-MessageTrackingLog after login/Authentication



$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri “https://outlook.office365.com/powershell-liveid/” -Credential $UserCredential -Authentication Basic -AllowRedirection/ .


But I'm getting the following error:




Get-MessageTrackingLog not recognized as the name of a cmdlet




I want to search all emails in a mail box.










share|improve this question

























  • You should share more of your script I think, and when looking on online documentation, I found that this command only applies to: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - This cmdlet is available only in on-premises Exchange. Are you in one of this cases?

    – Mikitori
    Dec 28 '18 at 16:17











  • @Mikitori I am using Office 365, I don't know how to set on-premises.

    – Rajesh Kumar
    Dec 28 '18 at 18:13














0












0








0








I'm using powershell, I just use Get-MessageTrackingLog after login/Authentication



$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri “https://outlook.office365.com/powershell-liveid/” -Credential $UserCredential -Authentication Basic -AllowRedirection/ .


But I'm getting the following error:




Get-MessageTrackingLog not recognized as the name of a cmdlet




I want to search all emails in a mail box.










share|improve this question
















I'm using powershell, I just use Get-MessageTrackingLog after login/Authentication



$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri “https://outlook.office365.com/powershell-liveid/” -Credential $UserCredential -Authentication Basic -AllowRedirection/ .


But I'm getting the following error:




Get-MessageTrackingLog not recognized as the name of a cmdlet




I want to search all emails in a mail box.







powershell office365






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Dec 28 '18 at 18:00









Goran Kutlaca

1,3751616




1,3751616










asked Dec 28 '18 at 15:30









Rajesh KumarRajesh Kumar

220115




220115













  • You should share more of your script I think, and when looking on online documentation, I found that this command only applies to: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - This cmdlet is available only in on-premises Exchange. Are you in one of this cases?

    – Mikitori
    Dec 28 '18 at 16:17











  • @Mikitori I am using Office 365, I don't know how to set on-premises.

    – Rajesh Kumar
    Dec 28 '18 at 18:13



















  • You should share more of your script I think, and when looking on online documentation, I found that this command only applies to: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - This cmdlet is available only in on-premises Exchange. Are you in one of this cases?

    – Mikitori
    Dec 28 '18 at 16:17











  • @Mikitori I am using Office 365, I don't know how to set on-premises.

    – Rajesh Kumar
    Dec 28 '18 at 18:13

















You should share more of your script I think, and when looking on online documentation, I found that this command only applies to: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - This cmdlet is available only in on-premises Exchange. Are you in one of this cases?

– Mikitori
Dec 28 '18 at 16:17





You should share more of your script I think, and when looking on online documentation, I found that this command only applies to: Exchange Server 2010, Exchange Server 2013, Exchange Server 2016, Exchange Server 2019 - This cmdlet is available only in on-premises Exchange. Are you in one of this cases?

– Mikitori
Dec 28 '18 at 16:17













@Mikitori I am using Office 365, I don't know how to set on-premises.

– Rajesh Kumar
Dec 28 '18 at 18:13





@Mikitori I am using Office 365, I don't know how to set on-premises.

– Rajesh Kumar
Dec 28 '18 at 18:13












1 Answer
1






active

oldest

votes


















0














The error message states that the Powershell environment does not have definition for function and yet cmdlet Get-MessageTrackingLog is not recognized.



Cmdlet Get-MessageTrackingLog is part of exchange Powershell module.



In order to use any function from this module you would need to install and then load it.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53960787%2fthe-term-get-messagetrackinglog-is-not-recognized-as-the-name-of-a-cmdlet%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    The error message states that the Powershell environment does not have definition for function and yet cmdlet Get-MessageTrackingLog is not recognized.



    Cmdlet Get-MessageTrackingLog is part of exchange Powershell module.



    In order to use any function from this module you would need to install and then load it.






    share|improve this answer




























      0














      The error message states that the Powershell environment does not have definition for function and yet cmdlet Get-MessageTrackingLog is not recognized.



      Cmdlet Get-MessageTrackingLog is part of exchange Powershell module.



      In order to use any function from this module you would need to install and then load it.






      share|improve this answer


























        0












        0








        0







        The error message states that the Powershell environment does not have definition for function and yet cmdlet Get-MessageTrackingLog is not recognized.



        Cmdlet Get-MessageTrackingLog is part of exchange Powershell module.



        In order to use any function from this module you would need to install and then load it.






        share|improve this answer













        The error message states that the Powershell environment does not have definition for function and yet cmdlet Get-MessageTrackingLog is not recognized.



        Cmdlet Get-MessageTrackingLog is part of exchange Powershell module.



        In order to use any function from this module you would need to install and then load it.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 29 '18 at 11:22









        Kirill PashkovKirill Pashkov

        2,5021815




        2,5021815






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53960787%2fthe-term-get-messagetrackinglog-is-not-recognized-as-the-name-of-a-cmdlet%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Monofisismo

            Angular Downloading a file using contenturl with Basic Authentication

            Olmecas