Managing Office 365 Click to install with SCCM

Hello,
I am looking at deploying Office 365 via SCCM, but it looks like we will loose the ability to patch via WU/MU and instead need to update via pointing 365 to a static update source in configuration.xml \\server\path\.
Has anyone found a way to deploy the click to run 365 Office version and still effectively manage and updates and patches using SCCM distribution points? We do not want to run the MSI version.
Can anyone from MS here comment on the future of SCCM and 365 click to run integration ?
TIA
Lance

I was hoping you'd ask ;)
We created a second app in SCCM with some different settings for deployment because we expected people would be using Office while we were trying to update. . We used the same deployment method as the original app and the only real difference in the XML
is the version number of the bits we are updating and the display level. We changed the display level so that if people were logged in an using Office when the installation deadline was reached they would get a nice popup that indicated if they wished to continue
with the Office update then they would need to close Office. If they declined then SCCM marked the application as failed and on next software eval cycle would prompt again until success.
Our XML for the update is below - hope this helps.
<Configuration>
<Add SourcePath="" Version="15.0.4623.1003" OfficeClientEdition="32" >
  <Product ID="O365ProPlusRetail">
   <Language ID="en-us" />
  </Product>
</Add>
<Updates Enabled="FALSE" />
<Display Level="Full" AcceptEULA="TRUE" />
<Logging Name="Office365Setup.log" Path="%temp%" />
  <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
</Configuration>

Similar Messages

Need assistance creating applications with superseedence to uninstall Office 2010, Lync 2010 and then install Office 365 click to run 2013

We are getting ready in a few months to uninstall our locally installed Office 2010 and head to the cloud with Office 365 2013. I have created applications to uninstall Office 2010 and Lync 2010 and then added them to the supersedence tab for Office 365
office 2013 click to run with appv5.
When deploying the office 365 2013 application it does not uninstall office 2010 or lync 2010 with the supersedence. I am able to manually uninstall Office 2010 and Lync 2010 with the command lines I am using in the applications.
The application uninstall for Office 2010 is:
The application uninstall is an exe so I created an application, created a deployment type with the location of our Office 2010 admin point, installation program and uninstall program are set with the same line as I have tried to deploy it separately and
also as a supersedence in the Office 365 application setup.exe /uninstall ProPlus /config "\\sccmserver\share\Office2010\ProPlus.ww\silentuninstallconfig.xml. The silentuninstallconfig.xml was created from the original config.xml file and edited
to these settings:<Configuration Product="ProPlus">
<Display Level="none" CompletionNotice="NO" SuppressModal="yes" AcceptEula="yes" />
<Setting Id="Reboot" Value="Never" />
<Setting Id="SETUP_REBOOT" Value="NEVER" />
<OptionState Id="ProductFiles" State="Local" Children="force" />
</Configuration>
The detection method is the folder path to see that office 14 exists. When I deploy this the machines finish with success showing this exists, but does not uninstall Office 2010.
running the command line manually mapped to this location on a machine uninstalls office 2010 without issue.
Lync 2010 uninstall:
Lync is an exe so I am using the LyncSetup.exe /silent /uninstall. The application is in the supersedence tab for Office 365 2013. This never installs. If I create a softare distribution and deploy it on its own it uninstalls without issue.
We are going to use Lync 2013 with our office 365 2013 installation so we need to uninstall this. The detection method for lync is file system folder and the Microsoft lync folder for detection.
MS Office 15 (Office 365) was created with the click to run tool. I can install this with the application I created using the appv5 package created with the click to run tool. The issue is we need Office 2010 and Lync 2010 uninstalled first.
Having both versions of Office installed in test has caused issues where Office 15 365 will not list in add and remove programs and cannot be uninstalled even with the fix it article to remove office 2013.
I have looked at many articles and so far it is not working for us. Any help appreciated to get us to the cloud.
Thanks,
Brit

