XPost: comp.os.linux.advocacy   
   From: ahlstromc@xzoozy.com   
      
   Tom Shelton wrote this copyrighted missive and expects royalties:   
      
   > After serious thinking Lawrence D'Oliveiro wrote :   
   >> In message , Ezekiel wrote:   
   >>   
   >>>> "Lawrence D'Oliveiro"  wrote in message   
   >>>> news:in8vd8$ee7$1@lust.ihug.co.nz...   
   >>>>   
   >>>> They scale up to thousands, even tens of thousands of machines, which your   
   >>>> Windows scripts will not.   
   >>>   
   >>> For starters there is no reason why my scripts wouldn't scale to thousands   
   >>> of users ...   
   >>   
   >> One obvious reason is how you do remote execution. On Linux/Unix systems,   
   >> you can take just about any local command   
   >>   
   >>     cmd   
   >>   
   >> and execute it on a remote host as follows:   
   >>   
   >>     ssh remote_host cmd   
   >>   
   >> whereas on Windows you can???t. The best PowerShell can manage is to use the   
   >> complex and clumsy WMI functions to perform tasks on remote machines, which   
   >> is completely different from how they???re done locally.   
   >   
   > LOL... You are an idiot.  PowerShell v2 lets you create remote sessions   
   > you dolt.  You are stuck in v1.   
      
   Yikes!   
      
      http://www.computerperformance.co.uk/powershell/powershell_remote.htm   
      
      One common problem is ERROR: Access is denied.   
      Solution: Launch PowerShell with elevated rights, in simple language: Run   
      as administrator.   
      
      Security experts will hold up the hands in horror at this suggestion, but   
      if you get the error message: "The rpc server is unavailable", then I   
      suggest that you turn off the firewall on both machines.   
      
   Reinventing ssh/sshd, badly.   
      
   --   
   World War III?  No thanks!   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)