Re: Another Best Practice Questioen

From: Evan [MSFT] (esc_at_online.microsoft.com)
Date: 06/24/04 

Date: Thu, 24 Jun 2004 09:05:31 -0700

No doubt the reason they don't install is that SMS 2003 RTM does not support
computers in workgroups - they must belong to a domain. However...

SMS 2003 SP1 (when it is released) provides limited support for computers in
a workgroup, with the following conditions and exceptions.

Workgroup support is for Advanced Clients only.
Clients must use NetBIOS for name resolution.
Administrative user rights on the computer are required to installing the
SMS client software.
Active Directory discovery and user targeting is not supported.
Advertisements targeted to Active Directory objects, users, or user groups
is not supported.
Global roaming is not supported. 

-- 
This posting is provided "AS IS" with no warranties, and confers no rights.
"BET" <BET@discussions.microsoft.com> wrote in message
news:566B40CE-0791-4DFC-9D2B-FC9C142FE8E3@microsoft.com...
> What is the best approach?
>
> I have a single site. The site is using advance security and all clients
are Windows2000 & XP Pro. I have setup a test lab before going to
production. The question is we have several remote sites using fractional
T1's and no secondaries installed. I am having great problems discovering
the remote clients. The remote clients are not part of AD, they are
configured for a workgroup. So in my lab I pointed the workgroup clients to
the WINS server which is on the two DNS servrers. I discovered the one
client but did not get a completed component installation. The System
Management icon in control panel showed that not all components installed.
In addition the Site code was not populated. Now at the site system you
could see it was assigned to the site. So I manually entered the site code
and applied this setting. Next I repaired the installation on the client
which is a XP Pro. I could see that the remote client registry was being
increased by the CCMSETUP script.
>
> My question is what is the best practice for handling this remote client?
should I recommend going with a secondary. Would this help discover and
better install my workgroup clients? I not sure my client will want to spend
the money to put servers at each location. But if that is my only route then
that is what I would like to present to them. If there are better options
please share them with me.
>
> One other thing each site only have 4 or five client the most.
>
> thanks,
>
> Bill

Relevant Pages

  • Re: Authentication on PIX, WatchGuard, Safe@Office & SonicWall
    ... The mobile user software works well, I've not had any problems with it. ... I use it for clients that have traveling support or sales staff. ... in cases where I install something that the client might have ...
    (comp.security.firewalls)
  • Re: From VC6 to .NET 2 questions
    ... Tech support is expensive. ... controls, or something that involves automation, either as a client or server. ... but those decisions are not mine but my clients'). ... correct version was installed because it was part of their install support problem. ...
    (microsoft.public.vc.mfc)
  • Re: Using Terminal Services for client support.
    ... Our main reason for looking into switching programs is the clients we ... Many want us to use Terminal Services to support the servers we ... install rather than having to purchase a PcAnywhere license. ...
    (microsoft.public.windows.terminal_services)
  • Re: domain client login
    ... deployed are members of the domain? ... On most of clients in the network ... see Help and Support Center at ... > available for domain WORKGROUP. ...
    (microsoft.public.win2000.active_directory)
  • Re: No MS Licence Support 24 / 7??? Client Add On Pack Password Problem
    ... When you purchase your replacement ... >> install and the Client Add on Pack disk will not allow me ... >> to install the clients on this different hardware without ... >> a password from MS support. ...
    (microsoft.public.backoffice.smallbiz2000)
Loading