The applications I have for uninstall of office 2010 and Lync 2010 for some reason do not uninstall. Manually testing the command lines they do. The detection method seems to be hanging things up. On the lync uninstall detection method I have
the setting type of file system, type folder, path c:\program files\ folder name Microsoft Lync.
I highly recommend using something other than a file/folder "exists" detection method. Installers are constantly leaving things behind due to environmental inconsistencies. It may leave files/folders behind with a schedule to delete files on next reboot.
These things are unpredictable and very hard to use. I just use the "HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall" Registry location. There you can actually key off the "Product Version" DWORD as well which gives you an even more accurate method
to determine if the application you are trying to deploy (or expect to exist) is truly there. This, of course, being if you are not using an MSI. If you have MSI technology ALWAYS use the product code unless the person writing the MSI chooses to use the same
product code for every version release of their product. In which case, Use the registry method.
As far as getting the supersedence and everything working. You need to start from the basics. Create Applications for all of the apps you want to remove. Make sure they install and uninstall properly (seems like overkill but it isn't that hard). Once you
have working install/uninstall applications then you can easily apply supersedence to your new applications with a setting of Uninstall on the superseded apps you should have no problem getting rid of them. I have done this for numerous things.
For example, I did this with Cisco Jabber to replace older versions of jabber, older versions of cisco unified personal communicator and lync and OSC. All of these replaced versions had to have an Application but once it was in it took two seconds to apply
all the supersedence rules and now I know when I push that software out no matter version is running on any machine it will pull all the old apps off and put the new one on.
Dustin Estes - MCP | www.dustinestes.com

With Multi-Factor Authentication ENABLED how can a admin connect remotely to manage Office 365 with PowerShell

With Multi-Factor Authentication ENABLED how can office 365 admin connect remotely to manage Office 365 with Power-Shell ?
When I key-in my credentials, auth fails with invalid username and password ?
Does any know the procedure ?

This question was closed over a year ago. You will need to start a new question. You can post a link back here if you think it helps.
I also recommend asking in the O365 developers forum for how to do bulk license upgrades. You can use the answer here and just remove and then add the new license.
¯\_(ツ)_/¯

Questions on managing Office 365/Exchange Online Mailboxes in Server 2012 Essentials

Wondered if anyone could answer a couple of queries:
When managing Office 365/Exchange Online mailboxes in Windows Server 2012 Essentials:-
1. Does the server itself act as the Exchange server i.e. does it do all of the downloading/sending of emails or does Outlook on each workstation still communicate direct with the Office 365/Exchange Online server address?
2. Does Outlook on each workstation have the Exchange server address set to the internal address of the Server 2012 Essentials box or does it still have the external Office 365/Exchange Online server address?
I don&#39;t work for Microsoft - I just use their products.

Hi,
When you integrate Office 365/Exchange Online mailboxes in Windows Server 2012 Essentials,you can see the mailbox usage information on the Essentials Dashboard and manager users. However, the essentials server won't download/send emails and Outlook
will still communicate with the O365/Exchange Online Server. In addition, the Exchange server address would be point to the external server address.
You can also refer to the article below to get more related information:
Email Options Supported by Windows Server 2012 Essentials
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

MS Office 365 fails to install in default on Win 8.1 new laptop S75-A7221

Hello,
New license MS Office 365 fails to install in default on Win 8.1 new laptop S75-A7221.
I downloaded software from Microsoft MS Office 365 site.
What is the contact for helpdesk in India for quick resolution?
Thanks,
Miroslaw

Run Microsoft FixIt in the following link to check the result.
http://support.microsoft.com/kb/2822317
If your Office installation problem continues to occur, try to perform the steps provided by the same link for general troubleshooting.
Tony Chen
TechNet Community Support

Office 365 Click to Run April Update version has changed


We are implementing a process for controlling Office 365 click-to-Run updates so that our application testers can verify that the updates have no adverse effects on their applications.
We started distributing the April update on April 14th and the update version at the time was 15.0.4711.1002. We are also using the group policy registry keys to control the version. Today after hours of troubleshooting why we are now getting
errors when PCs are trying to update to that version I discover that there is no longer a version 15.0.4711.1002 and has been replaced by 15.0.4711.1003. I cant find anywhere why this has been updated or what changes were made so I don't know if this
now has to be retested by our testing group.   Just wondering is this a minor change and if so what was it?

Thanks for responding Tony - here is my modified configuration.xml (I've only removed DFS location names)
<Configuration>
<Add SourcePath="\\OurDomain.com\Office365\Files" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="\\OurDomain.com\Office365\Files\Updates" />
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013Setup.log" Path="%windir%\Logs\Office\" />

</Configuration>
Carl Barrett | Twitter: @Mosquat

Add-in support on Office 365 click-to-run installed and Office 365 App-V installed

Hi,
We have to make a decision on deploying Office 365 via on premise click-to-run, with the Office Deployment tool, or via App-V. But the way add-ins are supported on Office 365 / Office 2013 on App-V 5.0 SP2 is not clear to me.
Some Technet sites mention that for add-in support on an App-V based office, the add-ins should be sequenced and put together in a connection group with the Office App-V package (created by the Office Deployment tool)
On
http://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx however, I read in the table “Full-featured Office with integration with other applications,
add-ins, and Windows”
When testing with third party applications and Visual Studio installed in a classical installer way, the add-ins are added to the App-V installed Office, but we are sometimes experiencing error messages in word / excel with the add-ins
enabled.
Should add-ins be sequenced to be used on an App-V based Office? Or in other words, is there a difference in add-in support between the click-to-run version and the App-V version of Office for non-virtualized add-ins?

Hi,
There is a new feature for Office 365 Pro Plus, it allow administrators the ability to exclude App element. We need to use Office 2013 Click-to-Run (Build 15.0.4615.1001) and logon as administrator.
http://blogs.technet.com/b/odsupport/archive/2014/05/14/new-application-selection-feature-offered-with-the-may-2014-update-of-office-2013-click-to-run.aspx
Then, we'd better follow this link and repeat the steps one by one:
http://lyncme.co.uk/office365/office365-proplus-click-to-run-lets-stop-onedrive-for-business-from-being-installed/
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does
not guarantee the accuracy of this information.
Regards,
George Zhao
TechNet Community Support

Office 365 Pro Plus install failures during SCCM OSD

Hi All,
I'm in the process of deploying Office 365Pro Plus using SCCM 2012 r2 and have found some very weird behaviour. I have already downloaded the source and the Office folder exists in the same folder as setup.exe and my install xml looks like this:
<Configuration>
<Add SourcePath="" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="" />
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />
</Configuration>
The install starts but completes after 5 seconds and OfficeSetup.txt shows Products configured successfully. Looking at other logs that are generated I can see a number of interesting entries:
The call to OfficeClickToRun.exe:
Calling {C:\Program Files\Microsoft Office 15\ClientX86\OfficeClickToRun.exe} with parameter {scenario=unknown baseurl="C:\Windows\ccmcache\b\Office\Data\15.0.4623.1003" version="15.0.4623.1003" platform="x86" displaylevel="False"
culture="en-us" updatesenabled="True" firstrun="root\office15\firstrun.exe" productstoadd="O365ProPlusRetail_en-us_x-none"}
A error code that does not seem to have been passed back to the main log:
Click-To-Run   ap11d   Medium   StandaloneStartupBehavior::Start - Exit with error code 17002
A fatal error of FileNotFound:
Click-To-Run   amcq9   Unexpected   CCS::IsReachable. Source (C:\Windows\ccmcache\b\Office\Data\15.0.4623.1003\Office\Data\15.0.4623.1003\stream.x86.en-us.dat) not reachable. Exception FileNotFound (Source
not reachable.)
I believe this last error is the root cause of the failures at the source directory seems to have been added to the file path twice. The streamfile is located in C:\Windows\ccmcache\b\Office\Data\15.0.4623.1003 but something is adding and additional \Office\Data\15.0.4623.1003
to the path which does not exist.
This is a massive issue for us which is preventing deployment so any help is greatly appreciated.
Simon.

Hello Simon,
What's the entire SoucePath that you entered in your Confirguration.XML file? Please try to remove "Office\Data\15.0.4623.1003" from it and have a try again.
Feel free to post back with any findings.
Thanks,
Ethan Hua CHN
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

For Your Consideration: Ultimate Lync 2010 client install with SCCM 2007

While the subject of my post may be very presumptuous, I submit the following for your consideration to answer the often-asked question about how to deploy Lync 2010 client with SCCM.
Background:
I cannot understand why Microsoft made the Lync install so darned confusing, complex, and convoluted.
After our Lync 2010 FE server was up and running and all users migrated off our OCS server to the Lync environment, I spent about a month and a half trying to figure out how to:
1. Uninstall the OCS 2007 R2 client
2. Install all prerequisites for the Lync client
3. Install Lync on all user workstations silently.
While researching this, the simple answer I kept seeing given to this question was, "just use the .exe with the right switches according to the TechNet article here: http://technet.microsoft.com/en-us/library/gg425733.aspx". Well, my response is, I
tried that and while the program installed itself correctly pushed through SCCM, because I was doing it using an administrative account (i.e. the SYSTEM account) due to our users not having admin rights, when the install was done, Lync would automatically
start up, but in the SYSTEM context so that the user couldn't see it was running, they go to run it and it won't run for them. I was unable to find any switch or option to prevent the automatic launch. I suppose the simple solution to that would
be to have the user reboot, but that's unnecessarily disruptive and was contrary to the desire to make this a silent install.
The next simplest answer I saw was, "extract the MSI and use that with the right switches". Problem with that is that the MSI by itself doesn't remove the OCS client or install the prerequisites, and also either requires a registry change to even allow
the MSI to be used or a hacked MSI that bypasses the registry key check. I tried to put a package together to uninstall OCS, install the prereqs, and use a hacked MSI, but I never could get the MSI hacked properly. The other problem I ran into
was detecting if the OCS client was running in a predictable way so I could terminate it, properly uninstall it, and then do the rest of the installations. It was this problem that ultimately led me to the solution that I'm about to detail and that has
worked marvellously for us.
Solution:
As I said before, when I first looked at this problem, I started by building a typical software deployment package (Computer Management -> Software Distribution -> Packages) and then created the programs to do the install. My first attempt was
just with the .exe file provided as-is by Microsoft using the switches they document in the link above for IT-Managed Installation of Lync, and...well, the end result wasn't quite as desirable as hoped. So, my next attempt was to extract all the prerequisite
files and the Lync install MSI (both for x86 and x64), attempt to hack it to get around the "UseMSIForLyncInstallation" registry key, and make the command-lines to terminate OCS and uninstall it.
In the past when I had an install to do with SCCM that also required uninstalling an older version of a given application, I typically used the program-chaining technique. That's where you have, for example, 3 or more programs that run in a package
in a sequence and you have Program 3 be set to run after Program 2 does and then set Program 2 to run after Program 1 so you get the desired sequence of Programs 1-2-3 running in that order. So, I created programs to 1) kill Communicator.exe 2) uninstall
Communicator 2007 R2 by doing an "msiexec /uninstall {GUID}" 3) install Silverlight 4) install Visual C++ x86 5) optionally install Visual C++ x64, and then 6) install the Lync x86 or x64 client. That final step was always the point of failure because
I couldn't get the hacked MSI for the Lync Client install to work. I also realized that if Communicator wasn't running when the deployment started, that step would fail and cause the whole process to bail out with an error. That's one of the downsides
of program-chaining, if one step fails, SCCM completely bails on the deployment. This is what also led me to the key to my solution: TASK SEQUENCES.
I'm not sure how many people out there look in the "Operating System Deployment" area of SCCM 2007 where Task Sequences normally live, but I also wonder how many people realize that Task Sequences can be used for more than just Operating System deployments.
One of the biggest advantages of a task sequence is you can set a step to ignore an error condition, such as if you try to terminate a process that isn't running. Another advantage is that task sequences have some very good built-in conditionals that
you can apply to steps, for example, having the sequence skip a step if a certain application (or specific version of an application) is not installed on the machine. Both of those advantages factor highly into my solution.
OK, for those who already think this is "TL;DR", here's the step-by-step of how to do this:
First, you need to extract all the files from the LyncSetup.exe for your needed architectures. We have a mix of Windows XP and Windows 7 64-bit, so my solution here will take both possibilities into account. To extract the files, just start up
the .exe like you're going to install it, but then when the first dialog comes up, navigate to "%programfiles%\OCSetup" and copy everything there to a new location. The main files you need are: Silverlight.exe, vcredist.exe (the x64 LyncSetup.exe includes
both x86 and x64 Visual C++ runtimes, you need them both, just rename them to differentiate), and Lync.msi (this also comes in an x86 and x64 flavor, so if you have a mix of architectures in your environment, get both and either put them into their own directories
or rename them to reflect the architecture).
For my setup, I extracted the files for the x86 and x64 clients and just dumped them each into directories named after the architectures.
Next, move these files into a directory to your SCCM file server, whatever it might be that you deploy from, in our case, it was just another volume on our central site server. Go to the SCCM console into Computer Management -> Software Distribution
-> Packages and then create a new package, call it something meaningful, and then point to the directory on your SCCM file server for the source files.
Now you need to create 3 to 5 programs inside the package:
1. Name: Silverlight
   Command Line: x86\Silverlight.exe /q     (remember, inside my main Lync install folder on my distribution point, I have an x86 directory for the files from the x86 installer and an x64 folder for the files from the x64 installer.
The fact is the Silverlight installer is the same in both, so you only need one of them.)
   On the Environment tab: Program can run whether or not a user is logged in, runs with administrative rights, Runs with UNC name
   On the Advanced tab: Suppress program notifications
   All other options leave default.
