wmi question with mdt 2008 task sequence

I need to get the size of the hard drive(s) installed in a system and based
on the size partition the drive a certian way. If > 36GB I need to make one
20GB partition but if <= 36GB I need to create one partition using the whole
drive. I need to plug this condition into an mdt 2008 task sequence. I
already know I can do this using vbscript.... add task that is a vbscript
that gets drive properties and sets task sequence variable(s), then have 2
subsequent tasks that execute based on the value of the task squence
variable the vbscript previously set. Both of these tasks would be partition
and format tasks, one for the <=36GB scenario, and one for >36GB scenario,
and only one of them would ever wind up running.

but what I'm wondering is if this is a scenario where wmi would be better?
simpler? cleaner? etc... I have never used wmi but mdt 2008 allows you to
insert a wmi query as a condition in a task sequence... so I'm wondering if
this little task is a good reason for me to try some wmi?

Aside from implementing WMI in VBScript what other options have you looked at
to do this task?

WMI is convenient and easy to use, and can be used to run locally or on
remote machines. The biggest draw back is that it can be slow...

"James" wrote:

> I need to get the size of the hard drive(s) installed in a system and based
> on the size partition the drive a certian way. If > 36GB I need to make one
> 20GB partition but if <= 36GB I need to create one partition using the whole
> drive. I need to plug this condition into an mdt 2008 task sequence. I
> already know I can do this using vbscript.... add task that is a vbscript
> that gets drive properties and sets task sequence variable(s), then have 2
> subsequent tasks that execute based on the value of the task squence
> variable the vbscript previously set. Both of these tasks would be partition
> and format tasks, one for the <=36GB scenario, and one for >36GB scenario,
> and only one of them would ever wind up running.
>
> but what I'm wondering is if this is a scenario where wmi would be better?
> simpler? cleaner? etc... I have never used wmi but mdt 2008 allows you to
> insert a wmi query as a condition in a task sequence... so I'm wondering if
> this little task is a good reason for me to try some wmi?
>
>
>
>