<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>How to deploy Microsoft Dynamics CRM Client through SMS</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx</link><description>This document explains the techniques that I have been using to deploy Microsoft Dynamics CRM Client through SMS. It is a series of steps that worked for us, and not necessarily is the best and for sure is not the only way to do this. For those already</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title> &amp;raquo; How to deploy Microsoft Dynamics CRM Client through SMS Microsoft CRM Development Information: Information and Research on Microsoft CRM Development</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx#7850805</link><pubDate>Fri, 22 Feb 2008 23:34:36 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7850805</guid><dc:creator> » How to deploy Microsoft Dynamics CRM Client through SMS Microsoft CRM Development Information: Information and Research on Microsoft CRM Development</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://crm.discoveryjournal.info/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms/"&gt;http://crm.discoveryjournal.info/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>re: How to deploy Microsoft Dynamics CRM Client through SMS</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx#8970522</link><pubDate>Tue, 30 Sep 2008 20:37:49 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8970522</guid><dc:creator>Troy Fugnitti</dc:creator><description>&lt;p&gt;is there a way to do this install without SMS?&lt;/p&gt;</description></item><item><title>re: How to deploy Microsoft Dynamics CRM Client through SMS</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx#9287109</link><pubDate>Wed, 07 Jan 2009 12:44:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9287109</guid><dc:creator>Jesper Jensen</dc:creator><description>&lt;p&gt;What about automatic configuration with xml file. Any idea how to do that with sccm?&lt;/p&gt;</description></item><item><title>re: How to deploy Microsoft Dynamics CRM Client through SMS</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx#9456152</link><pubDate>Tue, 03 Mar 2009 11:00:07 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9456152</guid><dc:creator>Daniel</dc:creator><description>&lt;p&gt;Well, what kind of components is needed that cant be installed whit the /q in (offline) It is a big risk to let the users self to go trough the installation guide, we are goping to upgrade from 3.0 to 4.0 and we have ALOT of laptop users so What to do???????&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;
&lt;p&gt;Daniel &amp;nbsp;&lt;/p&gt;</description></item><item><title>re: How to deploy Microsoft Dynamics CRM Client through SMS</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx#9472965</link><pubDate>Fri, 13 Mar 2009 13:40:48 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9472965</guid><dc:creator>Steph</dc:creator><description>&lt;p&gt;Was hoping to use this, but whilst CRM client is installed seemingly ok on the workstation, the SMS Software Dist throws a -2 exit code, so it's never reported as having succeeded. Because we want to chain the Rollup2 install directly afterwards, the fact that it doesn't cleanly succeed means that any other chained programs within the package also fail.&lt;/p&gt;
&lt;p&gt;Can we use client.msi instead of setupclient.exe with any particular switches when doing an SMS distribution? Using client.msi fails when manually running (it says you should use setupclient.exe instead) and was presuming it might do the same within SMS?&lt;/p&gt;
&lt;p&gt;Anyone?&lt;/p&gt;</description></item><item><title>re: How to deploy Microsoft Dynamics CRM Client through SMS</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx#9501584</link><pubDate>Mon, 23 Mar 2009 18:35:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9501584</guid><dc:creator>LucidioK</dc:creator><description>&lt;p&gt;Regarding:&lt;/p&gt;
&lt;p&gt;&amp;quot;what kind of components is needed that cant be installed whit the /q in (offline)&amp;quot;&lt;/p&gt;
&lt;p&gt;The component is SQL Express. SQL Express does not install silently.&lt;/p&gt;
&lt;p&gt;I believe that if you install SQL Express beforehand, you could install Offline client.&lt;/p&gt;
&lt;p&gt;Luci&lt;/p&gt;</description></item><item><title>re: How to deploy Microsoft Dynamics CRM Client through SMS</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx#9501637</link><pubDate>Mon, 23 Mar 2009 18:54:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9501637</guid><dc:creator>LucidioK</dc:creator><description>&lt;p&gt;Regarding&lt;/p&gt;
&lt;p&gt;&amp;quot;Can we use client.msi instead of setupclient.exe &amp;quot;&lt;/p&gt;
&lt;p&gt;Unfortunately MSI does not have all the needed functionality for client install. For instance, there are dependencies such as SQL Express that need to be tackled and MSI does not help. That's the reason for setupclient.exe.&lt;/p&gt;
&lt;p&gt;When I had this specific problem it was because some of the parameters were not as described here (especially item 4.10 Program Properties page).&lt;/p&gt;
&lt;p&gt;So I would try this:&lt;/p&gt;
&lt;p&gt;1. Review all entries in the configuration.&lt;/p&gt;
&lt;p&gt;2. In some cases, SMS informs that the package did not install properly at the server, but it went fine at the client. That's why the VBS code is being provided here, so the real issues can be separated from the flukes. Is it possible to separate the client and the Rollup2 in 2 packages? First install client for everyone, then install Rollup2?&lt;/p&gt;
&lt;p&gt;3. If that's not solving or you don't feel comfortable with these suggestions, contact CRM support.&lt;/p&gt;
&lt;p&gt;Thanks for your attention,&lt;/p&gt;
&lt;p&gt;Luci&lt;/p&gt;</description></item><item><title>re: How to deploy Microsoft Dynamics CRM Client through SMS</title><link>http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx#9826569</link><pubDate>Thu, 09 Jul 2009 15:27:17 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9826569</guid><dc:creator>Simon</dc:creator><description>&lt;p&gt;From Steph:&lt;/p&gt;
&lt;p&gt;&amp;quot;Was hoping to use this, but whilst CRM client is installed seemingly ok on the workstation, the SMS Software Dist throws a -2 exit code, so it's never reported as having succeeded&amp;quot;&lt;/p&gt;
&lt;p&gt;Any answer? I'm getting this and it's driving me mad.&lt;/p&gt;</description></item></channel></rss>