locked
Installing CRM30 Outlook Client RRS feed

  • Question

  •  

    To install the Outlook client for CRM 3.0 I have to make the user who will be using the client a member of the computers local admins group then logon as that user.

     

    I can then install the CRM 3.0 client.

     

    I then have to logoff, and logon as another user with admin rights and remove the CRM user from the local admins group.

     

    Is this the way CRM 3.0 Outlook client was designed to be installed?  Is there no way to install CRM 3.0 outlook client using my normal domain admin credentials and then enabeling the COM addin in outlook for the CRM user under thier profile?

     

     

    Wednesday, January 23, 2008 1:51 AM

Answers

  • Can we tie up and test it on coming sunday?

     

    Thursday, January 24, 2008 3:07 PM

All replies

  • As far as I know (from experience) the way you are doing it is correct and the way it was designed.

     

    When CRM is installed more than the addin gets created, also a local .pst file for the user and probably other stuff too.

     

    So, if you want the desktop client available for more than one user on a PC it has to be installed for each user.

     

    I don't know if the Outlook client for CRM 4 behaves differently in this respect.

    Wednesday, January 23, 2008 7:19 AM
    Moderator
  • Hi,

     

    You can do this all by one time effort using administrative image of CRM OUTLOOK CLIENT and Active Directory Group policy to publish a install folder. In this way setup for CRM Outlook client will appear in control panel "add remove programs". In this way installer won't have to have any administrative roles on the machine.

     

    To make the administrative image of CRM OUTLOOK CLIENT do following:

    Create an Administrative Install Location

    Create an Administrative Install Location
    ------------------------------------------
    You can create an administrative installation location (typically a shared server folder) and then allow clients to connect to the share to install the Microsoft CRM clients for Outlook. Advantages of installing the Microsoft CRM clients for Outlook include:
    ● Users who are valid Microsoft CRM users can install the Microsoft CRM clients for Outlook without local administrative privileges. (This method requires that the Microsoft Data Access Components (MDAC) 2.8 be installed on the client computer prior to installing the Microsoft CRM clients for Outlook.)
    ● A user with local administrative privileges on each client computer does not have to do the Microsoft CRM client for Outlook installation.
    ● You do not need to share or duplicate the Microsoft CRM Client CD.
    ● The Microsoft CRM clients for Outlook are installed with pre-defined settings.

    This method requires two separate procedures:
    ● Create a Microsoft CRM client for Outlook installation image on a shared resource.
    ● Publish the image so that users can access and install from the shared resource.

    ► Install Microsoft CRM client for Outlook in Administrative Mode
    1. Meet all requirements in the previous "Prerequisite Checklist" section.
    2. Logon to the computer as a user with local administrative privileges.
    3. Map a drive to the network location where you want to create an image of the Microsoft CRM Sales for Outlook CD. (This location can be entered as \\networkshare during setup of the Microsoft CRM Client for Outlook.)
    4. Insert the Microsoft CRM Client for Outlook CD in your CD-ROM Drive
    5. Open a command prompt window and navigate to the root folder on the Microsoft CRM Client for Outlook CD.
    6. Type one or both of the following commands. Make sure you use a separate target shared folder for each client image:
    msiexec /a client.msi Create an installation source image of the Microsoft CRM laptop Client for Outlook.
    msiexec /a LightClient.msi Create an installation source image of the Microsoft CRM desktop Client for Outlook.
    7. Point to the mapped drive or provide the network share where you want to create the administrative image.
    8. Enter a valid Microsoft CRM server name.
    9. Complete the Wizard.
    10. Share the image location. If this is on a server, then share the folder containing the installation images.

     

    http://solutiontalk.blogspot.com/2008/01/create-administrative-install-location.html

    How to use Group Policy to remotely install software in Windows Server 2003

    How to use Group Policy to remotely install software in Windows Server 2003
    -----------------------------------------------------------------------------------------------------------------------


    This step-by-step article describes how to use Group Policy to automatically distribute programs to client computers or users. You can use Group Policy to distribute computer programs by using the following methods:

    Assigning SoftwareYou can assign a program distribution to users or computers. If you assign the program to a user, it is installed when the user logs on to the computer. When the user first runs the program, the installation is finalized. If you assign the program to a computer, it is installed when the computer starts, and it is available to all users who log on to the computer. When a user first runs the program, the installation is finalized.

    Publishing SoftwareYou can publish a program distribution to users. When the user logs on to the computer, the published program is displayed in the Add or Remove Programs dialog box, and it can be installed from there. Note Windows Server 2003 Group Policy automated-program installation requires client computers that are running Microsoft Windows 2000 or later.


    Create a Distribution Point
    -------------------------------------------------------
    To publish or assign a computer program, you must create a distribution point on the publishing server:
    1.
    Log on to the server computer as an administrator.
    2.
    Create a shared network folder where you will put the Microsoft Windows Installer package (.msi file) that you want to distribute.
    3.
    Set permissions on the share to allow access to the distribution package.
    4.
    Copy or install the package to the distribution point. For example, to distribute Microsoft Office XP, run the administrative installation (setup.exe /a) to copy the files to the distribution point.


    Create a Group Policy Object
    -------------------------------------------------------
    To create a Group Policy object (GPO) to use to distribute the software package:
    1.
    Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
    2.
    In the console tree, right-click your domain, and then click Properties.
    3.
    Click the Group Policy tab, and then click New.
    4.
    Type a name for this new policy (for example, Office XP distribution), and then press ENTER.
    5.
    Click Properties, and then click the Security tab.
    6.
    Click to clear the Apply Group Policy check box for the security groups that you want to prevent from having this policy applied.
    7.
    Click to select the Apply Group Policy check box for the groups that you want this policy to apply to.
    8.
    When you are finished, click OK.


    Assign a Package
    -------------------------------------------------------
    To assign a program to computers that are running Windows Server 2003, Windows 2000, or Microsoft Windows XP Professional, or to users who are logging on to one of these workstations:
    1.
    Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
    2.
    In the console tree, right-click your domain, and then click Properties.
    3.
    Click the Group Policy tab, select the group policy object that you want, and then click Edit.
    4.
    Under Computer Configuration, expand Software Settings.
    5.
    Right-click Software installation, point to New, and then click Package.
    6.
    In the Open dialog box, type the full Universal Naming Convention (UNC) path of the shared installer package that you want. For example, \\file server\share\file name.msi.Important Do not use the Browse button to access the location. Make sure that you use the UNC path to the shared installer package.
    7.
    Click Open.
    8.
    Click Assigned, and then click OK. The package is listed in the right pane of the Group Policy window.
    9.
    Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.
    10.
    When the client computer starts, the managed software package is automatically installed.

    Publish a Package
    -------------------------------------------------------
    To publish a package to computer users and make it available for installation from the Add or Remove Programs tool in Control Panel:
    1.
    Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
    2.
    In the console tree, right-click your domain, and then click Properties.
    3.
    Click the Group Policy tab, click the group policy object that you want, and then click Edit.
    4.
    Under User Configuration, expand Software Settings.
    5.
    Right-click Software installation, point to New, and then click Package.
    6.
    In the Open dialog box, type the full UNC path of the shared installer package that you want. For example, \\file server\share\file name.msi. Important Do not use the Browse button to access the location. Make sure that you use the UNC path to the shared installer package.
    7.
    Click Open.
    8.
    Click Publish, and then click OK.
    9.
    The package is listed in the right pane of the Group Policy window.
    10.
    Close the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.
    11.
    Test the package:Note Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.
    a.
    Log on to a workstation that is running Windows 2000 Professional or Windows XP Professional by using an account that you published the package to.
    b.
    In Windows XP, click Start, and then click Control Panel.
    c.
    Double-click Add or Remove Programs, and then click Add New Programs.
    d.
    In the Add programs from your network list, click the program that you published, and then click Add. The program is installed.
    e.
    Click OK, and then click Close.


    Redeploy a Package
    -------------------------------------------------------

    In some cases you may want to redeploy a software package. For example, if you upgrade or modify the package. To redeploy a package:
    1.
    Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
    2.
    In the console tree, right-click your domain, and then click Properties.
    3.
    Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and then click Edit.
    4.
    Expand the Software Settings container that contains the software installation item that you used to deploy the package.
    5.
    Click the software installation container that contains the package.
    6.
    In the right pane of the Group Policy window, right-click the program, point to All Tasks, and then click Redeploy application. You will receive the following message:
    Redeploying this application will reinstall the application everywhere it is already installed. Do you want to continue?
    7.
    Click Yes.
    8.
    Quit the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.


    Remove a Package
    -------------------------------------------------------

    To remove a published or assigned package:
    1.
    Start the Active Directory Users and Computers snap-in. To do this, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
    2.
    In the console tree, right-click your domain, and then click Properties.
    3.
    Click the Group Policy tab, click the Group Policy object that you used to deploy the package, and then click Edit.
    4.
    Expand the Software Settings container that contains the software installation item that you used to deploy the package.
    5.
    Click the software installation container that contains the package.
    6.
    In the right pane of the Group Policy window, right-click the program, point to All Tasks, and then click Remove.
    7.
    Do one of the following:

    Click Immediately uninstall the software from users and computers, and then click OK.

    Click Allow users to continue to use the software but prevent new installations, and then click OK.
    8.
    Quit the Group Policy snap-in, click OK, and then quit the Active Directory Users and Computers snap-in.


    Troubleshoot
    -------------------------------------------------------

    Published Packages Are Displayed on a Client Computer After You Use a Group Policy to Remove Them

    This situation can occur when a user has installed the program but has not used it. When the user first starts the published program, the installation is finalized. Group Policy then removes the program.

    http://solutiontalk.blogspot.com/2008/01/how-to-use-group-policy-to-remotely.html
    http://support.microsoft.com/kb/816102
     
    Inform me if you get stuck somewhere.
    Thursday, January 24, 2008 7:39 AM
  •  

    Hi,

     

    I have tried your method using the GPO to publish it to users. It works great !

    Only one question: Using this option the user still has to confirm the options and select install for the SQL Express / .NET framework 1.1 sp1 / etc. We would like a complete installation, where the user can't change anything, preferably only a progress bar for the complete installation.

     

    Is this possible? Maybe with a .mst?

     

    Yuri Marcus

    DSM BV

    Netherlands

    Thursday, January 24, 2008 1:18 PM
  • i guess you want to facilitate client to let him run just one setup, sit back and relax....

    Yes it is possible but after creating the administrative image you will have to create a redistributeable package.

     

    Thursday, January 24, 2008 2:20 PM
  •  

    Yes, that is exact what I mean. Can you help me how I can create this for the CRM3.0 client?

     

    Thanks in advance,

     

    Yuri

    Thursday, January 24, 2008 2:57 PM
  • Can we tie up and test it on coming sunday?

     

    Thursday, January 24, 2008 3:07 PM
  • Hi!

    I having problem installing the CRM OUTLOOK CLIENT. I want to do it using the commandline silent install. I already done Administrative Install Location. Here is the syntax I used msiexec /i Client.msi CONFIG=default_client_config.xml /l*v c:\install.log. The User has outlook account, a valid CRM users and member of local administrator. It only install the pre-requisite but not the main application. Here is the error I got from logged file.

    MSI (s) (20:74) [09:54:16:612]: Note: 1: 1708 

    MSI (s) (20:74) [09:54:16:612]: Note: 1: 2205 2:  3: Error 

    MSI (s) (20:74) [09:54:16:612]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708 

    MSI (s) (20:74) [09:54:16:612]: Note: 1: 2205 2:  3: Error 

    MSI (s) (20:74) [09:54:16:612]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 

    MSI (s) (20:74) [09:54:16:612]: Product: Microsoft CRM laptop client for Microsoft Office Outlook -- Installation failed.

     

    MSI (s) (20:74) [09:54:16:612]: Windows Installer installed the product. Product Name: Microsoft CRM laptop client for Microsoft Office Outlook. Product Version: 3.0.5300.0. Product Language: 1033. Installation success or error status: 1602.

     

    Thanks!


    Thursday, April 28, 2011 3:07 PM