Roaming Profiles in Server 2003

[larciel]

Quick info

VMware running server2003 and two xp

Problem:

If I log on from the workstation say 'test1' BEFORE setting up roaming profiles in the server 2003 for that user, I can't switch it to Roaming Profile in the workstation System tab. It's greyed out

If I log on (say 'test2' whose roaming profile was set before logging on the domain), it works as advertised.

What could be the prob?

 

[Genx87]

A. Computer joined to the domain?
B. Logging in as a domain user?
C. Setup terminal profile in the users account?

 

[mcmilljb]

Were you setting the path of where you want to store the profile BEFORE changing to a roaming profile? I think once you set the location, then you can enable the roaming profile. If you don't set the path, I don't see how you could enable it since the 2K3 server is the one holding the profile, not the work stations.

 

[RebateMonger]

From an itnewsgroups.net article:

"I am going on a few assumptions here.
1. You are running Active Directory on a Win2k3 Domain Controller
2. Your XP machine is joined to that domain.
3. You are logging on to the XP machines with a domain account you created
on the Domain Controller, and not logging on "Local".

The option to switch to a roaming profile WILL be greyed out at the
workstation.
Your only options from the workstation is to tell the workstation NOT to
download a roaming profile, use "Local"

Roaming profiles are controlled from Active Directory Users and Computers
console on a domain controller (DC), or from any snap in pointed to that dc.

Open the proptries of your domain user account and go to the Profile tab.
Here is where you specify a "Profile Path".
If this cell is cleared, you will NOT have a roaming profile. Keep it empty
if you dont want a Roaming Profile.

If there is a path, it must be a valid UNC path \\servername\sharename.
That account also requires write permissions to that share.
If the path is incorrect or access is denied, you will most likely see slow
response times.

You will also see slow response times if your roaming profile is very large."

 

[larciel]

Thank you for the answers. I should've stated my question more clearly.

Yes, all three assumptions listed above are correct. Here's how the problem starts.

WorkStation1 - logs on to domain using login name test1
(Server2003 does NOT have profile path setup, so it's set at LOCAL)

While WS1 is logged on, Server2003 sets a path for roaming profile. \\server\profile\%username%

WS1 logs out, then logs back in. Still have local profile

If I log in same test1 from WorkStation 2, it's set at Roaming Profile correctly

Is this normal that once a Workstation is logged on to domain while it has local profile setting, it cannot switch to roaming once correct setting has been set in Server 2003?

 

[mcmilljb]

Here's what I think you should do. Create the share first (\\server\profile\%username%). Populate it with your default user profile. Then you're set from the start. If you might add more users later, consider a template user account. You create a dummy account that's disabled, but has all the settings and a default profile all set. Then you just copy over the user and its profile and change the profile path to match \\server\profile\%username%.

 

[larciel]

Will try that also.

By the way, is it normal that Admin account on server 2003 can't access each members profile folder? I get "Access is denied" error.

 

[mcmilljb]

Are you denied through local access or share? If it's a share, check the permissions for the share and NTFS. If it's local, look at the NTFS permissions. I don't know why you would be denied access, but you can take ownership and give yourself access.