locked
embedded devices RRS feed

  • Question

  • We have a lot of Dell thin clients which use the Write-Protect technology.  So while the write-protect is Enabled you can't install anything.   I read this link  https://technet.microsoft.com/en-us/library/gg682132.aspx#BKMK_DeployClientEmbedded  and it says the following:

    If your Windows Embedded device does not include the Configuration Manager client, you can use any of the client installation methods if the device meets the required dependencies. If the embedded device supports write filters, you must disable these filters before you install the client, and then re-enable the filters again after the client is installed and assigned to a site.

    We currently are not using CM2012 to build our thin client OS, we are using the Dell provided method.    How can you pre-stage your CM2012 client on a Write-Protected device?   We can Allow the CCMEXEC.EXE as an exception so it can run freely on the device but doing that did not seem to work, or at least the full client never installed, we got a partial client install.  Are there other .EXE's from CM2012 we need to allow to run as Exceptions?   


    mqh7

    Wednesday, June 10, 2015 2:16 PM

Answers

All replies

  • Hi,

    How do you set your exceptions? Follow this

    How to Manage Windows Embedded Write Filters Using System Center 2012 Configuration Manager


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 11, 2015 5:52 AM
  • thanks, that is a really helpful link !!  it talks about adding registry keys to the exclusion list.    when running fbwfmgr /addexclusion  I did not see anyway to add a reg key.  how is that done?

    mqh7

    Thursday, June 11, 2015 8:38 PM
  • Hi,

    This blog would be helpful

    Everything you wanted to know about FBWF but were afraid to ask? Including how it might be made to work on XP Pro.....

    In addition, why not just disable it before you install the client, and re-enable after this is done.


    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    • Marked as answer by mqh7 Friday, June 19, 2015 2:54 PM
    Friday, June 12, 2015 2:16 AM
  • I will look at this.  and we did exactly that.  We turned off the write-protect, installed the cm2012 client and then turned on the write-protect.   the cm2012 client did not fully function.   Example:  Software inventory never worked.  

    mqh7

    Friday, June 12, 2015 1:29 PM