Search the Community
Showing results for tags 'serviced'.
Found 2 results
Good morning, Ever since I started using the Current Branch version of SCCM, I experience issues with clients showing the "This computer is being serviced" message. This week I made a complete new image for our Thin Clients, based on Windows Embedded 8.1 Industry Pro. I followed the correct guide for creating this image and removed the SCCM client locally before capturing the image. Now when I deploy this image onto four different Thin Clients, two of them are showing the message after a second reboot. So the first boot after the task sequence is being deployed, I won't see the message. Then I log on with a test user account and everything works. After a logoff and restart again, those two Thin Clients are showing the message and the other two does not. I had these problems before with an earlier image but then, when I would log on as Administrator, the system gave me a message after a while te reboot the system and after the reboot the message was gone. With that earlier version the Write Filter would also be disabled when the message was being showed. Now with the latest image, the Write Filter is enable and still I get the message. I have been searching all over the internet for help but can't seem to find any solution. PS: our SCCM environment is upgraded to the 1702 version with the latest hotfix rollup deployed.
We are using SCCM 2012 in an environment that includes many Windows Embedded Standard 7 (WES7) clients. Sometimes we have problems with them getting stuck in Servicing Mode (screen says "This computer is being serviced" and prevents users from logging in). There is nothing deployed to them, but I believe the SCCM client (which is in the master image) is installing the WindowsFirewallConfigurationProvider.msi package. I have two questions: #1 How can we tell WHAT the WES7 client is doing or WHY it went into servicing mode? I found this great article about WEDM 2011 that says there is a log at \ProgramData\Microsoft\EDM\emdstate.txt but that is not the case for SCCM 2012. #2 How can we get a client out of servicing mode if it enters it at an inopportune time? Again, the article for WEDM says to use the commands "Edmwfcmd.exe /unlock" and "Edmwfcmd.exe /wfEnable" but these do not work with SCCM 2012. Your help is much appreciated!!!