4

I know there are a number of suites out there that allow Windows machines on a Domain, or in Active Directory to be remotely administrated (windows updates, program installs, maintenance, etc); but does there exist a package that does this for non-AD/Domain setups?

The kind of things I'm looking for:

  • manage windows updates, + automatic applying
  • custom package pushing (custom scripts, etc)
  • general maintenance, visibily of health
  • works for 2003/2008/2008R2
  • works without Active Directory or being part of a Domain
glasnt
  • 637
  • 2
  • 6
  • 21
  • If they're Windows clients, and they're not joined to a domain, then they're already in a workgroup. They may not all be in the same workgroup but making them so doesn't proffer any centralized management capability. – joeqwerty Mar 21 '12 at 00:37
  • joeqwerty: having them in the workgroup "WORKGROUP" vs a named workgroup, I thought, might help. That's ok, I've removed that confusing statement. – glasnt Mar 21 '12 at 00:49
  • 1
    Not sure who gave this -1, but it seems a legit quality question, even discounting the "niceties" Active Directory gives. – jscott Mar 21 '12 at 00:53

2 Answers2

1

Kaseya and N-able can be used to manage non-domain joined Windows clients.

joeqwerty
  • 109,901
  • 6
  • 81
  • 172
1

A WSUS server can easily be configured as the update server for a workgroup machine.

System Center Operations Manager (SCOM) 2007 would do the job of monitoring health for all 3 operating systems, and can also be set up on workgroup servers

For "packet pushing", depending on what that encompasses, System Center Configuration Manager (SCCM) might just do the job, also with workgroup servers.

You might want to wait a few weeks for the release of the new System Center 2012 suite, if you go with these options

Mathias R. Jessen
  • 25,161
  • 4
  • 63
  • 95