Storing Roaming Profiles on a fileserver

  • Thread starter Thread starter Burning_Ranger
  • Start date Start date
B

Burning_Ranger

Basically what I am trying to do is move some roaming profiles from
the local hard disk on a Win2000 DC to a NAS. I've moved them across,
changed the Profile Path in Active Directory users and computers to
point to "\\fileserver\profiles\test". I have set the login script of
the test account to connect to the "\\fileserver\" on login. When I
try to log into the domain using a test account it tells me that a
roaming profile could not be found.

When logging in using a remote Roaming Profile, is the profile
location provided by the DC or does it work some other way. I think
the problem might be that when logging in, it tries to load the
profile first, but becaus the fileserver location has not been mounted
it can't find the profile. Maybe...

Anyway to get this working? Does it matter if the fileserver share is
not mounted on the domain controller?

Any ideas appreciated.
 
Burning_Ranger said:
Basically what I am trying to do is move some roaming profiles from
the local hard disk on a Win2000 DC to a NAS.

What kind of NAS .... what OS does it run and does it participate in AD?
I've moved them across,

What did you use to do this, and did you also copy over the permissions? (I
generally use Robocopy from the resource kit for things like this).
changed the Profile Path in Active Directory users and computers to
point to "\\fileserver\profiles\test". I have set the login script of
the test account to connect to the "\\fileserver\" on login.

Well, the login script isn't going to run until the user is logging in - and
that's only going to happen after the profile is able to load.
When I
try to log into the domain using a test account it tells me that a
roaming profile could not be found.

What are the permissions on each user's folder?
What are the share permissions?
When logging in using a remote Roaming Profile, is the profile
location provided by the DC

It's whatever you put in the user's profile path in their ADUC properties.
or does it work some other way. I think
the problem might be that when logging in, it tries to load the
profile first, but becaus the fileserver location has not been mounted
it can't find the profile. Maybe...

I think you're right, but it might help narrow things down if you answered
my questions above.
Anyway to get this working? Does it matter if the fileserver share is
not mounted on the domain controller?

That isn't relevant. What is relevant is the availability of the NAS, and
the permissions & security set on it. If it isn't capable of particpating in
AD's security model I suggest you find something else, such as a device
running Windows Storage Server.
 
What kind of NAS .... what OS does it run and does it participate in AD?

It's SNAP Server running it's own proprietory OS (which is probably
some variant of Linux). I don't know what you mean by participate in
AD, it DOES synchronize user accounts from the DC.
What did you use to do this, and did you also copy over the permissions? (I
generally use Robocopy from the resource kit for things like this).

I copied it over to the NAS, all the shares on the NAS are readable
and writeable by Domain Users. The test user is part of Domain users
group in AD.
What are the permissions on each user's folder?

Well, i'm only testing the feature with a test account, the test user
in AD is part of Domain Users and the same in the NAS (synced with
AD). Domain Users have full access to the NAS.
What are the share permissions?

Can't remember 100% but as above I think.
That isn't relevant. What is relevant is the availability of the NAS, and
the permissions & security set on it. If it isn't capable of particpating in
AD's security model I suggest you find something else, such as a device
running Windows Storage Server.

Well it DOES synch with AD so I think it does participate in AD.
 
Burning_Ranger said:
It's SNAP Server running it's own proprietory OS (which is probably
some variant of Linux). I don't know what you mean by participate in
AD, it DOES synchronize user accounts from the DC.

I've never used a SNAP server, but I'd be inclined to want my profiles on a
member server in the AD domain.
I copied it over to the NAS,

How, though? You should use something that copies permissions, too.
all the shares on the NAS are readable
and writeable by Domain Users. The test user is part of Domain users
group in AD.


Well, i'm only testing the feature with a test account, the test user
in AD is part of Domain Users and the same in the NAS (synced with
AD). Domain Users have full access to the NAS.


Can't remember 100% but as above I think.

Check the share permissions. Everyone = Full control.
NTFS permissions should be Administrator & System = Full Control. On each
user's profile folder, add the username = full control.

Make sure the owner is the Administrators group.

This is all much easier if you use something that includes permissions when
you do the copy, note!
Well it DOES synch with AD so I think it does participate in AD.

Check the permissions.
 
Back
Top