Announcement

Collapse
No announcement yet.

Exchange 2010 weird behavior

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Exchange 2010 weird behavior

    Hi all

    Lately i just migrated an 2003 exchange server to 2010. At the Exchange command shell, When i try to give some (not all) command, nothing happens. it just jump to the command prompt again.
    I've gived the " Get-RoutingGroupConnector" command. nothing happens.
    When i gived "Get-RoutingGroupConnector | Remove-RoutingGroupConnector", i got
    this sign ">>" and a blinking cursor without anything to happen.
    1st time i see this. does anyone knows whats wrong

    Thanks in advance

  • #2
    Re: Exchange 2010 weird behavior

    the >> means you are in the middle of a cmdlet which is expecting input
    CTRL+C to get to the normal c:\users\administrator> (or whatever) prompt then try again
    Tom Jones
    MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
    PhD, MSc, FIAP, MIITT
    IT Trainer / Consultant
    Ossian Ltd
    Scotland

    ** Remember to give credit where credit is due and leave reputation points where appropriate **

    Comment


    • #3
      Re: Exchange 2010 weird behavior

      Hi Ossian and thank you for your fast reply as always

      I just dont understand why when i give a regular command like Get-RoutingGroupConnector nothing happens.
      Do you have any idea?

      Comment


      • #4
        Re: Exchange 2010 weird behavior

        Do any of the Exchange cmdlets work?
        Do other cmdlets work (e.g. get-help)?
        Are you on the exchange server or on another machine?
        Tom Jones
        MCT, MCSE (2000:Security & 2003), MCSA:Security & Messaging, MCDBA, MCDST, MCITP(EA, EMA, SA, EDA, ES, CS), MCTS, MCP, Sec+
        PhD, MSc, FIAP, MIITT
        IT Trainer / Consultant
        Ossian Ltd
        Scotland

        ** Remember to give credit where credit is due and leave reputation points where appropriate **

        Comment


        • #5
          Re: Exchange 2010 weird behavior

          Yes indeed. Thats what make this even more weird. Get-help for instance or Get-Command works. I Wanted to create a new routingGroup Bcoz of flowing mail problems between both servers. The command Get-RoutingGroupConnector
          Doesn't respond. No error nthing. Just jump back to the command prompt

          Comment


          • #6
            Re: Exchange 2010 weird behavior

            If you type in

            get-routinggroupconnector and then press enter and nothing comes back, then you don't have a routing group connector.

            It only returns results if there is something there to return.

            Simon.
            --
            Simon Butler
            Exchange MVP

            Blog: http://blog.sembee.co.uk/
            More Exchange Content: http://exchange.sembee.info/
            Exchange Resources List: http://exbpa.com/
            In the UK? Hire me: http://www.sembee.co.uk/

            Sembee is a registered trademark, used here with permission.

            Comment


            • #7
              Re: Exchange 2010 weird behavior

              Ok i understand and got to apologize for wasting your time. I got a little confuse when i gave this command before New-RoutingGroupConnector -Name "domainrouting" -SourceTransportServers "server1.domain.com" -TargetTransportServers "Server2.domain.com" -Cost 10 -Bidirectional $true -PublicFolderReferralsEnabled $true. I did this and was certain to have a routing group as it should be.
              For some reason it didnt happen. Then i read somewhere that some problem can appear with the Exchange Shell command. All i got to do is to delete c:\users\user\appdata\microsoft\exchange\powershel l folder, than run the again the shell and it will fix it. Then i ran again the adding routing command. Did the Get-RoutingGroupConnector again, and now all is fine.
              I really appriciate the time and the effort of you both Sembee and Ossian.

              Again, Thank you

              Comment

              Working...
              X