We do not have a DEV forest, per se.  We have a TEST Lab in which anything that would affect AD would be tested before it can be put into production.  Our DEV staff does not do any level of programming that would touch AD.  They do not do any level of LDAP, GC lookups, ADO connections to the AD, or Schema changes / looks / updates.
 
Given what our DEV staff does, it would be a huge waste of money for us to put them in their own forest.  If they start to develop AD integrated programs, we would likely reconsider as the risk to potential schema problems is still too high, IMHO.  Obviously, I'm not going to give access to DEV to make changes to schema anyway, but if the program needs to update schema, it's obviously going to need to be tested (in our current 'waterfall' project management model - ineffective and pointless as it is.....) and the test lab is currently where that would happen.
 
If they feel that they require production access to 'eat their own dog food', then we would have to reconsider.  Likely, a DEV forest would be implemented if the requirement changed to a Production-like' system for DEV.
 
Hope this helps.
 

Rick Kingslan  MCSE, MCSA, MCT
Microsoft MVP - Active Directory
Associate Expert
Expert Zone - www.microsoft.com/windowsxp/expertzone
 



From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of StickmanRunner87
Sent: Saturday, October 25, 2003 1:18 PM
To: [EMAIL PROTECTED]
Subject: [ActiveDir] Do you have a development (DEV) forest?

Hello!

BACKGROUND
Recently, our Active Directory Team was asked by executive management to implement a development forest that very much mimics our production forest in many ways.  However, many of us struggle with this request because we're afraid a development forest will incur more work and cost than benefit.   

QUESTIONS
Do you have a development (DEV) forest? 

If yes,

  1. How does DEV's size compare to PROD in terms of users, computers, domain controllers, domains, sites, gpo's?
  2. Do DEV admins support PROD too?
  3. How does DEV's SLA compare to PROD?
  4. How has DEV added-value to your company?  Any stories to share?
  5. How current is DEV compared to PROD?  Identical, one schema version behind, etc.?
  6. How does DEV's change control practices compare to PROD?

If no,

  1. Is there a specific reason why you don't have a DEV forest?
  2. Did you have a DEV forest previously and tear it down?
  3. Are you considering a DEV forest at the present time?

I appreciate any feedback you can share with me.  If you would prefer to discuss in a telephone call, I'm willing to "phone a friend."

Sincerely, 
Stick 


Do you Yahoo!?
The New Yahoo! Shopping - with improved product search

Reply via email to