Unsolved

This post is more than 5 years old

1307

June 25th, 2018 10:00

Office 2016 Provided by Dell Won't Work With Standard Window

When I setup a new Windows 10 Pro machine from Dell that comes with the Click2Run pre-installed version of Microsoft Office 2016 Home & Business I run into a problem once I join the domain and try to use Office with a standard (non-administrator) user.

Setup of Office is done normally with a local administrator account during pre-configuration. Then I join the domain (so far I've tried this on a Windows 2008 domain) and login as a standard user. When you open the start menu, no Office icons are available. In fact, I couldn't even find/launch Office manually in Program Files. It's like it just isn't there at all. Login as an administrator on the domain and everything appears and functions normally.

I've been in touch with Dell about this and the best they can tell me is there is some server/GPO setting that needs to be enabled, but I can't find anything about this. It's bizarre. Any help would be appreciated.

8 Wizard

 • 

17.1K Posts

June 25th, 2018 23:00

The thread is here:

https://dell.com/community/Optiplex/OptiPlex-7050-Windows-10-after-login-black-screen-with-mouse/m-p/6068092/highlight/true#M24187

It would be interesting if you updated machines to v1709 (or higher) and it still isn't working because it was supposedly a Microsoft problem (even though it only appeared on Dell's OEM factory software load) and a patch was released.

https://dell.com/community/Optiplex/OptiPlex-7050-Windows-10-after-login-black-screen-with-mouse/m-p/6071365/highlight/true#M24294

June 26th, 2018 08:00

Thanks for your reply, @Tesla1856. I'm not sure this is the same issue. I'm not having any black screens (although I did have issues with Office and other apps hanging for several minutes at a time on 7050's). My issue is that the shortcuts/program files aren't available at all to domain users unless they are administrators.

I installed one affected machine in late March and it had all of the most recent Windows updates applied when the issue occurred.

The only solution I've found is to do the following, but it adds about an hour to each machine's setup time:

  1. Activate the license using the Click2Run pre-install. Note which one it is in the Microsoft account.
  2. Remove the C2R version.
  3. Download the installation file directly from Microsoft and re-install.
  4. Hope that the license key will still function properly since you can't be sure which one you're choosing from their vague list.

This is far from ideal, obviously. Any further thoughts?

8 Wizard

 • 

17.1K Posts

June 26th, 2018 12:00


@jcarter_unison wrote:

0. I'm not sure this is the same issue. 

  1. Hope that the license key will still function properly since you can't be sure which one you're choosing from their vague list.

This is far from ideal, obviously. Any further thoughts?


0. Me either, it just sounds very similar and related.

1. Right. After that initial (local) redemption, we write-down the first 5 of Product-Key (so it can be matched-to later if needed).

I hope you read ALL my posts in that thread.

8 Wizard

 • 

17.1K Posts

June 27th, 2018 11:00


@jcarter_unison wrote:

I read all of your posts and most of the others. Not seeing anything there that changes my concerns since my previous post here. What am I missing?


Well first, have you tried applying the described patch manually?

Second, it only takes about 30 minutes to clean install Windows-10 Pro 64bit. Maybe even faster if machine has a bootable C: SSD (which it should these days ... so much faster, dependable, and even inexpensive now).

After it finishes, you just access the Microsoft Account (where you already redeemed the Office-2016 license) and simply install it fresh.

A couple of hours work this afternoon and you are done.

 

4 Operator

 • 

20.1K Posts

June 27th, 2018 11:00

If you are a member of a domain you have to use the MSI installer instead of click to run.

This might explain--

https://support.office.com/en-us/article/Office-installed-with-Click-to-Run-and-Windows-Installer-on-same-computer-isn-t-supported-30775ef4-fa77-4f47-98fb-c5826a6926cd

June 27th, 2018 11:00

I read all of your posts and most of the others. Not seeing anything there that changes my concerns since my previous post here. What am I missing?

No Events found!

Top