How do I deploy and run Datashift-Printer.vbs on all clients using SMS 2003?

I want to collect network printer information for each client in my organisation.  I downloaded the from '' and extracted the file renaming it to 'DataShift-Printer.vbs'.  I created a package in SMS 2003 with DataShift-Printer.vbs as the source file and created a program with the command line 'cscript.exe DataShift-Printer.vbs'.

I amended the sms_def.mof on the server by adding the following:

#pragma namespace("\\\\.\\root\\cimv2\\sms")
[SMS_Report(TRUE), SMS_Group_Name("SMX Printers"),
class SMX_Printer : SMS_Class_Template
[SMS_Report(TRUE)] string Comment;
[SMS_Report(TRUE)] boolean Default;
[SMS_Report(TRUE)] string DeviceID;
[SMS_Report(TRUE)] string DriverName;
[SMS_Report(TRUE)] boolean Local;
[SMS_Report(TRUE)] string Location;
[SMS_Report(TRUE), key] string Name;
[SMS_Report(TRUE)] boolean Network;
[SMS_Report(TRUE)] string PortName;
[SMS_Report(TRUE)] uint32 PrinterState;
[SMS_Report(TRUE)] string ServerName;
[SMS_Report(TRUE)] boolean Shared;
[SMS_Report(TRUE)] string ShareName;

I advertised the program to a test client and forced a hardware inventory.  SMX Printers is now displayed in Resource Explorer for that client but it only lists local printers.

I ran the vbs locally on the client and forced another hardware inventory.  The list of SMX Printers in Resource Explorer for that client now displays local AND network printers.

Why will the script work locally but not when deployed using SMS?  Am I doing something wrong?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Adam LeinssServer SpecialistCommented:
Under what account are you running the script in package: administrator or the user?  If you use administrator, it uses the computers local SYSTEM account which does not have access to Active Directory.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.