Automatic Deployed Updates Source Cleanup

I recently set up an automatic deployment rule for the scep definition updates. It works like a charm, new update are being downloaded, and old updates are beeing superseeded and at last expired.
But, the source folder, where my software update deployment package lies is just getting bigger and bigger. SCCM obviously don't distribute the expired updates to the DP anymore but does not cleanup the source folder.
Is there a mechanism which will cleanup my source folder or do i need to write a script for that? I also run the WSUS Cleanup Wizard, but it also won't cleanup my update source folder.
We are using SCCM 2012 SP1 CU3
Thanks in advance..

You should remove the expired updates from your software update Groups. That way the source and the DP will be "cleaned up"
Kent Agerlund | My blogs: blog.coretech.dk/kea and
SCUG.dk/ | Twitter:
@Agerlund | Linkedin: Kent Agerlund |
Mastering ConfigMgr 2012 The Fundamentals

Similar Messages

Automate CS4 Updates

Hi,
I'm supporting a group of 15 Mac users that are going to upgrade to CS4.
The users don't have local administrator rights on their machines, so I created a script that runs the Adobe Updater as the administrator, every 2 weeks. This works fine, but it still requires the user to stop what they're doing, install the updates, etc.
Is there any way to automate/deploy updates to CS4, like automatic updates for Windows or Mac?
Thanks!

Jeremy,
>Is there any way to automate/deploy updates to CS4
You may have to call Adobe tech support if no one chimes in here. But I, for one, would not automatically update ANY machine while there's a chance it is still being used for other work. In my opinion, that would increase the risk of a corrupted installation, particularly if the application being updated is still "live".
Although probably not your first choice, even scripted updates would be most safely done before or after hours or during lunch breaks.
Neil

SCEP definition update through Automate Deployment Rule

Hi all. Got a question on deploying SCEP 2012 definition updates to client PC through SCCM2012 R2 by using Automate Deployment Rule. It looks like the client PC is not receiving the definition updates immediately. The ADR seems working
fine, it completed the synchronization successfully, no error on "PatchDownloader.log" and "ruleengine.log"; deployment folder got filled up with new definition updates. However, the client is not receiving the new SCEP definition
updates immediately, although I've configured ADR to install the update as soon as possible, yet nothing happens for the past 2 hours. I ended up launch the SCEP console on the client PC and then click the "update" button manually, and this
launch the update process. I just wondering how much time we need to wait for the SCEP definition update to apply onto the client PC. Microsoft seems release 3 - 4 definition update per day, I am afraid we might not using the latest definition
update due to the time waiting issue. Thank you.

I've configured the polling interval to take place every 3 hours. I guess this contribute to the waiting time. I will keep an eye on it to see if the definition in deed installs automatically.
Yes that's one of the delay which is the major Contribution also there would be some delay for the updates when they are downloading and getting updated to the distribution points. You can check the 'Content Status' for that package to verify if it got updated.
Umair Khan
Microsoft Support Escalation Engineer
Blog: http://blogs.technet.com/umairkhan
Facebook:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Some Systems Restarted Automatically after Updates Deployment with Restart Suppressed

I've searched the forum and multiple blogs - but, I'm still confused about what is causing some of our workstations to restart after applying a software updates deployment.
I deployed the Dec 2013 Patch Tuesday updates to a collection of workstations. The deployment was set to:
Not allow restarts outside of a maintenance window (box is unchecked)
Suppress restarts on workstations (box is checked).
There is no maintenance window defined for any of our workstations
On all the workstations, the HKEY_LOCAL_MACHINE\Software\...\WindowsUpdate\ values are:
WUServer: http address of our SCCM SUP server
WUStatusServer: http address of our SCCM SUP server
Also, the key in HKEY_LOCAL_MACHINE\...\WindowsUPDATE\AU is:
UseWUServer: 1 (which I understand disables the use of the automatic Windows update service)
Some set of workstations automatically restarted shortly after 3:00 am the next morning. Clearly that's the Windows Update Agent jumping in a restarting the systems. However, I don't understand why it would do that. I really don't understand why it would
have occurred on only some of the workstations while others are still waiting for users to manually restart 36 hours later.
All of the workstations are in the same active directory OU - so the same set of GPOs applies to all.
Note: none of the registry keys were set directly in any GPOs - I assume the values were set by the SCCM client.
Any assistance would be appreciated.
Larry

