Profiles on windows 2012 servers

twodogs62

Under what conditions would local profiles be created on windows 2012 servers?

Slowhand

Any time you'd need to log in with a local profile, such as if the server isn't joined to the domain for example. The need for local profiles on individual servers on a domain is really dependent on what your lab/corporation/etc. requires.

twodogs62

These seem to be anamolies as a dozen or so regular users are creating profiles on a few of our domain file services. Wondering all cases of why a profile would be created? I can't think of reasons why I should be seeing this.

Qord

Are they true local user profiles or domain users who happen to have user profiles on the server in question? The first time someone logs in at the console or over rdp a profile *should* be created on the machine for them, that's by design. Outside of that, I can't think of why a user profile would be created without IT intervention. Maybe some special cases for specific program or file access.

Deathmage

bigger question, is why are they 'allowed' to make user profiles on the file server(s). The only person in the whole company that should have a profile is the administrator, everyone else should be access-based navigation.

If users need access to a server for profiles, make a terminal server. Most basic Microsoft Volume licensing comes with 5 Terminal Services CAL's, plenty for a terminal server farm where users need to access files.

It's just a very very bad omen to allow people to login directly to a file server, imagine they go on a website and get a virus, that profile and server are now at risk. Why take that risk with a file server?