Best practice for SCEP definition ADR?

This is how I understand the best practice to be for configuring the SCEP definition ADR:
Have synchronization run once per day during non peak hours
Configure the SCEP definition ADR to run after each synchronization rather than running in intervals such as every 6 hours
Do not run synchronizations multiple times per day because it can add extra load on the server and cause the software update package version to increase too quickly and impact the definition deployment success rate
Is this true?
If so, then if Microsoft releases SCEP definitions 3 times per day and the synchronization runs only once per day, then obviously SCEP clients will not be able to download the latest, most current SCEP definition due to the fact that the sync process is
what actually grabs the metadata from Microsoft's catalog.
Is it even possible to run multiple synchronizations per day? I am running SCCM 2012 R2 in my environment and I DO NOT see anywhere where one can configure multiple software update synchronizations to take place. It is possible from what I understand to
do this using 3rd party tools, but I really do not want to go there.
Can someone please help me with this?
As always, thanks so much.

Hi,
That changed after Sp1 so it was true but now with sp1 and R2 you can schedule them three times a day. If you have infrastructure that can't handle that, that is another topic. But from Sp1 and further synchronizing the SUP three times a day and set the
ADR to trigger after a synchronization is the best practice.
"For performance reasons, in Configuration Manager with no Service Pack, do not schedule automatic deployment rules to deliver definition updates more than once each day. In Configuration Manager SP1, do not schedule automatic deployment rules to deliver
definition updates more than three times a day."
http://technet.microsoft.com/en-us/library/jj822983.aspx
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

Similar Messages

Best practice for upgrading task definition without deleting task instances

best practice for upgrading task definition in production system without deleting or terminating task instances
If I try and update a task definition with task instances running I get the following error:
Task definition 'My Task - Add User' may not be modified while there are active task instances
Is there a best practice to handle this. I tried to force an update through the console but that didn't work. I tried editing the task from the debug page and got the same error.

1) Rename the original task definition.
2) Upload the new task definition with the original name.
3) Later, after all the running tasks have timed out, delete the old definition.
E.g., if your task definition is "myWorkflow":
1) Rename "myWorkflow" to "myWorkflow-old-2009-07-28"
2) Upload the new task definition as "myWorkflow".
Existing tasks will stay linked to the original (renamed) workflow definition.
New tasks will use the new definition.
As the previous poster notes, depending on the changes you are making, letting the old task definitions stay active could have bad side-effects and might be better avoided.

Best Practices for Defining NDS Java Projects...

We are doing a Proof of Concept on using NDS to develop non-SAP Java applications. We are attempting to determine if we can replace our current Java development tools with NDS/WAS.
We are struggling with SAP's terminology and "plumbing" for setting up/defining Java projects. For example, what is and when do you define Tracks, Software Components, Development Components, etc. All of these terms are totally foreign to us and do not relate to our current Java environment (at least not that we can see). We are also struggling with how the DTR and activities tie in to those components.
If any one has defined best practices for setting up Java projects or has struggled with and overcome these same issues, please provide us with some guidance. This is a very frustrating and time-consuming issue for us.
Thank you!!

Hi Peggy,
In Component Model we divide software projects into small components.Components can use other components in well defined manner.
A development object is a part of a component that can be changed or developed in some way; it provides the component with a certain part of its functionality. A development object may be a Java class, a Web Dynpro view, a table definition, a JSP page, and so on. Development objects are always stored as sources in a repository.
A development component can be defined as a frame shared by a number of objects, which are part of the software.
Software components combine components (DCs) to larger units for delivery and deployment.
A track comprises configurations and runtime systems required for developing software component versions.It ensures stable states of deliverables used by subsequent tracks.
The Design Time Repository is for versioning source code management. Distributed development of software in teams. Transport and replication of sources.
You can also find lot of support in SDN for the above concepts with tutorials.
Refer this Link for a overview on Java development Infrastructure(JDI)
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/java development infrastructure jdi overview.pdf
To understand further
Working with Net Weaver Development Infrastructure :
http://help.sap.com/saphelp_nw04/helpdata/en/03/f6bc3d42f46c33e10000000a11405a/content.htm
In the above link you can find all the concepts clearly explained.You can also find the required tutorials for development.
Regards,
Vijith

