This message was deleted.

yes, you can set bake everything into the image if you want. I prefer to have everything in the GPO and apply the policy to the master image.

We were having problems with that, and noticed that the documentation talks specifically about setting that prior to anything else during boot, so we just baked it in. However, we baked in the wrong one (we used the key for profile container), and have the GPO set for Office container, and it's put my search in the profile container. Wanting to revert, and bake the Office container settings instead, then just remove the GPO. Figured it would work, and wanted to make sure 😃

Isn’t it the same outcome if you apply the GPO to the PVS image in private mode? Yeah I guess that should work. Well you need to clean up your profile containers afterwards to get rid of the orphan indexes

Thanks @dready. You are correct, it should be the same. We have our image build automated, and have the registry keys set at install. I'm OK cleaning up the profiles, this is still currently in UAT, and there are only about 40 or so users who are affected.

if you apply the GPOs to the image in the build process, this should tattoo onto the reg, right?

Correct. We try not to do that. Everything is set in the build systems.

Only time you should tattoo is like this and e.g. services which starts before GPO applies. Then there’s 3 ways; software install, Build OU/GPO or a custom BISF prep script. I prefer the first like you :-)