Re: CLient installation failure
From: Jeff Harbaugh [MSFT] (jeffharb_at_online.microsoft.com)
Date: 10/04/04
- Next message: Luke Packard [MSFT]: "Re: SP1 secondary sites upgrade failed"
- Previous message: TV: "SMS 2.0 and DC"
- In reply to: Clay White: "Re: CLient installation failure"
- Next in thread: Kerwin Medina [MSFT]: "Re: CLient installation failure"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 4 Oct 2004 13:54:30 -0700
It sounds like you have a boundary issue. The client is de-installing
because it does not match the site boundaries. Please verify again that
these are correct.
-- Thanks, Jeff Harbaugh [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. "Clay White" <clay.e.white@wellsfargo.com> wrote in message news:2f3e01c4aa4e$e2819290$a301280a@phx.gbl... > Thanks, > > That was exactly what was trying to remember! I did > try that though, and can watch the SMS directories > getting built, then, in the middle of installing they un- > install themselves. > > Clay >>-----Original Message----- >>Are you using smsls.bat? Since you say that this is a > remote site, could the >>problem be that the slownet checking in smsls.bat causes > it to bail out >>before installing the client? >> >>When you talking about the file copy to CAP, I guess you > talk about CCR's. >>Just create a text file with the following and copy it > to >>\\<server>\cap_<sitecode>\ccr.box\<randomname>.ccr : >> >>[NT Client Configuration Request] >>Machine Name=COMPUTERNAME >>Forced CCR=True >> >>Rgds, >>Rune >> >> >>"Clay White" <clay.e.white@wellsfargo.com> wrote in > message >>news:1f5001c4aa43$34a4e8d0$a501280a@phx.gbl... >>> Here's my scenario: >>> >>> I have an SMS 2.0 /SP5 setup that has worked fine. I >>> installed some new servers out in a remote site and SMS >>> client & tools will not install properly no matter >>> what. The new servers are in utilizing fixed IP's > that >>> are within the site boundaries, the various SMS > accounts >>> have been given local access to the servers. the > client >>> tries to install but never finishes and gives no >>> errors. The %windir%\MS\SMS\CORE directory is created >>> but no other. I dimly recall (I am over 40 and have >>> slept) that there was a way that I could edit a > specific >>> file by putting the machine name of the problem machine >>> in this file, then copy it to a directory on the sie >>> server's cap directory? ring any bells? Any help >>> would be much appreciated. Thanks, >>> >>> Clay E. White >>> >>> clay.e.white@wellsfargo.com >> >> >>. >>
- Next message: Luke Packard [MSFT]: "Re: SP1 secondary sites upgrade failed"
- Previous message: TV: "SMS 2.0 and DC"
- In reply to: Clay White: "Re: CLient installation failure"
- Next in thread: Kerwin Medina [MSFT]: "Re: CLient installation failure"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
