Re: Ran ccmclean on site server, what are implications???

Right click on the package>all tasks > Update distribution points

This will tell you that it is going to send a new copy to all the dps..
Also go in to the package > distribution points> right click on your dps and
make sure you see their properties.
--
-----------------------
http://sms-hints-tricks.blogspot.com/


"John" wrote:

Hi,
i have scheduled the sync tool to run at 13pm and in package microsoft tool
properties schedule distribution point at 13:30pm.
Is this what you meant by "set the package to autoupdate"?

Earlier i manually entered a comment in package properties to force a change
of it and did a update distribution point.
Afterwards i tried running sync tool. I did this because i read in
http://kbalertz.com/909387/advertisement-remote-roaming-Advanced-Clients-after-configure-advertisement-remote-distribution-point.aspx
that this could fix the no DP found issue.

How do i do a manual update on a package? Do i change a setting in the
package properties and then distribute it to DP?

"Matthew Hudson" <MatthewHudson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DB0F45C4-1C8A-4E5B-9E6E-B0B31D2EAABD@xxxxxxxxxxxxxxxx
It will not fix the DP found problem but it will fix the problem with
updating the server and other information. If the content is not
up-to-date
then the client will not download it. To run the sync the next time. Do
a
manaul update on the package and send it to the DPs. Then tell the sync
tool
to run. This way the package is updated, sync will run and it will update
the package again (for the next run).

Also copy the sync in to a batch file or cmd file and run it from the
command line to see if the program will run manually. Watch the sycn log
in
the ccm folder to see what happens...


If this works then you can work backwards to make sure it works thru sms.

--
-----------------------
http://sms-hints-tricks.blogspot.com/


"John" wrote:

Hi Matthew,
i dont think that its set to autoupdate after the sync runs.

I can understand that the package should update on a schedule since a new
cab file could have been downloaded but so far i havent seen sync tool
run
succesfully so far.

If i turn update on schedule for the Microsoft Update tool on say like 30
minutes after sync tool runs will that fix the waiting status for sync
tool
advertisement? And that issue with CAS.log stating no DP point found?


"Matthew Hudson" <MatthewHudson@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:558F65A5-B64A-49CB-9908-DC1F15A129E9@xxxxxxxxxxxxxxxx
Do you have the package autoupdating after the sync runs. If you have
the
sync runningat 3:30pm every patch tuesday then set the package to
autoupdate
at say 4:00pm or shorter.


--
-----------------------
http://sms-hints-tricks.blogspot.com/


"John" wrote:

Great,that means running ccmclean & delcert, deleting the old sms
account
id
that became obsolete shouldnt effect sms operations.

Thanks alot

Now back to why i tried uninstalling sms client.
Im trying to run Microsoft Sync Tool on the site server.

When i try to run advertisement for Sync tool in Advertisement status
it
lists:
************************
The program for advertisement "SUR20001 has not yet started because
the
content for the package "SUR0000C" - "Microsoft Updates Tool Sync"
(version
4) has not been acquired. Possible cause: The content for this program
must
be downloaded into the computer's cache, or the content could not be
located.
Solution: If the program is being downloaded, no action is required.
The
program will start once the download has been successfully completed.
If
the
content can not be located, ensure that a distribution point with this
content is available for this computer. Distribution point
availability
can
be affected by roaming boundary configuration which is used to
determine
whether distribution points are classified as local or remote, or by
enabling distribution points as protected distribution points.
**************************
When i run report "Status of a specific advertisment" on Sync tool i
have
alot of waiting.
I checked CAS.log and this is what it states:
*******************
Requesting content SUR0000C.7, size(KB) 10008, under context System
ContentAccess 11/6/2007 8:31:55 AM 4840 (0x12E8)
LS job {C71173EC-4A98-4348-A13D-3CA64247C212} submitted to get DP
locations
for content SUR0000C.7 ContentAccess 11/6/2007 8:31:55 AM 4840
(0x12E8)
Successfully created location request
{B98E810A-A597-45B9-A596-FD206616E8CE}
for content SUR0000C.7 ContentAccess 11/6/2007 8:31:55 AM 4840
(0x12E8)
Location update from LS for content SUR0000C.7 and location request
{B98E810A-A597-45B9-A596-FD206616E8CE} ContentAccess 11/6/2007 8:31:58
AM
2160 (0x0870)
No matching DP Location found ContentAccess 11/6/2007 8:31:58 AM 2160
(0x0870)
Location update from LS for content SUR0000C.7 and location request
{B98E810A-A597-45B9-A596-FD206616E8CE} ContentAccess 11/6/2007 9:29:59
AM
4888 (0x1318)
No matching DP Location found ContentAccess 11/6/2007 9:29:59 AM 4888
(0x1318)
*************************

