Link to home
Start Free TrialLog in
Avatar of dgapinski
dgapinski

asked on

Automatic Installation roadblock for Lync 2013 client

I am trying to find a good way to deploy Lync 2013 standard & basic clients silently on  computers with Windows 7 / Office 2010 & have a few roadblocks.

1) I am successful installing the standard client (downloaded from VL), but when installing it automatically I am getting the error "The language of this installation package is not supported by your system". I am using the syntax:

setup.exe /adminfile lyncstd.msp /config lync.ww\config.xml

I made the MSP using setup /admin and gave it a full install. I also made the config.mxl file with the following syntax:

    <Configuration Product="Lync">

      <Display Level="none" CompletionNotice="yes" SuppressModal="yes" AcceptEula="yes" />
      
      <Logging Type="verbose" Path="%temp%" Template="Microsoft Office Lync Setup(*).txt" />
      
      <USERNAME Value="Me" />
      
      <COMPANYNAME Value="My company" />
      
      <INSTALLLOCATION Value="%programfiles%\Microsoft Office" />
      
      <DistributionPoint Location="\\vm-fs\public\Lync\Standard" />
      
      <OptionState Id="LOBiMain" State="absent" Children="force" /> -->
      
      <Setting Id="SETUP_REBOOT" Value="IfNeeded" />
      
</Configuration>

So this makes no sense to me - as in why installing from the GUI would present no such problem, but automating suddenly throws up a burning hemorrhoid. In the install log, I see towards the end a message: The language of this installation package is not supported by your system", so I have tried disabling options for language support in the admin install mode as well as to Remove the following earlier version of "Microsoft Office Multi-language User Interface Pack".

2) Or is the only way to install it using a GPO running a batch file in Computer Configuration > Policies > Windows Settings > Scripts, and have it run a silent install using setup.exe with the adminfile & configfile tags?

Thanks!
ASKER CERTIFIED SOLUTION
Avatar of ThwartedUserIDChoice
ThwartedUserIDChoice

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of dgapinski
dgapinski

ASKER

Thank you for that. When I was trying to understand this, it looked like both methods were required. Good to go now!
I came across one issue with deployment - they key. I am seeing a <PIDKEY="licensekey" /> reference for Office 2013, but that breaks the install if I try to insert that line into my config.xml. Does this method have a facility for entering a key? Automatic activation is a must for us really.