VCAP-DTD | Objective 6.3 | Determine Management Requirements for a View Client Design

Determine patching requirements

Depending on the client being used there are a number of methods that can be utilised.

Zero clients have no operating system and no local storage, therefore no OS patches are required, not anti virus or anti spyware. There maybe occasional firmware updates to the hardware, however this will be managed by the vendors propriety software. Wsye for example, have Wyse device manager, Samsung utilise MagicRMS.

Thin Clients will again have their own management software that will allow for updates to be sent, however for those clients running embedded versions of Windows, patch updates and AV solutions will need to be managed via another product. Windows WSUS is an option, however there are more comprehensive solutions available such as Shavlik, Lumension and even SCCM.

Fat clients can continue to be managed as they have been managed previously.

Normally little consideration needs to be given to mobile devices as software is updated from their respective App stores. If your design will need to accommodate a large number of mobile devices, then a MDM solution should be considered.

Establish software distribution requirements

Most thin and zero clients will already come pre-installed with the View client so nothing will need to be installed here, the updates will be managed though the broker software.

For traditional fat clients, then GPO could be used, alternatively, Lumension or SCCM.

Identify client peripheral requirements

This has already been discussed in Objective 6.1, refer back to this post.

Establish security requirements

This has already been discussed in Objective 6.1, refer back to this post.

Comments

  1. and last one seb – 6.2 is also broken 🙂

    I love the series , very very helpful

Speak Your Mind

*