How To Configure Roaming Profile In Windows Server 2012

What is the difference betwixt a profile and a roaming profile, y'all might ask yourself? Well, a profile is a folder that contains all the settings pertaining to a user'due south working environment. Past default, the profile is stored in the C:\Users directory.

A roaming profile, on the other hand, is stored on a network  instead on the local drive of the motorcar where y'all are logged. A Roaming profile is cached locally by default. The advantage of a roaming profile is that a user can log into any machine in the domain and accept a consistent working environs.

A contour has two types of content:

• Files and folders
• NTUSER.DAT

The concept of a roaming profile is that the user's profile is stored on a file share, and it is downloaded from the file server whenever a user logs in, doesn't matter on which machine. It is buried in C:\Users on the computer that the user is logged into.

When the user is logged out, the content changes of the profile are saved back to the file server.

OK, lets try to configure roaming profile share.

Also check: Uptime of the server with PowerShell

Creating a Roaming Profile Share

First, you lot need to take a file server, right? Correct. And that server should be in a domain environment. Right? Right.

Create a folder called R_Profiles in Eastward:\Shares:

Once you lot have created a new folder, you should disable the inheritance of permissions on the folder. Why, you lot might ask? Well, we will store all our future profiles in this folder, and if every user which volition exist created inherit the permissions from the parent folder, everyone volition accept the same permissions, and I believe you don't want that.

Then, information technology is better to disable inheritance, and instead of that, we make up one's mind the level of permissions for every user.

Get out Authenticated users, Creator Owner, Administrators, and System group, simply similar in this screenshot which I accept taken:

With this being washed, lets go to File and Storage Services and share the R_Profiles folder.

Likewise cheque: Deploying features and roles on remote servers using PowerShell

Open up Server Manager > File and Storage Services > Shares > Tasks > New Share…

Cull SMB Share – Quick (nosotros gonna do the easiest way now) and striking Side by side:

On next page, select the server and the place where the profiles will be (in our instance choose the last option "Type a custom path"):

Specify a share name, local path to share, remote path to share, and description if you want:

On a 'Specify permissions to command access' folio, click the customize permissions… button to configure the permissions:

When the Advanced Security Settings for R_Profiles opens, click on Share tab, remove Everyone group, and add administrators group (Total control) and Authenticated Users group (Change):

Ostend the configuration and click Create:

Creating a Namespace

Now, once nosotros take finished with the creation of the share were the roaming profiles volition be shared, lets make the profile share bachelor in the DFS namespace (make sure that you have DFS Namespaces installed). By using DFS namespace, yous will be able to replicate the folder or move information technology when yous demand to.

Also bank check: Installing Agile Directory

Alright, later on y'all accept installed DFS Namespace, open up the console:

Once the console is opened, right-click on 'Namespaces' and choose 'New Namespace…'

Choose the server that volition host the namespace. You can write it in the box, or you tin choose the 'Browse' button and search the domain for the server – whichever suites you improve.

On the next page, enter Proper name for the Namespace, for example 'Profiles', and cull 'Edit Settings' push, to configure the Namespace:

Hit the 'Browse' button and cull the binder on E: drive which we have created previously – R_Profiles.

For the permissions, choose the terminal choice, 'Employ Custom Permissions', remove Anybody group, add Administrators group (Total Control), and Authenticated users group (Change).

As well check: Features on Need in Windows 2012 R2

It is going to be a domain-based namespace (you tin can read the clarification, no need to explicate anything as information technology is self-explanatory)

On next page, review the settings and later on that, striking the 'Create' button.

And that is it. Namespace has been created.

Exam the Connexion to a Roaming Profile Share

Lets bring our Windows x Client machine and try to access this namespace (you can employ whatsoever server/customer which is in your domain).

In the Run box, type \server01\Profiles – you lot should be able to access share:

If you lot can't access the share (doesn't exist, or information technology is asking you to enter admin credentials), go back and check everything twice to exist sure you didn't skip whatsoever step.

Now, go to Active Directory Users and Computers > Users container > pick i account > right-click and cull Properties > Profile tab.

Also check: Installing Windows Deployment Services on Windows Server 2012 R2

in 'User Profile' section, in 'Profile Path' box, type the full network share path: \server01\Profiles\rusty

In 'Domicile Folder' department, cull 'Connect', enter the desired bulldoze letter and full network share path: \server01\Profiles\Rusty

So, lets try. Login with your user account to your Client machine and try to access your share. You lot should be able to see folder with the name of your account:

And you should also exist able to see the DFS share when you open file explorer/windows explorer:

Source: http://www.vladsitblog.com/creating-a-roaming-profiles-share-in-windows-server-2012-r2/

Posted by: gentryshom1981.blogspot.com

Share this post