2. Name: Visual C++ x86
    Command Line: x86\vcredist_x86.exe /q
   On the Requirements tab: Click the radio button next to "This program can run only on specified client platforms:" and then check off the desired x86 clients.
   Environment and Advanced tabs: same as Silverlight
   (If you have only x64 clients in your environment, change all x86 references to x64. If you have a mixed environment, create another program identical to this one, replacing references to x86 with x64.)
3. Name: Lync x86
    Command Line: msiexec /qn /i x86\Lync.msi OCSETUPDIR="C:\Program Files\Microsoft Lync" (The OCSETUPDIR fixes the issue with the Lync client wanting to "reinstall" itself every time it starts up)
    Requirements, Environment, and Advanced tabs: Same as with Visual C++ and Silverlight
    (Same deal as above if you have all x64 clients or a mix, either change this program to reflect or make a second program if necessary)
Now you need to make the Task Sequence. Go to Computer Management -> Operating System Deployment -> Task Sequences. Under the Actions pane, click New -> Task Sequence. In the Create a New Task Sequence dialog, choose "create a
new custom task sequence", Next, enter a meaningful name for the task sequence like "Install Microsoft Lync", Next, Next, Close.
The task sequence will have up to 12 steps in it. I'll break the steps down into 3 phases, the prereqs phase, uninstall OCS phase, and then Lync install phase.
Prereqs Phase:
These are the easiest of the steps to do. Highlight the task sequence and then in the Actions pane, click Edit.
1. Click Add -> General -> Install Software. Name: "Install Microsoft Silverlight". Select "Install a single application", browse to the Lync package created earlier and then select the Silverlight program.
2. Add -> General -> Install Software. Name: "Install Microsoft Visual C++ 2008 x86". Install Single Application, browse to the Lync package, select the Visual C++ x86 package.
As before, if you're an all-x64 environment, replace the x86 references with x64. If you have a mixed environment, repeat step 2, replacing x86 with x64.
3. Add -> General -> Run Command Line. Name: "Enable Lync Installation". This step gets around the UseMSIForLyncInstallation registry requirement. The Lync client MSI simply looks for the presence of this key when it runs, so
we'll inject it into the registry now and it doesn't require a reboot or anything. It just has to be there before the client MSI starts.
Command Line: reg add "hklm\Software\Policies\Microsoft\Communicator" /v UseMSIForLyncInstallation /t REG_DWORD /d 1 /f
Uninstall OCS Phase:
This part consists of up to 6 Run Command Line steps. (Add -> General -> Run Command Line)
4. Name: "Terminate Communicator". Command Line: "taskkill /f /im communicator.exe". On the Options page, check the box next to "Continue on error". This will terminate the Communicator process if it's running, and if it's not, it'll
ignore the error.
5. Name: "Terminate Outlook". Command Line: "taskkill /f /im OUTLOOK.exe". Check the "Continue on error" on the Options page here too. Communicator 2007 hooks into Outlook, so if you don't kill Outlook, it might prompt for a reboot
because components are in use.
(NOTE: If necessary, you could also add another step that terminates Internet Explorer because Communicator does hook into IE and without killing IE, it might require a restart after uninstalling Communicator in the next steps. I didn't run into
this in my environment, though. Just repeat step 5, but replace OUTLOOK.EXE with IEXPLORE.EXE)
6. Name: "Uninstall Microsoft Office Communicator 2007". Command Line: "msiexec.exe /qn /uninstall {E5BA0430-919F-46DD-B656-0796F8A5ADFF} /norestart" On the Options page: Add Condition -> Installed Software -> Browse to the
Office Communicator 2007 non-R2 MSI -> select "Match this specific product (Product Code and Upgrade Code)".
7. Name: "Uninstall Microsoft Office Communicator 2007 R2". Command Line: "msiexec.exe /qn /uninstall {0D1CBBB9-F4A8-45B6-95E7-202BA61D7AF4} /norestart". On the Options page: Add Condition -> Installed Software ->
Browse to the Office Communicator 2007 R2 MSI -> select "Match any version of this product (Upgrade Code Only)".
SIDEBAR
OK, I need to stop here and explain steps 6 and 7 in more detail because it was a gotcha that bit me after I'd already started deploying Lync with this task sequence. I found out after I'd been deploying for a while that a tech in one of our remote
offices was reinstalling machines and putting the Communicator 2007 non-R2 client on instead of the R2 client, and my task sequence was expecting R2, mostly because I thought we didn't have any non-R2 clients out there. So, at first I just had our Help
Desk people do those installs manually, but later on decided to add support for this possibility into my task sequence. Now, when you normally uninstall something with msiexec, you would use the Product Code GUID in the command, as you see in steps 6
and 7. All applications have a Product Code that's unique to a specific version of an application, but applications also have an Upgrade Code GUID that is unique for an application but common across versions. This is part of how Windows knows that
Application X version 1.2 is an upgrade to Application X version 1.1, i.e. Application X would have a common Upgrade Code, but the Product Code would differ between versions 1.1 and 1.2.
The complication comes in that Communicator 2007 and Communicator 2007 R2 have a common Upgrade Code, but different Product Codes and the "MSIEXEC /uninstall" command uses the Product Code, not the Upgrade Code. This means that if I didn't have step
6 to catch the non-R2 clients, step 7 would be fine for the R2 clients, but fail on non-R2 clients because the Product Code in the MSIEXEC command would be wrong. Luckily, we only had one version of the non-R2 client to deal with versus 4 or 5 versions
of the R2 client. So, I put the command to remove Communicator 2007 non-R2 first and checked for that specific product and version on the machine. If it was present, it uninstalled it and then skipped over the R2 step. If non-R2 was not present,
it skipped that step and instead uninstalled any version of the R2 client. It's important that steps 6 and 7 are in the order they are because if you swap them, then you'd have the same outcome as if step 6 wasn't there. What if neither is on the
machine? Well the collection this was targeted to included only machines with any version of Communicator 2007 installed, so this was not a problem. It was assumed that the machines had some version of Communicator on them.
8. Name: "Uninstall Conferencing Add-In for Outlook". Command Line: "msiexec.exe /qn /uninstall {730000A1-6206-4597-966F-953827FC40F7} /norestart". Check the "Continue on error" on the Options Page and then Add Condition ->
Installed Software -> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
9. Name: "Uninstall Live Meeting 2007". Command Line: "msiexec.exe /qn /uninstall {69CEBEF8-52AA-4436-A3C9-684AF57B0307} /norestart". Check the "Continue on error" on the Options Page and then Add Condition -> Installed Software
-> Browse to the MSI for this optional component and set it to match any version of the product. If you don't use this in your environment, you can omit this step.
Install Lync phase:
Now, finally the main event, and it's pretty simple:
10. Click Add -> General -> Install Software. Name: "Install Microsoft Lync 2010 x86". Select "Install a single application", browse to the Lync package created earlier and then select the "Lync x86" program. As before, if you
only have x64 in your environment, replace the x86 with x64, or if you have a mixed environment, copy this step, replacing x86 references with x64.
And the task sequence is done! The final thing you need to do now is highlight the task, click Advertise in the Actions pane, and deploy it to a collection like you would with any other software distribution advertisement. Go get a beer!
Some final notes to keep in mind:
1. You can't make a task sequence totally silent...easily. Users will get balloon notifications that an application is available to install. The notifications cannot be suppressed through the GUI. I've found scripts that supposedly
hack the advertisement to make it be silent, but neither of them worked for me. It was OK, though because in the end we wanted users, especially laptop users, to be able to pick a convenient time to do the upgrade. The task sequence will appear
in the "Add/Remove Programs" or "Programs and Features" Control Panel. You can still do mandatory assignments to force the install to happen, you just can't make it totally silent. On the plus side, the user shouldn't have to reboot at any point
during or after the install!
2. In the advertisement setup, you can optionally show the task sequence progress. I've configured the individual installs in this process to be silent, however, I did show the user the task sequence progress. This means instead of seeing
5 or 6 Installer windows pop up and go away, the user will have a single progress bar with the name of the step that is executing.
3. One step that I didn't consider when I actually did this was starting the Lync client as the user when the install was complete. The user either had to start the client manually or just let it start on its own at the next logon. However,
while I was writing this, I realized that I could possibly start the client after installing by making another Program in the Lync Package with a command line that was along the lines of "%programfiles%\Microsoft Lync\communicator.exe" and then in the Environment
tab, set it to "Run with user's rights" "only when a user is logged on".
4. My first revision of this task sequence has the Prereqs phase happening after the OCS uninstall phase, but I kept running into problems where the Silverlight installer would throw some bizarre error that it couldn't open a window or something wacky
and it would fail. Problem was, I couldn't re-run the task sequence because now it would fail because OCS had been uninstalled, so that's why the Prereqs happen first. It ran much more reliably this way.
5. For some reason that baffles me, when I'd check the logs on the Site Server to monitor the deployment, I'd frequently see situations where the task sequence would start on a given machine, complete successfully, almost immediately start again, and
then fail. I'm not sure what is causing that, but I suspect either users are going to Add/Remove Programs and double-clicking the Add button to start the install instead of just single-clicking it, or the notification that they have software to install
doesn't go away immediately or Lync doesn't start up right after the install, so they think the first time it didn't take and try it a second time.
I hope this helps some of you SCCM and Lync admins out there!

