Naming conventions (Full Version)

All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager



Message

turbokitty -> Naming conventions (6/12/2008 5:55:45 PM)

Does anyone use a naming scheme that they've found useful for SCCM? 

What I mean is a naming convention for queries, collections, images, packages and advertisements?

Ex. ADV_Microsoft_Office_2003_WXP_Tokyo

I've got one on the go here, but I'm looking for other ideas to help manage this before it gets unwieldy.

Thanks.



wbracken -> RE: Naming conventions (6/13/2008 11:12:53 AM)

We structure everything like so:
Console Root>Vendor>Vendor_AppName>Vendor_AppName_Version_PackageRevision

Example:
Adobe>Adobe_AcrobatReader>Adobe_AcrobatReader_8.1.2_R01
Adobe>Adobe_AcrobatPro>Adobe_AcrobatPro_8.0_R01

etc.

We carry this convention throughout everything.  Packages, Collections, Advertisments and Source Directory structures as well.



turbokitty -> RE: Naming conventions (6/13/2008 3:12:44 PM)

Great.. thanks.   I didn't think of using folders that way actually.  I wish there were folders in the collections view.

Do you have mulitple sites?  That's one part I'm having trouble with.  We have site-specific packages and regional SCCM admins that will have access to certain packages.

I was thinking about doing this:
Tokyo folder > Vendor folder > App Name Folder > Ver Folder > package
Global folder > Vendor folder > App Name Folder > Ver Folder > package
etc

As regional admins will need access to global apps (the majority of apps), it might not prove worthwhile to bother with a site subfolder.



wbracken -> RE: Naming conventions (6/13/2008 9:57:20 PM)

quote:

ORIGINAL: turbokitty

I wish there were folders in the collections view.



We use empty collection like folders to maintain the structure.  Just be sure to remove the check box for "update membership" on the unpopulated ones as to remove any overhead of uneeded collection evaluations.

I currently only have a Single primary site with multiple secondaries.  All of our packages are currently installed by basing the collection memberships of off AD Security Groups.  The only people that actually have to get into the console are the infrastrcutrue team (which is myself and 1 other).  The helpdesk is granted rights to the AD groups to add machines for daily distributions.  If you decide to go that sort of route then you could ACL the OU's as needed.



turbokitty -> RE: Naming conventions (6/15/2008 4:58:45 AM)

Thanks again.. I'll have to try that "empty collection" strategy when I get to work.  I can't get my brain around it without the console in front of me.

I've been researching using AD groups for policy but from what I understand, you'd need to use System Discovery and rerun it quite often.  Then set your collection update schedule to a high frequency as well.  Is this what you're doing?

What kind of delay are you seeing from the time the helpdesk adds the computer account to the group to the time the machine gets the application?  And what refresh interval are you using on the Discovery and collections?

Cheers.




wbracken -> RE: Naming conventions (6/15/2008 5:40:42 PM)

I guess it all depends on what your timelines are around software distirbution.  We do once a day distributions so this method is ideal for us.  We run AD Group Discovery (set to only look to the OU's that contain our SMS Distribution Groups) every 4 hours and set our collections to update once a day at 2:30 AM.  So overnight the machines will install the apps or whenever they next connect to the network.  We are looking at some of the 1E products that will allow us to wake up any machine at night for distirbutions, then shut them all down to save of resources.  (the ever popular "green" initiative)

If for some reason we need to push straight away we can add the machine(s) to the group, force a group discovery, wait 5 minutes then force the collection meberhsip update.  The clients are set to check for policy updates every 60 minutes but this can be forced right away as well using various tool like the console extension tools or one of my favorites for individual client management "SMS Cient Center".



hcortez463 -> RE: Naming conventions (6/17/2008 8:51:55 AM)

wbracken
do you organize your source files the same way?



wbracken -> RE: Naming conventions (6/18/2008 4:06:42 PM)

Yep.  Our source directories mimic the structure in SMS. (Or is it the other way around? [8D])




Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.359375