Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Art Saffran

Post 2003 to 2016 Essentials Questions

This user is a subscriber. Click on the logo to get your own subscription
  1. After adding Server 2016 Essentials to a 2003 Standard domain and making it the DC, I added all the computers using the Connector. Users and computers appear in the Dashboard and AD. On the 2003 server, there was a share named Users to which each person had personal access. When I create a new user on 2016, the user gets such a folder in c:\server folders\users. I want to move all the User folders from 2003 and give the same user access security. Is there a way to do this without manually re-creating security for each folder?
  2. There are three XP computers at the client site. Is it possible to add them to the 2016 server? They will be upgraded soon but for now need access to the database and some files. How can they be added? Remove from the domain and then add again?
  3. The Redirected Folders seem to give access to all Domain Users. What rights should be on the Redirected Folders and what on each of the folders in that share? It looks like the rights are inherited from the Redirected Folders level rather than being explicit.
  4. I tried to add DHCP as a role to the 2016 server but it errors out and fails after starting the installation. Is this because the 2003 Server is the DHCP server?

Thanks.

-Art

asked11/23/2017 02:10
936 views
Add Comment
Last Activity 12/10/2017 08:26

1 Answer(s)

  • Mariette Knap

    Hello Art,

    Here are the answers to your questions.

    1. If you need to move the Users Shared folders please read this How to move the default location of the server folders in the Dashboard on a new hard disk or partition. Migrating user data from the 2003 server to the Windows Server Essentials 2016 cannot be done with DFSR because the 2003 does not support that. Best way is to use either robocopy with "ROBOCOPY "\\servername\sharelocation" "\\newservername\newsharelocation" /MIR /SEC /LOG:location:\nameoflogfile" or use a commercial tool like Syncback.
    2. Those XP clients are already in your domain if they were previously joined to the domain when the 2003 server was your only DC. There is no need to join them again but using the Connector software will not work because anything older then Windows 7 is not supported. This means you will not be able to manage those XP clients from the dashboard.
    3. The Folder Redirected folders do not have permissions by default that would make it accessible for all users. If you create a user on the new server and log in to a workstation with that user's credentials a folder with the name of that user is created and that should only be accessible by that user. If something else happens then something is wrong.
    4. Migrating the old scope to the new server is for a small organization not really a good idea. It is much easier to stop and disable the DHCP server on the 2003 server and install and configure DHCP on the new server. Read this guide for installing DHCP How to install the DHCP Server role and configure a DHCP scope on a Windows Server 2016 Essentials (TP3)
    answered 11/23/2017 05:47
    Add Comment
    Art Saffran

    In reference to my question #3: New Redirected Folders seem to respect user rights properly however, Redirected Folders on the new server that appeared after running the Server Connector, do not appear to restrict access to other users. Security rights for the Folder Redirection folder are:

    • SYSTEM -- Full
    • Domain Admins -- Full
    • Domain Users -- Read & execute, List folder contents, Read
    • Administrators -- Full

    The rights are inherited by folders under Folder Redirection. When I tested using a standard User logon, I was able to browse other user's folders. I will be connecting a new user computer Friday morning and will test to see how their Folder Redirection folder appears. I will post an update.

    Thanks.

    --Art

    Mariette Knap

    Yes, sometimes this happens and that is because permissions of the old shares on the 2003 server allowed this. Did you migrate those files and folders with Robocopy?

    replied 11/24/2017 10:39
    Reply
    replied 11/24/2017 02:40
Add an Answer