B
Bart Perrier
I am needing to deploy some software to workstations that are Windows 95
(this is not a typo).
What I have done so far is define a BAT file in AD for the User Login Script
that uses the START \\myvbScript.vbs.
The vbScript then tries to make a WINMGTS: connection and when it fails
(Err.Number = 432, Class does not exist) it calls my 9xInstall.BAT file. For
the most part this works since we do not have the WMI Core Environment out
there but I'd rather be checking for the OS specifically, since that is what
I really need to know. Unfortunately, I cannot find a way to do this without
using WMI.
Is there an object I can use to get the OS in vbScript or even a command in
the BAT file that I can rely on?
As always, thanks.
Bart Perrier
(this is not a typo).
What I have done so far is define a BAT file in AD for the User Login Script
that uses the START \\myvbScript.vbs.
The vbScript then tries to make a WINMGTS: connection and when it fails
(Err.Number = 432, Class does not exist) it calls my 9xInstall.BAT file. For
the most part this works since we do not have the WMI Core Environment out
there but I'd rather be checking for the OS specifically, since that is what
I really need to know. Unfortunately, I cannot find a way to do this without
using WMI.
Is there an object I can use to get the OS in vbScript or even a command in
the BAT file that I can rely on?
As always, thanks.
Bart Perrier