RE: SMS Client deployment
From: Rhys (Rhys_at_discussions.microsoft.com)
Date: 03/18/05
- Next message: Richard Threlkeld
: "Re: Have Collection Exclude DC's" - Previous message: Rich: "RE: MP_CONTROL_MANAGAER Errors"
- Next in thread: Kim Oppalfens: "RE: SMS Client deployment"
- Reply: Kim Oppalfens: "RE: SMS Client deployment"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 18 Mar 2005 08:45:17 -0800
Put a file (not a folder) into the system folder called MS. Make sure it has
no extension. SMS 2.0 needs to create a folder called MS in the c:\winnt or
c:\windows directory to install. This file prevents the folder from being
created and will stop the installation process. There is probably a better
way to do this but it works. Test this first. It's cheap and cheesy and won't
stop them from being discovered but works.
"yaba daba doo" wrote:
> I am deploying one of the remote sites with about 50 users. all of them were
> success but 3. They are giving me following error in CCMsetup\log on the
> client
>
> Source \\BUSS5450\SMSClient\I386 is inaccessible (53)
> Failed to find accessible source. Waiting for retry.
>
> in the ccmsetup some of the installation files were missing.
>
> on one of the client I actually installed it manually and in advanced tab it
> shows the site code but on the site server it does show it as 'client'
>
> these might be two different problems.
>
> question 1) how can I fix this problem
> question 2) how can I stop automatic retries every 10 minutes in the future.
>
> facts:
>
> MS Server 2003 std
> MS SMS 2003 sp1 advanced security extended schema
> MS XP professional client
>
>
> Thanks folks
- Next message: Richard Threlkeld
: "Re: Have Collection Exclude DC's" - Previous message: Rich: "RE: MP_CONTROL_MANAGAER Errors"
- Next in thread: Kim Oppalfens: "RE: SMS Client deployment"
- Reply: Kim Oppalfens: "RE: SMS Client deployment"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
