JaSauders Posted May 20, 2013 Posted May 20, 2013 I work in a large public school district as a technician. We have decided to bump up our Windows clients to Windows 8 (with ClassicShell, of course, to bring back a usable menu). As we were building the image another tech noticed that the metro apps were not starting. Yet on Friday we left when they were working absolutely fine, and here they are not. What I'm worried about is, what if a teacher gets attached to the Metro apps and begins relying on them for whatever reason... and then magically they stop working. By no stretch of the imagination do I accept the wildly passed around answer of "Just create a new user and you'll be fine!" Yeah, no. That said, yes, when I create another local user, it acts absolutely fine on that account.
JaSauders Posted May 20, 2013 Author Posted May 20, 2013 Can I ask why that would be the way to go? Also, our machines that we ran into with this weren't even added to the domain yet...
Chris_Cook Posted May 20, 2013 Posted May 20, 2013 I think metro is still a little buggy and experimental. You're probably best off waiting for service pack 1 before deploying to end users.
free780 Posted May 20, 2013 Posted May 20, 2013 Wouldn't metro apps be attached to the user not your school.
disk Posted May 20, 2013 Posted May 20, 2013 I have noticed two things. 1) Modern apps won't launch if the UAC is disabled 2) Best not to mess with the default modern apps before sysprepping
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now