Iniciar sesión
 
InicioBibliotecaAprendizajeDescargaSoporteComunidadForos
Recursos para Profesionales de TI >
> 
> 
Updating Non-domain-joined Clients without an Agent

Answered Updating Non-domain-joined Clients without an Agent

  • martes, 15 de mayo de 2007 14:26
     
     
    Inicie sesión para votar
    0

    We can't install a agent on a client which is not in the domain. I know , that this is not supported.

    But we tried to configure the local policy on the non-domain-joined clients to connect to the wsus 3.0.

    In the console of wsus you can see the clients, but in the sce07 console you can't see the clients.

    After a time the clients disappears from the wsus console, too.

    We don't want to install a second wsus server to manage these clients or servers which are not in the domain, microsoft had to provide an alternative oppurtunity for this case.

     

     

Todas las respuestas

  • martes, 15 de mayo de 2007 16:02
     
     Respondida
    Inicie sesión para votar
    0

    In the SCE console, you should only see clients that have the OpsMgr agent installed.  If you add a computer that is not in the SCE console (doesn't have the OpsMgr agent installed) to a computer group in the WSUS console, it will be removed because we synchronize the members of the WSUS groups to match the membership of the corresponding Computer Groups in SCE.

     

    I haven't tested this, and it's not supported in SCE, but you could maybe accomplish this by creating new groups in the WSUS console and adding the computers to them....although I'm wondering if this would be broken when we synchronize the All Computers group.

     
  • miércoles, 16 de mayo de 2007 7:29
     
     
    Inicie sesión para votar
    0

    thanks for your answer, i can't test it i will try this method at the weekend, because i've got no time at the moment.

    You get an answer, if it works.

     
  • jueves, 17 de mayo de 2007 9:44
     
     
    Inicie sesión para votar
    0

    I also would like to a supported solution. We are looking at just using SCE to manage our servers, but won't be purchasing enough client licenses to cover all our PCs. However, we would still like to be able to control updates for all PCs using WSUS 3.0 (as we used to do with WSUS 2.0).

     

    In this scenario, you should be able to deploy updates to SCE unmanaged machines.

     
  • jueves, 17 de mayo de 2007 16:58
     
     
    Inicie sesión para votar
    0

    the problem still exists. when you create a new group in wsus you get an error in the sce management console that indicate a replication problem between the wsus console and sce.

     
  • martes, 22 de mayo de 2007 9:00
     
     
    Inicie sesión para votar
    0

    This is a real shame. It seems unfortunate that previously we could update all PCs free of charge using WSUS, but just because it is integrated into SCE, you now have to purchase a license for every PC.

     

    I would like to hear what others think. Should there be a way to use the WSUS component  for some machines separate to SCE?

     
  • martes, 22 de mayo de 2007 10:36
     
     
    Inicie sesión para votar
    0

    Hi,

    Are you comparing WSUS and SCE or? In WSUS you can only patch your clients with Microsoft Updates, in SCE you have Software Deployment, Patch Management for both Microsoft and other updates, Hardware/Software inventory and monitoring. Do you mean that this should be free? I wouldn't mind if it was free:-), actually when I had a meeting with the SCE team, I told them that the license fee should be included in Windows/Office instead!

     

    This will actually be true next year, SCE will be included in both the next version of SBS and Centro (Mid size server)

     

    Björn Axéll - Advisec AB

    http://blog.advisec.com

     

     
  • jueves, 24 de mayo de 2007 17:04
     
     
    Inicie sesión para votar
    0

    now i've got the problem with our next customer. They have criticial machines which arent' in the domain. The update feature is unemployable if there is no solution. They will be bothered to manage 2 WSUS Servers. They don't want to deploy software or generate reports on the  machines. Please correct the synchonisation between sce and the wsus database, so that the clients don't disappear.

     
  • viernes, 25 de mayo de 2007 9:42
     
     
    Inicie sesión para votar
    0

     

     

    Hi Bjorn,

    >>Are you comparing WSUS and SCE or? .... Do you mean that this should be free?

    No, I am happy to pay for all the extra features in SCE, for the machines that we want to fully manage. For the the machines that we currently just patch using WSUS, and would like to continue to do so, I want to be able to use the WSUS instance that is installed as part of SCE.

    As it stands, we either purchase SCE licenses for all machines (overkill for what we want to do), or we install a completely separate WSUS server and point the "non-managed" machines at this second WSUS.

     

    Like AchimH, I would like to see a way of overriding the tie between the list of SCE computers and WSUS computers.

     

    Sam