depending on the OS version, this could be relevant:
http://blogs.technet.com/b/wsus/archive/2013/06/11/wsus-blog-managing-updates-with-deadlines-in-an-era-of-automatic-maintenance.aspx
http://blogs.technet.com/b/wsus/archive/2013/10/08/enabling-a-more-predictable-windows-update-experience-for-windows-8-and-windows-server-2012-kb-2885694.aspx
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Automatic Deployment Rules - Just Not Working/Reboot

Good Morning:
For the better part of 5 days I have been trying to get ADR deployed in my lab to install and automatically reboot machines. I have gotten everything set up and the rule is working and downloading the update, just never making it to the clients to
install the updates and or reboot. For simplicity sake, I created a device collection, "domain controllers" and this finds my two DCs just fine. I then created a ADR
Collection - Domain Controllers, Add to Existing Software Update Group - Software Updates (date released - 2 months, Product - 2008 R2) as both of my DCs are 2008 R2 - Evaluation Schedule (Run on schedule - once a week at 11:30 pm) - Deployment Schedule
(software/specific time 1 hour) (installation/2 hours) - User Experience Software Installation Checked - Then I create a new deployment package and then run it.
It created the deployment packages, and the software update group, I checked the logs and it downloads the files just fine and shows 42 updates needed. However I cannot get those two servers to install updates and reboot for the life of me. I have
google and read everything possible. I checked the permissions of the package source, I created a maintenance window for that time, I attempted to change the work information via powershell in case it was overlapping.
Can anyone please give me a little push in the right direction on what I could possibly be missing?
I did see this in the log,
Could not find element DeploymentId SMS_RULE_ENGINE
1/3/2014 10:03:35 AM 3240 (0x0CA8)
Could not find element UpdateGroupId SMS_RULE_ENGINE
1/3/2014 10:03:35 AM 3240 (0x0CA8)
Could not find element UpdateGroupName SMS_RULE_ENGINE
1/3/2014 10:03:35 AM 3240 (0x0CA8)
SQL is: select cis.CI_ID from vCI_ConfigurationItems cis join vProvisionedCIs pci on cis.CI_ID = pci.CI_ID where cis.CI_ID in (16789853, 16789855, 16789865, 16789867, 16790069, 16790071, 16790077, 16790081, 16790087, 16790089, 16790164, 16790166,
16790193, 16790195, 16790203, 16790205, 16790213, 16790217, 16790221, 16790424, 16790426, 16790430, 16790436, 16790438, 16790444, 16790448, 16790452, 16790509, 16790517, 16790523, 16790527, 16790531, 16790535, 16790537, 16790547, 16790568, 16790574) order
by cis.CI_ID SMS_RULE_ENGINE
1/3/2014 10:03:35 AM 3240 (0x0CA8)
42 of 42 updates are downloaded and will be added to the Deployment.
SMS_RULE_ENGINE 1/3/2014 10:03:35 AM
3240 (0x0CA8)
Any assistance would be greatly appreciated as this is just making me spin in circles.

