We help IT Professionals succeed at work.

Deploy CRM Outlook Client via Group Policy

1,732 Views
Last Modified: 2012-02-27
I am in the process of getting things setup to deploy the CRM 2011 Outlook Client via group policy.  I understand I need to create the msi then I and put that in a target directory in order to deploy.  I have a few questions around all of this as I have not deployed many programs out ot machines let alone with group policy.

What is the best way to create the msi in order for it to run in the background.  Do I just run the setupclient.exe with the /A and /Q triggers?

We have a handful of users with the client installed already so how can I decipher if it is already installed and exclude those from getting installed?

If I have a mixture of 64bit and 32bit OS's how can I decipher which are which to install the appropriate one for that machine?

Once I get hese items addressed I should be on my way.
Comment
Watch Question

CERTIFIED EXPERT

Commented:
> What is the best way to create the msi in order for it to run in the background.  Do I just run the setupclient.exe with the /A and /Q triggers?

setupclient /a /targetdir \\server\share

More details at http://technet.microsoft.com/en-us/library/hh699665.aspx . It should be noted however that I just tried it, and it failed.


> We have a handful of users with the client installed already so how can I decipher if it is already installed and exclude those from getting installed?

The best is probably to ignore it; the installation will detect an existing installation and will either upgrade it, or leave it alone. Note that only installation initiated by group policy becomes "managed". For example, if you later publish (not assign) an upgraded version, it will upgrade existing installations automatically - but only those that are managed. It's much better to have all installations deployed by the same method, such as all by group policy.

> If I have a mixture of 64bit and 32bit OS's how can I decipher which are which to install the appropriate one for that machine?

Create two group policies, one for 32-bit, another for 64-bit; specify WMI filter in each. See this discussion for more details.

You can also specify WMI filter for question #2 if you really want, the one that will find out if product X is already installed. However, be prepared that WMI will most likely fail on 2 computers out of 3, for variety of very sophisticated reasons.

Author

Commented:
Okay when you use the /Q do I need to use a /i and xml file to specify the location to install the client and offline options?

For number 2 I guess I can just install it on all machines so they are all managed down the road.

As far as number 3 should I just install 32 bit on all machines since you say it will fail on 2 out of 3.  Then again if I install 32 bit on all then how would the xml work on item 1 or should I just disregard the xml and use the enableofflinecapabilities trigger for everyone?
CERTIFIED EXPERT
Commented:
This one is on us!
(Get your first solution completely free - no credit card required)
UNLOCK SOLUTION

Author

Commented:
I was not able to get this working but thanks for your assistance.
Unlock the solution to this question.
Join our community and discover your potential

Experts Exchange is the only place where you can interact directly with leading experts in the technology field. Become a member today and access the collective knowledge of thousands of technology experts.

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.