KACE Product Support Question

Customize Windows 10 Default Profile, Particularly Desktop and Tiles for Mass Deployment?

09/10/2017 3329 views

Hey Folks,

I am pretty new to imaging processes and Kace. I have read a lot of posts and done plenty of research but I am still struggling to customize the Windows 10 default profile for domain users after system deployment. I have seen many different suggestions and some saying it cannot be done.

Essentially, the objective is to customize the start tiles with common apps and shortcuts on a reference machine using Hyper V, have this reference copied to the default profile during sysprep and capture the image. Furthermore, have this customized tile menu available for all domain users on subsequent deployments using this image. I have played around with copying profiles, appdata, permissions etc and have yet to get it how I would like it.

I use an unattend.xml file using the Kace Sysprep builder with the 'Copy Profile' option checked for Sysprep. but this only seems to affect built in or local users and not domain users in my case of testing.

Has anyone else been successful with this scenario and can shed some light on the correct strategy for this?

Any help is greatly appreciated.



0 Comments   [ + ] Show comments


All Answers

This content is currently hidden from public view.
Reason: Member has been banned from the site For more information, visit our FAQ's.
For the local account,  'Copy Profile' works fine.

To customize domain accounts (Taskbar icons, tiles, colors, fonts, even wallpapers) is better to go with GPO.

Answered 09/11/2017 by: Channeler
Red Belt

  • Thank you. I actually stumbled upon something and tested this using a local policy on one of the machines and worked well. However, the tiles were unable to be unpinned from the tile/start menu. They could however be pinned/unpinned if I did a manual search in the all apps list. Have you seen this?
    I read about a bit and some suggest it's how the policy works, but also that it could be a bug given there was a workaround to remove them by searching,
you may have to be careful with this, as MS are changing how the StartMenu and Tiles are working.
I have a standard load of apps that are install on all machines, and I (using SCCM and a script) overwrite the existing XML file during deployment. This is for the 1607 LTSB. In the recent release MS are moving away from the XML file...
As you do not state what Win10 version (sic) you are using you may need to adjust...

Answered 09/11/2017 by: Pressanykey
Red Belt

  • Hi, interesting, Do you have any URL to read about this? Are you referring to the unattended xml file?
    • Hi,
      no, I read somewhere (I had a look but can't remember where I read it) that MS are moving away from the XML file for the start menu entries.. I'll keep looking to see if I can (re)find the reference...
 found the link... 

Tile Data Layer (depreciated)

Answered 09/12/2017 by: Pressanykey
Red Belt

  • My understanding is that the XML files will still work for group policy and creating a new default template, but overwriting the existing XML file won't work. I have not seen any updated documentation on how to configure the start menu and taskbar without using the XML file, so I'm assuming it will at least work through the Fall Creators Update.
    • Hi Chuck,
      it was more of a heads up than anything else. I use the "overwrite" the xml with a late stage custom task for all users, as I mentioned I have a standard load. I don't use the GPO method as in LTSB 1607 it prevented users making *any* changes.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