Office 365 for Shared computer activation

By : Dom
February 2, 2017
Category : Deployment, Office 365
Tags: Office 365, XML

We have a server that many people remote into do some work. We can now install office 365 that can be used on this shared device and it is called Shared Computer Activation.

Serveral users can log into the machine and run office at the same time.

Shared computer activation gets enabled during the install. Once enabled, Office installs without being activated. When a user signs in to a computer with Office installed via shared computer activation, Office will check to see if the user has been provisioned for Office 365 ProPlus and temporarily activates Office 365 ProPlus. If a second user signs in to the same computer, the activation does not persist from the first user and process is repeated.

It’s also important to note that deploying Office 365 ProPlus using shared computer activation does not count against a user’s five total installations of Office 365 ProPlus or Office for Mac.

To install with shared computer activation you need to include 2 lines in your xml file:

<Display Level="None" AcceptEULA="True" /> 
<Property Name="SharedComputerLicensing" Value="1" />

1 2	<Display Level="None" AcceptEULA="True" /> <Property Name="SharedComputerLicensing" Value="1" />

The complete xml for our install which does NOT install InfoPath, OneNote and Publisher looks like:

<Configuration>

  <Add SourcePath="\\server\Office365_2016\" OfficeClientEdition="64" >
    

    <Product ID="O365ProPlusRetail" >
      <Language ID="en-us" />
      <!-- <ExcludeApp ID="Access" /> -->
      <!-- <ExcludeApp ID="Excel" /> -->
      <!-- <ExcludeApp ID="Groove" /> -->
      <!-- <ExcludeApp ID="Lync" /> -->
      <!-- <ExcludeApp ID="Outlook" /> -->
      <!-- <ExcludeApp ID="PowerPoint" /> -->
      <!-- <ExcludeApp ID="Project" /> -->
      <!-- <ExcludeApp ID="SharePointDesigner" /> -->
      <!-- <ExcludeApp ID="Visio" /> -->
      <!-- <ExcludeApp ID="Word" /> -->
      <ExcludeApp ID="InfoPath" />
      <ExcludeApp ID="OneNote" />
      <ExcludeApp ID="Publisher" />
    </Product>

  </Add>

  <!--  <Updates Enabled="TRUE" UpdatePath="\\Server\Share\" /> -->

  <Display Level="None" AcceptEULA="True" /> 
  <Property Name="SharedComputerLicensing" Value="1" />

  <Logging Path="%temp%" />

  <Property Name="AUTOACTIVATE" Value="1" />

</Configuration>

</Product>

</Add>

</Configuration>

No Comments

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

SIMILAR NEWS

Deployment

MDT – Joining a Computer to a Domain Using PowerShell

Using PowerShell scripts within a task sequence provides more flexibility than using the CustomSettings.ini file to join a computer to a domain. The parameters of the CustomSettings.ini file are common to any deployment you perform. That’s why creating a custom PowerShell script to join your domain will be customize to …

Deployment

Task Sequence Tasks Explained

This document explains the tasks that you will find in standard task sequence. Initialization > Gather local only – gathers deployment configuration settings from local sources that apply to the target computer [ZTIGather.wsf] Validation > Validate – verifies that the target computer meets the specified deployment requirement conditions. Such as …

Deployment

How MDT uses XML to install Applications

Have you ever thought about what actually happens when you import applications into your MDT environment? How does the task sequence know what application to install? How does it know what command-line arguments to specify during the application install process? Technically, as a user, all that is required of us …