|
SMS Tutorials ::
Do's and Don'ts
Do’s
-
Use the comment fields whenever possible for
descriptions. Provide a link to a .txt file
if you run out of space.
-
When creating subcollections, add your SMS
Admins group to the instance rights and make
sure the rights are sufficient (full)
-
Only create items in your departmental
folders
-
Limit collection queries to your root
collection or to a collection that includes
an AD Security Group as part of the
collection query criteria.
-
Take advantage of Public Packages, Public Queries, and
Public Reports
-
Include contact information for all SMS
Admins that are in your SMS-Department-Admins
group in your Root Collection. Follow the
shown format.
-
Check advertisement status of deployed
software using
SMS Report 111.
-
Use the logs to troubleshoot (\\itsnt129\logs
and logs on the client c:\windows\system32\ccm\logs)
-
Call one of us or email us at
its-spa-ecm@uiowa.edu if you
have any questions or problems.
Don’ts
-
Alter the Class Security Rights section on
Security tabs of Collections,
Advertisements, Packages, Queries, Reports,
etc...
-
Create links to collections other than your
own(this shouldn't be possible due to
security restrictions, but we're posting it
anyway)
-
Set collections and packages to update on
extremely frequent intervals (less than
every 3 hours)
-
Create collections that are query based but
have no query criteria. When you do
this, it enters the default SQL query as
'select * from SMS_R_System' and thus
includes all systems that the query is
limited to.
-
Use the “Include members of subcollections”
checkbox in Advertisement properties
-
Use the “As soon as possible” assignment
schedule for Mandatory advertisements
-
Advertise other department’s packages
without their permission
- Hesitate to contact us with any questions or
concerns
...continue to Other
Resources >>>
|
