I see what you're saying, Norm, and in a theoretical sense, I agree. However, ITSM 7 is both very complicated and new enough that knowing what existing workflow to untangle to draw the data directly from AD would take more time than most of us have. So in the absence of a viable option of having two data sources, I will settle for the second best outcome - that of not having to maintain two duplicate data sources. The AD data that is actually useful will be maintained only there, and copied to Remedy. The rest, which is mainly better off in Remedy anyway (i.e. Group permissions, etc.) will be maintained in Remedy. Rick _____
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CS/SCCE Sent: Tuesday, May 08, 2007 5:54 AM To: [email protected] Subject: Why Import People into ITSM 7 at All? ** All: Inspired by the recent thread concerning the best way to import people into ITSM 7, I wanted to pose the slightly rhetorical question, "Why import people at all?" I'm not certain I agree with the methodology of duplicating data from one existing data source into another. If the Active Directory is an organization's authoritative source of user data, why import it into a separate database? Why not just do a direct pull from the AD on-the-fly? We don't use ITSM here (yet), but we don't import people data-we just pull AD data on-the-fly and it works like a champ. Thoughts? Norm __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
