Solved

Cisco Jabber on premises client install using Group Policy

Posted on 2014-02-24
10
2,063 Views
Last Modified: 2014-04-01
I am attempting to deploy CiscoJabberSetup.msi v9.6 via our Windows 2008 R2 Group Policy as part of a new CUCM installation. An initial manual install of the msi from a share proved successful.

I have built and assigned a package via a respective Group Policy object as per the Cisco deployment doc, and set the scope to include a security group (read + execute access) of test PC's.

I can browse to the package/msi at the software distribution point and install manually, but attempts through GPO fail. There are no indications in event viewer at all, no indications of file or folder creation on respective PC's. Running GPresult /scope computer /r on a respective indicates that the GPO is applied.

When running manually  I receive dialog prompts, so I'm wondering if the package needs to be modified to run 'quiet' (although Cisco docs do not indicate as such).

1) Has anyone deployed successfully/have any thoughts that might help?
2) Has anyone done so and created a transform using Orca to configure for presence server/log in etc?

I feel I am missing some key element here, so help would be appreciated.
0
Comment
Question by:agradmin
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 4
10 Comments
 
LVL 37

Expert Comment

by:Mahesh
ID: 39885434
Have you assigned (do not publish) package to clients through GPO ?

Also while building software package have you selected package from network share location which is accessible to everyone \ authenticated  users

make sure that you have not selected local path during package importing in GPO

Check below KB article for step by step to ensure that you have done right things
http://support.microsoft.com/kb/816102

Mahesh
0
 
LVL 9

Expert Comment

by:VirastaR
ID: 39885642
Hi,

Did you follow the 5 Steps in Deploy the Client with Group Policy Article?

Step 1:         Copy the installation package to a software distribution point for deployment.
Step 2:         Select Start > Run and then enter the following command:gpedit.msc
Step 3:        Create a new group policy object.
Step 4:        Set the scope of your deployment.
Step 5:         Specify the installation package.

Group Policy installs Cisco Jabber for Windows on each computer the next time each computer starts.

Courtesy - Cisco Jabber Article| Deploy the Client with Group Policy
Deploy the Client with Group Policy

Hope that helps :)
0
 

Author Comment

by:agradmin
ID: 39886054
1) Package is assigned
2) Package is on the same software distribution share as other assigned (working) packages
 - can browse to path and manually install
3) Scope is good (as verified in gpresult)
4) Have followed the Cisco doc

In essence, all that has been suggested has been verified. As a manual install of the package requires prompts to be answered I'm wondering if that is the issue and I need to modify accordingly.
0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 
LVL 37

Expert Comment

by:Mahesh
ID: 39886338
try below

on machine where jabber setup is copied create one folder and place jabber msi package there
Then open cmd with run as administrator and navigate to yammer setup folder and run below command

msiexec /a C:\software\jabber.exe

This should create administrative install package and then you can try building this new package with GPO, it should work

Mahesh
0
 

Author Comment

by:agradmin
ID: 39886824
Mahesh,
Should that be msiexec /a 'folder path'\CiscoJabberSetup.msi? I get an error when I run as stated.

Alan
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 39886849
yes please try that
0
 

Author Comment

by:agradmin
ID: 39901805
I have found that others have had a similar issue deploying this package so will be putting in a case with Cisco. If anyone has successfully deployed I'd be interested in understanding how they did so.
Thanks for the suggestions but I really need to hear from Cisco how to deploy complete with required configurations in a true & tested manner. I'll let you know how it goes.
0
 
LVL 37

Expert Comment

by:Mahesh
ID: 39902430
You can run Ciscojabber.MSI /? to check what options do you have exactly
0
 

Accepted Solution

by:
agradmin earned 0 total points
ID: 39960380
Sorry for the delayed response - we have been busy with the project. It turns out that Cisco is prompting for acceptance of the EULA when the PC boots, and as it is not accepted the install fails.
One of my team discovered this by reviewing the package in Orca, once he created a transform that accepts the EULA the GPO implementation of Jabber works fine.

NOTE to Cisco - why on earth do you GPO install instructions NOT point this out! What is the point of having instructions that do not work!!!!!!!!!!

Thanks to all that contributed.
0
 

Author Closing Comment

by:agradmin
ID: 39968788
In the end we had to discover the issue ourselves but thanks to all that contributed and help us rule out our own insanity.
0

Featured Post

Turn Insights Into Action

You’ve already invested in ITSM tools, chat applications, automation utilities, and more. Fortify these solutions with intelligent communications so you can drive business processes forward.

With xMatters, you'll never miss a beat.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question