On Step 8 I found multiple product codes for the Conferencing Add-In for Outlook. Here's a list of the ones I found in the machines on my network:
{987CAEDE-EB67-4D5A-B0C0-AE0640A17B5F}
{2BB9B2F5-79E7-4220-B903-22E849100547}
{13BEAC7C-69C1-4A9E-89A3-D5F311DE2B69}
{C5586971-E3A9-432A-93B7-D1D0EF076764}
I'm sure there's others one, just be mindful that this add-in will have numerous product codes.

Deployment of Office 365 Click to Run

Having an issue getting the O365 to install and wondering if I could get some help. I am new to SCCM and have managed to get a few other apps/packages pushed out without issue. I have followed a couple of online resources to get this one
going but am at the end of my rope.
Created an Application that pushes out to a user Group.
Client Computer (default device) is seeing the package and downloading for the appropriate users and I can see the complete package in the \windows\CCMCACHE
The issue appears that it is timing out waiting for user input when doing the install.
the app is calling setup.exe /configure configuration.xml
Contents of configuration.xml below
<Configuration>
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Here is the App enforcment log that tells me it is exceeding 120 minutes
<![LOG[+++ Starting Install enforcement for App DT "Deploy Office 365 Pro Plus X32" ApplicationDeliveryType - ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, Revision - 6, ContentPath - C:\windows\ccmcache\1i, Execution Context - System]LOG]!><time="14:16:04.873+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:1702">
<![LOG[ A user is logged on to the system.]LOG]!><time="14:16:04.885+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:2083">
<![LOG[ Performing detection of app deployment type Deploy Office 365 Pro Plus X32(ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, revision 6) for system.]LOG]!><time="14:16:04.889+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_F0A72C6A-71AD-48AB-9637-3C4F9DC381D0/DeploymentType_ee4472b1-c0c3-4ed5-aeda-b6d844c62944, Revision: 6]]LOG]!><time="14:16:04.910+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="localapphandler.cpp:291">
<![LOG[ App enforcement environment:
Context: Machine
Command line: setup.exe /configure configuration.xml
Allow user interaction: No
UI mode: 0
User token: null
Session Id: 4294967295
Content path: C:\windows\ccmcache\1i
Working directory: ]LOG]!><time="14:16:04.911+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:85">
<![LOG[ Prepared working directory: C:\windows\ccmcache\1i]LOG]!><time="14:16:04.912+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:189">
<![LOG[ Prepared command line: "C:\windows\ccmcache\1i\setup.exe" /configure configuration.xml]LOG]!><time="14:16:05.012+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcontext.cpp:338">
<![LOG[ Post install behavior is BasedOnExitCode]LOG]!><time="14:16:05.411+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appcommon.cpp:1094">
<![LOG[ Waiting for process 1612 to finish. Timeout = 120 minutes.]LOG]!><time="14:16:05.414+300" date="02-12-2015" component="AppEnforce" context="" type="1" thread="11560" file="appexcnlib.cpp:1958">
<![LOG[Exceeded timeout of 120 minutes while waiting for process 1612 to finish.]LOG]!><time="16:16:05.723+300" date="02-12-2015" component="AppEnforce" context="" type="2" thread="11560" file="appexcnlib.cpp:1972">
<![LOG[WaitForRunningProcess failed. Error 0x87d00213.]LOG]!><time="16:16:05.723+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appexcnlib.cpp:1988">
<![LOG[CMsiHandler::CompleteEnforcement failed with 0x87d00213]LOG]!><time="16:16:05.724+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="msihandler.cpp:320">
<![LOG[CAppProvider::CompleteEnforcement failed with error 0x87d00213]LOG]!><time="16:16:05.729+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appprovider.cpp:2544">
<![LOG[++++++ Failed to enforce app. Error 0x87d00213. ++++++]LOG]!><time="16:16:05.736+300" date="02-12-2015" component="AppEnforce" context="" type="3" thread="11560" file="appprovider.cpp:2467">
As this is the first package that really has failed miserably I would love any help trying to troubleshoot what is wrong.

