Re: Rights and Policies

The profile contains the user files, including background stuff like temp
files, temporary Internet files, cookies, etc., plus other files that are
specific to the user account (settings, etc.). If you delete the profile,
next time the user logs in, a new one will be created - it'll be the same as
a first-time login.

I don't generally bother deleting profiles. IMO there are only two reasons
to do so - drive space considerations, and security. A user with local admin
rights on the PC can browse the profile of another user. While deleting
unneeded profiles solves that, I prefer to set the security correctly so
that users don't have admin rights, which avoids the issue altogether.

To delete a profile from a workstation, go to CP -> System. It's on the
Advanced tab -> User Profiles.


"hijack" <hijack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:662CD13F-75EA-4008-AB16-353F76875D4A@xxxxxxxxxxxxxxxx
This can get complicated for multiple profiles on a single PC that already
exist on the server. (Your initial response answers this).
What will be the best way to remove a profile from a local PC ?
What exaclty does a profile contain ?
--

Jack
Thanks for your valuable input.

"Dave Nickason [SBS MVP]" wrote:

Migrating in what context? If you're migrating to domain profiles from
the
ones that already exist from before the client PC was joined to the
domain,
that's done when you join the domain with /connectcomputer.


"hijack" <hijack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72133B43-A032-426E-8257-CBF8BFEA587D@xxxxxxxxxxxxxxxx
Thanks for the explanation.
What about migrating profines of users?
--
Jack


"Dave Nickason [SBS MVP]" wrote:

Unfortunately a lot of this depends on the individual application and
how
well it's written.

Normally, you would log onto the client PC with either the Local or
Domain
Administrator account, and install the application. It should then be
available to any user who logs into that PC, even though they're not
an
administrator. If you have a poorly written app, you may have to make
the
user an administrator, install the app under that user's account, then
return the user to ordinary non-admin user. Again if the app is
properly
written, it should work fine for ordinary non-administrator users.

So the plan is to hope for the best. Log into one PC as an
administrator
and install the app. Then have the user with regular non-admin rights
log
in to his/her own account and test it. Hopefully all will work as
anticipated, and you can install on the rest of the clients. If the
app
only runs with admin rights, I would contact their tech support and
tell
them this is not acceptable, and you need to know what settings can be
made
to allow the users to run with standard rights.

"hijack" <hijack@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EAF326FF-796C-47C9-B8EA-8E5D72CF7464@xxxxxxxxxxxxxxxx
Hi,
I need guidance with rights and policy issues. I have SBS2003 and XP
/
Vista
clients. I want to install applications on these local PC's. This
application
will load itself on both the local PC and server. The local user has
limited
rights (remote user). How do I install this application. An error
pops
up
informing that I be a member of the local administrator security
group
to
install on the local PC.

On the local PC
Do I logon as the local administrator of the client PC. ( I assume
that
a
password may have to be set for the local administrator) ?

Do I logon as the client user (remote user) ? If so, how do I
install
with
administrative rights if the application is self starting from a CD.
The
exe
file may be difficult to locate on the CD because of the sequence of
the
many
applications.

Do I logon as the server administrator on the local PC?

If I install an application with elevated rights will a user with
lesser
rights have difficulty in accessing this application?

--
Thanks for the help
Jack








.

Relevant Pages

  • Re: "Classic logon" screen in XP does not remeber the user name
    ... would be to install RC. ... I recently upgraded a workstation from Windows 2000 Pro to Windows XP Pro. ... can copy missing shortcuts to the new profile. ... just temporarily] another user account that is also an administrator ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Rights and Policies
    ... ones that already exist from before the client PC was joined to the domain, ... Administrator account, and install the application. ... Then have the user with regular non-admin rights ...
    (microsoft.public.windows.server.sbs)
  • Re: Rights and Policies
    ... you would log onto the client PC with either the Local or Domain ... Administrator account, and install the application. ... Then have the user with regular non-admin rights log ...
    (microsoft.public.windows.server.sbs)
  • Re: Does ANYONE know the answer to this Admin question?
    ... Kent W. England, Microsoft MVP for Windows ... >>> profile that they limited to just "user" level with no ... >>> I have MY profile set with admin rights to install ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Rights and Policies
    ... ones that already exist from before the client PC was joined to the domain, ... Administrator account, and install the application. ... Then have the user with regular non-admin rights ...
    (microsoft.public.windows.server.sbs)