Server 2008R2 clear cache for exe from a share

Found another post but the fix doesn't appear to be available on Server 2008 R2.  I have an exe file published in Citrix from a file share.  The file share is server 2008R2 and the Citrix session hosts are server 2008R2.  The exe file is updated by another person that I don't want to have access to the Citrix servers.  Everything works great until he needs to update the exe files.  Citrix keeps using a cached version of the exe files until all sessions are logged off.  I found another post to restart the Superfetch service and this will clear out the cached copy of the exe file.  Server 2008R2 does not appear to have this service.  Does anyone know if there is a way to flush this cache?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brian CTXSupportCitrix ConsultantCommented:
Personally I would use dated folders on the share and put the updated EXE in a new folder each time it is updated, and change the publishing properties to point to the EXE in the new  folder.  New sessions will get the new file and old sessions can stay on the existing file until they are done.  That also gives you a roll-back option in the event of a bad update, and solves the "cache" issue due to the file being in use.
Superfetch is by default disabled in Windows 2008 R2 I guess.
Check this article, it talks about enabling and disabling superfetch. 

To me I will first set EnablePrefetcher Key to  0 (check the article for more details), reboot the server and see if that works for you.
JoePlaistedAuthor Commented:
Thanks for the responses.  I am currently using a different folder for updated exe versions but was wondering if there is a way to disable the caching on Server 2008R2.  I will try the EnablePrefetcher method and let you know.
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

JoePlaistedAuthor Commented:
Thanks for the response.  Tried EnablePrefetcher = 0 and still caches.
Create a new Key with name "EnableSuperfetch" (dword) and set the value to 1
And set the EnablePrefetcher to 0

Check if that helps.
Brian CTXSupportCitrix ConsultantCommented:
I don't think the cache settings are the issue.  It's not going to be able to release an in-use file, regardless of caching.  If closing all of the active sessions resolves the issue, that would confirm my suspicion.
JoePlaistedAuthor Commented:
I tried EnableSuperfetch and disabling Prefetcher.  Doesn't seem to do anything.  Closing the active connections to the exe file seems to release the cache.  What I found that might work is that when I update the exe file within Citrix published Windows Explorer in the same Delivery group new connections to the exe get the upgraded exe while active connections are still able to use the old version until the connection is closed.  When I rename the old exe then I get an error stating that it is in use but I can try again and the file gets renamed.  I am able to rename the new one to what is published in Citrix and new connections get the updated exe file.  I should be able to publish Windows Explorer to the user that needs to modify the exe files and have him use that.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
JoePlaistedAuthor Commented:
Brian's idea would work great but the user that needs to update the executable needs to inform me every time there is a change.  Sometimes the changes are urgent because a function is not working with the current executable.  The method to change the executable through Citrix seems to work well and allows this user to modify the executable when needed without me changing the published application each time.  He is able to fix it right away if he breaks it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.