Re: SMS Clients in Workgroup on Different Network

Nope...that didn't work. Remember, the client is in a workgroup...not a
member of the domain.

Question? From the log files in the ccmsetup.log, are these files the
result of the client attempting to authenticate to the server, or the server
attempting to authenticate to the client?

"Kim Oppalfens <MVP>" wrote:

in site settings; component configuration; software distribution configure
an advanced client network access account.
This can be a normal domain user.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"charles" <charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0D876104-C593-4CDD-9FF8-D19932C69F57@xxxxxxxxxxxxxxxx
Yes. I rebooted the client server this morning. Here is the log since
the
reboot:

<![LOG[==========[ ccmsetup started in process 2020
]==========]LOG]!><time="09:06:35.234+240" date="08-24-2006"
component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:4546">
<![LOG[Version: 2.50.4160.2000]LOG]!><time="09:06:35.281+240"
date="08-24-2006" component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:710">
<![LOG[Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe"
/runservice
/config:MobileClient.tcf]LOG]!><time="09:06:35.296+240" date="08-24-2006"
component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2092">
<![LOG[No network access account provided. Ccmsetup will use current
credentials for network access.]LOG]!><time="09:06:35.312+240"
date="08-24-2006" component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2547">
<![LOG[Config file:
C:\WINDOWS\system32\ccmsetup\MobileClient.tcf]LOG]!><time="09:06:35.312+240"
date="08-24-2006" component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2287">
<![LOG[Retry time: 10 minute(s)]LOG]!><time="09:06:35.312+240"
date="08-24-2006" component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2288">
<![LOG[MSI log file: ]LOG]!><time="09:06:35.312+240" date="08-24-2006"
component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2289">
<![LOG[MSI properties: INSTALL="ALL"
SMSSITECODE="AUTO"]LOG]!><time="09:06:35.312+240" date="08-24-2006"
component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2290">
<![LOG[Source List:]LOG]!><time="09:06:35.312+240" date="08-24-2006"
component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2298">
<![LOG[
\\ORANGESMS\SMSClient\I386]LOG]!><time="09:06:35.312+240"
date="08-24-2006"
component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2305">
<![LOG[Status MPs:]LOG]!><time="09:06:35.312+240" date="08-24-2006"
component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2315">
<![LOG[ ORANGESMS]LOG]!><time="09:06:35.312+240"
date="08-24-2006" component="ccmsetup" context="" type="1" thread="872"
file="ccmsetup.cpp:2330">
<![LOG[Updated security on object
C:\WINDOWS\system32\ccmsetup\.]LOG]!><time="09:06:35.312+240"
date="08-24-2006" component="ccmsetup" context="" type="0" thread="872"
file="ccmsetup.cpp:4389">
<![LOG[Running as user "SYSTEM"]LOG]!><time="09:06:35.328+240"
date="08-24-2006" component="ccmsetup" context="" type="1" thread="884"
file="ccmsetup.cpp:943">
<![LOG[Downloading file client.msi]LOG]!><time="09:06:35.328+240"
date="08-24-2006" component="ccmsetup" context="" type="1" thread="884"
file="ccmsetup.cpp:2919">
<![LOG[Determining source location...]LOG]!><time="09:06:35.328+240"
date="08-24-2006" component="ccmsetup" context="" type="1" thread="884"
file="ccmsetup.cpp:2762">
<![LOG[Source \\ORANGESMS\SMSClient\I386 is inaccessible
(53)]LOG]!><time="09:07:03.453+240" date="08-24-2006" component="ccmsetup"
context="" type="2" thread="884" file="ccmsetup.cpp:2848">
<![LOG[Failed to find accessible source. Waiting for
retry.]LOG]!><time="09:07:03.453+240" date="08-24-2006"
component="ccmsetup"
context="" type="2" thread="884" file="ccmsetup.cpp:2877">
<![LOG[Next retry in 10 minute(s)...]LOG]!><time="09:07:03.453+240"
date="08-24-2006" component="ccmsetup" context="" type="0" thread="884"
file="ccmsetup.cpp:3888">
<![LOG[Source \\ORANGESMS\SMSClient\I386 is inaccessible
(53)]LOG]!><time="09:17:28.468+240" date="08-24-2006" component="ccmsetup"
context="" type="2" thread="884" file="ccmsetup.cpp:2848">
<![LOG[Failed to find accessible source. Waiting for
retry.]LOG]!><time="09:17:28.468+240" date="08-24-2006"
component="ccmsetup"
context="" type="2" thread="884" file="ccmsetup.cpp:2877">
<![LOG[Next retry in 10 minute(s)...]LOG]!><time="09:17:28.468+240"
date="08-24-2006" component="ccmsetup" context="" type="0" thread="884"
file="ccmsetup.cpp:3888">



"Kim Oppalfens <MVP>" wrote:

Check whether your system has a windows\system32\ccmsetup\ccmsetup.log
file.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"charles" <charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:34665AF7-3756-42A4-9070-7A08068B56D8@xxxxxxxxxxxxxxxx
Kim,

There isn't a Systems Management applet in control panel. I rebooted
the
client...but still not there.

"Kim Oppalfens <MVP>" wrote:

check the systems mgmt applet in control panel at the client side,
what
does
the sitecode say?

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"charles" <charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:894515D8-E05A-4987-AC12-66A7ECDE5654@xxxxxxxxxxxxxxxx
Kim,

THAT WORKED!!! I think. I can see the ccmsetup service running on
the
remote server MPA10035. However, I still do not have an icon for
the
server
in the SMS Management console under "All Systems."

