If the directories are separate, I'm not sure that including the environment name provides significant benefit - I think there's pros/cons. E.g. it becomes another thing to change when porting scripts etc., and the domain name or DN can provide the context (if that's required).
Chris: as you point out, it can assist in documentation, but then (arguably) you should do this with all accounts (users, computers etc.) to avoid potential confusion. Or you could use DEV\<accountname> or similar. Cheers Ken From: [email protected] [mailto:[email protected]] On Behalf Of Guyer, Don Sent: Wednesday, 9 October 2013 1:22 AM To: [email protected] Subject: RE: [NTSysADM] OT: naming for service ID's Rather: Svc_widget_ID1-Dev Regards, Don Guyer Catholic Health East - Information Technology Enterprise Directory & Messaging Services 3805 West Chester Pike, Suite 100, Newtown Square, Pa 19073 email: [email protected]<mailto:[email protected]> Office: 610.550.3595 | Mobile: 610.955.6528 | Fax: 610.271.9440 For immediate assistance, please open a Service Desk ticket or call the helpdesk @ 610-492-3839. [Description: Description: Description: Description: InfoService-Logo240] From: Guyer, Don Sent: Tuesday, October 08, 2013 10:09 AM To: [email protected]<mailto:[email protected]> Subject: RE: [NTSysADM] OT: naming for service ID's We would use: Svc_widget_D1-Dev, etc. Regards, Don Guyer Catholic Health East - Information Technology Enterprise Directory & Messaging Services 3805 West Chester Pike, Suite 100, Newtown Square, Pa 19073 email: [email protected]<mailto:[email protected]> Office: 610.550.3595 | Mobile: 610.955.6528 | Fax: 610.271.9440 For immediate assistance, please open a Service Desk ticket or call the helpdesk @ 610-492-3839. [Description: Description: Description: Description: InfoService-Logo240] From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Christopher Bodnar Sent: Tuesday, October 08, 2013 10:00 AM To: [email protected]<mailto:[email protected]> Subject: [NTSysADM] OT: naming for service ID's Just looking for opinions here: Say you have multiple directory repositories across your development platforms (UAT, SIT, Dev, SIT, Prod, etc ...). Each with it's own directory (LDAP, AD, etc....). When you name your service accounts across the environments, do you prefer to note the environment in the name? For example do you do this for each service ID for an application: Widget_ServiceID1 So the name would be the same in each directory for that application? Or would you do something like this? Widget_ServiceID1_Dev Widget_ServiceID1_UAT Widget_ServiceID1_Prod I prefer the latter solution, and a colleague of mine vehemently objects to this. My reasoning is that when referencing the name of the account in e-mail, or discussions, it's self documenting. You immediately know what environment they are talking about. Thoughts? Thanks Christopher Bodnar Enterprise Architect I, Corporate Office of Technology:Enterprise Architecture and Engineering Services Tel 610-807-6459 3900 Burgess Place, Bethlehem, PA 18017 [email protected]<mailto:> [cid:[email protected]] The Guardian Life Insurance Company of America www.guardianlife.com<http://www.guardianlife.com/> ----------------------------------------- This message, and any attachments to it, may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, you are notified that any use, dissemination, distribution, copying, or communication of this message is strictly prohibited. If you have received this message in error, please notify the sender immediately by return e-mail and delete the message and any attachments. Thank you. Confidentiality Notice: This e-mail, including any attachments is the property of Catholic Health East and is intended for the sole use of the intended recipient(s). It may contain information that is privileged and confidential. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please delete this message, and reply to the sender regarding the error in a separate email.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
