It should be noted that WMI does pretty much everything. Seriously it makes most Win32 based extensions obsolete. That is, if you don't mind the overhead that WMI imposes (on faster/more memroy machines this is not so much an issue).
dave -----Original Message----- From: Timothy Johnson [mailto:tjohnson@;sandisk.com] Sent: Wednesday, October 23, 2002 10:38 AM To: 'Patrick J. LoPresti'; Timothy Johnson Cc: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] Subject: RE: Getting Environment Variables of remote machines That works too (and well, I might add). This will still only work on W2k+ systems. -----Original Message----- From: Patrick J. LoPresti [mailto:patl@;users.sourceforge.net] Sent: Wednesday, October 23, 2002 10:25 AM To: Timothy Johnson Cc: '[EMAIL PROTECTED]'; [EMAIL PROTECTED] Subject: Re: Getting Environment Variables of remote machines You could... (wait for it... wait for it...) ...use WMI. http://msdn.microsoft.com/library/en-us/wmisdk/wmi/win32_environment.asp Attached is a script (getenv.pl) which takes a hostname as argument and dumps its user and system environment settings. - Pat _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs _______________________________________________ Perl-Win32-Admin mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