How do I get these remote servers to show up in SMS Mnagement
console?

Below are the successsful log files:

Created service "ccmsetup" on machine "MPA10035".
$$<SMS_CLIENT_CONFIG_MANAGER><Wed Aug 23 08:33:12.156 2006 Eastern
Daylight
Time><thread=2304 (0x900)>
---> Started service "ccmsetup" on machine "MPA10035".
$$<SMS_CLIENT_CONFIG_MANAGER><Wed Aug 23 08:33:12.359 2006 Eastern
Daylight
Time><thread=2304 (0x900)>
---> Completed request "KUNWUL9C", machine name "MPA10035".
$$<SMS_CLIENT_CONFIG_MANAGER><Wed Aug 23 08:33:12.703 2006 Eastern
Daylight
Time><thread=2304 (0x900)>
Deleted request "KUNWUL9C", machine name "MPA10035"
$$<SMS_CLIENT_CONFIG_MANAGER><Wed Aug 23 08:33:12.703 2006 Eastern
Daylight
Time><thread=2304 (0x900)>
<======End request: "KUNWUL9C", machine name: "MPA10035".
$$<SMS_CLIENT_CONFIG_MANAGER><Wed Aug 23 08:33:12.703 2006 Eastern
Daylight
Time><thread=2304 (0x900)>
***********************************************************
"Kim Oppalfens <MVP>" wrote:

Do these machines have a standardized administrator account
password?
If so then add %machinename%\administrator to the client push
installation
account tab.

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"charles" <charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D07A0273-06A0-4887-95CD-06FA2D678123@xxxxxxxxxxxxxxxx
Here is the problem. Not sure how to fix it though.

======>Begin Processing request: "MPA10035", machine name:
"MPA10035"
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Aug 22 16:13:30.562 2006
Eastern
Daylight
Time><thread=3520 (0xDC0)>
---> Trying each entry in the SMS Client Remote Installation
account
list~
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Aug 22 16:13:30.562 2006
Eastern
Daylight
Time><thread=3520 (0xDC0)>
---> Warning: no remote client installation or SMS service
account
found
$$<SMS_CLIENT_CONFIG_MANAGER><Tue Aug 22 16:13:30.562 2006
Eastern
Daylight
Time><thread=3520 (0xDC0)>
---> ERROR: Unable to connect to remote registry for machine name
"MPA10035", error 5. $$<SMS_CLIENT_CONFIG_MANAGER><Tue Aug 22
16:13:30.843
2006 Eastern Daylight Time><thread=3520 (0xDC0)>
---> ERROR: Unable to access target machine for request:
"MPA10035"

Charles


"Kim Oppalfens <MVP>" wrote:

What does the ccm.log tell you?

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"charles" <charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:55EBDA3F-2D7C-44D4-ABEC-799488ACE2F5@xxxxxxxxxxxxxxxx
Thank you for your response.

I Used the CCRman program as you suggested. When I copied the
file
to
the
\\SMSserver\CAP_001\ccr.box directory, it mysteriously
dissapeared!
I
did
this twice with the same results.

I still am unable to see the client in the SMS Management
console.
Any
suggestion would be greatly appreciated.

"Kim Oppalfens <MVP>" wrote:

Force client push installation by manually creating your own
ccr's
and
copy
them into the ccr.box.
http://www.myitforum.com/articles/8/view.asp?id=7073

--
Kim Oppalfens
Telindus Belgium
MVP Windows Server System - SMS
"charles" <charles@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:D6F2E318-36D7-42C4-AA96-09AFCCB5FB67@xxxxxxxxxxxxxxxx
SMS 2003 server
Clients are all Windows Server 2003 std. All clients are
in
workgroups
and
cannot be member servers or otherwise join the domain.

We have an SMS 2003 Server in a domain. All of the clients
machines
are
Windows Server 2003 std. All clients are on different
networks
connected
to
the network with the SMS Server via VPN connections. I can
ping
all
clients
from the SMS Server.

The SMS Server is on a 172.16.1.0 network.
The clients are on 10.0.0.0 networks connected via site to
site
VPNs.

I have installed WINS and manually entered one of the
clients,
but I
still
am unable to discover or otherwise see the client from the
SMS
console.

How do I make this work?

thanks.
















.

Relevant Pages

  • Re: After reinstallation
    ... If you manually install the client and open the system manager in control ... See Ccm.log on site server ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... The MP installation was succesful, ...
    (microsoft.public.sms.setup)
  • Re: Adv Client with Workgroup Computers
    ... I was trying to use the SMS tools from the SMS server to initiate harware ... Inv for example the account is a domain account but the Client PC is in a ... Is there a procedure for installing the ADV client localy on a workgroup ... I have manually added to the WINS server. ...
    (microsoft.public.sms.admin)
  • Re: After reinstallation
    ... I guess what you say is that my server is running fine, but I should not expect client push to work. ... SMS Active Directory System Group Discovery Agent reported errors for 3 ... "Todd Hemsell" wrote: ...
    (microsoft.public.sms.setup)
  • Re: 4912: Cannot update the already existing object. Need some he
    ... Also, as far as the client pointing to the wrong server, you should use SMS ... SP3 client through a logon batch file. ...
    (microsoft.public.sms.admin)
  • Re: What doesnt lend itself to OO?
    ... >> proxy and instructs the server to constuct the real object. ... rather than client code. ... If 'clock' is instantiated in the server, ... > for the server interface at the OOA level. ...
    (comp.object)
Loading