I haven't pushed this application out but I have looked at OneDrive which was very similar.
https://social.technet.microsoft.com/Forums/en-US/fdc35051-796f-4c94-98b4-19df0bc316e3/one-drive-for-business-deployment-with-sccm?forum=configmanagergeneral
Forget about Configuration manager, it's just running the installation via a command line under the system account.
Copy your application to a local machine and run it from from a command line,
It might be worth changing the display level property so you can see if the installation is prompting for anything.
You could also add

and check the temp directory for the log file.
Start run %temp%
or if running under the system account this will be located C:\windows\temp.
Once you have your installation going through silently then run it under the system account. again do this from the local machine without configmgr using PSEXEC -i -s cmd.exe
http://richardbalsley.com/a-simple-tip-to-test-software-installation-using-the-local-system-account
One that works it will fly out using ConfigMgr.

Managing Office 365 Updates?

I use WSUS and/or System Center Configuration Manager 2012 to manage Office updates today. Can I continue to use these products to update Office 365 ProPlus? Plz Suggest? What is the best way?
Thanks

No. Unfortunately you cannot. There's a new update system for the Click To Run software. CTR is a whole nother animal. This document goes over the limitations: http://technet.microsoft.com/en-us/library/ee624360.aspx
If you want to control which updates are applied and distribute those internally, then it works something like this:
Deploy Office with configuration.xml (and/or GPO) configured for an internal update location
Write and schedule a script to regular run setup.exe with another configuration.xml to download the updates to a shared location
Microsoft just finally gave us a few more customization and some limited GPO control in April. Here's some information on that:
http://blogs.technet.com/b/odsupport/archive/2014/04/28/new-group-policies-introduced-with-the-april-2014-update-of-office-2013-click-to-run.aspx
http://blogs.office.com/2014/05/14/the-garage-series-for-office-365-updates-to-office-365-proplus-for-admins-and-first-look-at-upcoming-shared-computer-support/
Here's the references you'll need:
http://technet.microsoft.com/en-us/library/jj219420.aspx#BKMK_C2RUpdates
http://technet.microsoft.com/en-us/library/jj219426(v=office.15).aspx
Yes the documentation is spread out all over and is not all up to date. We haven't found the updates to be reliable either and are still frustrated with the lack of any central management or troubleshooting. It's like they released the software
but are still working on the tools to manage it. Good luck.

