none
2016 Essentials and Office 365 accounts RRS feed

  • Question

  • Hi,

    I'm very new to server setup and management and confused about how to give access to the new server shares on our new, and only, server.

    Before:

    Small office with 8 office 365 accounts.  All PC's just log in with their office 365 credentials to win windows 10 pro PC's.  At this point our office network is just peer-peer, no server, all authentication and email is done via office 365 cloud accounts

    Now- I've installed server 2016 essentials on a new box with the intention of using it for some shared space and a continuous integration and test system.

    - Installed 2016 - set up a domain called "PRECISON"

    -Did the office 365 integration steps

    - imported accounts from cloud services.

    (at this point a new list of temp passwords was created and the server said users would need to use those to log in and then change them)

    Now I'm stuck - all our work pc's still just log in via their normal office 365 credentials.  I tried to change one computer's identity from workgroup  WORKGROUP to be on the domain PRECISION, but no AD controller is found.

    Server (and of course the shares on the server) don't show up in anyone's network browser on the win 10 pc's

    If I try to use the name directly in an explorer window -- e.g. \\SERVER  it asks for credentials, but using the account name and password provided in the generated list doesn't work and neither does using a office 365 account login/pw pair.

    How do I get the shares accessible?

    Should the users in the office be logging in to the server?

    I tried using the suggested method of going to http://server/connect  on a client pc, but that resulted in "unexpected error" and failed.

    Any ideas?  Nothing seems to "just work" anymore.

    DR

    Wednesday, September 26, 2018 11:59 PM

All replies

  • 1 "at this point a new list of temp passwords was created and the server said users would need to use those to log in and then change them"
    Because of the way password synchronization works in Essentials, when we create or match user accounts, we basically need to reset their password in order to trigger a password synchronization to Office 365. Hopefully something that will be improved in the future.
    Step by Step How to Deploying & Configuring Server 2016 Essentials with Office 365
    https://newhelptech.wordpress.com/2017/08/04/step-by-step-how-to-deploying-configuring-server-2016-essentials-with-office-365/

    Manage Office 365 in Windows Server Essentials
    https://docs.microsoft.com/en-us/windows-server-essentials/manage/manage-office-365-in-windows-server-essentials

    2 I tried using the suggested method of going to http://server/connect  on a client pc, but that resulted in "unexpected error" and failed.
     1 check the preferred DNS address is 127.0.0.1 on server 2016 essentials. (like picture 1)
       check the alternate DNS address is your isp DNS
     2 check if you had disabled the ipv6 on win10 computer and poit preferred DNS address to server essentials ip address .(like picture 2)
     3 try to use http://servername/connect in brower on win10 and download "computer connector" then is

    Get Connected in Windows Server Essentials
    https://docs.microsoft.com/en-us/windows-server-essentials/use/get-connected-in-windows-server-essentials

    BEST REGARDS
    Andy YOU
    Please remember to
    mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.







    Friday, September 28, 2018 8:37 AM
    Moderator
  • Hi Andy,  Thanks for the response - the TCP config on the server did not have the ISP dns set as  the alternate, so I corrected that.  I am not sure exactly what you mean with the other suggestions - Should the IPv6 be enabled on the client computers or not?  It is currently. 

    The dns on the client PCs is currently set to "obtain automatically" which I suppose is supplied by our office router (NAT device) that is connected to the ISP.  Do you suggest that preferred DNS should point to the server 2016 ip now? Alternate should just be blank?  

    DR

    Monday, October 1, 2018 5:25 PM
  • ..also,  I found a bit in the docs regarding connecting without joining the domain.  The suggested procedure here was to upgrade the client's account on the server to admin status (!).  I did this for myself and the connect almost completed, (near the end it said "You're connected!") but it did not actually set up icons for launchpad etc.  I then found the .exe for Launchpad and with it I can see shared directories.  

    I very much don't like having to upgrade each account to admin - there must be a better way.

    Monday, October 1, 2018 6:32 PM
  • Please do NOT disable IPv6.

    I have many customers using essentials 2016 and in one place I disabled IPv6 and all hell was loose until I enabled it again.

    :)

    Monday, October 1, 2018 11:32 PM
  • Hi all -- I would love anyone to chime in here if they can assist!  

    We are still stuck with users unable to connect.  The above process is still failing with "unexpected error"  - elevating users to Admin for the connect process doesn't seem to work.  I was able to connect one person, but I have no idea why one pc succeeded and others did not.

    Quite frustrated with MS on this.  Tech support want $500 for one incident of support.  It would also be great if anyone has a success story where things did just work out of the box.  Please share if so. 

    A little new info - once the process ends with the error message the user will now be shown on the server to have access to the shared folders (as listed in the properties/sharing dialog for a folder), but will not actually be able to connect to it.  AND while the Launchpad software is on their pc, it won't start.

    hmm..

    Tuesday, October 9, 2018 6:30 PM