It is causing a conflict with a 3rd party software(Imprivata OneSign) where the user sees the message of "This computer is being serviced" on the subsequent reboot+login after Onesign is installed.  According to the customer, SCCM 2012 does not behave this way.  Microsoft Embedded Device Manager Client doesn't appear to be listed in Add/Remove Programs.

The workstations are Wyse Z90D7 with Windows Embedded Standard 7.

Not sure I get your question here.

It could be very well ConfigMgr 2012 that's causing the behavior as that's how it works with software that needs to be applied and the device is "protected" with a write filter. For an example see: http://blogs.technet.com/b/configmgrteam/archive/2012/11/26/managing-embedded-devices-with-write-filters-in-configuration-manager-service-pack-1.aspx

Let me see if I can explain it a different way...

These Windows Embedded Standard 7 workstations appear to have Microsoft Embedded Device Manager Client already installed and there's no way to remove Microsoft Embedded Device Manager Client from Add/Remove Programs.

1) Is there another way to remove Microsoft Embedded Device Manager Client if it's not listed in Add/Remove Programs?

or

2) Is there a way to prepare a Windows Embedded Standard 7 image for these Wyse workstations without Microsoft Embedded Device Manager Client installed?

Just wondering how you determined that it is installed then.. like I said that behavior could very well be caused by ConfigMgr 2012...

I'm not sure how that product should show-up, or if it even shows-up, but as it's an addition to the ConfigMgr 2007 client I can imagine that it doesn't show up. If it does it's removable via MSI, find the GUID in the registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall) and run MSIEXEC /x <GUID>.

Hi,

Please refer to the following instructions for uninstalling Device Manager 2011 client

Uninstalling Device Manager 2011 Client

http://technet.microsoft.com/en-us/library/hh709721.aspx

So it would appear that Windows Embedded Device Manager(WEDM) is now part of Configuration Manager 2012 SP1:

http://systemscentre.blogspot.com/2012/09/windows-embedded-devices-and.html

And it doesn't look like there's a way to remove just what used to be WEDM, and the customer is not willing to remove Configuration Manager.

If you have Windows Embedded Device Manager 2011 installed on the client machine it will show in Program and Features / Add remove programs.

I have a thin client and have Windows Embedded Device Manager 2011 SP1 installed on it. If required we can also remove this.

Coming back to the original issue, is Imprivata OneSign insalled using SCCM? if so review the settings for deployment, Specially Write Filter handling for Windows Embedded Devices section.

So it would appear that Windows Embedded Device Manager(WEDM) is now part of Configuration Manager 2012 SP1:

http://systemscentre.blogspot.com/2012/09/windows-embedded-devices-and.html

And it doesn't look like there's a way to remove just what used to be WEDM, and the customer is not willing to remove Configuration Manager.

True, managing embedded devices is part of the capabilities of ConfigMgr 2012. Like I said initially, it's just the way it handles write filters. If you want to install software on a write filter enabled device, you can't workaround servicing. It's the best way to temporarily "disable" the write filter, allow an installation and "enable" the write filter again.

So, what you're seeing is just normal behavior.

There's a specific specific installation sequence outlined when installing OneSign on an embedded OS where:

1) the installation needs to be done as a local admin

2) the write filter needs to be disabled before installation.  

3) WEDM needs to be removed prior to installation

SCCM is not being used to install the agent, it's simply present on the thin client.   Following this particular install sequence, there are no issues after the install when SCCM 2012 is present on the thin client.

It's only when SCCM 2012 SP1 is present(even after following the same installation method) on the thin client where we see the stated issue occur.   A user can log in afterwards even when they see the "this computer is being serviced" message, but there's a lengthy delay before the user sees the desktop of the thin client.  

This is isolated to SCCM 2012 SP1, this does not occur with SCCM 2012...because WEDM was not integrated with ConfigMgr on 2012.  I respectfully dispute the notion that this is expected behavior.

Yes, I know this is an old post, but Im trying to clean them up. Did you solve this problem, if so what was the solution?

Since no one has answer this post, I recommend opening  a support case with CSS as they can work with you to solve this problem.