New
#460
Windows 10 Pro Build 1607 // broken Search // MS Apps
Hi Chris,
Here is what we do (*also from a college using W10Enterprise builds 1507 and 1611):
First, from a FRESH install, we go directly into AUDIT MODE
- Unpin ALL apps from the start menu
- Install all programs (Office, etc...)
- pin OUR apps (Categorized by group i.e. Internet, Office, Intranet)
once the start menu looks like we want it to, we then launch PS in elevated (admin) mode and run these scripts:
Export-StartLayout -Path C:\Temp\LayoutModification.xml
Export-StartLayout -Path C:\users\administrator\appdata\Local\Microsoft\Windows\Shell\layoutmodification.xml
Followed by:
Import-StartLayout -LayoutPath C:\Temp\LayoutModification.xml -MountPath $env:SystemDrive\
THEN, using Windows Imaging and Configuration Designer, import layoutmodification.xml into a provisioning package project, sellect Common to All Windows Desktop Editions, click on Runtime Settings, Start, Start Layout, export the package, add it to a folder on your imaging machine that would be deleted in SCRIPTS and RUN the package (you only need to do this ONCE and accept the pop-up about coming from a trusted source) - this has NOT failed (yet) to maintain our start menus for staff as well as (different) menus for PUBLIC use.
Next, to "fix" the search function, first go to CONTROL PANEL, INDEXING OPTIONS, MODIFY and expand the C:\ drive, add check marks to PROGRAM FILES and PROGRAM FILES (x86) (USERS should already be checked) once again using PowerShell in an elevated mode, run this script:
Get-AppXPackage -Name Microsoft.Windows.Cortana | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
(If you get the RED ERROR codes saying that Cortana needs to close, just wait until it dies a "natural death" - about a minute or so and re-run the command).
Gives this command about 30 seconds to complete and then check to make sure the search works in AUDIT mode (start typing WORD and it should show you MS WORD as a result AS WELL AS WORDPAD).
We also include a CMD file located in the %windir%\setup\scripts directory (SETUPCOMPETE.CMD) that removes ALL instances of your UNATTEND.XML file as well as activates our W10 via our SKMS server - it also removes ALL traces of the default start menu from MS.
rd C:\Users\Default\AppData\Local\TileDataLayer /q /s
rd C:\Users\Administrator\AppData\Local\TileDataLayer /q /s
del /Q /F c:\windows\system32\sysprep\unattend.xml
del /Q /F c:\windows\panther\unattend.xml
cscript //B "%windir%\system32\slmgr.vbs" /skms ###.###.###.###
cscript //B "%windir%\system32\slmgr.vbs" /ato
icacls %userprofile%\appdata\locallow /setintegritylevel (OI)(CI)L
icacls %userprofile%\appdata\locallow\microsoft /setintegritylevel (OI)(CI)L
icacls “%userprofile%\appdata\locallow\microsoft\Internet Explorer” /setintegritylevel (OI)(CI)L
*** CREATE THE IMAGE NOW ***
Run your SYSPREP with your UNATTEND FILE (we use the COPY PROFILE=TRUE without issues).
After a DOMAIN ADMINISTRATOR first logon (to activate windows and join our domain), RECHECK the start menu (should be same as your image) and the search feature (should work without issues).
From this point, all subsequent logons WILL work properly.
We've been successful with this setup with laptops and desktops of different configurations including some using standard drives, some with SSD as well as Hybrid drives.
(Please note that in ALL our images, the DESKTOP shortcut in the QUICK ACCESS file explorer still points to the ADMIN account, I have yet to get this issue resolved).