Office 2016 on Windows 7, 10 or Windows 2012 and 2016 – No Internet connection to sign-in users to Office 365
We had a strange issue on our hosted environment on Azure with Windows 7, 10, Windows 2012 R2 and Windows 2016 RDS / Citrix servers. Users could not sign in to Office Pro with their Office 365 user credentials, to a batch of newly installed servers. They received the message when they start any of the Office applications (in the screenshots below I use Word):
We are unable to connect right now. Please check your network and try again later.
The next message users receive is:
UNLICENSED PRODUCT Most features are turned off because a shared computer license isn’t available.
As the message states: most features are turned off ๐
Shared Computer Licensing on RDS
We have installed Office 2016 with a Shared Computer License model as stated by Microsoft, to enable Office for multiple users simultaneously.
Our configuration.xml file does what it supposed to do, install Office silently, US and NL languages enabled and of course Shared licensing enabled:
<Configuration> <Add OfficeClientEdition="32" Channel="Monthly"> <Product ID="O365ProPlusRetail"> <Language ID="en-us" /> <Language ID="nl-nl" /> </Product> <Product ID="VisioProRetail"> <Language ID="en-us" /> <Language ID="nl-nl" /> </Product> </Add> <Display Level="None" AcceptEULA="True" /> <Property Name="SharedComputerLicensing" Value="1" /> </Configuration>
So this is not really spectacular and after installation of Office I have confirmed we have the Shared Computer Licensing activated (you can check this via Word – File – Account – About Word):
The solution
Well, in a nutshell, I have tried a lot… and found an issue under Network and Sharing center, I saw the message The service to detect this status is disabled.
When clicking the More information… you receive the following message: Do you want to turn on Network List Service. Well yes, turn it on, please…
So pressing the Turn this on button I received the following error message: The dependency service or group failed to start.
Ok, let’s start the Services MMC (WindowsKey + R, services.msc and OK).
Let’s open the Network List Service and look at the Depedencies. We see two dependent services if you look at the above screenshot you can see that the Network Location Awareness service is disabled! Now open the Network Location Awareness service and set the startup properties to Automatic. After pressing OK, start the Network List Service.
Now start Word and you can successfully connect to Office 365!
That’s all for today.
Regards,
Daniel Nikolic
Is interested in everything connected to technology. Has a passion for cloud, virtualization and software development. Always finds appropriate IT solutions for customers that match their needs strategically, technically and financially.
Core qualities
Quick thinker, result driven, ambitious, customer-friendly, enthusiastic
Hobbies
Running, listening to music, good food and doing fun things with family
Job description
CTO PepperByte, LoadGen, and BlueParq
Many thanks Daniel Nikolic. It was very helpful. Have been struggling for several weeks with this issue but you blog did it all.
I echo the words from Vikalp! Thanks a lot Daniel!
I just disabled an undefined “ethernet cable” and it worked after that. Thanks tho ๐
I can’t “like” this post enough, wow. So many suggestions out there on the internet that are completely useless. Thank you for your hard work and for sharing your solution… OneNote works like a charm now.
Many Thanks, this fixed a problem I was troubleshooting for a week.
Thank you, Daniel! This helped me too, and I’m very grateful to you for it. From my research while trying to solve this problem, it looks to me like you are the only one who posted the solution.
For anyone who’s curious, I have Office 2016 in Windows 7.
Thanks Tim, I have updated the article.
Daniel
Thanks
This fixed a problem.
For some reason I very rarely post on these sorts of things, but this problem has been plaguing me for several days . . . but I’ve been limping along. Today I started trying to resolve in earnest. My entire Office Suite was then made “unlicensed.” Your solution worked for me, and I am very grateful. Back up and running now! Thanks!
Thanks this one worked for me too.
Many Thanks Daniel.
I was struggling quite hard to fix this issue and Finally your post brought new year smile ๐
Thanks Daniel.
This fixed my issue.
I echo what everyone else has been saying. I have been racking my brain. Thank you.
A million thanks, my entire IT team failed to resolve this.
Thank you, saviour ๐ You saved me big time.
Thanks a lot.
Ohhh man I never comment on posts however you made me to do so. It worked like a charm however problem was created by me only I had disabled the windows event log service for some reason before and due to which this service was not coming up ๐
Thank you so much. Your explanation was very clear and it solved my issue.
works like a charm ! thanks!
Thank you so much!!! as a workaround i was using the online version of office.
This was exactly the fix I needed. Somehow this morning Office decided I had no internet connection, and it was because that service shut off silently. Didn’t even have any failed dependencies, it was just a transient failure.Thank you!
Thank you !! ๐
Thank you. This worked for me, although I did not need to follow the complete solution, I only had to go as far as turning on the Network List Service. This is a well-written and useful solution and I hope you leave it online for other users.
Thank you very much. I literally tried all solutions on the internet but it had not worked at all.
Finally I found your post and it works smoothly.
I got my head twisted troubleshooting this issue, and you saved me from twisting my head further.
Thanks a lot. Great job.
So pleased to have found your blog. We were about to halt our whole Office 365 rollout after trying all night and all day in vain to fix this problem.
Thank You
Awesome, thanks!
This solved my activation problem. Thank you!