vbscript is best suited to small scripts to do admin type tasks. it is also suited to logonscripts. it has basic gui functionality stand alone. it cant call API's directly, well not without some messing around.
i have vbscripts which are 2000 odd lines long. we use scripts to handle automatic w2k to wxp upgrades on pcs without user intervention. this includes all pre software upgrades, the os upgrade and then post installation software installs and upgrades.
we have a script which handles unattended w2k and wxp installations.
our logon script is based on 4 levels of ini files. enterprise, location, group, user. the logon script is component based and each component is configurable based on LAN/RAS/VPN/WAN. based on connection type you can turn components on or off in each of the ini files, one can also configure the logging options from file, screen, file&screen, eventlogonly, full, file&eventlog.
i guess all i am trying to say is that vbscript is capable of just about anything your imagination and determination allows.
have fun.
start with WSH then moved onto ADSI and WMI would be my advice if you want to look into vbscripts capabilites with regards to windows, AD, computer config and management, automatic builds etc