Norm, I can tell you from my aspect, being at the bottom of the food chain.. Making AD my main source can be painful. Here you get everything working.. and your singing along.. The next morning you wake up and some yo-yo upstairs deleted or waxed all the data in fields that you needed for your tickets is most painful. It took 5 months for them to fix it so the data was not being wiped out every 3 hours. So having the data, and actually Replicating the data that is good and clean into your system has its advantages. Plus you can push back the data that they hosed your on. I have found over my years of computer work, that if it is not all on one server, and you are dependent on multiple applications, you can get yourself wrapped around an Axle that you have invented. In theory yes.. sounds great. But when people are involved.. and people are inherently full of errors and ... well forget it.
Just a thought. On 5/8/07, Kaiser Norm E CIV USAF 96 CS/SCCE <[EMAIL PROTECTED]> wrote:
** Rick: Yeah, don't get me wrong—I'm certainly not criticizing those of us out there who choose not to untangle the mass of spaghetti in ITSM 7 as far a people data goes. In fact, even if you had the time I'd recommend not doing it because it deviates so drastically from the OOTB design and code. I'm questioning BMC's decision to go that way in the first place. ------------------------------ *From:* Action Request System discussion list(ARSList) [mailto: [EMAIL PROTECTED] *On Behalf Of *Rick Cook *Sent:* Tuesday, May 08, 2007 8:52 AM *To:* [email protected] *Subject:* Re: Why Import People into ITSM 7 at All? 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___ __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___
-- Patrick Zandi _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
