Thanks for your reply,
We have used that function before, it simply doesnt work consistently for
us, the issue seems to be that it doesnt always delete the profile (in fact
it fails more often than not), then when the user logs back on again it
creates another version with typically a number appended to the end of the
filename.
Have you any other thoughts?
Thanks,
Phil
"BT" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> oh!! forgot to attachment the KB no.
>
> Microsoft Knowledge Base Article - 274152
>
http://support.microsoft.com/default...roduct=win2000
>
> BT
>
>
> "Phil Holmes" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > Many of our W2k pro client machines create "extra" local copies of
roaming
> > profiles,
> >
> > e.g.
> >
> > C:\Documents and Settings\user.name.001
> >
> > C:\Documents and Settings\user.name.domain.001 etc
> >
> >
> >
> > The profiles are defined in the user objects in AD and stored on a
Windows
> > 2k adv cluster share.
> >
> >
> >
> > This is problem causes the paths in applications to be wrong.
> >
> > In fact the whole roaming profile thing does not seem to work
> consistently,
> > sometimes changes are not copied back to the server.
> >
> >
> >
> > How can I stop this from happening?
> >
> >
> >
> > Any help would be greatly appreciated.
> >
> > Phil
> >
> >
>
>
Similar Threads
