<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Rpc on Anything About IT</title><link>https://www.verboon.info/tags/rpc/</link><description>Recent content in Rpc on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Wed, 29 Oct 2014 17:03:43 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/rpc/index.xml" rel="self" type="application/rss+xml"/><item><title>How to solve &amp;ldquo;The RPC server is unavailable&amp;rdquo; when loading the ConfigMgr PowerShell Module</title><link>https://www.verboon.info/2014/10/how-to-solve-the-rpc-server-is-unavailable-when-loading-the-configmgr-powershell-module/</link><pubDate>Wed, 29 Oct 2014 17:03:43 +0000</pubDate><guid>https://www.verboon.info/2014/10/how-to-solve-the-rpc-server-is-unavailable-when-loading-the-configmgr-powershell-module/</guid><description>&lt;p&gt;Since a few weeks, I received the below error message when importing the ConfigMgr module in PowerShell, but everything I ran afterwards worked fine, so I kept ignoring it for a while. &lt;a href="images/image4.png"&gt;

 &lt;img src="images/image_thumb4.png" alt="image"&gt;


&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;But now it was about time to get rid of this annoying message. My friend Claude Henchoz gave me a hint a while ago that helped me solve the issue. Looking at the error message more closely, I noticed the name of our old meanwhile decommissioned POC environment for ConfigMgr 2012 R2.&lt;/p&gt;</description></item></channel></rss>