Jump to content

Recommended Posts

Posted

I've started to receive this on Windows 10 PCs when users login whether it's admin or a normal user...any ideas?

The error message detail doesnt help much!

 

wiin10.png

Posted

Having sussed the issue it seems there are some forums about it.

When using SSDs (not as common on HDDs) it seems when users log on or log off, the server with the roaming profiles on is keeping files locked including the ntuser.dat hence the reason it says in use.

When rebooting a machine if the files are in use still and showing as open on the server next time they login they get a temporary file.

If you close the client session to the server and login, the usr logs in fine.

 

Doesnt seem to be a cure right now, although a website says its recommended to use 2016 with v5 profiles but is there even a way to direct v2 (win 7 profiles) to a different server to the windows 10 v5 profiles?

 

Here's a forum link

https://social.technet.microsoft.com/Forums/en-US/ba54df5f-4356-4cee-b724-303aaad51266/file-locks-persisting-after-shutdownrestart-causes-serious-roaming-profile-redirected-folder?forum=win10itprogeneral

Posted
Not sure if this link will be helpful to you or not.

 

https://technet.microsoft.com/en-us/library/jj649079%28v=ws.11%29.aspx?f=255&MSPPError=-2147217396

 

I was under the impression that Microsoft was deprecating roaming profiles in favor of UE-V. I could have misread something though.

 

i had seen it mentioned but roaming profiles should still work in windows 10.

Strangely enough I contacted my MS Agreement reseller for a contact at microsoft and they said they have exactly the same issue.

Been advised to call MS and log a ticket as is easy to replicate

Posted
Did you hear anything back from Microsoft? Also, just curious which flavor of Windows 10 you are using, Windows 10 Enterprise? 1607 build or something else?
Posted
Did you hear anything back from Microsoft? Also, just curious which flavor of Windows 10 you are using, Windows 10 Enterprise? 1607 build or something else?

 

I haven't had change to give them a call yet, it's still on my to do list.

We are running Windows10 Education x64 Version 1607 Build: 14393.693

Posted (edited)
did or have you set ""Delete cache copies of roaming profile" this will cause this in windows 10. v5 profiles will be saved next to v2 profiles they remain separate. Edited by victory2015
Posted
did or have you set ""Delete cache copies of roaming profile" this will cause this in windows 10. v5 profiles will be saved next to v2 profiles they remain separate.

 

Yes I know they remain separate but in same folder. Yes I do have that policy set, always have done. However, as I thought it was a policy issue I blocked inheritance from all policies and it still did it, so know its nothing to do with that policy setting.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...