Re: Not able to push software nor download new patches
- From: "sherrylkissinger@xxxxxxxxx" <sherrylkissinger@xxxxxxxxx>
- Date: 10 Apr 2007 19:16:57 -0700
On Apr 10, 7:40 am, MJMJ <M...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Hello all,
I am having some issues in pushing software and downloading the new cab for
today's patches. First, let me being by saying I am a novice to SMS so
please bear with me if some questions seem rather elementary. Now I have
pushed out software before with no problems, but when I check the
advertisement status of all the software I have pushed to this point, nothing
has been distributed since Thursday, April 5th. It seems everything stopped
updated on that day. Next, I tried to update the Microsoft Updates Tool to
download the cab file for Qnumber 925902. In our environment we have to
download the file manually, therefore I did so just as our S.O.P. explains.
But when I go to the software updates table, the MS07-017 number does not
show up. I had this problem last week, but I was able to solve it by simply
updating my distribution point. Tried that here, but still nothing. I also
re-ran the advertisement and did a site reset, still nothing. I did notice
that when I checked the site status messages, I received the following
warnings over and over:
SMS Inventory Data Loader failed to process the delta MIF file
"Xje1y6qh5.MIF" because the file does not have a corresponding discovery
record. SMS Inventory Data Loader has moved this file to the Orphans
directory as file "E:\SMS\inboxes\auth\dataldr.box\ORPHANS\d8uk5un0.MIF" and
will retry processing it within 10 minutes.
Possible cause: The delta MIF file came from an SMS 1.2 site, and these
sites do not have discovery agents.
Solution: Verify that the delta MIF file is from a 1.2 site. If so, do
nothing.
Possible cause: Discovery Data Manager is not running.
Solution: Stop and restart Discovery Data Manager. You can use SMS Service
Manager, which is invoked from the SMS Administrator console, to stop and
start components.
I followed the directions and checked the DDM, it was already stopped, so I
restarted it, but still nothing.
I also noticed this warning in the log:
SMS Active Directory System Discovery Agent reported errors for 118 objects.
DDR's were generated for 0 objects that had errors while reading non-critical
properties. DDR's were not generated for 118 objects that had errors while
reading critical properties.
Possible cause: The SMS Service might not have access to some properties of
this object. The container specified might not have the properties available.
Solution: Please verify the Active Directory schema for properties that are
not replicated or locked. Refer to the discovery logs for more information.
Could it really be an Active Directory or Group Policy change in our network
that may be affecting SMS? As I mentioned earlier in this blog message,
none of the systems have updated with any of the patches or software I have
pushed out i.e. Quicktime, Java, etc, since Thursday, April 5th. Could the
reason I cannot push anything out nor download any new patches be related to
some sort of AD or Group Policy change? Help in this situation would be most
helpful ASAP, I am racking my brain to figure out what is going on, I
haven't changed anything in SMS .
IMHO, I don't think it could be an AD change--but perhaps a GPO change
may have affected service startup on your sms server? If your
Management Point, or your Server Locator Point are not working
properly, or if the SMS Server's OS was upgraded recently (i.e.,
server 2003 service pack), there may be dcom permissions, etc. that
need to be reset to re-enable all functionality.
Things to check on/try/look at (in no particular order):
- Use the SMS Toolkit 2's MP Troubleshooter.
- was the server's OS updated around April 5? If so, check
microsoft.com for how to adjust dcom permissions
- was the IIS lockdown tool possibly done on the server? If so, check
to make sure that the SMS-friendly IIS lockdown tool was used, not the
everyday one.
- Check log files at the server (in sms\logs), looking for error
messages.
- Check log files at a client (in system32\ccm\logs), looking for
error messages.
- Were any new GPO policies applied; possibly to stop/disable IIS
services, or other services automatically? SMS servers need IIS, and
the BITS extensions for IIS installed in order for the MP to work
correctly.
.
- References:
- Prev by Date: Re: Software Distributions failing at remote site with protected DP on
- Next by Date: Re: Package restarting XP - But not supossed to
- Previous by thread: Not able to push software nor download new patches
- Next by thread: RE: Delete all partitions before OSD deployment?
- Index(es):
Relevant Pages
|
Loading
