New Server 2016 Deployment - W10 Clients Logging in with temporary profiles

[talksr]

Hi, not sure where I am going wrong here. This is a vanilla install.

Followed this guide:

https://technet.microsoft.com/en-us/library/jj649079(v=ws.11).aspx

 

My roaming user profile sec group is AdminStaffGroup.

I have the following configured for my Profile$ share folder:

[ATTACH=CONFIG]41900[/ATTACH]

 

The profile path for my test user is as follows: "\\BGF-SR-003\Profile$\%username%"

 

When the user logs in, they are given a temporary profile.

 

The event viewer is showing the following:

 

[ATTACH=CONFIG]41901[/ATTACH]

 

[ATTACH=CONFIG]41902[/ATTACH]

 

Any ideas on where I could be going wrong? - Yes the test user is a member of the AdminStaffGroup!

Edited March 2, 2017 by talksr

[talksr]

Hi, not sure where I am going wrong here. This is a vanilla install.

Followed this guide:

https://technet.microsoft.com/en-us/library/jj649079(v=ws.11).aspx

 

My roaming user profile sec group is AdminStaffGroup.

I have the following configured for my Profile$ share folder:

 

The profile path for my test user is as follows: "\\BGF-SR-003\Profile$\%username%"

 

When the user logs in, they are given a temporary profile.

 

The event viewer is showing the following:

 

 

 

Any ideas on where I could be going wrong? - Yes the test user is a member of the AdminStaffGroup!

Edited March 2, 2017 by talksr

[Nausing]

Is your profile path %username or %username%?

 

can you show the permissions for the security group on that share?

[Nausing]

Is your profile path %username or %username%?

 

can you show the permissions for the security group on that share?

[talksr]

Is your profile path %username or %username%?

 

can you show the permissions for the security group on that share?

 

It was %username%, that part of things was working well. Not sure if it was just a permissions fault. I deleted the share and re-did it, so far it is behaving. I will create a couple of new accounts on AD and just double check.

[talksr]

Is your profile path %username or %username%?

 

can you show the permissions for the security group on that share?

 

It was %username%, that part of things was working well. Not sure if it was just a permissions fault. I deleted the share and re-did it, so far it is behaving. I will create a couple of new accounts on AD and just double check.

[bze2007]

the share is d:\shares\profiles$ shouldent it be \\servername\shares\profiles$ ?