Creating new domain user accounts

[Jason Aspinall]

While creating a batch of new users on a newly installed win2k server box
running AD, I note that the profile is set up such that the home and profile
paths are set as following:

User profile path: \\server\profile\%username%
and
Home folder path: \\server\home\%username%

Upon actually looking in the "Home" folder, multiple user account home
folders are being created under their username, as you would expect.
However, in the "Profile" folder, nothing is there, no user profile folders
are being created automagically

Any ideas why?

TIA

Jason Aspinall

 

[Dan DeStefano]

you may need to have the users enable roaming profiles on their machines.
check some of the client machine settings to see if the user profiles are
set to roaming.

Dan

 

[Jason Aspinall]

you may need to have the users enable roaming profiles on their machines.
check some of the client machine settings to see if the user profiles are
set to roaming.

So what you are saying is that the profile folder isn't created until the
user attempts to log in for the first time?

 

[Enkidu]

These are new users and I seem to recall that creating a profile path
causes them to use roaming profiles automatically.

Cheers,

Cliff

 

[Dan DeStefano]

no, once you hit ok in the user account properties box, the folder(s) should
be created. what enkidu said is also normally the case: as soon as you enter
a path in the profile path field and the user logs on, his account should be
set to roaming. what i was saying is just to check this in case the user(s)
already has a local profile on their workstations.
when creating the paths you are using the "%" variables, right? can the dc
communicate with the machine(s) on which the target share(s) reside? are the
permissions on the shared folders set properly? both ntfs and share-level
permissions?

Dan

 

[Jason Aspinall]

no, once you hit ok in the user account properties box, the folder(s) should
be created. what enkidu said is also normally the case: as soon as you enter
a path in the profile path field and the user logs on, his account should be
set to roaming. what i was saying is just to check this in case the user(s)
already has a local profile on their workstations.
when creating the paths you are using the "%" variables, right? can the dc
communicate with the machine(s) on which the target share(s) reside? are the
permissions on the shared folders set properly? both ntfs and share-level
permissions?

Well, all of the work I've done to date is purely on the server itself, thus
creating the user profiles with the relevant paths tagging %username% on the
end. Both ntfs and share permissions are set to "everyone - full access"
(inherited from the parent setting for the volume these folders reside on).

Like I said, the home folder is created, just not the profile folder... Both
root folders "home" and "profile" have been set up identically for
"everyone - full access"... Something quite weird going on... I've tried
both local paths and UNC paths for the folders, no cigar :|