Re: Installation of Client

Here is the output from the client.msi.log.

please take into consideration that I used the CCMCLEAN file to remove all
the attempts to install the client
---
client.msi.log

DEBUG: Error 2203: Database: C:\WINDOWS\Installer\8789c22.ipi. Cannot open
database file. System error -2147024629
MSI (s) (30:90) [16:16:28:975]: Product: SMS Advanced Client -- Internal
Error 2203. C:\WINDOWS\Installer\8789c22.ipi, -2147024629

Internal Error 2203. C:\WINDOWS\Installer\8789c22.ipi, -2147024629
Property(S): ErrorDialog = ErrorDialog
Property(S): SmsDetectDowngrade_ErrorMessage = A newer version of the SMS
Advanced Client is already installed
Property(S): SmsDetectColocationDowngrade_ErrorMessage = A newer version of
the SMS Management Point is installed. Cannot continue installing this
version of the client.
Property(S): WelcomeDialog_DesktopWarning = WARNING: The SMS Legacy Client
or SMS 2.0 Client is already installed on this machine. Continuing will cause
the SMS Legacy Client or SMS 2.0 Client to be removed.
Property(S): InstallDialog_Warning = WARNING: Installing the advanced client
on this computer may cause the Windows Management Instrumentation (WMI) and
Background Intelligent Transfer Service (BITS) services to stop and restart.
Property(S): InstallErrorDialog_Title = Setup Aborted
Property(S): InstallErrorDialog_SubTitle = Setup failed
Property(S): InstallErrorDialog_Info = Setup encountered an error and could
not continue.

--------





"Jeff W" wrote:

Hi and thank you for the response,

Yes and Yes.

I used the following script (with persephone being my primary SMS server and
local MP):

dim oSMSClient
set oSMSClient = CreateObject ("Microsoft.SMS.Client")
oSMSClient.SetCurrentManagementPoint "persephone",0
set oSMSClient=nothing

I also manually added the WINS information into the WINS server that both
servers point to.

the LMHOSTS file looks like this:
xxx.xxx.xxx.xxx persephone #PRE #DOM:XXXXXXX
xxx.xxx.xxx.xxx "SMS_SLP \0x1A" #PRE
xxx.xxx.xxx.xxx "MP_DG2 \0x1A" #PRE
xxx.xxx.xxx.xxx "SMS_MP \0x1A" #PRE



Basically since the problem server is not sharing the same DNS tree/settings
as the rest of the domain, I treated this as a server in a DMZ.



"Kim Oppalfens [MVP]" wrote:

Have you tried manually putting in the management point name using a script?
Is the problem server configured as a wins client?

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS

"Jeff W" <JeffW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:75C60542-9A50-4CA5-90A5-0924FD4B8D49@xxxxxxxxxxxxxxxx
Hi everyone,

I have a puzzle here that I'm trying to solve. I was just brought in to a
company that has had, lets say, a different approach in setting up thier
servers. Anyway, I have finally worked through what seems like 100
different
problems to get SMS site properly talking, but I'm having one machine that
I
cannot get the client to properly install.

The machine is a windows 2003 member server, joined to the main domain
that
SMS resides in. The server itself has the primary job of being a
Blackberry
Enterprise server, but has to have it's DNS entrees pointing to the public
DNS servers which does not reference the AD domain in any fashion and I
can
not change the DNS configuration without breaking the primary application.
We then had to modify the LMHOSTS file to point to the pre-windows 2003
name
and add the entrees to point to both the domain controller, SMS primary
site
(which is what server will be supporting this server).

The client will not install if I run ccmsetup, I basically get this error:

MSI: Action 16:16:28: InstallInitialize. ccmsetup 4/2/2007 4:16:28 PM 1780
(0x06F4)
MSI: Internal Error 2203. C:\WINDOWS\Installer\8789c22.ipi,
-2147024629 ccmsetup 4/2/2007 4:16:28 PM 1780 (0x06F4)
Installation failed with error code 1603 ccmsetup 4/2/2007 4:16:29 PM 1780
(0x06F4)
No status servers specified. Status will not be sent. ccmsetup 4/2/2007
4:16:29 PM 1780 (0x06F4)
Next retry in 120 minute(s)... ccmsetup 4/2/2007 4:16:29 PM 1780 (0x06F4)

I did make the WINS entry's on a WINS server to point to the management
point, and the problem server is pointing to it so that at least it can
communicate using WINS or at least that is my hope.

If I run the client.msi the client will install, just not all the way (it
will not update the policies). It will perform a correct discovery of the
SMS site, but since none of the policies get updated, it doesn't report
anything back to the primary site.
I’m able to ping the problem server by name from the primary site, and
ping
from the problem server to the SMS primary site. I have a feeling it’s
just
because of the DNS configuration, but hoping that someone with a “fresh
set
of eyes” can point out my missing piece.


Any help would be greatly appreciated..



.

Relevant Pages

  • Re: Fax on Terminal Server from SBS2K3
    ... please make sure the Fax service is installed on the TS server. ... you can try the steps below to install Shared Fax Client: ... 248340 Installing and Using Programs in Windows 2000 Terminal Services ...
    (microsoft.public.windows.server.sbs)
  • RE: Fax monitor incoming + outgoing calls?
    ... The detail steps to install share fax client as follows: ... Start server management console, locate Client Computers node, click ... To the folder redirection GPO issue: ... How to stop Folder Redirection in Windows Server 2003 and in Windows 2000 ...
    (microsoft.public.windows.server.sbs)
  • RE: No Client or Server Desktop Access Through RWW SBS 2003 SP2
    ... The SBS server is running SP2. ... However I don't know if the client computers do. ... To successfully install SBS 2003 SP1, ...
    (microsoft.public.windows.server.sbs)
  • Re: Cannot make SMS clients install; SMS_HIERARCHY_MANAGER problem
    ... you tried to push the client on, so I would first check the smsprov.log file ... Secondly, if SMS provider generate the CCR records successfully, then CCM is ... second log at server side to check would be ccm.log. ... > The only method I've tried to install the client with is by using a Client ...
    (microsoft.public.sms.setup)
  • Re: SBS 2003 Fax Sharepoint Routing
    ... Business Server 2003 and click "Change/Remove", ... If the Fax Services component was original installed by using the SBS ... Install fro the Fax Server component. ... And then we should push the shared fax client application from server to ...
    (microsoft.public.windows.server.sbs)