CRM 4 client and 'bug' for use in SMS Server/SCCM distribution?

• General discussion

• 

  

  0

  Sign in to vote

  
  I've been playing with this for days, originally using the steps as described here:
  
  http://blogs.msdn.com/crm/archive/2008/02/22/how-to-deploy-microsoft-dynamics-crm-client-through-sms.aspx
  
  Everytime it runs, whilst it appears to install the CRM client correctly to the workstation, it always returns a failure exit code of -2, which means that not only do we not get an accurate return of whether the SMS distribution of the client has worked cleanly or not, but it also fails to run daisy chained distributions too.
  
  I stumbled upon these two posts through google which describe the problem:
  
  http://www.bibble-it.com/2008/07/22/installing-crm-40-with-sccm
  
  http://social.microsoft.com/Forums/en-US/crmdeployment/thread/19f5eb90-0851-4b75-93f8-76d39e17a931
  
  So they suggest that Microsoft's set-up handler 'setupclient.exe' has a 'bug' which means that it doesn't properly complete and exit cleanly enough. To further complicate matters, it appears that you cannot use 'client.msi' directly either!
  
  Whilst the above articles have a workaround of sorts (which is rather cludgy based on using a wrap-around script with loops), I find it staggering that a reasonably new MS client installer should have this sort of problem?
  
  So, is anyone aware of a better solution to this?
  
  Are Microsoft/Dynamics actively addressing the 'bug' in the installer does anyone know?
  
  Thanks in advance,
  Steph
  

  Friday, March 13, 2009 11:18 AM