In the WUAHandler
<![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({425A8C16-C127-4006-B60D-8F04DF0333EB}). Error = 0x87d00692.]LOG]!><time="11:28:02.414+360" date="01-03-2014" component="WUAHandler" context="" type="3" thread="6796" file="cwuahandler.cpp:2325">
<![LOG[Its a WSUS Update Source type ({425A8C16-C127-4006-B60D-8F04DF0333EB}), adding it.]LOG]!><time="12:58:08.788+360" date="01-03-2014" component="WUAHandler" context="" type="1" thread="4344" file="sourcemanager.cpp:1232">
<![LOG[Enabling WUA Managed server policy to use server: http://KSP-SCCM.waw.local:8530]LOG]!><time="12:58:08.788+360" date="01-03-2014" component="WUAHandler" context="" type="1" thread="4344" file="sourcemanager.cpp:948">
<![LOG[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="12:58:08.803+360" date="01-03-2014" component="WUAHandler" context="" type="1" thread="4344" file="sourcemanager.cpp:954">
<![LOG[Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://KSP-SCCM:8530 and Policy ENABLED]LOG]!><time="12:58:10.348+360" date="01-03-2014" component="WUAHandler" context="" type="3" thread="4344" file="sourcemanager.cpp:1013">
<![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({425A8C16-C127-4006-B60D-8F04DF0333EB}). Error = 0x87d00692.]LOG]!><time="12:58:10.348+360" date="01-03-2014" component="WUAHandler" context="" type="3" thread="4344" file="cwuahandler.cpp:2325">
So now I think that GPO setting maybe causing my issues.

No automatic deployment for Portal Application Standalone DC?

Hi Experts,
     I created a Portal Application Standalone DC under NWDI track.
     I checked in the code and activate my request, the log showed that this DC had beed sucessfully built. BUT, I can not find this portal application had beed deployed. it seems that EP DC can not be deployed automatically
    I searched SDN and there are some topics about this problem, it seems that EP DC can not be deployed automatically, we need to deploy the DC manually, is it right?
   Thanks!
segement of my build log:
[pppacker] WARNING: Could not determine correct package of package folder for entity (portalapplication-api/Class, src.api/)
[pppacker] Packed   0 files for entity (portalapplication-api/Class, src.api/)
[pppacker] Packed   3 files for entity (portalapplication-core/Class, src.core/)
     [timer] Portal Application libraries packaging finished in 0.389 seconds
createApplication:
      [echo] create PAR..
       [jar] Building jar: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/t/80B8A4CDC19F36C272AD330774CF8FF0/com.hcm.isr.newtemplate.par
createPublicParts:
      [echo] Public Part: API
[pppacker] Packing public part 'API'
[pppacker] Packed   0 files for entity Portal API (Portal API)
[pppacker] Packed 1 entity for public part 'API'
     [timer] Public part packaging finished in 0.114 seconds
createDeployArchive:
      [echo] Creating portalapp-dd.xml
       [cda] Preparing archive for deploy unit "default"
       [cda]   deployment type: "J2EE"
       [cda]   explicit modules:
       [cda]     /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/t/80B8A4CDC19F36C272AD330774CF8FF0/com.hcm.isr.newtemplate.par
       [cda]
       [cda] Creating Ant build file: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/DCs/test/isrformtemp/_comp/gen/default/logs/buildDeployArchive.xml
       [cda]
       [cda]
       [cda] Creating descriptor META-INF/application.xml ...
       [cda]
       [cda] Creating descriptor META-INF/application-j2ee-engine.xml ...
       [cda] Adding module "com.hcm.isr.newtemplate.par" with container type "PortalRuntimeContainer".
       [cda]
       [cda] Collecting modules...
       [cda] Adding module 'com.hcm.isr.newtemplate.par' from current development component
       [cda] Ant build file creation finished in 0.119 seconds
packDeployArchive:
[srcpacker] Creating source archive
[srcpacker] No sources available for packing, no archive will be created.
     [timer] Source archive creation finished in 0.008 seconds
    [dcinfo] Creating deploy archive info
    [jarsap] Info: JarSAP version 20060908.1630
    [jarsap] Info: JarSAPProcessing version 20070423.1630 / JarSL version 20070906.1830
    [jarsap] Building: /usr/sap/EP1/JC00/j2ee/cluster/server0/temp/CBS/5/.B/3501/DCs/test/isrformtemp/_comp/gen/default/deploy/test~isrformtemp.sda with compression
     [timer] JarSAP finished in 0.461 seconds

The Standalone DC has a deployable result (opposed to the Module DC) and should thus be deployed when an activity is successfully activated. Is automatic deployment perhaps disabled?

Contract automatically set as source of supply for PR/PO

Hello MM experts,
I am thinking about implementing the following scenario and I have 4 questions
PM service order that creates a Purchase requisition automatically.
I will have in the system a MM contract for that material / vendor / plant
It is possible in SAP that the contract is set automatically as a source of supply in the automatically created purchase requisition?
If it’s not possible in the PR it’s is possible at the time of PO creation?
What configuration is needed in the system for this?
It is possible to automatically create a PO from a PR with no steps for the user?
Thanks a lot for your valuable help and regards.

Dear,
Here you need to consider two parameters.
Contract : Its an yearly or monthly contract with a desired vendor on Quantity(Quantity Contract) or Value(Value contract) based.
But if you are creating a service P.R using maintenance order for that particular maintenance service.Here system considers the account assignment as "F".
If you want to capture the service cost of contract,
Create an AMC for the services of that vendor and create P.O with account assignment as "U-Unknown". At the time of service required by maintenance department, They will create a maintenance order and do service entry with respect to "Maintenance Order". So actual cost will update in maintenance order.
You can create a "Automatic P.O "with respect to P.R as our friend Jurgen said for supply.This can be done by activating the check box in material master of "Purchasing" view.
You have an option of assigning the agreement in 'Maintenance Order"At the time of creating a P.R through it.But If your contract "Account assignment" and P.R "Account assignment" Creating through maintenance order will be different.So system will populate an error message as" Account assignment in agreement and Requisition incompatible"
Regards,
Pardhu

Deployed updates not being downloaded by clients - Error = 0x87d00692 is in the WUAHandler.log

Hi,
I've been setting up SCCM 2012 and mostly following the instructions and guides at
http://www.windows-noob.com/forums/index.php?/topic/4045-system-center-2012-configuration-manager-guides/. We used to use a WSUS server to deploy our updates but now I've setup SCCM 2012 and setup the SUP role (and WSUS) on the SCCM server.
I belive I've gotten most things properly configured. The SCCM Software Center application is successfully installed on all my clients and I'm able to setup software update groups and I just tried to deploy the most recent updates from this Tuesday
patch release. I can see the packages downloaded on my SCCM server in the folder that I specified but the updates don't seem to going down to my clients. I've looked at the WUAHandler.log on one of my clients and it keeps repeating the following
lines:
<![LOG[Group policy settings were overwritten by a higher authority (Domain Controller) to: Server
http://topanga:8530 and Policy ENABLED]LOG]!><time="15:54:01.474+420" date="08-16-2012" component="WUAHandler" context="" type="3" thread="8680" file="sourcemanager.cpp:1000">
<![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({382D7556-03CE-4803-8A55-13D9A3E061CB}). Error = 0x87d00692.]LOG]!><time="15:54:01.474+420" date="08-16-2012" component="WUAHandler" context="" type="3" thread="8680" file="cwuahandler.cpp:2322">
<![LOG[Its a WSUS Update Source type ({382D7556-03CE-4803-8A55-13D9A3E061CB}), adding it.]LOG]!><time="15:54:01.614+420" date="08-16-2012" component="WUAHandler" context="" type="1" thread="4840" file="sourcemanager.cpp:1222">
<![LOG[Enabling WUA Managed server policy to use server:
<time="15:54:06.772+420">http://topanga.kcicorp.com:8530]LOG]!><time="15:54:06.772+420" date="08-16-2012" component="WUAHandler" context="" type="1" thread="5308" file="sourcemanager.cpp:938">
<![LOG[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="15:54:06.812+420" date="08-16-2012" component="WUAHandler" context="" type="1" thread="5308" file="sourcemanager.cpp:944">
<![LOG[Group policy settings were overwritten by a higher authority (Domain Controller) to: Server
http://topanga:8530 and Policy ENABLED]LOG]!><time="15:54:09.242+420" date="08-16-2012" component="WUAHandler" context="" type="3" thread="5308" file="sourcemanager.cpp:1000">
<![LOG[Failed to Add Update Source for WUAgent of type (2) a[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="15:54:01.848+420" date="08-16-2012" component="WUAHandler" context="" type="1" thread="4840" file="sourcemanager.cpp:944">
<![LOG[Group policy settings were overwritten by a higher authority (Domain Controller) to: Server
http://topanga:8530 and Policy ENABLED]LOG]!><time="15:54:06.502+420" date="08-16-2012" component="WUAHandler" context="" type="3" thread="4840" file="sourcemanager.cpp:1000">
<![LOG[Failed to Add Update Source for WUAgent of type (2) and id ({382D7556-03CE-4803-8A55-13D9A3E061CB}). Error = 0x87d00692.]LOG]!><time="15:54:06.502+420" date="08-16-2012" component="WUAHandler" context="" type="3" thread="4840" file="cwuahandler.cpp:2322">
<![LOG[Its a WSUS Update Source type ({382D7556-03CE-4803-8A55-13D9A3E061CB}), adding it.]LOG]!><time="15:54:06.762+420" date="08-16-2012" component="WUAHandler" context="" type="1" thread="5308" file="sourcemanager.cpp:1222">
<![LOG[Enabling WUA Managed server policynd id ({382D7556-03CE-4803-8A55-13D9A3E061CB}). Error = 0x87d00692.]LOG]!><time="15:54:09.242+420" date="08-16-2012" component="WUAHandler" context="" type="3" thread="5308" file="cwuahandler.cpp:2322">
Can someone give me some hints as to what is happening?
Thanks in advance,
Nick

I was troubleshooting this issue earlier today and pulling my hair out until I came across this blog post: http://www.bibble-it.com/2009/07/24/sccm-update-scan-error . Like many others, I'm using WSUS to also push the new SCCM client, so the GPO for the
WSUS server needs to be in place. The issue you're running into here is that your server names don't match up EXACTLY.
<![LOG[Enabling WUA Managed server policy to use server: <time="15:54:06.772+420">http://topanga.kcicorp.com:8530]LOG]!><time="15:54:06.772+420" date="08-16-2012" component="WUAHandler" context="" type="1" thread="5308" file="sourcemanager.cpp:938">
<![LOG[Waiting for 2 mins for Group Policy to notify of WUA policy change...]LOG]!><time="15:54:06.812+420" date="08-16-2012" component="WUAHandler" context="" type="1" thread="5308" file="sourcemanager.cpp:944">
<![LOG[Group policy settings were overwritten by a higher authority (Domain Controller) to: Server http://topanga:8530 and Policy ENABLED]LOG]!><time="15:54:09.242+420" date="08-16-2012" component="WUAHandler" context="" type="3" thread="5308" file="sourcemanager.cpp:1000">
You need to change your group policy to use the FQDN. In your case it would be http://topanga.kcicorp.com:8530 instead of http://topanga:8530

Trying to comprehend the use of Automatic Deployment Rules

I am having a hard time trying to conceptualize ADRs. I would appreciate it if someone can let me know if I am on the right track here.
The way I see it is I can set up an ADR for every 2nd Tuesday of every month (Patch Tuesday) to run to build my initial deployment to a pilot test group. Then I have to build subsequent deployments after that since ADRs can only build one deployment (the
one for my pilot test group).
My question is, should an ADR be used only for a pilot test deployment and not a production deployment?
Thank you very much everyone, I appreciate your help

I thought during the wizard it allows you to specify which type of patches you want to deploy such as Security, etc?
You select the update filter and criteria in the ADR wizard:
http://blogs.technet.com/b/configmgrdogs/archive/2012/05/08/configmgr-2012-automatic-deployment-rules.aspx
An example scenario:
http://technet.microsoft.com/en-us/library/jj134348.aspx#BKMK_Step2
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

ConfigMgr 2012 Update Source content deleted

Greetings,
I am experiencing a problem that is appears to be the same as the old thread here:
http://social.technet.microsoft.com/Forums/en-US/bee18ffb-f779-4aa4-900d-046e7711424c/sccm-2012-source-content-gets-deleted?forum=configmanagergeneral
Rather than revive an old post, I thought it best to start my own.
We have a rather large environment (CAS +5 Primaries + Many DP's) and we are currently adding several new remote DP's each week. Each time a new DP is added it is placed in a Distribution Group and the "core" package content is sent
to it.
I have a problem where my Windows Update Packages keep failing due to content disappearing from the source folder location. This started some time ago, and is now becoming a regular event to correct. Not every day, but once a week or so.
The Update group has the updates all showing as "downloaded"
I have a report query that matches the updates to the "GUID" subfolder so I know all the content is there
I distribute the content from the CAS. Distrmgr.log shows all is good. Packagemgr.log on the Primaries show all is good
Client have been installing the updates as expected so the deployment does work
Days/weeks later, ALL the DP's will show as "failed" for that update package. Checking the distmgr.log shows that it is failing to distribute due to a missing source folder. I use my query to work out which update that subfolder GUID belongs to,
but it is already flagged as downloaded, and when trying to download it again CM just "skips" it thinking it already has the content in that package.
The "fix" is to download the same update to a new package instead. CM then does a proper check, realises it doesn't have the content and will download the update to the new package source location. I can then copy the missing GUID subfolder
from the new package into the original package and try the distribution again.
The problem now is that there are usually many folders missing, so distmgr.log will fail again on the next missing folder. Because it stops at the first error, repeating the above process is incredibly tedious when there are a lot of missing folders.
My current "solution" is to select ALL the updates that should be in the current package and download them all to a "Temp package" that isn't deployed or distributed anywhere. Then in future when the main deployment package fails, I just
"select all, copy" the contents of the temp folder into the original folder (skip duplicates) and it puts back all the missing content and distribution will work again.
We are not using ADR's for this content, although I do have an ADR for the Endpoint updates which go into a completely different distribution package.
*Something* is cleaning up or purging these folders from the source location, but I have no idea what process or mechanism this might be.
Any thoughts or suggestions most welcome.
Scott.

I've found the cause, blog post write here:
http://kickthatcomputer.wordpress.com/2014/10/11/configuration-manager-update-source-content-being-deleted/
Microsoft was working with me trying to identify what was deleting the folders, however nothing was appearing as the cause.
I just realised this morning that I had used the built-in CM12 Migration function some time back to migrate update packages and groups over to our second hierarchy but hadn't updated any of the migrated content since then. The migrated packages on the second
hierarchy still point to the same source location and so whenever my original hierarchy added content to the update packages, the second hierarchy would delete it because it though it was "orphaned" content.
This is something people will have to watch out for when using the migration wizard as the same type of issues will impact things like WIM boot image packages as well where the source content can be manipulated directly by the CM12 system on one hierarchy
without the other one being aware of that change.
At the moment the options are to either
Make sure you run a "migrate changes" job whenever you make changes to updates on your source hierarchy to keep them in sync
Manually make a copy of the source content to a different folder or location, then update the package source location on the migrated packages to point to that new content (undesirable for massively large content)
Create a scripted method to schedule regular migration jobs between the hierarchies (looking into this option now)

SAPGui Automatic Workstation update service

Hi All:
We deployed SAPGui 720 to end users with installation server. After deployment we disabled automatic workstation update from installation server. SAP released new patch 1 for SAPGui 720 recently. We upgraded our deployment server with patch 1 and enabled automatic update but users are not getting updates.
SAP Document says once you disable automatic workstation update, it can not be undone. you need to reinstall service.
Is their any other way to enable it and get automatic update? We tried another option with double click on desktop icon 5 times to check update but it is not working.
Any ideas?
Thanks,
Miral.

ULA_RANDY,
We did the same thing ... had auto update service disabled on the server and front ends and needed to re-activiate it.
To "Turn it Back On" for your front end clients is easy.
1) Turn Automatic Updates back ON on your server. Change check in time and reboot switch to whatever you need.
2) Run the following command on your front ends:
[yourInstserver]\[share]\setup\nwsapsetup.exe /update /product=SAPWUS /NoDlg
If it runs correctly you will find additional files in the front end folder ...\Program Files\sap\sapsetup\setup\updater
You also will find WkstaUpdater.cfg (same location) to have changed entry of DISABLED =FALSE
There are many ways to run the command ... Copy/paste to Start, Run, CMD file, Logon Script, AD Startup Script, ... we have a vb script that we push to the clients via Microsoft SCCM. This assumes you have LSH configured so that end user does not have to have local admin rights.
Make sure your installation server is patched with the latest SAP SETUP 9.0 patch. And watch out ... it's confusing there are TWO downloads presented for SAP SETUP 9.0. The smaller one is setup only, the larger is a combined setup and AWUS patch. You need the larger one. See note 1587566
Also ... then once you have all your clients participating in Auto Update ... wait a few days, and then you can patch your server with the main 7.20 patch. Don't dump too much on the front end clients at once
Good luck!
Bob H
Minneapolis, MN

[svn:osmf:] 13994: Updating source path to control bar plugin.

Revision: 13994
Revision: 13994
Author:   [email protected]
Date:     2010-02-05 00:47:30 -0800 (Fri, 05 Feb 2010)
Log Message:
Updating source path to control bar plugin.
Modified Paths:
    osmf/trunk/apps/samples/plugins/ControlBarPluginTest/.actionScriptProperties
    osmf/trunk/apps/samples/plugins/ControlBarPluginTest/.project

http://validator.w3.org/check?uri=http%3A%2F%2Fwww.coloradorealestatetours.com%2 Fbrandnewhomes%2Frockinghorse%2Fcolter%2Fdefault.aspx%23TourViewer&charset=%28de tect+automatically%29&doctype=Inline&group=0
Take a look through this page to help sort things out.
Your page code suggests you're using the javascript method to embed the QTVR's and you even have a link to the proper QuickTime .js file on your server. But your page code is incorrect (object/embed) for that file to work.
Your source file (at the link you provided) is 800X600 but you've used the "tofit" tag to reduce its size. A 600 width "tofit" would need 450 for the height. But you've set it at 345 (your code above). This would cut things off.
http://www.qtbridge.com/pageot/pageot.html
Free software that can help with proper html code and it understands the special .js code required for the modern javascript coding for Internet Explorer:
http://developer.apple.com/internet/ieembedprep.html

SCCM 202 R2 - Automatic Deployment Rules

Hi all,
just got a question about the way in which the Automatic Deployment Rules work in SCCM 2012 R2. I've got a number of patching collections configured with different types of machines in (Pilot Group, Desktops, Test Servers, Prod Servers etc...) and was
hoping to set up a corresponding ADR for each of these collections.
Having had a quick test of the ADR, it seems to work well. When the Evaluation Schedule deadline hits, I see the updates are downloaded (watching RuleEngine.log) and then a new Software Update Group is created and is deployed to the machines
in the collection.
My question is, what's the best way to set up the ADRs to patch these collections? Does each patching collection need it's own ADR? If so, does this mean I will end up downloading the same updates multiple times since most of the ADRs will have the
same Products/Classifications selected?
Realise this is probably a fairly simple question but can't quite get my head round it so any help/info would be much appreciated!
Cheers

There really are three possible strategies here:
- Use an ADR for each collection. This will of course cause duplicate update groups but will be fully automated.
- Use a single ADR for each OS type; e.g., one for workstations and one for servers. Then manually add deployments to the appropriate ADR for each collection. This requires a bit of manual intervention but its not much and offers a QA checkpoint.
- Use a single ADR targeting a master collection and then use maintenance windows to control deployment times to "sub-collections". This is fully automated as well but does require some manipulation of the maintenance windows on a month to month
basis.
I often do a combination of the above depending upon the exact needs of the environment.
Jason | http://blog.configmgrftw.com | @jasonsandys

System Center 2012 Error on Automatic Deployment Rule

Good day,
I have created and Automatic Deployment Rule to deploy my EndPoint Protection updates. So far, I have been able to deploy the agents, and the Antivirus to all my network computers. The problem I have is when the update rule runs. I have checked the SMSProv.log
file, and this I what I get:
Execute SQL =select all SMS_AutoDeployment.AutoDeploymentEnabled,SMS_AutoDeployment.AutoDeploymentID,SMS_AutoDeployment.SecurityKey,SMS_AutoDeployment.Description,SMS_AutoDeployment.LastErrorCode,SMS_AutoDeployment.LastErrorTime,SMS_AutoDeployment.LastRunTime,SMS_AutoDeployment.LocaleID,SMS_AutoDeployment.Name,SMS_AutoDeployment.Schedule
from vSMS_AutoDeployments AS SMS_AutoDeployment where SMS_AutoDeployment.AutoDeploymentID = 1
I am running System Center 2012 R2 on Windows Server 2012 R2. With this, I run SQL Server 2012 Sp1.
Thanks
Chris

Hi,
UpdatesHandler.log on the client records about the download and installation of software updates on the client.
Best Regards,
Joyce Li
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Disable Automatically Deleted Updates Download on SCCM 2012 with WSUS

Hi
I have SCCM 2012 SP1 with WSUS integrated, both are on the same server, I created a structure where I downloaded the updates:
D:\Wsus\HotfixWinX
D:\Wsus = The folder where I installed the WSUS role
HotfixWinX = The folder where I downloaded the hotfix
When I run "Synchronize Software Updates" the updates downloaded with a time of old age are eliminated automatically, have reviewed the log wsyncmgr and I found this:
My question is, how can I prevent updates and updates folders to be automatically deleted?
Thank you.

This is a fully automated process that only works for expired updates. Do keep in mind that after this specific message the updates still exist in the console. For a very good complete explanation, see:
http://blogs.technet.com/b/configmgrteam/archive/2012/04/12/software-update-content-cleanup-in-system-center-2012-configuration-manager.aspx
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Automatic Deployed Updates Source Cleanup

Similar Messages

Maybe you are looking for