It's really the best piece on the subject.. I used it several years ago to implement restricted ABVs at $vbc.
> -----Original Message----- > From: Blunt, James H (Jim) [mailto:[EMAIL PROTECTED]] > Sent: Monday, May 20, 2002 10:06 AM > To: Exchange Discussions > Subject: RE: Address Book Views > > > Thanks Chris...that article is going in my reference binder. > > I had kinda figured out that not only did I need to create an > ABV, but I needed to apply the ABV somehow...and I couldn't > figure out how to do that. I thought maybe I could figure out > how to apply something on just my side, without having to > bother them, but I'll finish reading this article and see > what happens. > > Jim Blunt > > -----Original Message----- > From: Chris Scharff [mailto:[EMAIL PROTECTED]] > Sent: Monday, May 20, 2002 7:41 AM > To: Exchange Discussions > Subject: RE: Address Book Views > > > OK, thanks for the clarification, it saves me from having to > lay out every permutation of ABVs. :) > > In order to achieve this objective, you'll (well, actually > every site in the org who shouldn't see this info) need to > use restricted address book views. You can create the users > in any container you'd like and group them in any manner > you'd like, but in order to keep people from seeing these > entries in the GAL, you'll need to set search restrictions on them. > > There used to be a TechNet article on it, but I can't find > it... > http://www.exchangeadmin.com/Articles/Index.cfm?ArticleID=4844 > might help. > > > -----Original Message----- > > From: Blunt, James H (Jim) [mailto:[EMAIL PROTECTED]] > > Sent: Monday, May 20, 2002 8:58 AM > > To: Exchange Discussions > > Subject: RE: Address Book Views > > > > > > Chris, > > > > Yes...the current users in the organization should be able to > > see each other and actually do see each other, in the GAL. > > The reason for this is to facilitate the communication > > between all the site DOE contractors, for purposes of > > meetings related to environmental cleanup and project statuses. > > > > However, the Custom Recipients that I want to import are the > > names, locations and e-mail addresses of approximately 22,000 > > other employees around the world that work for our parent > > company. We need to have access to this information, in > > order to collaborate with these people on other projects. > > > > It's not confidential data...we don't care if the data is > > replicated over to the other site, we just don't want the > > other site's users to be able to see the list of people in > > that container. > > > > Jim Blunt > > > > -----Original Message----- > > From: Chris Scharff [mailto:[EMAIL PROTECTED]] > > Sent: Friday, May 17, 2002 6:22 PM > > To: Exchange Discussions > > Subject: RE: Address Book Views > > > > > > Disclaimer: I haven't worked with address book views in > > years, I'm tired and I'm cranky. > > > > Let's establish what the goals are here. Do the users from > > each company currently see each other in the GAL? Should they? > > > > I'll answer the rest once I know the answer to the previous > > quesion(s), but the short answer is that unless there are > > some things in place which aren't mentioned the plan below > > does not appear to meet the desired objectives (yet). > > > > -----Original Message----- > > From: Blunt, James H (Jim) > > To: Exchange Discussions > > Sent: 5/17/2002 5:12 PM > > Subject: Address Book Views > > > > I think I know what I'm doing, but I just want to make sure, > > before I do it. I would also like to know what effect this is > > going to have on what my users see. > > > > If I really don't know what I'm doing, please feel free to > > correct my ignorance in whatever fashion you feel necessary > > (flames, links to reading, helpful tips, etc). I am currently > > reading Paul Robichaux's book, "Managing MS Exchange Server", > > Chapter 9, pgs 322-330. > > > > CONFIGURATION: > > -Ex5.5, SP4 / Win2k, SP2 > > -Organization consists of two sites...let's call them A & B. > > -Both sites have a single Recipient container (right now) > > that replicate to the GAL. -The two companies that share this > > organization have nothing to do with each other. They are > > completely separate companies, that due to both being > > government subcontractors on the same site, share the same > > Exchange organization. > > > > SITUATION: > > - I'm going to create a "Corporate" recipient container in > > our site, Site B. > > - In the initial ABV that I create, on the Group By tab, I'm > > going to set the "Group Items by" option to Site, then City. > > - On the Advanced tab, I'm going to uncheck the "Promote > > entries to parent containers" option. > > - I am then going to import the .csv file containing the > > e-mail addresses of all our employees around the world as > > Custom Recipients (approx. 22,500 & 11 mb worth of contacts) > > into the new "Corporate" recipient container I created for Site B. > > > > OUTCOME: > > I'm hoping that this will allow me to: > > 1) Create the new container; > > 2) Import all these contacts into the container; > > 3) Have the container name show up in the other site, but > > they won't be able to see any of the recipients. > > > > Did I get it right? > > > > Jim Blunt > > > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > > _________________________________________________________________ > List posting FAQ: http://www.swinc.com/resource/exch_faq.htm > Archives: http://www.swynk.com/sitesearch/search.asp > To unsubscribe: mailto:[EMAIL PROTECTED] > Exchange List admin: [EMAIL PROTECTED] > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
