PENDING Deploy Lync 2016 with SCCM 2016 without user's action.

[Faisal Raza]

Hi All,

I am having an issue with SCCM 2016. Need to deploy Skype for Business 2016 through System Center Configuration Manager 2016 without user's action. All the process should go through fully automated and install Lync 2016 if its not installed.

I've tried the procedure provided in Form but it gives "Install Skype" option at end user side. This is what I don't want.

Thanks in well Adv.
Regards

Faisal

 

[Faisal Raza]

You would be better off upgrading those Office 2010 to 2016 and make everything x64.

Hopefully there wouldn't be any issue to upgrade to Office 2016 x64 even though if the OS is Win7 (32 / 64) as well as Win10 (32 / 64). Will it go smooth?
Actually we have large number of machines and I don't any hassle

Thanks in well Adv.
Regards
Faisal

 

[Big_Mark]

Hello Mark,

Using the arguments you provided didn't work and popped up with Office Customization action. Below are the help of the exe I've. Is there nay msi for Lync 2016?


lyncentry_4417-1000_x64_en-us.exe /quiet /passive


---------------------------
Skype for Business Basic
---------------------------
Usage:
/extractath, extracts the content of the package to the path folder
/log[ath to log file], enables verbose logging for the update installation
/lang:lcid, sets the user interface to the specified locale when multiple locales are available within the package
/quiet, runs the package in silent mode
/passive, runs the update without any interaction from the user
/norestart, prevents prompting of user when reboot of machine is needed
/forcerestart, forced restart of machine once update is complete
/?, shows this help message
---------------------------
OK
---------------------------

Thanks
Regards

Faisal

Hello Faisal, sorry for the delay I was on a much needed vacation.
Regarding the switches, and results of the commands, since I do not have the executable to test with over here (or time to do so) I can only provide you with some general guidance. These are things I've learned building out deployments over the last 10 years. Read through them and then do some trial and error testing to figure out how to get the executable to bend to your will.

Here are some tips:
1. run the executable from an Administrator command prompt as is;
\\path to the executable\exectable.exe
See what the installer does by default.

2. After you figured out what it does by default, try to silence it /q /s are common switches but each installer seems to have it's own flavors, /quiet instead of /q or /Q instead of /q

3. after you get it to install you will need to figure out how to get it to uninstall, silently if possible
places to look for uninstallers or GUID:
c:\Program Files\aplication\uninstall.exe < Older installers, certain installer types
c:\Windows\installer < MSI and exe with msi embedded components

4. IMPORTANT TO KNOW > SCCM installs programs with the machine account, not a local admin account. I have run into a couple of situations where the software installs just fine in testing (Admin CMD) but fails when deployed via SCCM for this very reason. So always test the SCCM deployment to a subset of your PCs before deploying to your entire fleet.

Over time you will get better at figuring out how to figure out what switches to use, when a script deployment is better than just adding a command in the deployment type window (uninstalls!!!)and so on.

Sorry I don;t have a solid answer but discovery is part of the job, this is how you gain experience.

Good luck!

 

[Edy]

Hopefully there wouldn't be any issue to upgrade to Office 2016 x64 even though if the OS is Win7 (32 / 64) as well as Win10 (32 / 64). Will it go smooth?
Actually we have large number of machines and I don't any hassle

Thanks in well Adv.
Regards
Faisal

In order to achieve this, you then need to spend a lot of time configuring to make it seamless for the users.

as always, test and test and test.

 

[Edy]

oh, just based on experience upgrading Office. Make sure you use Task Sequence and show a notification to user not to re-launch office products (eg word or outlook) during the upgrade as it will corrupt the re-installation and force reboot computers.