Today is our last technical blog post about configuration samples for client computers. This is a compilation of topics we already discussed partially in the last weeks. We will have a look at settings which affect client runtime behavior, not settings used for server operations.
Client configuration is mostly done in the Lights-Out Console or in Dashboard, some parts (backup or scripts) may require local editing on the machine. First of all let’s start with the basics.
Basic client configuration
The device properties window is used for basic configuration of clients. We discussed that briefly in Day 7: Computers, Network devices and Mobile equipment.
The properties window has two tabs. On “Properties” there is an option (8) which defines the calendar group, the client belongs to. All calendar schedules of the group are applied to this client. The other two settings are on the “Backup” tab. Backup provider selection (1) and action after backup (2) affect the client right away.
Configuration samples for client computers
Runtime behavior is primarily controlled by calendar schedules and to a lesser extent by backup operations. We discussed client schedules on Day 10: Using client computer schedules and calendar groups on Day 11: Using calendar groups.
To summarize: Create and use calendar groups if you want to apply schedules to multiple client computers. These client computers are typically used in a similar manner or in a similar environment. Furthermore you can combine group schedules and individual schedules.
Use schedules to start computers or to perform backups. Keep them running for a fixed amount of time or only if used. And finally stop your computers after a selected point in time to save energy.
To map complex use cases, create multiple adjacent schedules with different properties.
Example 1: Computer with printer attached
Different people may access this computer over the network. Create a schedule with fixed start and end time to ensure it is available.
Example 2: Rarely used computer
A rarely used computer tends to install Windows updates in unfavorable moments. Or it misses a regular backup and you see many complains of the backup software. Create a schedule which will wake the computer after every path Tuesday to install updates. Create a second schedule which will run a weekly backup.
Example 3: Daily used computer
Create a schedule which wakes the computer ahead of your working hours. As a result you can immediately start working because all Windows updates have been already installed.
These are only a few configuration samples for client computers out of the many possibilities you get with Light-Out. I’m sure you will find more use cases. If you like to share your ideas or setups, add a comment.
In the last two articles, we will look at non-technical aspects, namely licensing and feature sets and we will close the series with a look at maintenance and support options.
Here you will find the complete list of all days of our step-by-step series.