Windows 10 search issues.

[ICT_GUY]

Random users are having the issue where when you search for applications in the search bar nothing comes up or no local applications.

 

Any idea whats going wrong?

 

We having roaming profiles, build 1803 with all updates.

 

Reenabling windows firewall and doing a gpupdate + reboot fixed the issue for a couple of users but not others.

 

pls help!

[ICT_GUY]

A different user on the same machine and it all works, so this seems to be a corruption in the profile. Though it is inconsistent as a reboot on other users sometimes clears it.

 

This is driving me insane.

[skell]

I think your problem will be roaming profiles. They are no longer supported or recommended by Microsoft. I would suggest moving across to UE-V

 

https://docs.microsoft.com/en-us/windows/configuration/ue-v/uev-for-windows

[ICT_GUY]

Ok, this would explain a lot of the issues that we have been having.

 

Anything I should know beforehand or is it a question of just implementing it as per the instructions? :-)

[skell]

Have a think about the programs you want to have settings roam for. We have XMLs for Chrome, VLC, Office, Adobe Reader and other things.

Decide where you want to store the settings for the users. We put them back into their redirected root folders.

You'll need to enable it in Windows 10 - we do this when the computers are imaging via SCCM.

 

Other than that, its pretty straight forward, but I would test thoroughly. Its a great piece of tech, reducing login times here to around 15 seconds on SSDs. First login between 30 and 60 seconds.

[ICT_GUY]

Currently we use WDS for imaging. We have only just moved over to windows 10 and eliminated widows 7from the network. We have approximately 200 pcs in a primary school.

 

I am aware of SCCM and it was on the books to be looked into but I have zero experience with it. With this in mind do you have any advice as to where to start? The system works atm, most of the time but logon speeds for the laptops are terrible, something UE-V looks like it will solve.

 

What do I need hardware and software wise and an idea of the amount of head aches I might encounter and maybe timescale would be really helpful. Also how disruptive would it be to implement on a live system.

 

Sorry for the vagueness of the question, I am just trying to get an idea of what lies ahead and how painful its going to be to get working.

[skell]

It took me a couple of weeks of testing, but I was working out the Windows 10 build at the same time, so if you're just concentrating on UE-V, I would expect it to be quicker.

 

There will be a Powershell command that you can invoke on your PCs to enable UE-V. Off the top of my head it would be something like

 

Invoke-Command -ComputerName {name} Enable-Uev

 

The act of getting UE-V working shouldn't be disruptive. Implementing it might be tricky as everyone will lose their settings in the switch over. With summer coming up, this might be less of an issue.

[Arthur]

There will be a Powershell command that you can invoke on your PCs to enable UE-V.

UE-V can also be enabled through Group Policy...

 

https://gpsearch.azurewebsites.net/#13467

[Rawns]

I think your problem will be roaming profiles. They are no longer supported or recommended by Microsoft. I would suggest moving across to UE-V

 

https://docs.microsoft.com/en-us/windows/configuration/ue-v/uev-for-windows

 

Is there any article/page that officially states Microsoft do not support/recommend with Windows 10? I've seen a few posts where people have said this, but can;t seem to find anything solid from MS saying this is 100% the case...

[Arthur]

Is there any article/page that officially states Microsoft do not support/recommend with Windows 10? I've seen a few posts where people have said this, but can't seem to find anything solid from MS saying this is 100% the case...

 

Source: https://social.technet.microsoft.com/Forums/en-US/9a6427b9-571f-4255-afa4-5e91b9f1cb70/folder-redirection-deployment?forum=win10itpronetworking#9ccd2f2a-24b2-45d2-bab6-53bfa8ac9754

 

 

Also:

 

https://docs.microsoft.com/en-us/windows/configuration/start-layout-xml-desktop

 

 

And:

 

https://blogs.technet.microsoft.com/yongrhee/2018/03/12/windows-10-using-copyprofile-for-the-start-menu-has-been-deprecated/

[Rawns]

Thanks @Arthur

[Arthur]

We having roaming profiles, build 1803 with all updates.

Have you added the 'SpecialRoamingOverrideAllowed' registry value? A lot of people still using roaming profiles seem to forgot to add it and consequently experience issues with the Start Menu.

 

https://blogs.technet.microsoft.com/askpfeplat/2017/05/08/mysteriously-disappearing-start-menu-tiles-and-roaming-user-profiles

 

Per the Deploying Roaming User Profiles there is a new step to using Roaming User Profiles in Windows 10, which is Step 7. You need to enable the SpecialRoamingOverrideAllowed key for the Start menu to display and work correctly. I didn’t pick the name for the registry key, I just work here. Below are the steps mentioned in the hyperlink. It does state mandatory start menu layouts; however, if you are not using mandatory start menus, you can still test it out in a DEV environment and make sure it works for you. This registry key of course can be deployed via GPO, set in your base image, or baked into your master VDI. I personally like the GPO option because it allows me to centrally control it, but, it is up to you how you want to deploy it.

 

Btw, are you aware of the following issue with roaming profiles and Windows 10 v1803?

 

"Roaming profile was not completely synchronized" error and logon, logoff delays on Windows 10 Version 1803

 

On a computer that's running Windows 10 Version 1803, you experience logon or logoff delays when you use roaming user profiles. You also receive the following error message:

 

Your roaming profile was not completely synchronized. See the event log for details or contact administrator"

 

Cause

This problem occurs because of a change that was made in Windows 10 Version 1803. This change inadvertently caused folders that are ususally excluded from roaming to be synchronized by roaming user profiles when you log on or log off.

 

Status

Microsoft is researching this problem and will post more information in this article when the information becomes available.

 

Workaround (courtesy of this Reddit post)

 

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon]
"ExcludeProfileDirs"="AppData\\Local;AppData\\LocalLow;$Recycle.Bin;OneDrive;Work Folders"

[Rawns]

Have you added the 'SpecialRoamingOverrideAllowed' registry value? A lot of people still using roaming profiles seem to forgot to add it and consequently experience issues with the Start Menu.

 

https://blogs.technet.microsoft.com/askpfeplat/2017/05/08/mysteriously-disappearing-start-menu-tiles-and-roaming-user-profiles

 

 

 

Btw, are you aware of the following issue with roaming profiles and Windows 10 v1803?

 

"Roaming profile was not completely synchronized" error and logon, logoff delays on Windows 10 Version 1803

I was not aware of the known issue (or the Win 10 specific reg key)! Thanks for pointing them out.

 

As a work around, we have been manually excluding Local and LocalLow via a GPO, but it's a bit of a pain to fully implement as you need to delete the Local and LocalLow folders from the server profiles with the users logged off, otherwise they continue to sync as they already exist despite the GPO being applied.

Edited June 29, 2018 by Rawns