Now, that is interesting because I prevent the Temporary Internet Files
folder from roaming with the profile as many of my users tend to build up
rather large profiles with their internet activity... Arrgh! - It's all my
fault!!

Thanks Louis!

PBB




-----Original Message-----
From: Joyce, Louis [mailto:[EMAIL PROTECTED]] 
Sent: 04 December 2001 15:17
To: Exchange Discussions
Subject: RE: Spurious attachment permissions issue...


The way i do it when i have the problem is to just simply make sure they
have a Temporary Internet Folder in their roaming profile. I dont do any of
the registry editing or anything. Make sure they are logged out first.

Regards

Mr Louis Joyce
Computer Support Analyst
Network Administrator
BT Ignite eSolutions




-----Original Message-----
From: Paul Bouzan [mailto:[EMAIL PROTECTED]]
Sent: 04 December 2001 14:53
To: Exchange Discussions
Subject: RE: Spurious attachment permissions issue...


Very very close except there is no TS in the mix.  I did come across this
and even tried the reg hack to see if it worked... but no, sadly.  Thanks
anyway...

PBB


-----Original Message-----
From: Joyce, Louis [mailto:[EMAIL PROTECTED]] 
Sent: 04 December 2001 14:36
To: Exchange Discussions
Subject: RE: Spurious attachment permissions issue...


http://support.microsoft.com/support/kb/articles/Q268/7/44.ASP

Try this.

Regards

Mr Louis Joyce
Computer Support Analyst
Network Administrator
BT Ignite eSolutions




-----Original Message-----
From: Paul Bouzan [mailto:[EMAIL PROTECTED]]
Sent: 04 December 2001 14:33
To: Exchange Discussions
Subject: Spurious attachment permissions issue...


~ndi

EX5.5 sp4 - 1 site, 11 servers - all attached via leased lines.  Clients are
all O2K on NT4 sp6a - identical builds.

Random users at different sites complain of the inability to open
attachments, getting a failure because of a lack of permissions.  The
not-so-helpful help message suggests saving the attachment first which of
course does not work... because of a lack of permissions.  Other users
equivalent to the affected user who also receive a copy of the message can
open it OK therefore because of single-instance messaging I can discount a
corrupted file issue.   Having the affected user send me the message, I can
open it fine.  

The only resolution so far is to eventually trash their NT profile - once
recreated the problem goes away.  This is obviously not the best way to do
it.

I have done the usual searches of the archives, MS support and even some
anti-virus sites and the web in general but no joy.  Any ideas or pointers
would be most appreciated.

Regards,

Paul W. Bouzan.
Network Manager.
Millfield Group plc.
T 020 8680 5200
F 020 8680 5900
M 07940 583525


_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to