Re: SMS 2003 in multiple AD domains (one forest)

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 12/06/04


Date: Mon, 6 Dec 2004 12:36:08 -0800

When everything is in the same forest you should not have any limitations.
The most important thing is to make sure you lay out your site boundaries
correctly and do not have over lapping boundaries. This would be the only
thing that would cause any issues. Also make sure your SLP is on the central
site so that clients can compare the site boundaries to make the corret
assignment.

-- 
Thanks,
Jeff Harbaugh [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ragnar" <none@all.com> wrote in message 
news:%23ZBU25f2EHA.4004@tk2msftngp13.phx.gbl...
> Hello!
>
> I have some questions regarding SMS 2003 in an Active Directory 
> environment, one forest but multiple domains. Using SMS 2003 AD schema 
> extensions and SMS Advanced Security and SMS Advanced Client.
>
>
>
> Having a SMS 2003 hierarchy with a central primary site and multiple sms 
> primary sites - all in different AD domains but in the same forest. How 
> will the different SMS Advanced Clients discover and find the correct SMS 
> primary site when SMSSITECODE=AUTO? I'm thinking about that the AD 
> information will be stored in /System/System Management containers in the 
> various domains? I know that the SMS site codes is available in Global 
> Catalog, so I guess all this will be handled automatically - both the 
> assignment and roaming? Any limitations when you have SMS Advanced Clients 
> and SMS site systems in different AD domains but in same AD forest?
>
>
>
> The SMS 2003 Concepts, Planning, and Deployment Guide states that if your 
> SMS hierarchy spans more than one AD domain, you must configure the 
> DNS-suffix search order of clients systems to include the DNS suffixes of 
> all domains with SMS clients or servers. Is this due to the SMS clients 
> (including SMS Advanced Client) looking for SMS servers not using the 
> FQDN? I see from a previous post that this also applies to SMS site 
> servers performing discovery.
>
>
>
> Thanks!
>
>
>
>
>
> /Ragnar
>
> 


Relevant Pages

  • SMS 2003 in multiple AD domains (one forest)
    ... Using SMS 2003 AD schema extensions and SMS ... Advanced Security and SMS Advanced Client. ... primary sites - all in different AD domains but in the same forest. ... know that the SMS site codes is available in Global Catalog, ...
    (microsoft.public.sms.admin)
  • Imaged computers and SMS client
    ... ith a disk image via Ghost. ... in SMS with the name of the original, ... image was derived) instead of the name of the newly deployed computer. ... the SMS Advanced Client that came pre-installed is functioning and can ...
    (microsoft.public.sms.installer)
  • How to Distribute Applications Quickly
    ... I have setup a SMS 2003 test lab and need to know I can can minimise the time between installing the SMS advanced client and a notification appearing at the windows xp workstations. ... Application deployment is via group membership. ... Applications are deployed to computer objects, ...
    (microsoft.public.sms.swdist)
  • Re: SMS 2K3 Client on ISA 2004 cant talk to SMS server
    ... This script demonstrates how to set the management point for an SMS Advanced Client. ... In that case, the first parameter is the computer name and the second parameter is 1, which indicates that the first parameter is the computer name. ...
    (microsoft.public.sms.misc)
  • Re: Office 2003 deploy can you use alternate credentials from the comm
    ... SMS Advanced client will only run a program in logged on user or localsystem ... SMS legacy client can run a program in the context SW ... This posting is provided "AS IS" with no warranties, and confers no rights. ...
    (microsoft.public.sms.swdist)