sccmlouis

We have tested with fresh installs with and without impero (rather than uninstalling it) and have found that without fail it only occurs when Impero has been installed. Indeed arggg!

Impero again?!

We also deploy Impero outside of our image using SCCM to install the MSI.

Well... you can. The way in which it works, it interacts with every part of the OS. Causing little issues along the way it seems! We have tested 10 pcs, 5 with impero, 5 without and the issue is non existent on the 5 without.

Very interesting. - Impero have said that Impero 6.1 resolves the issue - unsure what else that might bring! (Not yet released)

Best way would be to make a script to log them on and then use psexec to execute this on a room of computers I would have thought.

Was really a case of playing around (literally hit and miss) with the profile and permission to certain registry keys in order to make it all work. - There are some good guides online, however none seem to provide everything you need.

We are seeing a strange issue. We have Impero on site, when deploying 1703 with Impero and login with a mandatory profile, Explorer has no text (eg. no 'This PC' just the icon)! If we deploy without Impero, the issue goes away. Just wondering if anyone else has experienced this.

We seem to have cured this one! - - - Updated - - - Profile version in 1703 is still V6 as far as I am aware.

Has anybody started testing Windows 10 1703 for deployment yet? We use SCCM to deploy, however are having some issues with mandatory profiles (v6 from 1607) etc.

Have you tested any machines that don't have Impero on?

I agree, we always set ours before giving out devices - little amount of time to do and saves a lot of hassle in the long run!