problem with Windows XP SP1 roaming profile requirements
When installing the Windows XP Service Pack 1, we lost the ability to use our roaming profile. A search on the knowledge base revealed that SP1 now requires the ownership of the directory pointed by the User Profile field.
When installing the Windows XP Service Pack 1, we lost the ability to use our roaming profile. A search on the knowledge base revealed that SP1 now requires the ownership of the directory pointed by the "User Profile" field.
So I did take ownership and the only users having rights on this directory are my account and the "SYSTEM" account. Both are set at full control. Now the profile loads just fine! But when I log off, the system keeps telling me it cannot update the profile because of insufficient rights. Now of course my server profile is now about 2 weeks outdated.
Anyone got idea of how to fix this?
By the way I did try setting the profile on my hard disk to test, (I used one of my shared directory) ans the exact same behavior occurs.
By the way here's how we're set up:
One Windows 2000 Server (10.10.0.5)
One Redhat Linux machine (10.10.0.1) with ip masquerading
the DCHP loan ips from 10.10.0.0 to 10.10.0.254 (excluding 1 and 5)
the DNS are those of my ISP
the Gateway are set 10.10.0.1 to enable routing
We had to add a modified HOSTS file to add the following lines
10.10.0.5 onyx
10.10.0.5 onyx.local
(onyx is the domain name)
it was required to avoid waiting like 2 minutes before being able to logon and the roaming profile would refuse to load sometimes
setting the DNS at the server IP also solve the problem but it disables the router (now the internet wouldn't work)
Ideas anyone?
I need that profile to update
So I did take ownership and the only users having rights on this directory are my account and the "SYSTEM" account. Both are set at full control. Now the profile loads just fine! But when I log off, the system keeps telling me it cannot update the profile because of insufficient rights. Now of course my server profile is now about 2 weeks outdated.
Anyone got idea of how to fix this?
By the way I did try setting the profile on my hard disk to test, (I used one of my shared directory) ans the exact same behavior occurs.
By the way here's how we're set up:
One Windows 2000 Server (10.10.0.5)
One Redhat Linux machine (10.10.0.1) with ip masquerading
the DCHP loan ips from 10.10.0.0 to 10.10.0.254 (excluding 1 and 5)
the DNS are those of my ISP
the Gateway are set 10.10.0.1 to enable routing
We had to add a modified HOSTS file to add the following lines
10.10.0.5 onyx
10.10.0.5 onyx.local
(onyx is the domain name)
it was required to avoid waiting like 2 minutes before being able to logon and the roaming profile would refuse to load sometimes
setting the DNS at the server IP also solve the problem but it disables the router (now the internet wouldn't work)
Ideas anyone?
I need that profile to update
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
That did work!
While recreating the directories I did notice something awkward. While the directory was owned by the account that used it, some parts weren't. So I did recreate all the profile tree and took ownership with the corresponding account.
Now everything just work perfectly again...
I must have moved some data in the directory tree that was owned by Administrator. That would explain the errors.
Thanks a lot APK!
While recreating the directories I did notice something awkward. While the directory was owned by the account that used it, some parts weren't. So I did recreate all the profile tree and took ownership with the corresponding account.
Now everything just work perfectly again...
I must have moved some data in the directory tree that was owned by Administrator. That would explain the errors.
Thanks a lot APK!
