Re: SMS 2.0 and SMS 2003 Running at same time in same domain.

Here is the errors I recieve. I have no idea why this is happening!!! I have
tried everything, the clients are on the network. Do I need to extend AD
schema before I send out the client if I am running in advance mode??

Thanks
Jon

Severity Type Site code Date / Time System Component Message ID Description
Warning Milestone MP2 6/1/2005 12:25:51
PM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "DOC1" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 10:24:40
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3014 SMS Client Configuration Manager cannot
connect to the machine "BAXTER-PARK5". The operating system reported error 5:
Access is denied. Possible cause: The client is not accessible.
Solution: Verify that the client is connected to the network and that the SMS
Service account or (if specified) the SMS Client Remote Installation account
have the required privileges, as specified in the SMS documentation.
Information Milestone MP2 6/1/2005 10:16:03 AM ZAX . The operating system
reported error 53: The network path was not found. Possible cause: The
client is offline. Solution: Verify that the client is connected to the
network.
Warning Milestone MP2 6/1/2005 3:39:42
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "BAXTER-PARK1" on the network. The operating system reported
error 53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 3:39:22
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "ADMIN4" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 3:39:08
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "ACCOUNTING7" on the network. The operating system reported
error 53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 3:39:02
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "ACCOUNTING4" on the network. The operating system reported
error 53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 3:38:52
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "ACCOUNTING2" on the network. The operating system reported
error 53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 2:42:33
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "WHATEVER" on the network. The operating system reported error
53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 2:42:13
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "STEMCELL2" on the network. The operating system reported error
53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 2:41:43
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "QS7" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 2:41:19
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "QRA-12" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 2:41:15
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "QS6" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 2:41:08
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "QA5" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 2:40:53 AM ZAX the network.
Warning Milestone MP2 6/1/2005 2:35:37
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "BAXTER-PARK2" on the network. The operating
SMS_CLIENT_CONFIG_MANAGER 4609 SMS Component Status Summarizer set the
status of component "SMS_CLIENT_CONFIG_MANAGER", running on computer "ZAX",
to Critical. Possible cause: The component is experiencing a problem.
Solution: Diagnose and fix the problem by: 1. Examining the status messages
that the component reports. 2. Correcting the problem. 3. Instructing SMS
Component Status Summarizer to reset the counts of Error, Warning, and/or
Informational status messages reported by the component. To reset the counts,
right-click Reset Counts on the component in the Component Status summary in
the SMS Administrator console. When the counts are reset, SMS Component
Status Summarizer will change the status of the component to OK. This might
take some time if site "MP2" is a child site. 4. Delete any unwanted status
messages from the SMS site database, if necessary. 5. Monitor the component
occasionally to verify that the problem does not reoccur. Possible cause:
The component is OK and you were unnecessarily alerted because the Component
Status Thresholds are set too low for the component. Solution: Increase the
Component Status Thresholds for the component using the Thresholds tab of the
Component Status Summarizer Properties dialog box in the SMS Administrator
console. Possible cause: The component is flooding the status system by
rapidly reporting the same message repeatedly. Solution: Diagnose and
control the flood of status messages by: 1. Verifying that the component is
actually flooding the status system. View the status messages reported by the
component and verify that the same message is continually reported every
several minutes or seconds. 2. Noting the Message ID of the flooded status
message. 3. Creating a Status Filter Rule for site "MP2" that instructs
Status Manager to discard the flooded status message when component
"SMS_CLIENT_CONFIG_MANAGER" on computer "ZAX" reports it. 4. Verifying that
your sites' databases were not filled up by the flooded status message.
Delete any duplicate status messages from the
Information Milestone MP2 6/1/2005 1:36:27
AM ZAX SMS_CLIENT_CONFIG_MANAGER 4604 SMS Component Status Summarizer
detected that component "SMS_CLIENT_CONFIG_MANAGER", running on computer
"ZAX", has reported 50 or more Warning status messages during the Component
Status Threshold Period. Possible cause: The count equals or exceeds the
Component Status Critical Threshold (50 status messages) for Warning status
messages for the component. Solution: SMS Component Status Summarizer will
set the component's status to Critical in the Component Status summary in the
SMS Administrator console.
Warning Milestone MP2 6/1/2005 1:36:17
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "M013" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 1:35:59
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "M012" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 1:34:07
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "EDUCATION1" on the network. The operating system reported error
53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 1:32:22
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "C016" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:33:16
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "RL1" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:30:40
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "HR8" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:27:21
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "BAXTER-PARK7" on the network. The operating system reported
error 53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:26:48
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "ACCT7" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:15:37
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "HR7" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:12:50
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "DOC4" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:12:28
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "BAXTER-PARK4" on the network. The operating system reported
error 53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:12:25
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "IT11" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:11:24
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "ADMIN8" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:10:54
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "HR6" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:10:42
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "QS4" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:09:57
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "TSTSP" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:09:56
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3014 SMS Client Configuration Manager cannot
connect to the machine "COONRAPIDS1". The operating system reported error 5:
Access is denied. Possible cause: The client is not accessible.
Solution: Verify that the client is connected to the network and that the SMS
Service account or (if specified) the SMS Client Remote Installation account
have the required privileges, as specified in the SMS documentation.
Warning Milestone MP2 6/1/2005 12:09:45
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "QA9" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:09:12
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "BAXTER-PARK5" on the network. The operating system reported
error 53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:08:33
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "IT4B" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:08:30
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "ADMIN5" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:07:57
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "IT7" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:07:33
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "QS8" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:06:52
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "LABDIR" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:06:33
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "GHOST6" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:06:31
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "IT12" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:06:21
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "C024" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:06:03
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "HR-MKR" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:05:33
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3014 SMS Client Configuration Manager cannot
connect to the machine "IT6A". The operating system reported error 5: Access
is denied. Possible cause: The client is not accessible. Solution:
Verify that the client is connected to the network and that the SMS Service
account or (if specified) the SMS Client Remote Installation account have the
required privileges, as specified in the SMS documentation.
Warning Milestone MP2 6/1/2005 12:05:28
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "DT12" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:04:48
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "TESTBED" on the network. The operating system reported error
53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:04:48
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "DT10" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:04:36
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "DR8" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:04:07
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "GHOST18" on the network. The operating system reported error
53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:03:46
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "HR4" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:03:27
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "GHOST17" on the network. The operating system reported error
53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:03:13
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "FOXINSOCKS" on the network. The operating system reported error
53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:02:29
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "CDIGGS" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:02:23
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "DOC2" on the network. The operating system reported error 53:
The network path was not found. Possible cause: The client is offline.
Solution: Verify that the client is connected to the network.
Warning Milestone MP2 6/1/2005 12:02:14
AM ZAX SMS_CLIENT_CONFIG_MANAGER 3015 SMS Client Configuration Manager cannot
find machine "ACCOUNTING8" on the network. The operating system reported
error 53: The network path was not found. Possible cause: The client is
offline. Solution: Verify that the client is connected to the network.
Information Milestone MP2 6/1/2005 12:01:45
AM ZAX SMS_CLIENT_CONFIG_MANAGER 4610 SMS Component Status Summarizer set the
status of component "SMS_CLIENT_CONFIG_MANAGER" running on computer "ZAX" to
Warning. Possible cause: The component is experiencing a problem.
Solution: Diagnose and fix the problem by: 1. Examine the status messages
that the component reports. 2. Correcting the problem. 3. Instructing SMS
Component Status Summarizer to reset the counts of Error, Warning, and/or
Informational status messages reported by the component. To reset the counts,
right-click Reset Counts on the component in the Component Status summary in
the SMS Administrator console. When the counts are reset, SMS Component
Status Summarizer will change the status of the component to OK. This might
take some time if site "MP2" is a child site. 4. Deleting any unwanted
status messages from the site database, if necessary. 5. Monitor the
component occasionally to verify the problem does not reoccur. Possible
cause: The component is OK and you were unnecessarily alerted because the
Component Status Thresholds are set too low for the component. Solution:
Increase the Component Status Thresholds for the component using the
Thresholds tab of the Component Status Summarizer Properties dialog box in
the SMS Administrator console. Possible cause: The component is "flooding"
the status system by rapidly reporting the same message repeatedly.
Solution: Diagnose and control the flood of status messages by: 1. Verifying
that the component is actually flooding the status system. View the status
messages reported by the component, and verify that the same message is
continually reported every several minutes or seconds. 2. Noting the Message
ID of the flooded status message. 3. Creating a Status Filter Rule for site
"MP2" that instructs Status Manager to discard the flooded status message
when component "SMS_CLIENT_CONFIG_MANAGER" on computer "ZAX" reports it. 4.
Verifying that your sites' databases were not filled up by the flooded status
message. Delete any duplicate status messages from the site data
Information Milestone MP2 6/1/2005 12:01:45
AM ZAX SMS_CLIENT_CONFIG_MANAGER 4607 SMS Component Status Summarizer
detected that component "SMS_CLIENT_CONFIG_MANAGER", running on computer
"ZAX", has reported 10 or more Warning status messages during the Component
Status Threshold Period. Possible cause: The count equals or exceeds the
Component Status Warning Threshold (10 status messages) for Warning status
messages for the component. If the component's status is not already set to
Warning, SMS Component Status Summarizer will set the component's status to
Warning in the Component Status summary in the SMS Administrator console.
Warning Milestone MP2 6/1/2005 12:01:36 AM ZAX Milestone MP2 6/1/2005
12:00:00 AM ZAX SMS_CLIENT_CONFIG_MANAGER 4611 SMS Component Status
Summarizer reset the status of component "SMS_CLIENT_CONFIG_MANAGER", running
on computer "ZAX", to OK. SMS Component Status Summarizer will
automatically reset a component's status to OK every time the Component
Status Threshold Period elapses and a new Threshold Period begins. For
example, if the Threshold Period is "Since 12:00:00 AM", SMS Component Status
Summarizer will reset the component's status to OK every 24 hours at
midnight. At this time, the counts of status messages reported by the
component for the Threshold Period will be reset to zero. Solution: SMS
Component Status Summarizer will also reset a component's status to OK when
an administrator manually resets the counts of status messages reported by
the component for the Threshold Period. Solution: SMS Component Status
Summarizer will also reset a component's status to OK when an administrator
adjusts the Component Status Thresholds to be higher than the current counts
of status messages reported by the component.


