SBS 2003 roaming profiles

Hello, I setup my SBS 2003 and joined all my computers to the domain with the
connectomputer wizard. I also setup folder redirection in the GPO but there
are insane login times.
Also I followed the advice from someone on here sorry i forgot your name,
to allow administrator to see the users files on the server but it still
doesn't work.
The profiles are saved on the D under a folder called User Profiles and it
is shared as Profiles$
The folders are redirected to a folder on the D called Users Shared Folders
and this is shared as Users$

Am I just blind on how to fix this.

I'll include my boilerplate on roaming profiles below, but you'll probably
need to provide more detail (what you redirected, whether you have UPHClean
installed, what you see in the event logs, etc) if the steps below were
followed & you're still having problems. Re the admin rights - this won't
work on existing folders; just on ones created after you enabled that in the
policy

********************
General 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! (that's on by default - disable it)

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 - if this is an existing user
with a profile you wish to keep, have them log in at their usual
workstationand 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/user
profiles - there's an option to add administrators group to the roaming
profiles permissions. Do this *before* the users' roaming profile folders
are created - it isn't retroactive.

********************
Notes:

Make sure users understand that they should not 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, which has major disadvantages),. Explain that the 'last one out wins'
when it comes to uploading the final, changed copy of the profile. If you
want to restrict multiple simultaneous network logins, look at LimitLogon
(too much overhead for me), or this:
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=8768

********************
Keep your profiles TINY. Via group policy, you should be redirecting My
Documents (at the very least) - to a subfolder of the user's home directory
or user folder. Also consider redirecting Desktop & Application Data
similarly..... so the user will end up with:

\\server\users\%username%\My Documents,
\\server\users\%username%\Desktop,
\\server\users\%username%\Application Data.

You should use folder redirection even without roaming profiles, but it's
especially critical if you *are* using them.

If you aren't going to also redirect the desktop using policies, tell users
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.

*********************
If you also have Terminal Services users, make sure you set up a different
TS profile path for them in their ADUC properties - e.g.,
\\server\tsprofiles$\%username%

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

********************
The User Profile Hive Cleanup Utility should be running on all your
computers. You can download it here:
http://www.microsoft.com/downloads/d...displaylang=en

********************
Roaming profile & folder redirection article

There are at least two possible problems. One is DNS, so if you are not
positive about that post the results of:

ipconfig /all > c:\iptest.txt

from both the SBS and an affected client workstation. Please don't change
anything, and let us know which is which.

The other possibility is the amount of data that is being redirected, but
this should only occur on first restart.

all that has been done, except i cannot keep the users my documents and their
desktop small. the workers are working with 50 to 60 pdfs daily, and they
have of media (pictures, and small videos)

server

Host Name . . . . . . . . . . . . : pdc1

Primary Dns Suffix . . . . . . . : Euro.lan

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : Yes

WINS Proxy Enabled. . . . . . . . : Yes

DNS Suffix Search List. . . . . . : Euro.lan

Ethernet adapter Server Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/1000 PM Network Connection

Physical Address. . . . . . . . . : 00-30-48-D3-1C-36

DHCP Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.2.100

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.100

Primary WINS Server . . . . . . . : 192.168.2.100

workstation

Windows IP Configuration

Host Name . . . . . . . . . . . . : NurseStation

Primary Dns Suffix . . . . . . . : Euro.lan

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : Euro.lan

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network
Connection

Physical Address. . . . . . . . . : 00-11-11-CA-83-69

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.2.144

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 192.168.2.1

DNS Servers . . . . . . . . . . . : 192.168.2.100

Sorry, much of this has to be discipline. *Nothing* should ever stored
on the desktop except shortcuts and temporary files until the end of a
session. Nothing should be kept there across a logoff.

It's a business workstation, not a private PC, and all stored data
should be accessible in the case of someone being absent/sick/etc., so
nothing should be stored in any folder beginning with 'My', either.
Roaming profiles can include a server folder automatically mapped to a
drive letter on logon, and that should be done with permissions set
appropriately. Any genuinely confidential business data should have its
own server folder, again with appropriate permissions set.

I realise this may not be easy to achieve, but profile corruption is not
unusual, and business data should not be stored there. Individual
companies will have their own policies about the storage of personal data.

With Vista, this is all even more important, as permissions are much
more restrictive, needing more administrative work to get at data in a
user's absence, and the profiles seem much more fragile, at least with
SBS2003.

So let me see if i get this straight,
1. nothing ever should be on the desktop except the shortcuts
2. I have a home folder setup so everything should be moved to there than?
3. wouldn't redirecting the folders to a server mean, that all data sits
on the server and the workstations just pull from there? are am i thinking of
something else.

Yes, if you aren't going to redirect Desktop. I like to discourage people
from storing crap on the desktop anyway, though.

You don't need home directories; those are a pretty archaic concept. Just
folder redirection via group policy. You can still map a drive - e.g.,

net use h: "\\server\users\%username\My Documents" /persistent:no

Yes, that's precisely what it means, and it's a good idea.

I disagree about not using My Documents - I think it's important that users
not store anything locally. Even non-business-related stuff. I'd rather have
it all on the server and just have a company policy about a) privacy or lack
thereof for all such items and b) what sorts of files are not permitted
(e.g., MP3, etc). Train users that the My Docs data is for stuff that not
everyone needs access to. Set up other shares (e.g., \\server\shared$) for
company-wide data. Set up shares for Accounting, HR, Management & assign
permissions via security groups. Just don't store anything on the local
workstation hard drive

Man i feel stupid, I forgot to exclude the folders like my desktop my
documents and applications data in the roaming profiles. now everything is
fast and nice. only problem is some stations dont like the loginscript to map
and folder as Z: i have to do it maulayy on each workstation but thtas not
too bad. thankyou everyone.
Also Lanwench i will give you good ratings.

Your syntax is incorrect....

net use x: \\server\share
or
net use x: \\server\share\subfolder

and better still

net use \\server\share /persistent:no

net use x: \\server\share

[LatinKreationz]

I don't mean to thread hijack but what about if I need to update someone's login information, i.e. marriage, divorce? What happens to the files that are currently in those folders?