Windows 10: Powershell command Connect-ExchangeOnline failed

Hi,I am trying to get space used by mailboxes of users in exchange.I tried to connect to Exchange Online using powershel command Connect-ExchangeOnline.I failed with message :New-ExoPSSession : La connexion au serveur distant outlook.office365.com a échoué avec le message d’erreur suivant: Le client WinRM a reçu un statut d’erreur du serveur HTTP 500, mais le service distant n’a pas inclus d’autres informations sur

:)

 

PowerShell instead of Commandline in Creators Update

Interestingly enough my personal laptop just got the update...and still has Command Prompt listed, not PowerShell...

Edit: Not that it matters...I use both regularly. *Toast :toast:

 

PowerShell 5.1 ExchangeOnline Module not allowing authentication. Browser is out of date.

I'm currently utilizing PowerShell 5.1 to run ExchangeOnline to do several admin things that the Exchange Admin Center doesn't seem to allow or utilize. Normally when I try to Connect-ExchangeOnline it opens up a browser and asks me to use my SSO creds to log in to the admin center to make sure I'm able to connect. Lately though it's not been letting me log in and this is causing serious workflow issues. My senior tech doesn't have a clue what it could be about. I've made sure that my default browser for everything is Edge (its trying to open an old version of explorer from what I can gather) in settings. I just can't seem how to get it to proc correctly.





Clicking the link to the aka.ms/mysecurityinfo throws me into a login loop where I'm asked to SSO into my admin account then asked to set up an MFA app (I have authentication through my phone and don't want to use an application) and I can't ever be "logged in" to utilize PowerShell.

It should be noted that I can use and login to PowerShell 7 but the code I'm running doesn't function correctly in it and the rest of my team is using 5.1 so I need to stay cohesive in my environment.

If anyone has any advice, I'd be grateful.

 

How to factory reset Cisco 1700 Router

Hopefully I can help you here....its a very common thing to happen.


First, I take it you dont know the passwords for console access or telnet/ssh?

I will assume that these devices belong to you.

step 1. Plug a cisco console cable into a serial port on your pc
step 2. Plug other end into Cisco console port
step 3. Using hyperterm or putty or similar connect to the serial port
step 4. boot router, and make sure you clearly can see the output (this confirms you have good serial comms)
step 5. if this fails, adjust the comm port settings (9600, 8,1,n are the default)
step 6. now you have to do the only hard part...send the break command:

Break command list: Break Commands

Go down the list and match your OS and SW and try the sequence suggested.

If this fails several times do what I do: Install putty (free) and then to send a break so you can get into rommom just hit "ctrl-a b".