Thanks ... but on this screwy project, I don't have access to the login script ( amongst other things ) and the new software will be deployed via SaaS from a web connection. So I can only delete the file as part of the install. I cannot guarantee that anyone will close outlook even if asked via memo, and if we have to force Outlook closed programattically the PHB will have yet another fit for inconveniencing the users ... Rock-ME-HardPlace
Erik Goldoff IT Consultant Systems, Networks, & Security ' Security is an ongoing process, not a one time event ! ' -----Original Message----- From: Ben Scott [mailto:[email protected]] Sent: Friday, April 30, 2010 3:23 PM To: NT System Admin Issues Subject: Re: Deleting extend.dat while outlook is open On Fri, Apr 30, 2010 at 2:23 PM, Erik Goldoff <[email protected]> wrote: > The issue at hand is after removal, when outlook starts, the SAV9 plug in > information is still cached in the extend.dat and the end users get an error > message. When we ran into this issue (during an upgrade from one version of SAV to another), we added a something to our user logon script that deleted EXTEND.DAT on every logon. Hasn't caused us any known problems yet. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
