Cortana/Windows Search breaks in default profile
-
@csuther3 Wait you deleted the folders I mentioned or everything but the ones I mentioned. You were meant to the latter.
If this is a win 7 upgrade that may complicate things. You may need to take out just the pieces you need from the old profile to put them in a new one with the ntuser.dat registry hive using the load hive command @Quazz mentioned and then finding things like the task bar pins location and such.
You should be able to recreate just the profile in a fresh install of windows 10 and copy it over to the upgraded image. That should work too.
-
@Arrowhead-IT Sorry I misspoke, I kept the folders you mentioned and deleted the rest, but that didn’t change anything. I’m officially on vacation starting this evening, so I won’t get a chance to dig into this any deeper until I return. I’ll follow up at that time. Thanks for all your help!
-
I’ve been trying some stuff out regarding the taskbar icons and it’s frustrating to say the least.
It’s like windows either ignores or overrides the registry keys for the default user when you create a new user.
-
@Quazz arrowhead’s scripts do work. I can confirm this. The registry keys I mentioned about Win7 earlier in this thread are totally ignored by Win10 - I’ve already tried lol.
Microsoft takes one step forward, two steps back.
Their programmers are hard-coding values instead of using the registry that is ALREADY THERE! lol I hope someone from Microsoft reads this.
-
@Wayne-Workman So the script works for W7 and W10 default taskbar icons?
-
@Quazz Arrowhead’s scripts work for Win10. The methods I posted way back work for Win7.
-
@Arrowhead-IT can you make a git repo with your two scripts in it, with a read me and a GNU GPLv3 license?
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Arrowhead-IT @Wayne-Workman
I found some more interesting information on this subject: https://cwiki.apache.org/confluence/display/VCL/How+to+Configure+the+Windows+Default+User+Profile
They recommend deleting the shell items of the ntuser.dat if you copy it from a different profile.
-
@Quazz I’ve not done that, everything seems fine. I wonder what potential issues there could be? I’m not copying the default user’s registry entries, just the files I believe.
-
@Wayne-Workman Not sure what the copy profile thing actually transfers, but if ntuser.dat is part of it then that’s where the user’s registry keys are in.
You can test it by loading it in regedit and searching for the account it was transfered from.
I figure windows would alter that regardless upon account creation, though, so you may be right that it’s unnecessary.
-
@Wayne-Workman It seems like this is not necessary on Pro versions of Windows, but it is on Home Premium! At least that’s how my test situations have turned out so far. In Home Premium it seems to copy over literally everything and in Pro it is more clever about it.
-
@Quazz I’m sure Arrowhead wrote this for Pro/Enterprise. Makes sense.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!
Daily Clean Installation Results:
https://fogtesting.fogproject.us/
FOG Reporting:
https://fog-external-reporting-results.fogproject.us/ -
@Wayne-Workman @Quazz
Sorry I took an extra day on the long weekend and was out of town. Just seeing these posts.I will make a public git repo when I have a chance with these scripts.
I will also look into the deleting shell items from the ntuser.dat. I wonder what those hold.
The ntuser.dat is the registry entries, so you are copying a file that contains registry entries.
I did make it with enterprise and only enterprise in mind really. That’s all I use in a work environment. Granted, I imagine they could be adapted to work on the other versions.
-
@Wayne-Workman said in Cortana/Windows Search breaks in default profile:
@Arrowhead-IT can you make a git repo with your two scripts in it, with a read me and a GNU GPLv3 license?
@Tom-Elliott Say, could my github user be added to the fog project group so I can add this there?
-
The scripts are working fine. But my problem is that i want to use the default profile to use as mandatory profile. When i do that i get an error “the service Group Policy Client prevents logon”. What can i do about it?
Is there anyone uses Mandatory Profiles for Windows 10?
It’s for our environment. It’s a school with students. So we don’t want they can make any changes in the profile. That’s the reason we choose for a mandatory profile. -
@Twilems http://www.linuxgfx.co.uk/karoshi/documentation/wiki/index.php?title=Creating_a_Windows_10_Mandatory_Profile might help.
Basically you need to alter the registry key permissions and ownerships of the default ntsuer.man
-
@Twilems I work in a school as well. I’m not concerned about the students customizing what they are allowed to customize. A great deal of things are locked down via group policy, to include wallpaper, screensavers, themes, resolution, control pannel, access to the command prompt, numerous file extension screenings and rules, no access to the c:\ drive. However, if they want to re-arrange the tiles in the start menu I don’t care about that, also re-arranging or customizing the task bar icons, that’s fine with me. Maybe they have a good reason for it, maybe it makes their life easier.
-
@Wayne-Workman said in Cortana/Windows Search breaks in default profile:
@Arrowhead-IT can you make a git repo with your two scripts in it, with a read me and a GNU GPLv3 license?
I made the repo where they will go.
I was trying to decide whether I wanted to make one repo or a bunch for a few other fog-snapin/image prep type scripts.
For now it’s just the one repo. I’d prefer it to be in the fog-project group of repos, but it doesn’t have to be. I’ll link to the fog-project repos for sure though.https://github.com/darksidemilk/Create-and-Deploy-Windows-Default-Profiles
-
@Arrowhead-IT Just a fyi, you can modify it slightly to allow for spaces in share names/paths by putting quotation marks whenever the share variables are called. I tested this earlier and it works great.
Your script is pretty awesome
-
Yeah, this script was a life saver for me. It accomplishes SO much stuff that I’d otherwise have to set a TON of bloated Microsoft group policy for. I’m not scared of group policy at all, in fact I’m really good at it. But I’ve learned through experience that overall, less group policy is better group policy. So now I always always always try to find alternatives to it before using it. This script being a great example, fog snapins and printer management being another great example. Hell even startup scripts or login scripts are more safe than a pile of bloated group policy. Group Policy usually works, but it slows things down. I’ve ran extensive tests on this, recording times for different things, recording environment setups, making tables of results, and replicating results from scratch to confirm, for months on end (Scientific Method). Group Policy is always my last choice now.
