Roaming and local cached profiles

[Guest LJC]

Has anyone seen this problem? I have Windows 2003 SP2 running on a few

servers in terminal services mode with a GPO policy to delete locally cached

profiles. The problem I am experiencing is that the user’s profiles are not

getting completely deleted. The index.dat file, cookies folder and local

settings folder remain on the servers. Now every time when users login they

get a new user profile folder with their name appended with a new number

(.001 )

 

What can I do to make sure the profiles get completely deleted?

 

Thanks,

 

Lenny

[Guest Frankster]

Re: Roaming and local cached profiles

 

 

"LJC" <LJC@discussions.microsoft.com> wrote in message

news:21D2E19D-B5F7-4BF9-ACCD-3EC3C997EB2B@microsoft.com...

> Has anyone seen this problem? I have Windows 2003 SP2 running on a few

> servers in terminal services mode with a GPO policy to delete locally

> cached

> profiles. The problem I am experiencing is that the user’s profiles are

> not

> getting completely deleted. The index.dat file, cookies folder and local

> settings folder remain on the servers. Now every time when users login

> they

> get a new user profile folder with their name appended with a new number

> (.001 )

>

> What can I do to make sure the profiles get completely deleted?

>

> Thanks,

>

> Lenny

>

 

The only times I have seen this happen was due to either permission or

connectivity issues that needed to be solved.

 

-Frank

[Guest LJC]

Re: Roaming and local cached profiles

 

Frankster,

 

Thanks for getting back. What in particular should I check for regarding

permissions?

 

Lenny

 

"Frankster" wrote:

>

> "LJC" <LJC@discussions.microsoft.com> wrote in message

> news:21D2E19D-B5F7-4BF9-ACCD-3EC3C997EB2B@microsoft.com...

> > Has anyone seen this problem? I have Windows 2003 SP2 running on a few

> > servers in terminal services mode with a GPO policy to delete locally

> > cached

> > profiles. The problem I am experiencing is that the user’s profiles are

> > not

> > getting completely deleted. The index.dat file, cookies folder and local

> > settings folder remain on the servers. Now every time when users login

> > they

> > get a new user profile folder with their name appended with a new number

> > (.001 )

> >

> > What can I do to make sure the profiles get completely deleted?

> >

> > Thanks,

> >

> > Lenny

> >

>

> The only times I have seen this happen was due to either permission or

> connectivity issues that needed to be solved.

>

> -Frank

>

>

[Guest Frankster]

Re: Roaming and local cached profiles

 

Just make sure they have read/write/delete (usually full) file permissions

in their profile directory. Also that the share itself allows them full

permissions.

 

-Frank

 

"LJC" <LJC@discussions.microsoft.com> wrote in message

news:3A08B74A-A5E5-4E36-9761-CF07D40365C0@microsoft.com...

> Frankster,

>

> Thanks for getting back. What in particular should I check for regarding

> permissions?

>

> Lenny

>

> "Frankster" wrote:

>

>>

>> "LJC" <LJC@discussions.microsoft.com> wrote in message

>> news:21D2E19D-B5F7-4BF9-ACCD-3EC3C997EB2B@microsoft.com...

>> > Has anyone seen this problem? I have Windows 2003 SP2 running on a few

>> > servers in terminal services mode with a GPO policy to delete locally

>> > cached

>> > profiles. The problem I am experiencing is that the user’s profiles are

>> > not

>> > getting completely deleted. The index.dat file, cookies folder and

>> > local

>> > settings folder remain on the servers. Now every time when users login

>> > they

>> > get a new user profile folder with their name appended with a new

>> > number

>> > (.001 )

>> >

>> > What can I do to make sure the profiles get completely deleted?

>> >

>> > Thanks,

>> >

>> > Lenny

>> >

>>

>> The only times I have seen this happen was due to either permission or

>> connectivity issues that needed to be solved.

>>

>> -Frank

>>

>>

[Guest LJC]

Re: Roaming and local cached profiles

 

Frank,

 

Thanks I'll recheck permissions

 

Lenny

 

"Frankster" wrote:

> Just make sure they have read/write/delete (usually full) file permissions

> in their profile directory. Also that the share itself allows them full

> permissions.

>

> -Frank

>

> "LJC" <LJC@discussions.microsoft.com> wrote in message

> news:3A08B74A-A5E5-4E36-9761-CF07D40365C0@microsoft.com...

> > Frankster,

> >

> > Thanks for getting back. What in particular should I check for regarding

> > permissions?

> >

> > Lenny

> >

> > "Frankster" wrote:

> >

> >>

> >> "LJC" <LJC@discussions.microsoft.com> wrote in message

> >> news:21D2E19D-B5F7-4BF9-ACCD-3EC3C997EB2B@microsoft.com...

> >> > Has anyone seen this problem? I have Windows 2003 SP2 running on a few

> >> > servers in terminal services mode with a GPO policy to delete locally

> >> > cached

> >> > profiles. The problem I am experiencing is that the user’s profiles are

> >> > not

> >> > getting completely deleted. The index.dat file, cookies folder and

> >> > local

> >> > settings folder remain on the servers. Now every time when users login

> >> > they

> >> > get a new user profile folder with their name appended with a new

> >> > number

> >> > (.001 )

> >> >

> >> > What can I do to make sure the profiles get completely deleted?

> >> >

> >> > Thanks,

> >> >

> >> > Lenny

> >> >

> >>

> >> The only times I have seen this happen was due to either permission or

> >> connectivity issues that needed to be solved.

> >>

> >> -Frank

> >>

> >>

>

>