maiosan.blogg.se - Windows 10 enterprise 1803 64 bit iso download

This is also true for the base AppX apps that get installed natively like Bing News and others. If you remove those apps on one account that doesn’t mean those apps are removed from any other accounts you may have logged into. You have to remember that if the image is network connected then the Windows Store can download and install Sponsored Apps for every account you login to. If you follow the above rules you can easily avoid problems with AppX apps and Sysprep. You may run into a situation where you cannot remove the AppX app because it’s stuck in the database as deployed to an account that no longer exists. If you delete an account/profile that has an AppX app deployed it can effectively get stuck.

DO NOT delete accounts or profiles from the image until you’ve run the AppX removal scripts.

You must also ensure that you remove exactly the same AppX apps and do not install any additional AppX apps on any of the logged in accounts. You must run the AppX Removal scripts on every account you logged into on the image.

If you do logon under other accounts, run the AppX removal scripts under ALL accounts removing the SAME apps from all accounts.

You can login to multiple accounts but you have to follow the next 2 rules. AppX apps are provisioned or downloaded on every account you login to. Once you login to other accounts the AppX apps will be installed under the additional user accounts/profiles and has greater potential to cause Sysprep to fail. This is the first and most common mistake. You may have even joined the image to the domain and logged on under multiple accounts or even enabled and logged on as the local administrator. When building an image you usually don’t want to have the “temp” account as the one you use going forward. I usually call it “temp” or something like that since it’s intentionally temporary. The first time you boot up after installing Windows 10 it asks you to create a new account.

DO NOT log on more than one account after installing Windows 10.

There’s 3 rules to follow and if you follow them you should not have issues with AppX and Sysprep. Ok so this is a LOT easier than you may think. I also wanted to talk through how most people end up breaking Sysprep and how to avoid doing so altogether. I wanted to detail those as an addition to my previous article. Surprisingly it’s one of the more popular articles on here.ĭuring my day job I’m constantly working with images for VDI deployments and I’m finding additional apps to remove and new ways to view and sort through them all. I explained how I ran into the issue and then I went a little further than that and provided a couple scripts to help remove the AppX packages and to remove provisioning of those apps so they don’t install under other accounts. Hey welcome to my blog and Happy 2018! Some of you may remember I did an article last year about AppX apps and how they can break Sysprep.