Re: New and additional user SBS client setup

Tech-Archive recommends: Fix windows errors by optimizing your registry



In news:2E7E4170-19A0-4970-9CDD-FA74DD669BE6@xxxxxxxxxxxxx,
Dodge <Dodge@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
> Lanwench, thanks for the input. In this case the laptop computer is
> already part of the domain... I want to add a new user's
> profile/account to the computer so they have their Outlook setup,
> access to shares, on the domain, etc.
> The option, which I was still thinking about, was whether to keep the
> existing user's setup on this, or remove it when adding the new user.

You don't add a user to a workstation if it belongs to a domain and this is
a domain account. You merely log in as the user.

Perhaps you want to look into roaming profiles, as it seems profiles are
what you're talking about. You can't re-run connectcomputer -

Here's my boilerplate on roaming profiles:


1. Set up a share on the server. For example - d:\profiles, shared as
profiles$ to make it hidden from browsing. Make sure this share is not set
to allow offline files/caching!
2. Make sure the share permissions on profiles$ indicate everyone=full
control. Set the NTFS security to administrators, system, and users=full
control.
3. In the users' ADUC properties, specify \\server\profiles$\%username% in
the profiles field
4. Have each user log into the domain once from their usual workstation
(where their existing profile lives) and log out. The profile is now
roaming.
5. If you want the administrators group to automatically have permissions to
the profiles folders, you'll need to make the appropriate change in group
policy. Look in computer configuration/administrative
templates/system/logon - there's an option to add administrators group to
the roaming profiles permissions.

Notes:

* Make sure users understand that they should never log into multiple
computers at the same time when they have roaming profiles (unless you make
the profiles mandatory by renaming ntuser.dat to ntuser.man so they can't
change them). Explain that the
last one out
wins, when it comes to uploading the final, changed copy of the profile.

* Keep your profiles TINY. Redirect My Documents
to a subfolder of each user's home directory on the server - either via
group policy (folder redirection) or manually (less advisable). If you
aren't going to also redirect the desktop using policies, tell people that
they are not to store any files on the desktop or you will beat them with a
stick. Big profile=slow login/logout, and possible profile corruption.

* Note that user profiles are not compatible between different OS versions,
even between W2k/XP. Keep all your computers. Keep your workstations as
identical as possible - meaning, OS version is the same, SP level is the
same, app load is (as much as possible) the same.

* Do not let people store any data locally - all data belongs on the server.



> - Thanks, Dodge
>
> "Lanwench [MVP - Exchange]" wrote:
>
>>
>>
>> In news:A84E2B05-AA80-4F4D-921E-A81547F8E1DE@xxxxxxxxxxxxx,
>> Dodge <Dodge@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:
>>> Hi, I need to take an existing laptop computer and add an new
>>> SBS2003 user account to it.
>>> I might want to leave the older existing client setup on it or
>>> remove it, not sure, so I'll ask both ways:
>>> What is the best way to take an existing computer from one user's
>>> setup, and set it up for a new user? I'm wondering if re-running
>>> ConnectComputer is the way to go?
>>> In most cases I'd reimage the drive and just set it up for the new
>>> user from scratch. But in this case I need a more rapid deploy and
>>> again, might want the older user setup retained on this laptop.
>>> Thanks in advance - Dodge
>>
>> Presuming you mean, you have a laptop that doesn't belong to the
>> domain, and you want to add it to the domain, you can indeed run
>> /connectcomputer on it. Presuming it doesn't already belong to
>> *another* domain, and is running an NT-based operating system such
>> as Win2k or WinXP Pro (not Home), that is.
>>
>> You don't add domain user accounts to a domain workstation, note -
>> you join a workstation to the domain, and log in as a user.


.

Relevant Pages

  • Re: Roaming Profiles Slow with Windows 2003 and XP
    ... If you create a new user and set them up for roaming profiles is the logon ... effort into developing a workstation build process. ... deploying folder redirection. ...
    (microsoft.public.win2000.setup_deployment)
  • Re: Can I treat roaming profiles different depending on the connection?
    ... roaming profiles, but TS profiles. ... workstation with their domain userid, ... we are in the process of trying to get roaming profiles in place ... >> workstation) from a Citrix server and>> those who do a domain logon at their workstation and use published icons>> from the Citrix server. ...
    (microsoft.public.win2000.active_directory)
  • Re: Roaming Profiles
    ... Ok it seems that I will try to roll out the folder redirection beginning next ... At times I've seen flaky issues with roaming profiles in our network. ... log in to the appropriate workstation, then log off copy over all their ...
    (microsoft.public.win2000.active_directory)
  • Re: Local/Domain Logon
    ... No users should have local workstation accounts - there's no value ... Go to control panel, system, advanced, and find the profiles settings ... computers at the same time when they have roaming profiles (unless you make ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I set up roaming prifiles
    ... > Many thanks, David, UK ... Create a "parent" folder for profiles, and share it as a hidden share - I ... Have each user log in on their "usual" workstation once, ... worried when roaming profiles are larger than about 20MB. ...
    (microsoft.public.backoffice.smallbiz2000)