Writing scripts for remote computer management can save man-hours and shoe leather. But like any part of Windows, it has to be properly secured, or you risk opening up your network to the bad guys.

Over the last few months, we’ve been discussing a variety of security-related topics. We’ve placed a particular emphasis on using Windows Management Instrumentation (WMI) to accomplish these tasks.

It's time to step back a bit, however, and learn some of the technical details of remote scripting before we go any further. It's all well and good to jump in and try things, but sometimes we hit a ...

You could wrap it up as a software install, or run it with something like a login script or psexec, but you could just change the SID on every machine, instead of ...

Can't figure this one out. <BR><BR>I'm a member of the Domain Admins group in a Windows 2000 Mixed Mode domain. No NT servers anywhere though.<BR><BR>My desktop is running Windows XP Sp2. I go to ...

WMI is a DCOM application; therefore, when you make calls to WMI in your script—whether they’ll run on a local or remote machine—DCOM comes into play. If your WMI script attempts to execute WMI ...