Manage Office 365 Licensing via Azure API

I am at a loss. We have an issue with limited available licenses for Office 365 Pro Plus for users to use on their home/personal machines. As a result we can not add all of our users, nor does anyone want to manage this manually.
The solution I proposed is to write a web portal where users can go and selectively apply a license for their account. On the back end, the page would execute an API of some kind to Azure and assign a license. In return, they can also go to remove the license
if they so desire (It will never happen but give the option).
What is the best way of doing this? The Azure management portal is extremely confusing and I can not figure out where to begin... I created an API that I can't even figure out how to use and I'm not even sure that I will be able to accomplish this using
an API. Any suggestions?
I am using Visual Studio 2013 and at this point purely using a bare bones console app just to see if I can get connected and execute a test API.
Thanks!
Tony

Hi,
Your second sentence is unclear "We have an issue with limited available licenses for Office 365 Pro Plus for users to use on their home/personal machines".
Users can install Office 365 ProPlus on up to five different computers with a single Office 365 license. For example, a user can have Office 365 ProPlus installed on a computer in the office, on a laptop to use when traveling, and on a home computer.
With that in mind, do you really need to create this API?
Here's some more info on the Pro Plus license:
To use Office 365 ProPlus, a user must have an Office 365 account and have been assigned a license. If you, as the Office 365 administrator for your organization, remove a user’s license or account, the user’s installations of Office 365 ProPlus go into
reduced functionality mode.
Even though users don’t need to be connected to the Internet all the time to use Office 365 ProPlus, users must connect to the Internet at least once every 30 days. This is so that the status of their Office 365 subscriptions can be checked. If users don’t
connect within 30 days, Office 365 ProPlus goes into reduced functionality mode. After users connect to the Internet and their subscription status is verified, all the features of Office 365 ProPlus are available again.
https://technet.microsoft.com/en-us/library/gg702619.aspx?f=255&MSPPError=-2147217396
Cheers
Amjad

