<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Security permission was insufficient to update your device error on Motorola Q Devices</title><link>http://blogs.technet.com/sbs/archive/2006/07/24/443178.aspx</link><description>[Today's tip comes to us courtesy of James Frederickson] So you got a new Motorola Q phone from Verizon Wireless and you are trying to install a Certificate and you are getting the following error: Security permission was insufficient to update your device</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Security permission was insufficient to update your device error on Motorola Q Devices</title><link>http://blogs.technet.com/sbs/archive/2006/07/24/443178.aspx#443257</link><pubDate>Tue, 25 Jul 2006 10:15:37 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:443257</guid><dc:creator>Nico</dc:creator><description>Indeed, this works fine. I've been looking for a solution to these troubles for a while, funny enough, there's no other article on the net yet that tells you you need the certificate in place. I just figured it out myselve a few days ago.&lt;br&gt;&lt;br&gt;Some things i'lld like to add:&lt;br&gt;- If your server isued an certificate to itsself (so not through a third party certificate manager), you should export the root certificate. In some occasions i noticed that IIS uses a sub-certificate, so make realy sure you got the root certificate or it wont work!.&lt;br&gt;- To export the root certificate, open 'Certification Authority' (under administrative tools, or add the snapin into a new mmc) on your server. Right click on the root certificate and choose 'properties'. On the genral tab, you can see the root certificate, just select it and click on 'view certificate'.&lt;br&gt;In the newly opend window you can double check you selected the root certificate if you take a look at the 3 tab. Now that you are sure, go back to the second tab, and click on 'copy to file'. the wizard for exporting the certificate will open. Click Next. Select 'der encoded binary x.509 (.CER)' and click next. enter a filename where you want the store the certificate in., click next and click finish.&lt;br&gt;&lt;br&gt;Testing the exported file (to make sure you wont have isues with it). Take any pc that hasnt got the certificate installed yet. (to verify you can open owa through https, if you get prompted to accept the certificate, its not installed yet) &lt;br&gt;Ok, now to verify you successfuly exported the certificate, you can double click on it. to install the certificate on the local machine, click 'install certificate'. In the wizzard click next. Select 'Place all certificates in the following store'. Click 'browse'. Select 'show physical stores'. Under 'trusted root certificate autothorities' select 'local computer' (this way you install it in the right place). click 'ok', click 'next', click 'finish'. A popup will apear stating that the import worked (hopefully ;) )&lt;br&gt;&lt;br&gt;Now, to make sure the certificate worked, close the browser, and reopen it (to be sure). Surf to the https site of your OWA. Now IE wont prompt you to accept the certificate. If IE still prompts you, you exported the wrong certificate.&lt;br&gt;&lt;br&gt;- Another thigh i'lld like to suggest, is not to select the 'require secure channel (SSL)' option in IIS manager under 'default web site', properties on 'exchange', directory security tab, 'secure communications', 'edit'. Why, internaly IIS communicates throughout its virtual folders. that's done using http, and not https. so if you enable that option, loads off other stuff might fail to work. (like RPC over HTTPS fi)&lt;br&gt;&lt;br&gt;Also, exporting and importing the certificate &amp;nbsp;is something you'll need to do aswell if you want to use RPC over HTTPS.&lt;br&gt;&lt;br&gt;Hope this helped anyone trying to figure out why it doesn't work.</description></item><item><title>re: Security permission was insufficient to update your device error on Motorola Q Devices</title><link>http://blogs.technet.com/sbs/archive/2006/07/24/443178.aspx#443389</link><pubDate>Wed, 26 Jul 2006 00:34:20 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:443389</guid><dc:creator>markstan</dc:creator><description>Nico,&lt;br&gt;&lt;br&gt;Excellent points, all. &amp;nbsp;Thank you so much for taking the time to post this!&lt;br&gt;&lt;br&gt;---Mark</description></item><item><title>re: Security permission was insufficient to update your device error on Motorola Q Devices</title><link>http://blogs.technet.com/sbs/archive/2006/07/24/443178.aspx#443445</link><pubDate>Wed, 26 Jul 2006 10:10:43 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:443445</guid><dc:creator>Nico</dc:creator><description>My pleasure. After reading it all over I see I made quite alot of typo's. English aint my native language, but i should have done better.&lt;br&gt;&lt;br&gt;You dont have to allow this to be posted publicaly though.&lt;br&gt;&lt;br&gt;Maybe I can send you some articles by mail sometime. So, if you would like to post it, you could fix the typo's for me. TBH, i cant be arsed to start my own blog. I aint got that much time on my hands.&lt;br&gt;&lt;br&gt;Drop me an e-mail if you are interested: Nico@noid.Be&lt;br&gt;&lt;br&gt;Again, please just delete this post ;)&lt;br&gt;&lt;br&gt;Nico.</description></item><item><title>re: Security permission was insufficient to update your device error on Motorola Q Devices</title><link>http://blogs.technet.com/sbs/archive/2006/07/24/443178.aspx#444433</link><pubDate>Wed, 02 Aug 2006 01:53:46 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:444433</guid><dc:creator>Steve Downs</dc:creator><description>There is an alternate method to install the self signed SBS certificate. Take a look at this article - &lt;a rel="nofollow" target="_new" href="http://www.stevereno.net/weblog/sbs/index.php?/sbs/verizons_motorola_q_smartphone_installing_sbs_self_signed_certificate/"&gt;http://www.stevereno.net/weblog/sbs/index.php?/sbs/verizons_motorola_q_smartphone_installing_sbs_self_signed_certificate/&lt;/a&gt;</description></item><item><title>Motorola Q ActiveSync problems | keyongtech</title><link>http://blogs.technet.com/sbs/archive/2006/07/24/443178.aspx#3185333</link><pubDate>Sun, 18 Jan 2009 19:52:29 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3185333</guid><dc:creator>Motorola Q ActiveSync problems | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/4215002-motorola-q-activesync-problems"&gt;http://www.keyongtech.com/4215002-motorola-q-activesync-problems&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>Certifcate reset error - cannot get to OWA - Page 2 | keyongtech</title><link>http://blogs.technet.com/sbs/archive/2006/07/24/443178.aspx#3210725</link><pubDate>Mon, 09 Mar 2009 14:07:12 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3210725</guid><dc:creator>Certifcate reset error - cannot get to OWA - Page 2 | keyongtech</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://www.keyongtech.com/5016618-certifcate-reset-error-cannot-get/2"&gt;http://www.keyongtech.com/5016618-certifcate-reset-error-cannot-get/2&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>