Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 513
  • Last Modified:

I cannot get SMS 2003 Advanced Client to install Via Push Install Method

Hi All,

Need some help getting this to work please.  Here are some details and then a log from my client at the end.

SMS Server Info:
1.  Windows 2003 standard SP2 (not R2), also updated Active Directory Schema for SMS 2003.

2.  SMS 2003 SP2 (about says SMS 2.5 SP2 Build 4160)- Site Server - 2.50.4160.2000 (4160), Admin UI - SMS 2.50 SP2 (4160), SMS Provider - 2.50.4160.2000

3.  In SMS Administrator, Site Settings---> Site Systems I have two servers.  One is the SMS server, and the other is my SMS component server/SQL server.

4.  If you double click the SMS server and go into each tab, here is what is enabled:
---General Tab - Nothings checked here.  The name of the SMS server appears in top line.
---Reporting Point Tab - Server is not checked for "use this server for a reporting point".
---Server Locator Point - Server is not checked for "use this server for a locator point".
---Management Point - Use server as site management point IS checked.  Database is set to "site database".
---Client Access Point Tab - This IS Checked to use server as client access point.
---Distribution Point Tab - Use this system as a distribution point IS checked.  Enable BITS is unchecked.  There is nothing in the "GROUP MEMBERSHIP" window.  Protected distribution point is NOT checked.
---System Roles Tab - SMS Client Access Point, SMS Component Server, SMS Distribution Point, SMS Management Point, SMS Site Server.

5.  Under Site Settings---> Component Configuration:  Double Click "Software Distribution".  I have under General Tab - Advanced Client Account configured to use a domain admin account.

6.  Under Site Settings ---> Connection Accounts: Client has a local system SMS account, Site System has the Domain Admin SMS account I manually created and use for various SMS stuff.

7.  Discovery Methods - Active Directory

8.  Site Hierarchy ---> (sms site name), right click and go to properties.  Site boundries are set to Active Directory Site and then I gave it a generic name.

Client Push Installation settings:
1.  General Tab (listed are checked) - System Types (all checked), Enable Client Push Installations to site systems, Client Type - Advanced Client is checked.

2.  Accounts Tab - I am using a custom made SMS account that is a domain administrator, and in all SMS groups.

3.  Advanced Tab - there is only one string in here, SMSSITECODE=AUTO

Target Desktop for client installation testing:
1.  Windows XP SP3
2.  File and Print sharing is enabled
3.  Windows Firewall is turned "OFF"

Symptoms and description of process:

1.  I can see the ccmsetup.exe process running on my local target desktop.  I can also see ccmexec.exe process running.  They never go away and have been this way for over 24 hours.

2.  The client description in SMS Management shows client = no, assigned = yes.

3.  I tried unchecking the Site Settings ---> Site Systems ---> Management point and then rebooted the server.  I then came back in and checked it and gave it 30 minutes to do whatever it needed to do to re-install the management point.  I was told to do this as advice earlier.  Now when you read the log file from the client, notice that AFTER I did that, the location at which it's trying to pull the client (URL) has changed.  It's actually now trying to go to a URL on the network that is not even reachable because it don't exist.  The old original path in the logfile is where the client is really located (\\na02sms\SMS_777\Client\i386 exists and is a real path. \\NA02SMS\SMSClient\I386 does not exist, but is what the system is trying to use after removing, then re-installing the management point).

Attached is the logfile "ccmsetup.exe" from the windows XP workstation.

Any assistance you can give is much appreciated.  Hope I gave enough information.
ccmsetup.log
0
maestro2be
Asked:
maestro2be
  • 6
  • 4
1 Solution
 
maestro2beAuthor Commented:
I tried to manually install the client by connecting to the share point and it also does the exact same thing as mentioned above.  I am upgrading to SMS SP3 right now.  Not sure it will help, but I want to be sure I am on the most current updates and fixes.

Would love to hear any ideas you all have.

Thanks!
0
 
Adam LeinssCommented:
The log is pretty clear:
<![LOG[Source \\na02sms\SMS_777\Client\i386 is inaccessible (5)]LOG]!><time="23:42:07.723+240" date="04-22-2009" component="ccmsetup" context="" type="2" thread="628" file="ccmsetup.cpp:2848">
<![LOG[Failed to find accessible source. Waiting for retry.]LOG]!><time="23:42:07.723+240" date="04-22-2009" component="ccmsetup" context="" type="2" thread="628" file="ccmsetup.cpp:2877">
It doesn't think that  \\na02sms\SMS_777\Client\i386 exists.
Does it?  Does the everyone group have read permissions on that folder, both at the NTFS and Share level?
0
 
