Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Write filter on thin clients using DS 6.9 SP5

Created: 06 Sep 2012 • Updated: 03 Oct 2012 | 6 comments
This issue has been solved. See solution.

We have about 180 Thin clients deployed across our sites.  All of our new thin clients (HP t5740e's) come with Windows Embedded Standard 7.  After we deploy the network agent via the Deployment Solution Console the write filter keeps on switching back to the "Commit" state instead of being locked.  How can I prevent this from happening? We purchase these so users cant make permanate changes to the system.

Comments 6 CommentsJump to latest comment

MKOKA's picture

Hello Peter,

Do you mean to say that you are unable to install the plugins ? Or after installing the plugins it reverts back to "Commit",

I am considering that you are unable to install the plugins.

 

You may want to disable the Enhanced Write Protection via command line :

EwfMgr.exe C: -disable

Commit the installation via

EwfMgr.exe C: -commit

And if you do not want any user to make any changes further then enable the Enhanced Write Protection via following command Line

EwfMgr.exe C: -enable

 

I hope this helps. Let me know.

Mrinal

 

 

ianatkin's picture

As Peter hasn't come back on this and Mrinal's comments are sensible I am marking Mrinal's post as the solution.

Kind Regards,
Ian./

 

Ian Atkin, IT Services, Oxford University, UK

Connect Etiquette: "Mark as Solution" those posts which assist you most in resolving your problem, and give a thumbs up to useful articles and downloads

Peter_65535's picture

I thought I replied but I guess I didn't.  Its not the command line options which are the problem.  After I deploy the DAgent (using the remote agent installer) to the thin client and enable the write filter, the system keeps reverting to Commit mode, which is an unwanted action.  It should just stay locked as enabled.

After spending awhile on the phone with Symantec support they told me this is a known issue and will be resolved in an update and they gave me an ETA of December.

I have thought about using those commands to clear the commit command as a shutdown or logoff script but that would make it difficult for us to then make changes to the system.

SOLUTION
ianatkin's picture

Hi Peter -thanks for the update!

Ian Atkin, IT Services, Oxford University, UK

Connect Etiquette: "Mark as Solution" those posts which assist you most in resolving your problem, and give a thumbs up to useful articles and downloads

mortenleth's picture

Hi Peter

I might have a customer who has this problem, do you know if there is a subscription somewhere which i can sign up to, so i get a notification when the update is released?

/Morten

ianatkin's picture

Hi Mortinleth, this might be TECH171884

Ian Atkin, IT Services, Oxford University, UK

Connect Etiquette: "Mark as Solution" those posts which assist you most in resolving your problem, and give a thumbs up to useful articles and downloads