So it’s pretty simple, you create a baseline with whatever fixlets/tasks in the order you want them to install. Make sure they all have actions selected (usually default action). You’ll also want to make sure that the relevance for each component is something that changes on a successful install. If you have a task that just runs on a given condition you can find that potentially looping and that’s bad mmk.
Once the baseline is created, deploy it with no expiration and set is reapply whenever relevant. Target dynamically by property > by retrieved properties > by OS type > server (assuming you don’t have non-Windows servers, but it’s also pretty safe because any good fixlet/task does its own OS check before running). If you don’t have ‘by OS type’ you’ll need to go to ‘computers’ and right click on the headings bar and search for ‘OS type’ which should be in the ‘BES Inventory and License’ site. If you don’t have that module you can create the analysis property from scratch. There’s a couple ways to do that which you’re probably better looking up a guide on creating properties, but the relevance for it is:
if (name of operating system as lowercase starts with "win") then (if (name of operating system = "Win95" OR name of operating system = "Win98" or name of operating system = "WinME") then "Workstation" else (if (value "ProductType" of key "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ProductOptions" of registry = "WinNT") then "Workstation" else "Server")) else "Unknown - " & name of operating system
Bear in mind that if you update the baseline you will have to stop the action and set it up again.