They had been putting in every password they could think of, trying to resolve their “account problem.” Nothing worked. Four people called me on the same day last week about the scary message. If you see that message and you know you haven’t changed any passwords lately, you will worry that your Microsoft account has been hacked. Select here to fix it in Shared experiences settings.” The message reads: “ Microsoft account problem – We need to fix your Microsoft account (most likely your password changed). Trust me – you won’t miss “shared experiences.” (Sometimes they keep popping up even after those switches have been turned off. Turn off Nearby Sharing and Share across devices. The only suggestion I have left is to ignore it.)Ĭlick on Start / Settings (the gear in the left column).Ĭlick on Shared Experiences in the left column. For some people – including on my own computers for the last few months – this notice still appears even after turning everything off. (Update 09/2020: Try the tips in this article but they may not work. You haven’t been hacked and you don’t have a virus. + PSComputerName : ps. you get a notification that you have a “Microsoft account problem,” you don’t have a problem and you don’t have to fix anything. + CategoryInfo : OperationStopped: (ps.:String), PSRemotingTransportException Starting a command on the remote server failed with the following error message : The I/O operation has been aborted because of either a thread exit or an applicationįor more information, see the about_Remote_Troubleshooting Help topic. Again, if I log in, everything resumes for 2 more minutes. Oh, and the error I get when the logon prompt comes up is below.
If you have any options, it would be much appreciated. Both methods seemed to work the same way for me. I've also tried using an Export-PSSession instead of Import-PSSession, but that didn't seem to make any difference. Import-PSSession $Session -CommandName Get-RetentionCompliancePolicy, Set-RetentionCompliancePolicy, New-RetentionCompliancePolicy, New-RetentionComplianceRule, Get-RetentionComplianceRule | Out-Null Credential $UserCredential -Authentication Basic -AllowRedirection $SessionOptions = New-PSSessionOption -IdleTimeout 600000 -NoCompression: $True I'm also only importing theĬommands I need to use in the Import-Session line. The $UserCredential variable contains my admin account/password. I added the IdleTimeout and NoCompression options to try and fix my issues, but it has not helped.
To be specific, the Session I'm creating and using is below. Want to do so I'm looking for a solution. Babysitting this script for all 20,000 accounts is not something I If I was running a small job, this wouldn't be that big of a deal, but I am trying to process requests against about 20,000 accounts and I can only do about 30-40 in the 2 minute window. During that 2 minute window, it seems I can run the variousĬommands as much as the script can get through, but after those 2 minutes, I am prompted. If I enter my credentials, the script will continue fine, but again after about 2 minutes, I will get prompted again. I can connect just fine and run the commands I need without much issue, however, after aboutĢ minutes of processing, the session suddenly pops up a credential dialog box. The issue is when running Exchange/SharePoint related commands. I am running into an issue when running a PowerShell script against our Office 365 environment.
0 kommentar(er)
