Re: After reinstallation

As far as I can tell it is correct.

some things to look at:

If you manually install the client and open the system manager in control panel can you do an "Auto Detect site Code" successfully? also see LocationServices.log on the client

Did you set an account for client push to use? must be a local admin on the workstations
Can you connect to the Admin$ share on the pc you are trying to push to? See Ccm.log on site server

Have you run Ad system discovery? (I assume so or you could not try to push unless you did netowkr discovery) See Adsysdis.log on site server

On the clients you manually installed and that have a site code, do they show up in the console and are they getting policies?
Install the SMS toolkit v2, open trace32, and look throuogh some log files. There are a lot of them, this page is a good "decoder" http://msmvps.com/blogs/lduncan/articles/17901.aspx
and this one for the server http://msmvps.com/blogs/lduncan/articles/17900.aspx

RE the MP cert -> look in Mpcontrol.log on the site server and PolicyAgent.log on the client. I cannot remember the cases but MP Trobleshooter does not always work, local or remote, one of them bombs on some items. Those logs I mentioned will tell you for sue

RE wbemwrap.log:
Warning - could not find C:\SMS\core\bin\smsclreg.dll. Defaulting to English.
I use only english SW, can I ignore this?

Yes, pretty sure you can ignore,

Also, open site status on the site server and go have a look at anything red. Expand it until you see the component then right click and show all messages.
quite a few of them include the solution. That is one of my fav places to check status and track down errors. It is a good place to look to find errors you might be haivng that have not "surfaced" in other places yet (read user complaints)

Hope that helps some.
I am a poor typist so if I need to clarify something let me know. I often do not type all I think :-)

Regards,

Todd
"RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:2DC51F46-D9F3-45EB-8290-3E2ADB0D7988@xxxxxxxxxxxxxxxx
Hi Todd

After reinstallation:

I can now deploy SW, if the client is manualy installed.
I can assign the client, but it dosent install.
I can not deploy the Client with client push.

The MP installation was succesful, YES!
The amount of error messages is reduced, so I am getting closer.
But I must have forgotten some setting, etc. Hope you can help.

I tryed the MP Trobleshooter, it returns only one error:
Testing MPCERT HTTP request functionality
- Failed - The server is not operational

Error messages:
SLPsetup.log
ERROR: Cannot read reg value of Software\Microsoft\SMS\IIS\SMSPortList (0)
ERROR: Cannot read reg value of Software\Microsoft\SMS\IIS\SMSPortUsageCount
(0)

wbemwrap.log:
Warning - could not find C:\SMS\core\bin\smsclreg.dll. Defaulting to English.
I use only english SW, can I ignore this?

Below is described how I did the installation

I reinstalled the server, like this:
Win2003SP1
ASP, COM+, DTC,
IIS inkl.:
- BITS
- active server pages
- IDC
- Server side includes
- WebDav
- WWW
Without Remote admin (HTML)

SQL2000SP2
- upgraded to SQL SP4

SMS 2003 SP1, advanced security.
- Upgraded to SMS 2003 SP2

Upgraded SQL 2000 to SQL 2005

Did I do this corectly?

Thanks in advance

Best regards
Ruben





"Todd Hemsell" wrote:

> do oyu have an account at licensing.microsoft.com ? it is for software assurance customers. you can download an integrated CD from there.
>
> I have heard, though do not have firsthand experience.. you cannot integrate one yourself.
>
> Todd
> "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:3B5332EE-A33D-46FD-96D6-E2A9C3C55B78@xxxxxxxxxxxxxxxx
> Hi Todd
>
> I tried to find a ISO image, SMS 2003 with SP2 integrated, on MSDN without
> success. Now I try to integrate SP2 in the installationfiles SMS2003 with SP1
>
> I recive error as below no matter what path I write.
>
> Path to the installation files: E:\SMS2003
> ex.:
> en_SMS_2003_sp2.exe /integrate:E:\SMS2003\SMSsetup\bin\i386
> en_SMS_2003_sp2.exe /integrate:E:\SMS2003\SMSsetup\bin
> en_SMS_2003_sp2.exe /integrate:E:\SMS2003\SMSsetup
> en_SMS_2003_sp2.exe /integrate:E:\SMS2003
>
> [smssp2.log]
> 0.032:
> ================================================================================
> 0.047: 2006/09/05 14:17:52.843 (local)
> 0.047: e:\f0f5290f74c7f75931\update\update.exe (version 6.1.22.0)
> 0.047: Slipstream mode
> 0.047: Service Pack started with following command line:
> /integrate:E:\SMS2003\smssetup\bin\i386 /log:e:\smssp2.log
> 0.125: Package Type: CLASSIC
> 0.125: GetBuildInformation: Error 0x3 while trying to retrieve target OS
> version information from E:\SMS2003\smssetup\bin\i386.
> 0.125: GetTargetOSInformation: Error retrieving build information: GLE = 0x3
> 0.125: IntegrateHotfix: Error 0x3 while gathering information about target
> E:\SMS2003\smssetup\bin\i386.
> 0.125: Hotfix Integration failed with error 0x3
> 4.047: Message displayed to the user: An error occurred while attempting to
> integrate this software update package. Verify that the architecture,
> language, and service pack level of this software update are valid for the
> target distribution folder.
> 4.047: User Input: OK
> 4.047: An error occurred while attempting to integrate this software update
> package. Verify that the architecture, language, and service pack level of
> this software update are valid for the target distribution folder.
>
> How to do?
>
> Regards
>
> Ruben
>
>
> "Todd Hemsell" wrote:
>
> > Only SMS 2003 SP2 will work with SQL 2005.
> > Unless you have a SP2 CD you will have to go SQL 2000 then install SMS SP2, then upgrade SQL to 2005
> >
> > Sorry you could not get it resolved.
> >
> > Regards,
> >
> >
> > Todd
> > "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:0D66CBFE-473E-473C-9CAA-DCBB249509D0@xxxxxxxxxxxxxxxx
> > HI Todd
> >
> > Well, I gave up. I am now reinstalling the server. Can SMS 2003 run on a
> > Win2003R2 with SQL 2005? that is my plan anyways.
> >
> > "Todd Hemsell" wrote:
> >
> > > Not sure where to go next with this. I did find a KB article on your issue, I hope it helps you
> > >
> > > http://support.microsoft.com/kb/917675
> > > "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:9FA94B54-2EEA-4E0C-88B5-9C8E1118DB56@xxxxxxxxxxxxxxxx
> > > IIS, BITS, webdav is installed. Webdav is set to Allowed, In the Web Services
> > > Extensions. On default website, I have set Allowed clients to transfer data
> > > to this virtuel directory. Is that the corect settings?
> > >
> > > Under default website I have:
> > > aspnet_client
> > > BITS-Sessions
> > > SMSComponent
> > > SMSReporting_001
> > >
> > > What rights do I need to set?
> > >
> > >
> > > "Todd Hemsell" wrote:
> > >
> > > > check permissions and ensure you have bits server extensions installed and webdav enabled..
> > > > Also ensure iis is installed etc...
> > > >
> > > > ccm incoming is a bits enabled virtual directory in iis where the clients communicate with the server (upload events ect)
> > > >
> > > >
> > > > "RUBEN @ DK" <RUBENDK@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:7DB5617F-B34C-457A-93FF-884878855ABD@xxxxxxxxxxxxxxxx
> > > > From MPSetup.log:
> > > >
> > > > Setup was unable to create the Internet virtual directory CCM_Incoming
> > > > The error code is 80020009
> > > >
> > > > What does this meen, and how do I solve it?

Relevant Pages

  • RE: MS Software Update Service
    ... and approve the patches before releasing them to your clients. ... Automatic Update client) ... Doesn't patch SQL Server, Exchange, Office, etc. ... distributed through Active Directory software installation, ...
    (Focus-Microsoft)
  • Re: Small Biz Design
    ... After we installed SBS 2003 successfully on the server box, the Client ... >When we setup SBS 2003 server using installation disks, ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I reinstall setup.exe file for clients in server?
    ... I rebooted the server and afterwards I looked at the event log for specific ... interesting because our sbs 2003 installation is supposed to be 32-bit! ... And where in the wizard will there be the option just to install the Client ...
    (microsoft.public.windows.server.sbs)
  • Re: How do I reinstall setup.exe file for clients in server?
    ... Did you go to the Control Panel> Windows Small Business Server 2003 and click on the Change Remove button? ... interesting because our sbs 2003 installation is supposed to be 32-bit! ... And where in the wizard will there be the option just to install the Client ...
    (microsoft.public.windows.server.sbs)
  • Re: Configure ISA to allow ISA Server to make external FTP Connect
    ... your Server name and select properties, Installation mode is listed at the ... client, as well as being all three at the same time. ... This means that the workstation has the proxy server details ... Enter the name 'FTP Access', press next twice, from the drop down box ...
    (microsoft.public.isa.configuration)
Loading