JSF - Best Practice For Using Managed Bean

I want to discuss what is the best practice for managed bean usage, especially using session scope or request scope to build database driven pages
---- Session Bean ----
- In the book Core Java Server Faces, the author mentioned that most of the cases session bean should be used, unless the processing is passed on to other handler. Since JSF can store the state on client side, i think storing everything in session is not a big memory concern. (can some expert confirm this is true?) Session objects are easy to manage and states can be shared across the pages. It can make programming easy.
In the case of a page binded to a resultset, the bean usually helds a java.util.List object for the result, which is intialized in the constructor by query the database first. However, this approach has a problem: when user navigates to other page and comes back, the data is not refreshed. You can of course solve the problem by issuing query everytime in your getXXX method. But you need to be very careful that you don't bind this XXX property too many times. In the case of querying in getXXX, setXXX is also tricky as you don't have a member to set. You usually don't want to persist the resultset changes in the setXXX as the changes may not be final, in stead, you want to handle in the actionlistener (like a save(actionevent)).
I would glad to see your thought on this.
--- Request Bean ---
request bean is initialized everytime a reuqest is made. It sometimes drove me nuts because JSF seems not to be every consistent in updating model values. Suppose you have a page showing parent-children a list of records from database, and you also allow user to change directly on the children. if I hbind the parent to a bean called #{Parent} and you bind the children to ADF table (value="#{Parent.children}" var="rowValue". If I set Parent as a request scope, the setChildren method is never called when I submit the form. Not sure if this is just for ADF or it is JSF problem. But if you change the bean to session scope, everything works fine.
I believe JSF doesn't update the bindings for all component attributes. It only update the input component value binding. Some one please verify this is true.
In many cases, i found request bean is very hard to work with if there are lots of updates. (I have lots of trouble with update the binding value for rendered attributes).
However, request bean is working fine for read only pages and simple binded forms. It definitely frees up memory quicker than session bean.
----- any comments or opinions are welcome!!! ------

I think it should be either Option 2 or Option 3.
Option 2 would be necessary if the bean data depends on some request parameters.
(Example: Getting customer bean for a particular customer id)
Otherwise Option 3 seems the reasonable approach.
But, I am also pondering on this issue. The above are just my initial thoughts.

Best Practice for using multiple models

Hi Buddies,
     Can u tell me the best practices for using multiple models in single WD application?
    Means --> I am using 3 RFCs on single application for my function. Each time i am importing that RFC model under
    WD --->Models and i did model binding seperately to Component Controller. Is this is the right way to impliment multiple            models in single application ?

It very much depends on your design, but One RFC per model is definitely a no no.
Refer to this document to understand how should you use the model in most efficient way.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/705f2b2e-e77d-2b10-de8a-95f37f4c7022?quicklink=events&overridelayout=true
Thanks
Prashant

Best practices for gathering statistics in 10g

I would like to get some opinions on what is considered best practice for gathering statistics in 10g. I know that 10g has auto statistics gathering, but that doesn't seem to be very effective as I see some table stats are way out of date.
I have recommended that we have at least a weekly job that generates stats for our schema using DBMS_STATS (DBMS_STATS.gather_schema_stats). Is this the right approach to generate object stats for a schema and keep it up to date? Are index stats included in that using CASCADE?
Is it also necessary to gather system stats? I welcome any thoughts anyone might have. Thanks.

Hi,
Is this the right approach to generate object stats for a schema and keep it up to date? The choices of executions plans made by the CBO are only as good as the statistics available to it. The old-fashioned analyze table and dbms_utility methods for generating CBO statistics are obsolete and somewhat dangerous to SQL performance. As we may know, the CBO uses object statistics to choose the best execution plan for all SQL statements.
I spoke with Andrew Holsworth of Oracle Corp SQL Tuning group, and he says that Oracle recommends taking a single, deep sample and keep it, only re-analyzing when there is a chance that would make a difference in execution plans (not the default 20% re-analyze threshold).
I have my detailed notes here:
http://www.dba-oracle.com/art_otn_cbo.htm
As to system stats, oh yes!
By measuring the relative costs of sequential vs. scattered I/O, the CBO can make better decisons. Here are the data items collected by dbms_stats.gather_system_stats:
No Workload (NW) stats:
CPUSPEEDNW - CPU speed
IOSEEKTIM - The I/O seek time in milliseconds
IOTFRSPEED - I/O transfer speed in milliseconds
I have my notes here:
http://www.dba-oracle.com/t_dbms_stats_gather_system_stats.htm
Hope this helps. . . .
Don Burleson
Oracle Press author
Author of “Oracle Tuning: The Definitive Reference”
http://www.dba-oracle.com/bp/s_oracle_tuning_book.htm

