Re: NT4 Domain Design Question

You'd need to install your SMS 2003 servers and site systems on Windows 2003
servers. You could make your Windows 2003 servers member servers in the NT
4.0 domain.

Steve
"MPR2609" <MPR2609@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:358ED980-E417-4D7A-A18B-160B892B3198@xxxxxxxxxxxxxxxx
> Hi
>
> I'm in the process of designing an SMS 2003 infrastructure and want to
gauge
> the best way forward. The client is upgrading to windows 2003 active
> directory by March 2006 but have an urgent requirement to distribute a
> business critical app across their environment by August 2005. I've toyed
> with the idea of creating a 'management active directory domain' but as
this
> would be the first AD domain, it would also be the forest root. Creating
two
> new domains (forest root and management domain) for the sole purpose of
> manageing the NT4 domain and providing a more structured upgrade path
seems a
> bit overkill considering the urgency of the project. I suspect the client
may
> be pushed down a forest model to comply with certain security requirements
by
> 2006 but they quite like the idea of a single domain model even when they
go
> to 2003 active directory.
>
> Also, Most of their clients are windows 2000 sp4 so would be applocable
for
> the advanced client.
>
> My thoughts are to implement sms 2003 with NT4, albeit sacrificing
advanced
> security and the obvious advantages of AD integration. This can be done at
a
> later stage.
>
> Any thoughts?
>
>
>
>
>
>
>


.

Relevant Pages

  • RE: DFS
    ... Based on my research, to enable all features in DFS Namespaces, you must ... Servers where namespace management tasks are performed must run Windows ... Clients that access namespaces can run any of the supported client ...
    (microsoft.public.windows.server.sbs)
  • Re: Rolling Out Office 2003 Fails
    ... This is not an SMS issue, but rather an Office 2003 issue when you ... installation on a clean Windows 2003 Server and it runs smoothly, ... Advancec Client tab on the advertisement is set to "run program from ... Software Installation Account. ...
    (microsoft.public.office.setup)
  • Re: subnet inclusion in the AD site boundary is not being seen by
    ... Are you sure the other 50 servers weren't manually assigned? ... Windows Server System MVP - SMS ... subnet to the SMS site boundaries - even though their subnet is already part ... the sms client is in the correct ad site ...
    (microsoft.public.sms.setup)
  • Re: Client Push Installation Running but not Working
    ... I am new to SMS and just finish creating an SMS Server/Console (Windows Server 2003). ... I am trying to do the Client Push Installation through the console and when I check the Client's Window's Task Manager, the ccmsetup.exe is in the taskbar but not moving. ... I also notice the following Site Status Critical Errors such as: "SMS Site Component Manager failed to install this component because it either can't find or configure IIS BITS Server Extensions." ...
    (microsoft.public.sms.installer)
  • Re: SMS 2003 and NAT firewall
    ... To get the full function of the SMS client, you need the IP's to be 'real' ... the IP assigned to the client by DHCP should be the one you ... There are numerous issues with NAT including but not limited to site ... > How does the SMS site servers behaves in a NAT environment? ...
    (microsoft.public.sms.misc)
Quantcast