Start a Conversation

Unsolved

Closed

S

2 Posts

451

March 9th, 2023 08:00

First steps: WSM and pushing apps/app policy

First, thanks for taking a second to read this. This small company I'm working for is trying to roll out a group (approx 50) of thin clients (optiplex 3000s). I assisted with a rollout about 10 years ago, but during that time I was mostly focused on simply taking already-made packages and pushing them to devices, monitoring them, and making sure things looked healthy. Now, obviously, WDM is WSM and a lot of things have changed, including trying to figure out how to actually make and setup the items I want on the thin clients using WSM.

I've clearly already done something wrong. Attempting to push a basic .bat file for turning off the write filter (something I remember having to do) is throwing checksum errors, and then figuring 'app' = application, I've attempted to run an install of a small, basic app (notepad++), which has apparently caused the test thin client to be stuck on a 'reconfiguration' screen in perpetuity. 

I'm clearly lacking in basic understanding of these processes. I've spent two days trying to read the administrator guide, but can't find a basic breakdown of... building blocks, I guess. Where should I be starting with all of this?

3 Apprentice

 • 

741 Posts

March 10th, 2023 06:00

You have the admin guide.  Have you had a chance to read through this guide?  It gives some nice examples of building install packages if needed. 

https://dl.dell.com/topicspdf/addons_wes_dg_en-us.pdf

A few key points

  1. When using App policies to install software from WMS,
    1. There is no need to explicitly disable the WF, it is done automatically as part of the process, then enabled when completed
    2. The file/application you push must execute silently.  MSI,MSU,PS,EXE, whatever you push must run and complete without any user interaction.  There is the ability to use command line parameters in the App Policy.
    3. When creating an app policy, the box "Application Installation Timeout" is your friend.  If you don't set this to something reasonable and your installation doesn't automatically exit (success or fail) you will leave your device in a stuck state 

 

No Events found!

Top