{"id":70,"date":"2012-05-27T08:37:00","date_gmt":"2012-05-27T08:37:00","guid":{"rendered":"\/post\/2012\/05\/27\/Exchange-Powershell-Max-Quota-exceeded-.aspx"},"modified":"2012-05-27T08:37:00","modified_gmt":"2012-05-27T08:37:00","slug":"exchange-powershell-max-quota-exceeded","status":"publish","type":"post","link":"https:\/\/www.vatland.no\/index.php\/exchange-powershell-max-quota-exceeded\/","title":{"rendered":"Exchange Powershell Max Quota exceeded."},"content":{"rendered":"<p>When doing some exchange powershell you would probably get this error or somthing like it sooner or later:<\/p>\n<p>Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. This user is allowed a max<br \/>imum number of 18 concurrent shells, which has been exceeded. Close existing shells or raise the quota for this user. For more information, see the about_Remote_Trouble<br \/>shooting Help topic.<br \/>&nbsp;&nbsp;&nbsp; + CategoryInfo&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; : OpenError: (System.Manageme&#8230;.RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException<br \/>&nbsp;&nbsp;&nbsp; + FullyQualifiedErrorId : PSSessionOpenFailed<\/p>\n<p>Workaround&nbsp;for this is to recycle the MSExchangePowerShellAppPool Application Pool<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When doing some exchange powershell you would probably get this error or somthing like it sooner or later: Connecting to remote server failed with the following error message : The WS-Management service cannot process the request. This user is allowed a maximum number of 18 concurrent shells, which has been exceeded. Close existing shells or &hellip; <a href=\"https:\/\/www.vatland.no\/index.php\/exchange-powershell-max-quota-exceeded\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Exchange Powershell Max Quota exceeded.<\/span> <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false},"categories":[5],"tags":[],"class_list":["post-70","post","type-post","status-publish","format-standard","hentry","category-exchange"],"aioseo_notices":[],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"jetpack_likes_enabled":false,"jetpack-related-posts":[{"id":84,"url":"https:\/\/www.vatland.no\/index.php\/error-1603-installing-exchange-2010-rollups\/","url_meta":{"origin":70,"position":0},"title":"Error 1603 installing Exchange 2010 RollUp&#8217;s","author":"Atle","date":"October 7, 2011","format":false,"excerpt":"Getting error installing Rollup 5 for Exchange 2010 Sp1. Error 1603. According to msi log file it is ServiceControl.ps1 that is causing the error. Solution was to set execution policy to RemoteSigned and also run the \"ServiceControl.ps1 AfterPatch\" script from the Exchange 2010 Bin folder\u00a0. Also remember to start Powershell\u2026","rel":"","context":"In &quot;Exchange&quot;","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":96,"url":"https:\/\/www.vatland.no\/index.php\/smtp-unreliable-links\/","url_meta":{"origin":70,"position":1},"title":"SMTP unreliable links","author":"Atle","date":"July 30, 2011","format":false,"excerpt":"Had a problem with large emails between exchange 2010 servers. Got the smtp error 421.4.4.2 . I solved this by increasing the MaxProtocolError and ConnectionTimeout on the receiving connector. Use the powershell set-receiveconnector . In this senario we are talking about a 1mb sat link.","rel":"","context":"In &quot;Exchange&quot;","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":553,"url":"https:\/\/www.vatland.no\/index.php\/imap-disabled-in-exchange-2013-servercomponentstate\/","url_meta":{"origin":70,"position":2},"title":"IMAP disabled in Exchange 2013 ServerComponentState.","author":"Atle","date":"September 15, 2015","format":false,"excerpt":"IMAP\u00a0was enabled on the Exchange\u00a0\u00a0server and had been used for a long time. One\u00a0day the Exchange\u00a0server's IP subnet\u00a0was placed in a Active Directory site without any Domain Controllers. Of course\u00a0 Exchange the services stopped\u00a0running after a while. When We managed to get it back to its original site and rebooted,\u2026","rel":"","context":"In &quot;Exchange&quot;","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"imaptest","src":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2015\/09\/imaptest.png?resize=350%2C200","width":350,"height":200,"srcset":"https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2015\/09\/imaptest.png?resize=350%2C200 1x, https:\/\/i0.wp.com\/www.vatland.no\/wp-content\/uploads\/2015\/09\/imaptest.png?resize=525%2C300 1.5x"},"classes":[]},{"id":765,"url":"https:\/\/www.vatland.no\/index.php\/list-exchange-mailboxes-with-forwarding-rules\/","url_meta":{"origin":70,"position":3},"title":"List Exchange mailboxes with forwarding rules","author":"Atle","date":"May 4, 2018","format":false,"excerpt":"Simple list of all mailboxes and rules. Displays more info if one of them contains a forwarding rule:","rel":"","context":"In &quot;Exchange&quot;","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":85,"url":"https:\/\/www.vatland.no\/index.php\/test-network-with-filecopy-and-powershell\/","url_meta":{"origin":70,"position":4},"title":"Test network with filecopy and Powershell","author":"Atle","date":"September 26, 2011","format":false,"excerpt":"Needed a way to test and time filecopy between servers using powershell. This is what I came up with. This example will use copy testfile.zip to server and time the progress. I used a file of 1.8 Gb. $servers=\"server1\",\"server2\",\"server3\",\"server4\",\"server5\",\"server6\"foreach($server in $Servers){if (!(test-path \\\\$server\\share\\temp)) {\u00a0\u00a0\u00a0 new-item -path \\\\$server\\share -name temp -ItemType\u2026","rel":"","context":"In &quot;Exchange&quot;","block_context":{"text":"Exchange","link":"https:\/\/www.vatland.no\/index.php\/category\/exchange\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":21,"url":"https:\/\/www.vatland.no\/index.php\/list-members-of-dynamic-groups-show-incorrect-members\/","url_meta":{"origin":70,"position":5},"title":"List members of dynamic groups show incorrect members.","author":"Atle","date":"January 23, 2014","format":false,"excerpt":"If you use PowerShell to list members of dynamic distribution Groups in Exchange 2013 you would probably see more entries than expected. The PowerShell commands $dgr=Get-DynamicDistributionGroup \"GroupNAme\"Get-Recipient -RecipientPreviewFilter $dgr.RecipientFilterdoes not take in to consideration OU filtering. If you look at $dgr.RecipientFiler it only contains the other attributes.I do not know\u2026","rel":"","context":"In &quot;Categories&quot;","block_context":{"text":"Categories","link":"https:\/\/www.vatland.no\/index.php\/category\/categories\/"},"img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/70","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/comments?post=70"}],"version-history":[{"count":0,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/posts\/70\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/media?parent=70"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/categories?post=70"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vatland.no\/index.php\/wp-json\/wp\/v2\/tags?post=70"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}