"Best practice" for components calling components on different panels.

I'm very new to Swing. I have been learning from tutorials, but these are always relatively simple interfaces , in which every component and container is initialised and added in the constructor of a main JFrame (extension) object.
I would assume that more complex, real-world examples would have JPanels initialise themselves. For example, I am working on a project in which the JFrame holds multiple JPanels. One of these Panels holds a group of JToggleButtons (grouped in a ButtonGroup). The action event for each button involves calling the repaint method of one of the other Panels.
Obviously, if you initialise everything in the JFrame, you can simply have the ActionListener refer to the other JPanel directly, by making the ActionListener a nested class within the JFrame class. However, I would like the JPanels to initialise their own components, including setting the button actions, by using an extension of class JPanel which includes the ActionListeners as nested classes. Therefore the ActionListener has no direct access to JPanel it needs to repaint.
What, then, is considered "best practice" for allowing these components to interact (not simply in this situation, but more generally)? Should I pass a reference to the JPanel that needs to be repainted to the JPanel that contains the ActionListeners? Should I notify the main JFrame that the Action event has fired, and then have that call "repaint"? Or is there a more common or more correct way of doing this?
Similarly, one of the JPanels needs to use a field belonging to the JFrame that holds it. Should I pass a reference to this object to the JPanel, or should I have the JPanel use "getParent()", or some other method?
I realise there are no concrete answers to this query, but I am wondering whether there are accepted practices for achieving this. My instinct is to simply pass a JPanel reference to the JPanel that needs to call repaint, but I am unsure how extensible this would be, how tightly coupled these classes would become.
Any advice anybody could give me would be much appreciated. Sorry the question is so long-winded. :)

Hello,
nice to get feedback.
I've been looking at a few resources on this issue from my last post. In my application I have been using the Observer and Observable classes to implement the MVC pattern suggested by T.PD.(...)
Two issues (not fatal, but annoying) with this are:
-Observable is a class, not an interface; since most of my Observers already extend JPanel (or some such), I have had to create inner classes.
-If an Observer is observing multiple Observables, it will have to determine which Observer called its update() method (by using reference equality or class comparison or whatever). Again, a very minor issue, but something to keep in mind.I don't deem those issues are minor. The second one in particular, is rather annoying in terms of maintenance ("Err, remind me, which widget is calling this "update()" method?").
In addition to that, the Observable/Observer are legacy non-generified classes, that incurr a loosely-typed approach (the subject and context arguments to the update(Observable subject, Object context) methods give hardly any info in themselves, and they generally have to be cast to provide app-specific information.
Note that the "notification model" from AWT and Swing widgets is not Observer-Observable, but merely EventListener . Although we can only guess what reasons made them develop a specific notification model, I deem this essentially stems from those reasons.
The contrasting appraoches are discussed in this article from Bill Venners: The Event Generator Idiom (http://www.artima.com/designtechniques/eventgenP.html).
N.B.: this article is from a previous-millenary series of "Design Techniques" articles that I found very useful when I learned OO design (GUI or not).
One last nail against the Observer/Observable model: these are general classes that can be used regardless of the context (GUI/non-GUI code), so this makes it easier to forget about Swing threading rules when using them (essentially: is the update method called in the EDT or not).
If anybody has any information on the performance or efficiency of using Observable/ObserverI would be very surprised if this had any performance impact. If it had, that would mean that you have either:
- a lot of widgets that are listening to one another (and then the Mediator pattern is almost a must to structure such entangled dependencies). And even then I don't think there could be any impact below a few thousands widgets.
- expensive or long-running computation in the update methods. That's unrelated to the notification model itself.
- a lot of non-GUI components that use the Observer/Observable to communicate among themselves - all the more risk then, to have a GUI update() called outside the EDT, see remark above.
(or whether there are inbuilt equivalents for Swing components)See discussion above.
As far as your remark 2 goes (if one observer observes more than one subjects, the update() method contains branching logic) : this also occurs with the Event Delegation model indeed: for example, it is quite common that people complain that their actionPerformed() method becomes unwieldy when the same class listens for several JButtons.
The usual advice for this is, use anonymous listeners, each of which handles the event from only one source (and generally very close in code to the definition of that source), and that simply translates the "generic" event notification method into a specific method call of a Controller or Mediator .
Best regards.
J.
Edited by: jduprez on May 9, 2011 10:10 AM

Best practice for OSB, OER and OSR

Hi,
I would like to know what are the best practices for using OSB, OER and OSR together in a run-time environment for a simple WSDL service.
From how I see it:
1) Create service-definition in OER
2) Create proxy and business service in OSB
3) Use harvester to harvest the proxy and business services in OER
4) Use Exchange Utility to publish the proxy service to OSR
Then the client and discover the proxy service and use OSB for invoking the operations from service.
Kindly correct me where I am wrong.
Some questions:
1) Do we ever publish business service to OSR? Or is it only meant for proxy services?
2) Is synching of OSB and OSR only meant when we are not using OER?
Looking forward...