The advertisemen with the same package with Microsoft Tool program
runs
without problems on two test clients on a daily basis but the Sync
tool
program/advertisement doesnt run succesfully, keeps reporting waiting.

Since the Sync tool runs on the site server that also is dp i do not
understand how it cannot locate a matching DP (according to CAS.log)

Anyone have an idea why this might occur and how to resolve this?

I even ran the syncxml.exe /s /site SURAPP003 /code SUR /package
SUR0000C
/target \\SURAPP003\PackageSrc
under system account in a cmd box and it ran successfully.

The SMS Cache of sms client on sms site resides in D:\SMS_CCM\Cache as
far
as i can tell ( is this correct or is there a way to check for its
location)
and that folder remains empty.

Any input will be greatly appreciated.

Thanks in advance.

"Kim Oppalfens [MVP]" <""Kim dot Oppalfens\"@google mail.com"> wrote
in
message news:%23Xm6ISHIIHA.4880@xxxxxxxxxxxxxxxxxxxxxxx
John wrote:
Hi again,
i just checked and the old sms id of the site server listing all
its
role
is stated as obsolete and inactive :S.

Does anyone know if this affect SMS operations or that its just a
sms
record that can be deleted without effecting sms itself?



Assuming you see this in one of the collections, than it is just a
client
record and shouldn't harm the rest of your sms functions in any way.

--
"Everyone is an expert at something"
Kim Oppalfens - Sms Expert for lack of any other expertise
Windows Server System MVP - SMS
http://www.blogcastrepository.com/blogs/kim_oppalfenss_systems_management_ideas/default.aspx









.

Relevant Pages

  • Re: SMS Support Question
    ... I am writing a design document of upgrading SMS 1.2 to SMS 2003 ... But I do not know why the package cannot be copied to it. ... with about 20 Distribution Point. ... starting to distribute package "Windows Resource Kit Tools - ...
    (microsoft.public.sms.admin)
  • Re: SMS 2003 slows down client computers during boot
    ... Does the package run from DP or downoad and execute? ... I wonder if our current patch distribution scheme (all Post-SP2 XP ... Clear SMS cache files. ... About the log entry, the log entries you see is a normal behavior. ...
    (microsoft.public.sms.admin)
  • Re: Two Distribution Points on Primary Server
    ... How to Specify Drives for Client Access Points and Distribution ... Or if you're on SMS 2003 SP2, I think you can create a file named ... A unique share name and path to be created for the package source files on ... If you distribute the package to clients that do not support long file names, ...
    (microsoft.public.sms.admin)
  • RE: Software distribution from a non site system
    ... In a simple manner a package could allso be starting up notepad on ... So in your case you would like have the SMS client to start een application ... package will not be more than a command to execute "yourapp.exe" with perhaps ... distribution point. ...
    (microsoft.public.sms.swdist)
  • Re: Ran ccmclean on site server, what are implications???
    ... properties schedule distribution point at 13:30pm. ... Is this what you meant by "set the package to autoupdate"? ... Afterwards i tried running sync tool. ... If this works then you can work backwards to make sure it works thru sms. ...
    (microsoft.public.sms.setup)