Re: Local & SBS profiles

Lanwench [MVP - Exchange] wrote: 
In news:70021968-0856-4E90-9EEA-CB968808B9A1@xxxxxxxxxxxxx,
Jeff <Jeff@xxxxxxxxxxxxxxxxxxxxxxxxx> typed:

Hi folks. I am an SBS newbie who is installing an evaluation copy of
SBS. (The network currently has no server.) Next step is to add users
& computers. Would like advice on how to best meet the following
requirements:

1. Each user has an SBS account/profile that looks the same from
computer to computer (roaming profile?)



Yes, but this doesn't happen by default....see below.


2. Each user has a local account/profile, so they can log onto their
computer's local domain (not SBS) and work they way they currently do.


There's no such thing. They either log into the domain, or to the local computer.

And they shouldn't log into the local computer once you configure the domain and join the computers from it. I remove local user accounts once I've joined computers to the domain and migrated their profiles (note that this will happen automatically if you use http://server/connectcomputer.



3. The SBS profile and local profile differ in the way Outlook is
used. In the SBS profile, Outlook will operate in conjunction with
Exchange. For the local profile, Outlook will go directly to the
ISP's mail server.


This can work, if they do indeed have two profiles, but why would you want to do this? If you're using the eval version, don't put it in your production network. Get a spare workstation so you can play with it and do it properly. When you're convinced/sold on it, buy the full SBS and migrate properly.


What's the best way to do this? Thanks in advance for your help--this
community is super!



Roaming profile tips


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, that answered a dumb question I posted earlier. Will this process work the same if they are connecting via client VPN into the SBS server ?
simon
.

Relevant Pages

  • RE: Reinstalled WSUS 3.0 SP1 Now Issues
    ... Follow Up For Microsoft SBS Public Newsgroup Post [Reinstalled ... WSUS 3.0 SP1 Now Issues] with Gary Wang ... Typically I managed the SBS server ... | The Server Computers group was not found: ...
    (microsoft.public.windows.server.sbs)
  • RE: IPSEC question
    ... access SBS. ... Microsoft network client: Digitally sign communications (if server ... Windows Server 2003 Service Pack 1-based computers ...
    (microsoft.public.windows.server.sbs)
  • RE: Server kicks off users
    ... The times on the computers are almost exactly the same already... ... to the client computers' WINS server. ... you need to configure on SBS server and client computer as ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Cannot browse or open shared printers or server on sbs 2003 from client pc
    ... Thank you for posting in SBS newsgroup. ... DNS Service as the DNS Server. ... Computer Browser service on client computers and SBS as following: ...
    (microsoft.public.windows.server.sbs)
  • Re: Installing SBS 2003 R2
    ... I had planned on "learning by doing" by installing SBS into my home lab (5 ... Dell server, I don't know if I'll use the new server for the test or use one ... the client computers and use the router he already has in place. ... If it's primarily remote access you can get by easier ...
    (microsoft.public.windows.server.sbs)
Loading