Re: Secondary Site Setup
From: Kim Oppalfens (kim_at_computacenter.nospam)
Date: 02/23/05
- Next message: mcseNewbie: "Re: Management Point"
- Previous message: Kim Oppalfens: "Re: SMS 2003 - Distribution error when getting software from NT 4 domain"
- In reply to: Jeff Harbaugh [MSFT]: "Re: Secondary Site Setup"
- Next in thread: Atif Gul [MS]: "Re: Secondary Site Setup"
- Reply: Atif Gul [MS]: "Re: Secondary Site Setup"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 23 Feb 2005 12:12:52 +0100
Jeff,
Putting the account in the administrators group will indeed solve the
communication problem. Putting the everyone account in the domain admins
group would most likely solve it as well, but both have a varying degree
of overkill.
Shouldn't adding the account to the sms site to site connection group be
sufficient?
Kim
article <esmnpGRGFHA.2932@TK2MSFTNGP15.phx.gbl>,
jeffharb@online.microsoft.com says...
> First of all the error 5 in the sender log is access denied. Please make
> sure you have added the machine account of the primary site to the local
> admin group of the secondary site. And vice versa.
> Net localgroup Administrators machinename$
> That should fix the communication problem.
>
> 2. You can put an MP on the secondary site and it will serve as a proxy MP.
> All advanced clients only report to primary sites. However, they will
> receive policy through the proxy MP.
>
>
-- Kim Oppalfens Proud father of Lennart Oppalfens Since 05/11/2004 08.53 GMT+1
- Next message: mcseNewbie: "Re: Management Point"
- Previous message: Kim Oppalfens: "Re: SMS 2003 - Distribution error when getting software from NT 4 domain"
- In reply to: Jeff Harbaugh [MSFT]: "Re: Secondary Site Setup"
- Next in thread: Atif Gul [MS]: "Re: Secondary Site Setup"
- Reply: Atif Gul [MS]: "Re: Secondary Site Setup"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|