Home All Groups Group Topic Archive Search About

proper method for roaming profiles

Author
11 May 2005 1:43 PM
Mike Brearley
A few questions here just so I set up my shares the 'proper' way.  Now
what's proper and what's not, who really know... :-)

Anywho, I started by sharing things the following way:
home directories as \\server\username$
terminal server profiles as \\server\usernamep$
roaming profiles as \\server\usernamerp$

Now my question is...  should the roaming profiles and terminal server
profiles be merged into one profile or is it best to leave them separate?
I'm using Citrix for 1/3 to 1/2 of my users.

Also, I'm pretty sure the home directory share is set up right, but for some
reason I'm thinking the profile shares should have one main directory shared
(profile) and then connect to the directory.  Kinda like this:
roaming profile as \\server\profiles$\username

I may be wrong in both cases, I'm not sure...  Can someone 'enlighten' me?

Thanks...

--
Posted 'as is'.  If there are any spelling and/or grammar mistakes, they
were a direct result of my fingers and brain not being synchronized or my
lack of caffeine.

Mike Brearley

Author
11 May 2005 2:41 PM
Todd J Heron
The profile folder should never be more than the third-level deep so it
should look like this:

Terminal or roaming profile:
\\server\profiles$\%username%

Note:  Terminal and roaming profiles should be kept separate.

Home directory:
Terminal and roaming profiles
\\server\Users$\%username%

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
Are all your drivers up to date? click for free checkup

Author
11 May 2005 3:01 PM
Daniel
Todd J Heron wrote:
> The profile folder should never be more than the third-level deep so it
> should look like this:
>
> Terminal or roaming profile:
> \\server\profiles$\%username%
>
> Note:  Terminal and roaming profiles should be kept separate.
>
> Home directory:
> Terminal and roaming profiles
> \\server\Users$\%username%
>
I would also recommend keeping the path as short as possible otherwise
you'll run into the 256 char limit in the Local Settings folder

--

Daniel
MCSE, MCP+I, MCP in Windows 2000/NT

--------------------------------------
remove the 2nd madrid from my mail address to contact me.
Author
11 May 2005 3:44 PM
Mike Brearley
Thanks...

The next question would then be for permissions on the folder.  Should I add
Creator Owner with Full Control, Subfolders and Files Only and set the user
as the owner?  Or simply add the user's ID with full control?  Or both?

--
Posted 'as is'.  If there are any spelling and/or grammar mistakes, they
were a direct result of my fingers and brain not being synchronized or my
lack of caffeine.

Mike Brearley

Show quoteHide quote
"Todd J Heron" <todd_heron_no_spam@hotmail.com> wrote in message
news:%23bSS4djVFHA.3108@TK2MSFTNGP10.phx.gbl...
> The profile folder should never be more than the third-level deep so it
> should look like this:
>
> Terminal or roaming profile:
> \\server\profiles$\%username%
>
> Note:  Terminal and roaming profiles should be kept separate.
>
> Home directory:
> Terminal and roaming profiles
> \\server\Users$\%username%
>
> --
> Todd J Heron, MCSE
> Windows Server 2003/2000/NT; CCA
> ----------------------------------------------------------------------------
> This posting is provided "as is" with no warranties and confers no rights
>
Author
12 May 2005 1:13 AM
Todd J Heron
For the user's roaming profile folders, which should be located underneath a
hidden share, it should look like this:

User: Full Control
Administrators: Full Control
System: Full Control

For the user's home directory folders, which should be located underneath a
different hidden share, it should look like this:

User: Modify
Administrators: Full Control
System: Full Control

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Bookmark and Share