"Kim Oppalfens" wrote:

>
> Different sms versions can perfectly coexist in one domain, even
> identical versions have no problem working in the same domain. So
> bringing down sms 2.0 will probably not resolve much.
>
> With the very basic errors you are giving us it is difficult to tell you
> how to solve everything. (You can right-clock on these components and
> click show messages; All to have more detailed errors.
>
> Sms Site component mgr & sms hierarchy manager probably complain that
> they cannot create an object in Active Directory. Assuming you have
> extended the AD Schema you would have to do the following to resolve
> this. Make sure you give your site server account (advanced security) or
> sms service account (standard security) full control permissions on the
> systems container. For more info check the AD Publishing white paper.
>
> http://www.microsoft.com/smserver/techinfo/productdoc/default.asp
>
> For the other errors I would have to see the actual error messages to
> take a stab at them.
>
> Kim Oppalfens
> MVP SMS
> In article <7480713A-063A-4F59-B43D-D0474D163B8D@xxxxxxxxxxxxx>,
> Jon@xxxxxxxxxxxxxxxxxxxxxxxxx says...
> > I have just installed SMS 2003 in a domain that is already running SMS 2.0. I
> > am trying to push the client out. Will I will I be able to do this or do I
> > need to bring down the SMS 2.0 server first. SMS has built the collections
> > and everything from the domain is showing up, but I can not deploy the
> > client. Here are some of the error messages I recieve listed below.
> >
> > I will be bringing the SMS 2.0 Server down at the end of the week. My
> > question basically, is will this solve my problem????
> >
> > Critical Errors
> > -SMS_CLIENT_CONFIG_MANAGER
> > -SMS_MP_CONTROL_MANAGER
> > -SMS_SITE_COMPONENT_MANAGER
> >
> > Warning
> >
> > -MS_NT_USER_GROUP_DISCOVERY_AGENT
> > -SMS_NT_USER_DISCOVERY_AGENT
> > -SMS_HIERARCHY_MANAGER
> >
> > Please help!
> >
> > Thanks
> > Jon
> >
>
> --
> Kim Oppalfens
> SMS MVP
>
.

Relevant Pages

  • RE: Lost my outlook contact... :(
    ... the network configuration is started from a web page located ... client computer, you will see a welcome page to invite you to start the ... local user profiles to the domain user profile. ... Before joining client computers to the network, ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Wireless Security Notes and Findings (from this list and other places)
    ... There are two general areas of wireless security: Authentication and ... authentication standard that works with wireless networks. ... client computer runs a client program to connect to the network with a ...
    (Security-Basics)
  • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN Authentication Problems
    ... > network addresses and external - public network address) in front of ... I am trying to connect to the network via a VPN ... > The client is a XP Professional machine running NAT behind a Linksys ... Go through that 1 step wizard, verify ...
    (microsoft.public.isa.vpn)