I did some digging around for this one and found a few crafty articles about adjusting throttling policies using PowerShell and making changes through ADSIEdit (http://reidablog.blogspot.com/). However, none of these seemed to fix my issue.
We had a newly built Exchange 2010 SP1 server which was ready to go into production but kept throwing the error when attempting to use PowerShell. Two other servers appeared to be running fine.
The server had recently received a new SSL certificate using the Exchange 2010 certificate provisioning and assignment process in the GUI. Unfortunately the IIS service hadn't been restarted yet and the URL used for remote PowerShell was using a certificate which wasn't trusted or valid anymore.
A quick "IISRESET" on the server resulted in my fix.
Cheers!
Monday, January 17, 2011
Subscribe to:
Post Comments (Atom)
Thank you, that helped me alot to quickly fix my problem. Certificates are not really the first thing I would have thinked about.
ReplyDeleteErich
It helped me spot on. I was wondering what to do and no other site gave me this quick fix.
ReplyDeleteExcellent! Thank you, that did the trick! :)
ReplyDeleteCool Beans! Fixed it for me too. Thanks.
ReplyDeleteOh wow, that worked like a charm. I am surprised it was something that easy. Thank you!
ReplyDeleteSweet! That command did the trick indeed! =)
ReplyDeleteMan you're the greatest, my woes ended in seconds - stay sharp
ReplyDeleteFixed our issues as well, and enabled us to get our TSM backups running again.
ReplyDeleteSuperb, no warning in the management tool when you change the certificate, Boo to microsoft yea to Jason Shave
ReplyDeleteWorked like a charm!!!!!! Awesome post dude!
ReplyDeleteSolved. Thanks a lot!
ReplyDeletePerfect. IISRESET, who would have believed it?
ReplyDeleteThat helped, thanks!
ReplyDeleteWorked perfectly, thank you!
ReplyDeleteWorked!! Thanks.
ReplyDeleteYou are a scholar and a gentlemen. That worked perfectly. Thanks.
ReplyDeleteSweet! That worked right away. Thanks!
ReplyDeleteWorked great here! Thanks
ReplyDeleteA scholar and a gentleman indeed! Many thanks.
ReplyDeleteThanks! Worked great.
ReplyDeleteYep, that worked for me too. Thanks!
ReplyDeleteDang...I'm seeing it on my HT servers. When do IISReset \noforce, I get
ReplyDeleteC:\Windows\system32>iisreset \noforce
The RPC server is unavailable.
C:\Windows\system32>
Thanks!
ReplyDeleteAwesome.
ReplyDeleteAnother happy camper! It worked.
ReplyDeleteThank you for posting this!
Word
ReplyDeleteWorked!! Thanks.
ReplyDelete