Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AFPS 4.0.2 and Win2k roaming profiles

Status
Not open for further replies.

Sunemaster

IS-IT--Management
Jun 26, 2002
2
DK
Hi all!

We're having some problems in Windows 2000 with roaming profiles placed on
an SCO Openserver 5.0.6 with AFPS 4.0.2.
_Probably_ WinXP will have the same problems.

Problems:
1.
Antivirus software prevents Win2k from renaming the uploaded "ntuser.dat"
file.

2.
Win2k cannot update directories in the user profile. Says "The system cannot
find the file specified"


Details:
1.
When Win2k updates the profile located at the server, it uploads
"ntuser.dat" as a ".tmp" file, deletes the original "ntuser.dat" and renames
the ".tmp" file to "ntuser.dat".
A real-time AV scanner prevents Win2k from performing the final task.
(renaming the ".tmp" file, that is)
At least the problem goes away, if the real-time scanning is disabled.

2.
As far as I know, Win2k needs less restrictive permissions for updating a
roaming profile directory than WinNT4.
But even though that there has been granted "Full Control" on both the share
permissions and the "NTFS" permissions, Win2k is not able to update the
directory structure.
AFPS is set to ignore UNIX permissions.
While logging out of Win2k, the error "The system cannot find the file
specified" pops up.
I believe that Win2k tries to update ACL's as well as the directories, while
WinNT4 only does directories.
If UserEnv debugging is enabled in Win2k, I can see an error message that
states that Win2k "...failed to copy over the attributes for..."


Questions:
1.
Are any of you aware of any settings in AFPS that could possibly be the root
of the AV problem?

I was kind of having a far out idea about perhaps an enabled WriteBehind
setting could cause something like that.
Read about a similar problem in Compaq's Advanced Server for their Tru64UNIX
OS. But I think that had something to do with a read-only bit setting
somewhere.

2.
This one has really bugged me.
Again: Do you know of any settings that could be the problem?
This seems to be a problem with or without permission inheritance.


I really hope there's someone out there who can help me.

Thanks a lot!

--

Kind regards
Sune T. Tougaard
SeriousSysadm
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top