You are browsing the archive for WES.

ConfigMgr 2012 SP1 Beta : Skipping Client prerequisites in the OSD “Setup windows and install Configmgr client” step.

6:22 pm in CM12, ConfigMgr 2012, ConfigMgr 2012 SP1, Operating System Deployment, OSD, SCCM 2012, SCCM 2012 SP1, System Center, WES, WES 2009, WES2009 by Kenny Buntinx [MVP]

 

Hi guys ,

Working for a customer on managing WES 2009 Clients with Configmgr 2012 sp1 in TAP. On of the requirements by the customer was not to install Silverlight 5.0 or .net 4.0 onto the WES2009 Device as they did not manage or support their core image.

The client prerequisites documentation can be found here on technet http://technet.microsoft.com/en-us/library/gg682042.aspx .

Silverlight is not required, Software Center and Software Catalog are the only things that need it.  You can specify a commandline switch on ccmsetup to not install Silverlight.  Example: CCMSetup.exe /skipprereq: silverlight.exe but that only works to client push or manual install in RTM

If my base image has .net 2.x installed and I don’t want install .net 3.0/3.5/4.0 because of lack of disk space – (image being build by another company and no possibility to adjust ) and app compatibility on the embedded, how can I use the */skipprereq* on the OSD “Setup windows and install Configmgr client” step ?

GOOD NEWS ! They fixed that in SP1 . Now you are able to pass that “/SKIPPREREQ” parameter in your  OSD “Setup windows and install Configmgr client” step .

Hope it Helps ,

Kenny Buntinx

ConfigMgr 2007/2012 , WEDM 2011 & HP Thin clients with WES 7 : Part 1

7:40 pm in CM12, ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr 2012, ConfigMgr SP2, ConfigMgr2007 R3, embedded, HP, SCCM 2007, SCCM 2007 R2, SCCM 2007 R3, SCCM 2007 SP2, SCCM 2012, System Center, Task Sequence, ThinClient, WES, Wyse by Kenny Buntinx [MVP]

 

Hi there ,

Your company has decided to invest in thin clients with Windows Embedded standard 7 ? You are already working with ConfigMgr 2007 or Configmgr 2012 ? Then you probably heard about WEDM 2011 ( WIndows Embedded Deivice Manager 2011) , which is a plugin on Configmgr .

Embedded devices such as HP’s thin clients utilize a Microsoft feature called enhanced write filtering. It’s a way of using local memory as a cache for storing the  changes that software makes when running on the client and it may try to write to the disk  but write filtering lets the disk’s original contents be instantly restored by simply rebooting and "forgetting" the changes.

That’s nice, until you want to make permanent changes to the operating system like security patches or install applications like flash player. You might have had to write a script that turned filtering off, applied the patch, then turned filtering on again. And someplace in that scenario, you worked in some time for praying it all worked right before re-engaging the filter. One of the benefits of using WEDM 2011 is that it knows how to programmatically disengage enhanced write filters prior to deploying updates or software.

Like any other vendor , HP , Dell or Wyse have their own way of Managing and deploying OS images. Usually the pre-installation of software on a system is not up-to-date or enough to serve the companies need . Embedded systems have historically been more difficult to manage and maintain than PCs. Until recently!

Hewlett-Packard announced that for the first time, it will offer thin client PCs – systems that run Windows Embedded Standard 7 already – that have Windows Embedded Device Manager 2011 (WEDM 2011) pre-installed. This way, out of the box, customers that run Windows Embedded 7 (based on the Windows 7 kernel) don’t have to install a separate server with their native HP tooling  (even if it’s just a virtual or cloud-based one) to monitor and maintain devices.Now that EDM comes pre-installed on a thin client like a t5570e (right) or t5740e (above) costing somewhere in the mid-three-digit range, depending on configuration, admins can use a thin client to capture and redeploy fully configured system images to a collection of clients.

Microsoft announced System Center 2012 Configuration Manager during MMS , though it will take time for ConfigMgr 2012 WEDM 2012  to make its way into the field. For now, HP’s solution supports SCCM 2007 and EDM 2011.

For managing those devices in ConfigMgr 2007 , you will need a few prerequisites :

Also have these hotfixes and articles by hand , you might need them :

Device Manager 2011 extends the capabilities of Configuration Manager to let you deploy a new or updated operating system image to thin client (a process referred to as device imaging). You can perform device imaging on one device or on a collection of devices using the Configuration Manager console. To do this, you must integrate the following components into your Configuration Manager installation:

That’s it for part 1 , check later for Part 2 when we explain how to implement all the above components for doing the actual work itself Smile

Hope it Helps ,

Kenny Buntinx

SCCM OSD Deployment : The IIS Admin service is not starting anymore on a deployed sysprepped Windows Embedded 2009 with IIS 6.0 installed

12:44 pm in ConfigMgr, ConfigMgr 2007, ConfigMgr 2007 R2, ConfigMgr SP2, configmgr2007, IIS, Installation, Known Issue, OSD, sccm, SCCM 2007, SCCM 2007 R2, SCCM 2007 SP2, sccm2007, script, WES, WES 2009, WES2009, XPe by Kenny Buntinx [MVP]

Lately I have been busy with testing & deploying for a big project some Windows Embedded 2009 devices , called the Advantech ARK –1388 .One requirement from the customer was to have IIS 6.0 installed.We decided to include the IIS 6.0 component into the WES 2009 image with Target builder  ( witch is a tool for building the WES image ), but every time we deployed an image after it had been sysprepped with SCCM, the IIS Admin service would fail to start .