Office 365 Pro Plus Install or deployment issue.

Users downloading the software direct from the user portal leaves them stuck on the setting up office when they don’t have office on their systems and does not allow them to download it.
Downloading to the network to deploy gives the error that they may not be connected to the internet which makes no sense at all but I’ve tried it three times all with the same result. IT downloads the actual installer file to
the server but it keeps giving that same error.

Hi,
Would you like to give me the whole error message? Please see the "Troubleshoot specific errors in Office 365 ProPlus",we can find the resolution of
Internet Connection Required.
Since you want to install or deploy the Office 365 pro plus, please read the following articles and check they are helpful.
http://technet.microsoft.com/en-us/library/gg715562(v=office.15).aspx
http://blogs.technet.com/b/office_resource_kit/archive/2013/08/08/how-to-deploy-office-365-proplus-from-an-on-premises-web-portal.aspx
http://www.microsoftvirtualacademy.com/training-courses/office-365-deployment-for-it-pros
http://community.office365.com/en-us/w/upgrade/installing-office-365-proplus-with-the-office-deployment-tool.aspx
Regards,
George Zhao
TechNet Community Support

Office 365: Prgramtically sync Calendar with SharePoint team site calendar

Hello everyone,
I need to sync office 365 Calendar with SharePoint team sites Calendars. We have SharePoint online site which having multiple sub sites, each sub site has a calendar control and we need calendar controls need to be sync with the outlook calendar available
on top bar of office 365.
We need to do it programmatically as we have more then 200 hundred sub sites, please guide me on this that how it is possible using developer app or PowerShell commands.

