auto logon to roaming profile: computer is too fast , i get an error that the profile cannot be found

Question

_{Tuesday, November 29, 2016 12:37 PM}

Hello all, I'll hereby describe the situation: I am the help desk of a library, we configured our public computers to auto logon a specific user account .

they all use exactly the same user account, and everything works fine. ( those machines are all lenovo a540 machines) The profile is accessed via a dfs link,and logs on perfectly. After logoff the profile is deleted from the local disk. However, we have a few Intel nuc's with ssd and 8gb memory, and they always logon with a temporary profile. this is only when i startup the machine. If i logoff the machine and manually logon, the profile is loaded correctly. so this only happens if the machine is still in startup.

there is a gpo configured to wait for network. the windows version used is windows 10 build 1607

In previous windows 10 builds it is no problem at all, only the 1607 + intel nuc refuses to logon the correct profile at startup.

Does anynone here have a logical course of action?

With Kind regards,

Peter

All replies (4)

_{Tuesday, November 29, 2016 6:44 PM}

So"Always wait for the network at computer startup and logon" under Computer Configuration > Administrative Templates > System > Logon is set? Checked that gets set with rsop?

If so have a look at Windows 7 "Always wait for the network at computer startup and logon" group policy older thread but has some registry settings that may help.

_{Wednesday, November 30, 2016 12:19 PM}

Hey Mr Happy, 

thnx for the reply

but as so often, if i post my question on a forum, i almost always find the answer a  few hours later ......

My solution was to put in an extra startup delay.
the policy i used now is:
Computer Configuration > Administrative Templates > System > group policy > specify startup policy processing wait time 
with a value of 30 seconds extra

Now everything works fine, however the startup is delayed an extra 30 seconds ....
but that is within the acceptable tolerance

before this solution:
Wait for network was applied, but it still couldn't find the profile
i guess the machine is simply too fast?

_{Wednesday, November 30, 2016 6:29 PM}

So to me the machine is too fast with your chosen configuration, i.e. delete profile on logoff. Without that would work very nicely I would think.

_{Thursday, December 1, 2016 7:24 AM}

Hi,

I have feedback this issue in our platform.

BTW, I agree with Mr Happy and your consideration. According to your condition, have you tried to turn of fast startup?

http://www.tenforums.com/tutorials/4189-fast-startup-turn-off-windows-10-a.html

Please Note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does not guarantee the accuracy of this information.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].