Hi Anuj,
Thanks for the links, they have been helpful.
I understand now that OSR is only meant to contain only Proxy services. The synch facility is between OSR and OSB so that in case when you are not using OER, you can publish Proxy services to OSR from OSB. What I didn't understand was why there was a option to publish a Proxy service back to OSB and why it ended up as a Business service. From the link you provided, it mentioned that this case is for multi-domain OSBs, where one OSB wants to use the other OSB's service. It is clear now.
Some more questions:
1) In the design-time, in OER no Endpoints are generated for Proxy services. Then how do we publish our design-time services to OSR for testing purposes? What is the correct way of doing this?
Thanks,
Umar

Best practice for simply invoking a web service

Hello,
We have web services deployed and accessible as wsdl documents in the SOA service manager/UDDI product. What is the best practice for simply calling a web service method deployed without regard to whether it is deployed on Tomcat, WebSphere, Oracle, etc.
I'd just like to create a java client to make a web service call and JAXRPC has me confused because you seem to have to have custody of the web service implementation code to call a service. Can someone point me in the right direction?
Thanks,
Sean

Thanks. Here is my wsdl, how would you say this is encoded?
<?xml version="1.0" encoding="UTF-8"?>
<definitions
     name="OracleProcess"
     targetNamespace="http://xmlns.oracle.com/OracleProcess"
     xmlns="http://schemas.xmlsoap.org/wsdl/"
     xmlns:tns="http://xmlns.oracle.com/OracleProcess"
     xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
     xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
     xmlns:client="http://xmlns.oracle.com/OracleProcess"
    >
    <types>
        <schema attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xmlns.oracle.com/OracleProcess"
             xmlns="http://www.w3.org/2001/XMLSchema">
            <element name="OracleProcessProcessRequest">
                <complexType>
                    <sequence>
                        <element name="input" type="string"/>
                        <element name="input2" type="string"/>
                    </sequence>
                </complexType>
            </element>
            <element name="OracleProcessProcessResponse">
                <complexType>
                    <sequence>
                        <element name="result" type="string"/>
                    </sequence>
                </complexType>
            </element>
        </schema>
    </types>
    <message name="OracleProcessRequestMessage">
        <part name="payload" element="tns:OracleProcessProcessRequest"/>
    </message>
    <message name="OracleProcessResponseMessage">
        <part name="payload" element="tns:OracleProcessProcessResponse"/>
    </message>
    <portType name="OracleProcess">
        <operation name="process">
            <input message="tns:OracleProcessRequestMessage"/>
            <output message="tns:OracleProcessResponseMessage"/>
        </operation>
    </portType>
    <binding name="OracleProcessBinding" type="tns:OracleProcess">
        <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
        <operation name="process">
            <soap:operation style="document" soapAction="process"/>
            <input>
                <soap:body use="literal"/>
            </input>
            <output>
                <soap:body use="literal"/>
            </output>
        </operation>
    </binding>
    <service name="OracleProcess">
        <port name="OracleProcessPort" binding="tns:OracleProcessBinding">
            <soap:address location="http://st4s:9700/orabpel/default/OracleProcess/1.0"/>
        </port>
    </service>
