Re: RWW Default Profiles

See Cliff You do have People Skills!
http://www.hulu.com/watch/12879/office-space-people-skills#s-p1-so-i0



Russ :)

--
What I did the Last Year of Intel
(And why I left Intel)
http://www.hulu.com/watch/12638/office-space-peters-interview#x-4,vclip,1


"Cliff Galiher" <cgaliher@xxxxxxxxx> wrote in message
news:u8mdnRCRt4YCyjfVnZ2dnUVZ_uOdnZ2d@xxxxxxxxxxxxxx
Inline:


"Jay" <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E9D66906-7076-4C91-A287-57F9F971204C@xxxxxxxxxxxxxxxx
The reason that we have chosen to use local account profile
Again, there is a difference between an account and a profile. It is very
important to understand the difference.

is simply that
when we have changed or upgraded servers in the past, it seemed easiest
to
have a local account so that all the client workstations needed was to
disjoin from the old domain and join the new DC. The users desktop would
remain the same and no extensive maintenance would be needed at the
client
other than joining the domain and pointing to login scripts.
This can be done with tools such as ADMT and USMT (both microsoft tools)
or using swing migrations (a third party offering) but none of these
requires much work on the client, but only on the server. I don't know
what problems you had, but I can say that since NT4, they could've been
avoided. The only time that desktop and settings would change are when
you upgrade the *client machine,* not the server. The client OS
determines the profile settings, local or roaming (not to be confused with
ACCOUNTS.)

We don't have a situation where users move from one computer to another,
or
share computers, so there has never been a need for roaming.
See above, domain accounts can have local profiles too. You don't need to
roam a profile, but you *should* use domain accounts.

If putting everyone back on Domain accounts and deleting all the local
accounts is the only way to get rid of the duplicate accounts problem i
described when logging into RWW and/or there is no way to set a default,
then
I will consider going back to domain accounts.
It is.

Is there any other reason to
use domain accounts other than it being the general practice?
There are many reasons. For SBS, the default user group policies will
only be applied to domain users. The ability to restrict access to server
resources. for example only allowing the accounting person/department
access to accounting files on the server, should be done at the domain
level. Centralizing control of the network results in reduced support
costs and troubleshooting time. The list goes on and on....don't just
"consider" moving back to domain accounts. Do so. You'll be happier. :)

-Cliff

Thank you for all your responses,
Jay






"Cliff Galiher" wrote:

After reading Gumby's post, I was left scratching my head wondering
"nowhere
did I read the user was logging in using local accounts."

So, I went back and re-read the original post, and sure enough...had I
been
paying more attention, I would've realized that "click the Options
button on
the login screen and select the local profile" was what I had missed.
This
option is not a profile selection, but is selecting whether you are
using a
local ACCOUNT or a domain account....far more than just profiles.

So basically, ignore my first post. I won't bother repeating what has
already been written elsewhere in this thread, but Gumby is dead-on with
his
analysis and you should take some time to read it and make sure you
understand it thoroughly. You'll be far happier once you do. :)

-Cliff

"Cliff Galiher" <cgaliher@xxxxxxxxx> wrote in message
news:F96dnSZZoJoNaTTVnZ2dnUVZ_hqdnZ2d@xxxxxxxxxxxxxx
Logging into a machine via RWW is, for all intents for profiles, like
logging into the machine when you are sitting in front of it. So if
the
local profile is properly configured FOR THE USER LOGGING IN, and the
system has not been told to roam the profile (ADUC) then you should be
fine. If you are getting a roaming profile where you don't expect it,
then it is time to look at the user setup, not RWW. :)

As far as customizing the RWW login screen, to my knowledge such a
thing
is currently not possible.

-Cliff

"Jay" <Jay@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:245211D2-8270-48B4-B042-1F84FE8FFD5E@xxxxxxxxxxxxxxxx
We use local profiles alsmost exclusively on our Client workstations.
RWW
seems to default to the Domain roaming profile every time, leaving
our
users
having to click the Options button on the login screen and select the
local
profile. Is there anyway that I can control the default profile when
RWW
is
initiated? Also, I'd like to customize the RWW login screen. Is
that
possible?

Please advise,
Jay






.