Because this needed to be deployed onto three thousand (3000) WES devices , we contacted Microsoft PSS support for some help. Below you will find our findings and workaround for the issue .

Our problem :

We installed a Windows Embedded 2009 image with IIS 6.0 on a Advantech ARK-1388 and it is running fine.The OS is prepared for system cloning using the sysprep.exe tool ( supported since WES 2009 ).

When we reapplied the master image  with SCCM R2 SP2 and mini-setup was completed, the OS seems to run fine, however the "IIS Admin" service does not start and returns the following error:
"Windows could not start the IIS Admin on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -2146893818."

There are no related errors in the Event Logs. IIS cannot be repair-installed using the Add/Remove Programs component of the Control panel.( this was done to see if we could automate a self –repair )

We would like to deploy the WES image using the OSD feature of SCCM 2007 R2 ,but the problem also occurs when customer calls sysprep.exe manually without the usage of SCCM. ( that’s what we thought , SCCM always works great !! :-) )

 

Our environment :

We have a Windows Embedded 2009 image with IIS 6.0
We have a SCCM 2007 R2 SP2 environment

 

The summary of our troubleshooting :

1. Microsoft CSS discussed with the WES and SCCM teams if WES2009 is supported on SCCM 2007 R2. After a discussion they have modified there statement on the web , see http://blogs.technet.com/configmgrteam/archive/2010/01/25/things-you-need-to-know-when-using-windows-embedded-standard-2009.aspx

2. the proposed workarounds from Microsoft (re-installing MSDTC and IIS) from the " WES Resource Kit" didn’t solve the problem.

3. We checked the FBWF status on the sysprepped image. It was still disabled as it should .

4. Microsoft spoke with the IIS team about the issue. Discussion results:
  a) It’s a known problem that IIS doesn’t work after sysprepping the image because of the changes made by sysprep.
  b) Using sysprep on XP Pro is not supported, see KB326779 "Supported IIS configurations for use with Sysprep"
  c) The only supported solution is to install IIS after the sysprep phase. On XP Pro PCs you can run an unattended IIS installation
     using the Sysocmgr command (which can add or remove Windows Components). E.g. as described in
     KB309506 "How To Perform an Unattended Installation of IIS 6.0"
     Here is the catch !! : Unfortunately Sysocmgr.exe is not shipped with the XPe database ===> meaning that it is impossible to install IIS 6.0 after we have deployed our WES 2009 client !

5. As discussed with Microsoft and the IIS team I tried to "repair" the IIS Admin service after the final sysprep boot by using SysOCmgr.We have copied the missing sysocmgr.exe from an XP Pro SP3 PC and I’ve had to insert an XP Pro SP3 CD into the CD drive for the missing files.We don’t believe this workaround can be used by my customer (legal and technical issues).

6. For a test we have used fbreseal instead of sysprep. The IIS Admin service was running after fbreseal.But as I know deployment via SCCM 2007 OSD requires the usage of sysprep and fbreseal cannot be used in this scenario.

 

Our Solution :

Together with the WES product team & Microsoft PSS support we found an easy workaround to get the "IIS Admin" service running again on the sysprepped WES 2009 image.
The workaround switched off the IIS components in the registry and called the FBAOC.exe tool to re-install IIS.It solved the problem on our test devices.

Here’re the details about this workaround:

1. It doesn’t need the XP Pro SP3 CD.
2. It doesn’t need any file from an XP Pro SP3 PC (like sysocmgr.exe).
3. It doesn’t need to collect any IIS files into a special installation location.

The workaround is just:

1. Uses your original SLX file and WES 2009 image which uses the FBOCMgr phase 5550 for the IIS components.
   It means you can run the workaround on your original sysprep-ed images.
2. Changes some IIS registry settings used by the OS to install IIS.
3. Uses a WES-specific command (FBAOC.exe) which is part of your original SLX file and image.
4. Step 2-3 can be executed by the attached files:

  a) MyIIS-Off.reg      for changing the registry

*********************************CODE BEGIN**********************************

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup\OC Manager\Subcomponents]
"iis_common"=dword:00000000
"iis_inetmgr"=dword:00000000
"iis_www"=dword:00000000
"iis_www_vdir_scripts"=dword:00000000
"iis_www_vdir_printers"=dword:00000000
"iis_doc"=dword:00000000
"iis_ftp"=dword:00000000

*********************************CODE ENDS**********************************


  b) MyIISinstall.bat   runs the workaround (by using MyIIS-Off.reg)

*********************************CODE BEGIN**********************************

@echo off

echo Changing registry settings…
regedt32 /s \MyIIS-Off.reg

echo Enabling IIS features…
\windows\FBA\FBAoc.exe

echo Done.

*********************************CODE ENDS**********************************

Pls. put the files in the C:\ root folder on your sysprep-ed WES 2009 image and call the MyIISinstall.bat file from a command line.

When running properly the batch file will run for 1-2 minutes and it’ll display 3 output lines:
        Changing registry settings…
        Enabling IIS features…
        Done.

Afterwards the "IIS Admin" service should be running.

So this scenario is not supported on XP Pro. But this workaround is supported.
This is a known problem/limitation on XP Pro. The same problem occurs on WES installations because WES uses exact the same XP Pro binaries.

 

Hope it Helps ,

 

Kenny Buntinx