<plnk:partnerLinkType name="OracleProcess">
    <plnk:role name="OracleProcessProvider">
      <plnk:portType name="tns:OracleProcess"/>
    </plnk:role>
</plnk:partnerLinkType>
</definitions>

Best Practice for Production IDM setup

Hi, what is the best practice for setting up prodcution IDM:
1. Connect IDM prod to ECC DEV,QA and Prod or
2. Connect IDM prod to ECC prod only and Connect IDM dev to ECC Dev and QA.
Please also specify pros and cons for both options if possible.
Thanks in advance,
Farhan

We run our IDM installation as per your option 2 (Prod and non-prod on separate instances)
We use HCM for the source of truth in production and have a strict policy regarding not allowing non HCM based user accounts. HCM creates the SU01 record and details are downloaded to IDM through the LDAP extract. Access is provision based on Roles attached to the HCM Position in IDM. In Dev/test/uat we create user logins in IDM and push the details out.
Our thinking was that we definitely needed a testing environment for development and patch testing, and it needs to be separate to production. It was also ideal to use this second environment for dev/test/uat since we are in the middle of a major SAP project rollout and are creating hundreds of test and training users with various roles and prefer to keep this out of a production instance.
Lately we also created a sandpit environment since I found that I could not do destructive testing or development in the dev/test/uat instance because we were becoming reliant on this environment being available. Almost a second production instance - since we also set the policy that all changes are made through IDM and no direct SU01 changes are permitted.
Have a close look at your usage requirements before deciding which structure works best for you.

Best practices for customizing the standard OBIA metedata repository (RPD)

Hello
Is there a Best practices document published by oracle or a partner that talks about best practices for customizing OBIA out-of-box RPD. I am specifically looking for guidance around:
1. adding new objects to physical layer or modifying an exisitng table definition to add more columns
2. Building new Logical columns in BMM layer
3. Modifying the exisitng Subject areas.
Thanks