I think it might help to clarify what you mean. When you say "Office 365 Calendar", what you really mean is the Calendar associated with whomever is logged in, stored in Exchange. When you see the "Calendar" link in the little bar at the top of the page,
that's actually just a link to the Outlook Web Access calendar for a particular user's calendar stored in the Office 365 Exchange server. It's exactly the same calendar that would show up if a user had Outlook installed on their local computer and opened it
up and looked at the calendar.
That being said, you aren't going to want to synch every calendar in your whole SharePoint site with a single user's calendar. I think there are a couple approaches for you:
Create a calendar overlay in SharePoint, which displays other calendars on the current calendar view. Unfortunately, there's a limit as to how many calendars you can do this for, it's far less than 200.
Allow users to create calendar overalys in Outlook. This is the same idea as what you're doing in SharePoint, except users are doing this within Outlook. Again, adding 200 overlays isn't practical.
You can try creating an additional company calendar in Exchange that's not tied to a particular user, but then you'll have to run a timer job to keep the Outlook calendar in synch with the SharePoint calendar. This is a lot more cumbersome than just displaying
the SharePoint calendar, since you're physically copying events over to the Outlook calendar. If you do that, you personally are responsible for keeping the two calendars synched up, rather than just displaying an Exchange calendar in SharePoint, or displaying
a SharePoint calendar in Outlook.
You might looking into third party tools such as
http://www.boostsolutions.com/calendar-rollup-feature-list.html. (I haven't tried that product, it just looks like it might be the type of thing to check out.
If I have any advice, I would recommend as much as possible creating views of calendars, not actually trying to synch data, unless you're doing a one-way synch. (Synching calendar data can be a little bit difficult because you have reoccurring events to
take into account.)
Blog:
blog.beckybertram.com |
RSS | @beckybertram |
SharePoint 2010: Six-in-One

Anyone using Office 365 but still flooded with spam emails / phishing attempts?

How are you dealing with it?New article published todayon configuring SpamTitan for Office 365 frommaximum protection. You can read the articlehere.The article outlines some reasons that companies use SpamTitan along with an Office 365 subscription, among them:A greater level of protection.A higher spam catch rate.A greater level of customizationBetter outbound mail controlsBusiness continuity.Any questions please get in touch.Regards,Geraldine
This topic first appeared in the Spiceworks Community

Hi DT655,
Thanks for your reply. Since my original post I have upgraded and subscribed to Office 365 Midsize Business. All has gone well, everything has been migrated over and all has been synced correctly.
Except my BlackBerry Z10 where Calendar syncs everything going forward, but only three months back. My BB PlayBook is the same (only three months back). However, my desktop and iPads sync all events going back many years.
I have followed your instructions by deleting my old e-mail accounts on both my Z10 and my PlayBook and reinstalled them using the Microsoft Exchange ActiveSync, but it is still the same - only three months back on both BB devices.
As my other devices sync all events going back many years, and as there used to be an option within the old BB Desktop Manager to sync All Events, I am sure the restriction I now have must be a BB issue and not an Office 365 issue. Do you agree, and do you know where I can get to some settings that allow me to change the three month default?
Thanks.

Managing Office 365 Click to install with SCCM

Similar Messages

Maybe you are looking for