Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1467
  • Last Modified:

CRM 4 Client for Outlook install with GP

I'm trying to push the new client to all computers in my org. We have an internal only w/AD enviroment for the CRM

1. What is the best way to automatically unistall the CRMv3 client form everyones system?
2. When installing the CRM 4 Outllook client, I've doctored the config.xlm file used by an administative install as follows.
3 Is the  <Organization>Management</Organization> name the name of the organization on the CRM? or our domain ?
4.0 What are the correct switches to use for a silent non user interface/non user input install that will just run the first time the computer is logged on to the domain after the GP goes out
5. I do not see a place to specify the CRM server address in the XLM


<?xml version="1.0" encoding="utf-8"?>
<CRMConfiguration>
  <Client>

    <ServerUrl Type="OnPremise" ShowUser="False" />
    <!--      
    Specifies the details to connect to Microsoft Dynamics CRM.
     Type - Determines the type of deployment:
      - "OnPremise" - For users on Microsoft Dynamics CRM with Active Directory authentication.
      - "Live" - For users on Microsoft Dynamics Live CRM.
      - "SPLA" - For users on Microsoft Dynamics CRM through a hosting partner.
         
     ShowUser - Determines whether the "Connect to Microsoft Dynamics CRM" screens are displayed to the user.
        - "True" - Will show this screen (default).
      - "False" - Will not show this screen.  
       
     Specifying a URL is optional when the deployment type is Live. For OnPremise and SPLA, this should be the path to the Discovery Service.
    -->

    <!--
    <ExtranetServerUrl>http://PathToExternalDiscoveryService</ExtranetServerUrl>
    For OnPremise deployments that are configured to be Internet-facing, the ExtranetServerUrl should point to the External Discovery Service.
    -->

     
    <Organization>management</Organization>
    <!--
    Specifies the unique name of the organization.
    -->

    <!--
    <CEIP option="True|False" />
    Specifies whether you allow Microsoft to collect anonymous data from your deployment to help improve future versions of the software.
    -->

    <!--
    <Database Reuseexisting="True | False"/>
    For users of Microsoft Dynamics CRM for Outlook with Offline Access, this flag specifies whether you want to reuse a previously attached database.
    -->
   
   
  </Client>
</CRMConfiguration>
0
ChrisDD
Asked:
ChrisDD
1 Solution
 
WilyGuyCommented:
Lots of questions.

First, there is a distinct difference between the OFFLINE and ONLINE versions of both, so I am going to assume ONLINE/DESKTOP or whatever you want to call that one :)

IN the CRM 3.0 IG, (http://www.microsoft.com/downloads/details.aspx?familyid=1ff067f8-4f77-40f0-ae9c-68ada7d4f16a&displaylang=en) there is a similar GP push as the one you are likely working on in the CRM 4.0 IG.(http://www.microsoft.com/downloads/details.aspx?familyid=1CEB5E01-DE9F-48C0-8CE2-51633EBF4714&displaylang=en)  One of the flags on that is going to be /X for Uninstall.  I would push that command out first.

The 4.0 Installation requires 2 parts, (and both are documented in chapter 7 of the Installation document in the 4.0 IG)  You have the install and then the configuration.

The Install is going to be first (and you will want to make sure you meet pre-reqs first) and should be done with an administrative install package that you will create using a /A and /Q (for quiet).  Then you'll push that out.  I highly recommend altering the Default_Client_Config.xml in your package to fit your needs.  You likely need the OnPremise, the ShowUser=False that you see in your example above.  In that sample config, there is a HTTP://MSCRM at the end of that same line that you will edit for your server url (this is the discovery URL) make sure if you are on a non-default port that you add the port.

The Organization is your CRM organization UniqueName (the one with no spaces and it is cAsE sEnSiTiVe)

Following the install you are going to use Step 2 (also in ch 7) to run a command that will apply that config file.  You can continue to leave that one out there as if the client is already configured, it will essentially ignore that command.

Hope that helps.  Off on Vacation for a day or two.  Be back Monday.

0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now