Don't try to AutoActivate

Question

In our environment, we are not using ADFS.  Our windows domain is different from out email domain.  When we deploy office and a user opens it, in the user account info, it auto-populates with their AD Domain info.  This is confusing, as we have to have them log out and then log in with their correct information.  It would simplify the process if on deployment, no user information was entered at all and it just forced them to enter it the first time they went into office.  Is this possible at all?

Answer 1

Kerwin:

**1.**Does this issue occur to a non-domain added computer?

not sure if it does it with a non-domain added since the computer I'm doing it on IS domain added.

2. For the domain added machines, please try downloading and installing the Office suite from Office 365 portal to check if this issue happens.

This seems to defeat the purpose of deploying it using an xml file.

**3. Could you share with us the xml file you are using to configure the Office?**Certainly, this should be what it is:

onfiguration>

<Add SourcePath="\Server\Installpoint\Installers\Office2016" OfficeClientEdition="32" Branch="Current">

    <Product ID="O365ProPlusRetail">

      <Language ID="en-us" />

    </Product>

  </Add>  

  <Updates Enabled="TRUE" AutoUpgrade="FALSE" Branch="Current" />

  <Display Level="None" AcceptEULA="TRUE" />

  <Logging Name="OfficeSetup.txt" Path="C:\temp" />   

  <Property Name="FORCEAPPSHUTDOWN" Value="TRUE"/> 

</Configuration>

4. If it’s convenient, please try a simple network share between two computers to check if this issue will happen, this will help us identify if this issue is related to the 3rd party tool.

I'm not sure I understand the question here.  All that I am doing is essentially running setup.exe /configure configuration.exe.  The third party app is not doing anything that wouldn't be done locally.

5. Also you can check if there’s any related group policy about the Office is enabled for the windows domain.

There are no group policies enabled on these machines regarding office.

Answer 2

Hi Jwood.mls,

We haven't heard from you for a while. Could you let us know any updates at your convenience so we can provide any further assistance that is required?

Thanks,

Kerwin

Answer 3

Hi Jwood.mls,

Thanks for your clarify.

As you have mentioned you were using a 3rd party tool to configure Office suite, could you share with us the details about it so we can better understand the situation you met? To further investigate this issue, please also help us clarify the following information:

1. Does this issue occur to a non-domain added computer?
2. For the domain added machines, please try downloading and installing the Office suite from Office 365 portal to check if this issue happens.
3. Could you share with us the xml file you are using to configure the Office?
4. If it’s convenient, please try a simple network share between two computers to check if this issue will happen, this will help us identify if this issue is related to the 3rd party tool.
5. Also you can check if there’s any related group policy about the Office is enabled for the windows domain.

Thanks,

Kerwin

Answer 4

Kerwin,

I am deploying using a 3rd party tool, but also using the configure option with some .xml files configured (I believe using the ODT as you said).  However, the first time the end user uses office, it has already populated the user info in the upper right with their domain username, and I would prefer it not do this.

Answer 5

Hi Jwood.mls,

To investigate this issue, could you let us know how did you deploy the Office? For example, if we download and install the Office suite from the Office portal page, after the Office suite is installed, actually the Office application is already activated, when we open the Office applications, it’s just a sign in process.

About your requirement to disable auto-activate and let user enter their account information in the first time to activate the Office applications, I suggest you consider using Office deployment tool (ODT). After you downloaded the Office suite via ODT, you can put the Office suite on the network share or deploy the Office via Group policy as you like:

Download Click-to-Run for Office 365 products by using the Office Deployment Tool

Overview: Office Deployment Tool

Supported deployment methods for Office

Thanks,

Kerwin