Adam LeinssCommented:
OK, you did state that:
The old original path in the logfile is where the client is really located (\\na02sms\SMS_777\Client\i386 exists and is a real path. \\NA02SMS\SMSClient\I386 does not exist, but is what the system is trying to use after removing, then re-installing the management point
But I'm still confused.  Was this the latest log file you posted?
You should have the setups for BITS, XML, etc. in the i386 folder
0
Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

 
maestro2beAuthor Commented:
That path does indeed exist.  The client is sitting in that folder.

To answer your question, the log I posted was the most current.  As soon as I made the management point change, i ran the setup again and it simply added it to the current log so I got one consolidated log.

I did confirm that the everyone group has full control to the share, and then read NTFS permissions all the way down.

Inside that client folder (\\NA02SMS\SMS_777\Client\i386) are just 4 files.  "capinst.exe", "ccmsetup.exe", "client.msi" and "smsman.exe".  This folder looks 100% identical to the client folder that is on the install CD.  I ran the install from the CD and it worked perfectly (obviously) but it still shows my client as not installed in the SMS Management console (most probably needs a pointer to the distribution server).

I don't have BITS enabled under Site System ---> Distribution Point.  Am I supposed to be using this?  And how would I change the pointer on this server to start trying to push the client install from the proper distribution location instead of that broken one it up in place that doesn't exist?

Thanks!
0
 
maestro2beAuthor Commented:
One more thing.  I have complete the SP3 upgrade and it went flawlessly.  Also updated the AD Schema so I am currently now on SMS 2003 SP3 just in case that affects what were doing here in any way.
0
 
Adam LeinssCommented:
You don't have to use BITS, except it is mandatory for BDPs.
It seems you are missing files from i386.  I did a SMS->SCCM upgrade, but I believe they are the same for both versions:

04/28/2009  02:49 PM    <DIR>          .
04/28/2009  02:49 PM    <DIR>          ..
09/15/2008  02:04 PM    <DIR>          BITS20
09/15/2008  02:04 PM    <DIR>          BITS25
05/20/2008  04:00 AM        17,401,856 client.msi
09/15/2008  07:58 AM           543,048 msrdcoob_x86.exe
04/08/2008  05:27 PM         1,521,152 msxml6.msi
04/08/2008  05:27 PM           787,968 wimgapi.msi
04/08/2008  05:27 PM         2,585,872 windowsinstaller-kb893803-v2-x86.exe
09/15/2008  07:58 AM         6,157,336 windowsupdateagent30-x86.exe
09/15/2008  07:59 AM           540,160 wmirdist.msi
4 files doesn't seem enough...can anyone confirm that?
0
 
maestro2beAuthor Commented:
Keep in mind that the CD itself only has 4 install files in that directory.  When I put the SMS 2003 install CD into my machine, I ran the ccmsetup.exe and it worked perfectly.  Same 4 files on it as in the folder.  I just don't understand why when I launch it off the network share, it thinks it cannot see it when it is sitting right there in that path.  This is strange.
0
 
maestro2beAuthor Commented:
Well this is finally solved but unfortunately I cannot tell you exactly "how to fix it".

It took a call to Microsoft support and they found all kinds of things not working.  Basically it was due to running SMS on a server that already had 2 other IIS applications running on it (Websense and Microcall).  They were causing SQL and IIS Issues.

Once we removed those apps, Microsoft walked me through a bunch of repair scenerio's using service packs (2003 server and SMS) as well as some custom things that only they have access too.

They did get it running and its been flawless since.

Thanks so much for trying to help me out.  Am I allowed to grant points to people for triny to help even if it's not the resolution?

Thanks!

Maestro2be
0
 
maestro2beAuthor Commented:
Well this is finally solved but unfortunately I cannot tell you exactly "how to fix it".

It took a call to Microsoft support and they found all kinds of things not working.  Basically it was due to running SMS on a server that already had 2 other IIS applications running on it (Websense and Microcall).  They were causing SQL and IIS Issues.

Once we removed those apps, Microsoft walked me through a bunch of repair scenerio's using service packs (2003 server and SMS) as well as some custom things that only they have access too.

They did get it running and its been flawless since.

Thanks so much for trying to help me out.  Am I allowed to grant points to people for triny to help even if it's not the resolution?

Thanks!

Maestro2be
0
 
Adam LeinssCommented:
You can accept your comment as the solution and it will still get added to the knowledgebase.
I don't think we gave you that much help to warrant any award of points, but that is your call.
0
 
ee_autoCommented:
Question PAQ'd, 500 points refunded, and stored in the solution database.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 6
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now