There is a very good presentation by Rittman mead on extending and customizing BI Applications. Refer to this link (http://www.rittmanmead.com/files/OOW2008%20-%20Extending%20and%20Customizing%20the%20BI%20Apps%20Data%20Warehouse.pdf ).
Thanks,
-Amith.

Seeking advice on Best Practices for XML Storage Options - XMLTYPE

Sparc64
11.2.0.2
During OOW12 I tried to attend every xml session I could. There was one where a Mr. Drake was explaining something about not using clob
as an attribute to storing the xml and that "it will break your application."
We're moving forward with storing the industry standard invoice in an xmltype column, but Im not concerned that our table definition is not what was advised:
--i've dummied this down to protect company assets
CREATE TABLE "INVOICE_DOC"
   (     "INVOICE_ID" NUMBER NOT NULL ENABLE,
     "DOC" "SYS"."XMLTYPE" NOT NULL ENABLE,
     "VERSION" VARCHAR2(256) NOT NULL ENABLE,
     "STATUS" VARCHAR2(256),
     "STATE" VARCHAR2(256),
     "USER_ID" VARCHAR2(256),
     "APP_ID" VARCHAR2(256),
     "INSERT_TS" TIMESTAMP (6) WITH LOCAL TIME ZONE,
     "UPDATE_TS" TIMESTAMP (6) WITH LOCAL TIME ZONE,
      CONSTRAINT "FK_####_DOC_INV_ID" FOREIGN KEY ("INVOICE_ID")
             REFERENCES "INVOICE_LO" ("INVOICE_ID") ENABLE
   ) SEGMENT CREATION IMMEDIATE
INITRANS 20
TABLESPACE "####_####_DATA"
       XMLTYPE COLUMN "DOC" STORE AS BASICFILE CLOB (
TABLESPACE "####_####_DATA" XMLTYPE COLUMN "DOC" STORE AS BASICFILE CLOB (
TABLESPACE "####_####_DATA" ENABLE STORAGE IN ROW CHUNK 16384 RETENTION
NOCACHE LOGGING
STORAGE(INITIAL 81920 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
XMLSCHEMA "http://mycompanynamehere.com/xdb/Invoice###.xsd" ELEMENT "Invoice" ID #####"
{code}
What is a best practice for this type of table? Yes, we intend on registering the schema against an xsd.
Any help/advice would be appreciated.
-abe

Hi,
I suggest you read this paper : Oracle XML DB : Choosing the Best XMLType Storage Option for Your Use Case
It is available on the XML DB home page along with other documents you may be interested in.
To sum up, the storage method you need depends on the requirement, i.e. how XML data is accessed.
There was one where a Mr. Drake was explaining something about not using clob as an attribute to storing the xml and that "it will break your application."I think the message Mark Drake wanted to convey is that CLOB storage is now deprecated and shouldn't be used anymore (though still supported for backward compatibility).
The default XMLType storage starting with version 11.2.0.2 is now Binary XML, a posted-parsed binary format that optimizes both storage size and data access (via XQuery), so you should at least use it instead of the BASICFILE CLOB.
Schema-based Binary XML is also available, it adds another layer of "awareness" for Oracle to manage instance documents.
To use this feature, the XML schema must be registered with "options => dbms_xmlschema.REGISTER_BINARYXML".
The other common approach for schema-based XML is Object-Relational storage.
BTW... you may want to post here next time, in the dedicated forum : {forum:id=34}
Mark Drake is one of the regular user, along with Marco Gralike you've probably seen too at OOW.
Edited by: odie_63 on 18 oct. 2012 21:55

Best practice for placing module

Hello
I have an enterprise application project, with :
1) EJB Module
2) Web Module .
I want to add the hibernate jars+classes+data+servlets+utils etc...
Should i create a new Web module for hibernate or should i add it to the existing EJB module which is my business logic ?
What is the best practice for that?
Thanks !

Thanks for the reply, Jiri.
I believe that the answer is 'yes' to both of your questions above. I do have a question about the formatting of the meta tag itself, as my main question is how do I extract the needed information from a particular CDF so that it is displayed in the <head> section located in the page template.
I have a Region Definition for the content section of my page with a 'Title' field, which a contributor can fill in, save, and create a Contributor Data File with their own specified title. Let's also say that my page template, which formats the entire page, looks like this (rough):
<html>
<head>
<title>Web page</title>
</head>
<body>



</body>
</html>
What would my <meta> tag look like for the following:
<meta property="og:title" content="Title of the content section"/>
Let's name our templates/definitions:
Page Template: PT_META
Region Template: RT_META
Region Definition: RD_META
Contributor Data File: CDF_META
In other words, how do I extract the information included in the Contributor Data File (as well as its metadata) for use in the Page Template? Is there some sort of Idoc Script call that can be used?
Thank you so much,
Josh

Best practice for confirmation creation?

Dear Experts,
I would like to have your opinion on best practices for confirmation creation in classic scenario. Whether most organizations prefer to create confirmation in SRM or ECC? One advantage of confirmation creation in SRM is that you can avail different workflow scenario, while ECC MM does not support any workflow or release strategy for confirmation/goods receipt.
Your input on it will be highly appreciated.
Regards,
Ranjan

Hi Ranjan,
As far as best practice for confirmation creation goes , it should be decided by who is the goods recipient , what access the goods recipient have and and what type of material it is , direct or indirect ..
Ideally for most of Indirect procurement where requestor is creating a cart for himself or his department and would be reciving the good/ service himself , he/she should do the confirmation in SRM.
In case of direct material definitely GR need to be done in the ECC.
Thanks
Iftekhar Alam

Automatic Deployment Rule for SCEP Definitions growing too large.

See the deployment package for SCEP definition is now 256MB and growing. How can we make sure it stays small? The ADR creating the package is leaving 26 Definition in there right now.

The method that Kevin suggests above is what is implemented as part of a default deployment template included with SP1. This limits the number of definitions in the update group to the latest eight (I think).
As a supplemental note here, whenever an ADR runs and is configured to use an existing update group, it first wipes that update group.
Jason | http://blog.configmgrftw.com

Best practice for SCEP definition ADR?

Similar Messages

Maybe you are looking for