comparing two public contact folders

someone at one of the offices accidentally dragged and created a copy of a
public contact folder a while back. So now they have two versions of the
folder. is there an easy way to do a comparison of the contents of the two
list of contacts, and identify those that don't match or don't exist between
the two?

also, what's the best way to restrict who can create/move/delete public
folders? I assume it's through a combination of admin rights -vs- directory
rights -vs- client permissions for each public folder?

thanks!
kw

Dave
Mon Dec 01 09:27:58 CST 2003

I'm sure there's a way to do it programatically, but how about opening each
folder in its own window. Switch the views to "phone list," which is a
table view, and just compare them visually in two tiled windows. This
shouldn't be much of a job unless there are thousands of contacts.

A possibly riskier alternative - if one of the folders contains more
contacts than the other, import the smaller folder into the larger, choosing
not to import duplicates. The risk is that if a contact were edited most
recently in the smaller folder, those edits will be lost with this method.

I only set permissions using Outlook - there are issues created by setting
some permissions in Outlook and others in the file system. Our users don't
have delete rights to the shared contacts folder. Our theory is that if
someone makes a mistake in editing data, we'll catch that eventually, but a
deleted contact could go unnoticed until it's too late. On the rare
occasion when we need to delete one (a duplicate, for example), they have to
come to me or the big boss to get something deleted. Our Default is Create,
Read, Edit All, Delete None.


"Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> someone at one of the offices accidentally dragged and created a copy of a
> public contact folder a while back. So now they have two versions of the
> folder. is there an easy way to do a comparison of the contents of the two
> list of contacts, and identify those that don't match or don't exist
between
> the two?
>
> also, what's the best way to restrict who can create/move/delete public
> folders? I assume it's through a combination of admin rights -vs-
directory
> rights -vs- client permissions for each public folder?
>
> thanks!
> kw
>
>
>
>

Kevin
Mon Dec 01 10:23:14 CST 2003

Thanks, Dave - there's about 1,000 names in the contact list, which is why I
would prefer a semi-automatic method.

As to rights with public folders, you have me concerned ... with your
statement "there are issues" when mixing permissions on Outlook and the
server. Granted, I have seen cases where I could not delete or move a public
folder from within Outlook (options would be grayed out), even though I was
the owner. In those instances, I go to ESM and delete or move them.

-kw

"Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:uPhz0%23BuDHA.2360@TK2MSFTNGP09.phx.gbl...
> I'm sure there's a way to do it programatically, but how about opening
each
> folder in its own window. Switch the views to "phone list," which is a
> table view, and just compare them visually in two tiled windows. This
> shouldn't be much of a job unless there are thousands of contacts.
>
> A possibly riskier alternative - if one of the folders contains more
> contacts than the other, import the smaller folder into the larger,
choosing
> not to import duplicates. The risk is that if a contact were edited most
> recently in the smaller folder, those edits will be lost with this method.
>
> I only set permissions using Outlook - there are issues created by setting
> some permissions in Outlook and others in the file system. Our users
don't
> have delete rights to the shared contacts folder. Our theory is that if
> someone makes a mistake in editing data, we'll catch that eventually, but
a
> deleted contact could go unnoticed until it's too late. On the rare
> occasion when we need to delete one (a duplicate, for example), they have
to
> come to me or the big boss to get something deleted. Our Default is
Create,
> Read, Edit All, Delete None.
>
>
> "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> > someone at one of the offices accidentally dragged and created a copy of
a
> > public contact folder a while back. So now they have two versions of the
> > folder. is there an easy way to do a comparison of the contents of the
two
> > list of contacts, and identify those that don't match or don't exist
> between
> > the two?
> >
> > also, what's the best way to restrict who can create/move/delete public
> > folders? I assume it's through a combination of admin rights -vs-
> directory
> > rights -vs- client permissions for each public folder?
> >
> > thanks!
> > kw
> >
> >
> >
> >
>
>

Dave
Mon Dec 01 15:50:40 CST 2003

I don't think there's anything to be concerned about, but I do think there
are several KB articles about problems that can be created when setting
permissions in ESM, Outlook, and Windows Explorer. Actually, I think it's
using Windows Explorer that causes the problem - I believe Outlook and ESM
are interchangeable.

A quick search brought up this one, for example:
http://support.microsoft.com/default.aspx?scid=kb;en-us;270905. Not wanting
to have to troubleshoot this, I just use Outlook or ESM for all permissions.



"Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
news:OL$FtdCuDHA.424@TK2MSFTNGP11.phx.gbl...
> Thanks, Dave - there's about 1,000 names in the contact list, which is why
I
> would prefer a semi-automatic method.
>
> As to rights with public folders, you have me concerned ... with your
> statement "there are issues" when mixing permissions on Outlook and the
> server. Granted, I have seen cases where I could not delete or move a
public
> folder from within Outlook (options would be grayed out), even though I
was
> the owner. In those instances, I go to ESM and delete or move them.
>
> -kw
>
> "Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
> news:uPhz0%23BuDHA.2360@TK2MSFTNGP09.phx.gbl...
> > I'm sure there's a way to do it programatically, but how about opening
> each
> > folder in its own window. Switch the views to "phone list," which is a
> > table view, and just compare them visually in two tiled windows. This
> > shouldn't be much of a job unless there are thousands of contacts.
> >
> > A possibly riskier alternative - if one of the folders contains more
> > contacts than the other, import the smaller folder into the larger,
> choosing
> > not to import duplicates. The risk is that if a contact were edited
most
> > recently in the smaller folder, those edits will be lost with this
method.
> >
> > I only set permissions using Outlook - there are issues created by
setting
> > some permissions in Outlook and others in the file system. Our users
> don't
> > have delete rights to the shared contacts folder. Our theory is that if
> > someone makes a mistake in editing data, we'll catch that eventually,
but
> a
> > deleted contact could go unnoticed until it's too late. On the rare
> > occasion when we need to delete one (a duplicate, for example), they
have
> to
> > come to me or the big boss to get something deleted. Our Default is
> Create,
> > Read, Edit All, Delete None.
> >
> >
> > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> > > someone at one of the offices accidentally dragged and created a copy
of
> a
> > > public contact folder a while back. So now they have two versions of
the
> > > folder. is there an easy way to do a comparison of the contents of the
> two
> > > list of contacts, and identify those that don't match or don't exist
> > between
> > > the two?
> > >
> > > also, what's the best way to restrict who can create/move/delete
public
> > > folders? I assume it's through a combination of admin rights -vs-
> > directory
> > > rights -vs- client permissions for each public folder?
> > >
> > > thanks!
> > > kw
> > >
> > >
> > >
> > >
> >
> >
>
>

Kevin
Mon Dec 01 15:57:26 CST 2003

I always try to do it thru ESM ... so I guess I can stop worrying...
:-)
kw

"Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
news:%23rw3qUFuDHA.3140@TK2MSFTNGP11.phx.gbl...
> I don't think there's anything to be concerned about, but I do think there
> are several KB articles about problems that can be created when setting
> permissions in ESM, Outlook, and Windows Explorer. Actually, I think it's
> using Windows Explorer that causes the problem - I believe Outlook and ESM
> are interchangeable.
>
> A quick search brought up this one, for example:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;270905. Not
wanting
> to have to troubleshoot this, I just use Outlook or ESM for all
permissions.
>
>
>
> "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> news:OL$FtdCuDHA.424@TK2MSFTNGP11.phx.gbl...
> > Thanks, Dave - there's about 1,000 names in the contact list, which is
why
> I
> > would prefer a semi-automatic method.
> >
> > As to rights with public folders, you have me concerned ... with your
> > statement "there are issues" when mixing permissions on Outlook and the
> > server. Granted, I have seen cases where I could not delete or move a
> public
> > folder from within Outlook (options would be grayed out), even though I
> was
> > the owner. In those instances, I go to ESM and delete or move them.
> >
> > -kw
> >
> > "Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
> > news:uPhz0%23BuDHA.2360@TK2MSFTNGP09.phx.gbl...
> > > I'm sure there's a way to do it programatically, but how about opening
> > each
> > > folder in its own window. Switch the views to "phone list," which is
a
> > > table view, and just compare them visually in two tiled windows. This
> > > shouldn't be much of a job unless there are thousands of contacts.
> > >
> > > A possibly riskier alternative - if one of the folders contains more
> > > contacts than the other, import the smaller folder into the larger,
> > choosing
> > > not to import duplicates. The risk is that if a contact were edited
> most
> > > recently in the smaller folder, those edits will be lost with this
> method.
> > >
> > > I only set permissions using Outlook - there are issues created by
> setting
> > > some permissions in Outlook and others in the file system. Our users
> > don't
> > > have delete rights to the shared contacts folder. Our theory is that
if
> > > someone makes a mistake in editing data, we'll catch that eventually,
> but
> > a
> > > deleted contact could go unnoticed until it's too late. On the rare
> > > occasion when we need to delete one (a duplicate, for example), they
> have
> > to
> > > come to me or the big boss to get something deleted. Our Default is
> > Create,
> > > Read, Edit All, Delete None.
> > >
> > >
> > > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > > news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> > > > someone at one of the offices accidentally dragged and created a
copy
> of
> > a
> > > > public contact folder a while back. So now they have two versions of
> the
> > > > folder. is there an easy way to do a comparison of the contents of
the
> > two
> > > > list of contacts, and identify those that don't match or don't exist
> > > between
> > > > the two?
> > > >
> > > > also, what's the best way to restrict who can create/move/delete
> public
> > > > folders? I assume it's through a combination of admin rights -vs-
> > > directory
> > > > rights -vs- client permissions for each public folder?
> > > >
> > > > thanks!
> > > > kw
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Merv
Mon Dec 01 21:55:24 CST 2003

Kevin:

Your post got me to playing around with Outlook 2002 and folders (not public
folders but I think the method should be similar). Here's what I have so
far.

1. Open OL 2002 on a client with permissions to both public folders (called
PF1 and PF2).
2. Create two new personal folders: CopyPF1 and CopyPF2
3. Copy the content of the PF1 and PF2 folders into their respective COPYPF
folders. You'll be working on the local machine with copies instead of the
real PF folder contents (in case this process goes south).
4. Now, create another Personal Folder called FinalPF. (This step may not
be necessary but it makes things a little cleaner).
5. Copy (drag copy) the contents of CopyPF1 into FinalPF.
6. Copy (drag copy) the contents of CopyPF2 into FinalPF. At this point,
OL2002 should respond with a "Duplicate Contact Detected" message and
default to "Update new information from this contact to the existing one".
Select "Yes to All". The contents of the two Public Folders should then
merge.
7. Delete the contents of one of the real public folders on the server (or
create a new public folder on the server) and copy the contents of the
FinalPF folder back to it. (Assign permissions as required if a new PF
folder is created).

This won't give you a comparison of the PFs but it should get you to a final
PF folder that has all the contact info from each PF in it.

Have I missed something here? This seems too easy.

--
Merv Porter [SBS MVP]
===================================
"Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
news:OL$FtdCuDHA.424@TK2MSFTNGP11.phx.gbl...
> Thanks, Dave - there's about 1,000 names in the contact list, which is why
I
> would prefer a semi-automatic method.
>
> As to rights with public folders, you have me concerned ... with your
> statement "there are issues" when mixing permissions on Outlook and the
> server. Granted, I have seen cases where I could not delete or move a
public
> folder from within Outlook (options would be grayed out), even though I
was
> the owner. In those instances, I go to ESM and delete or move them.
>
> -kw
>
> "Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
> news:uPhz0%23BuDHA.2360@TK2MSFTNGP09.phx.gbl...
> > I'm sure there's a way to do it programatically, but how about opening
> each
> > folder in its own window. Switch the views to "phone list," which is a
> > table view, and just compare them visually in two tiled windows. This
> > shouldn't be much of a job unless there are thousands of contacts.
> >
> > A possibly riskier alternative - if one of the folders contains more
> > contacts than the other, import the smaller folder into the larger,
> choosing
> > not to import duplicates. The risk is that if a contact were edited
most
> > recently in the smaller folder, those edits will be lost with this
method.
> >
> > I only set permissions using Outlook - there are issues created by
setting
> > some permissions in Outlook and others in the file system. Our users
> don't
> > have delete rights to the shared contacts folder. Our theory is that if
> > someone makes a mistake in editing data, we'll catch that eventually,
but
> a
> > deleted contact could go unnoticed until it's too late. On the rare
> > occasion when we need to delete one (a duplicate, for example), they
have
> to
> > come to me or the big boss to get something deleted. Our Default is
> Create,
> > Read, Edit All, Delete None.
> >
> >
> > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> > > someone at one of the offices accidentally dragged and created a copy
of
> a
> > > public contact folder a while back. So now they have two versions of
the
> > > folder. is there an easy way to do a comparison of the contents of the
> two
> > > list of contacts, and identify those that don't match or don't exist
> > between
> > > the two?
> > >
> > > also, what's the best way to restrict who can create/move/delete
public
> > > folders? I assume it's through a combination of admin rights -vs-
> > directory
> > > rights -vs- client permissions for each public folder?
> > >
> > > thanks!
> > > kw
> > >
> > >
> > >
> > >
> >
> >
>
>

Kevin
Mon Dec 01 23:59:33 CST 2003

Merv, you asked if your solution was "too easy" - not sure. But my concern
using your scenario is this: when I copy PF2 on top of PF1, and it gives the
option to "update new information" - it will simply force PF2 version of a
specific contact on top of the one in PF1.

Also, copying PF1 onto PF2 would probably create a different FinalPF than
copying PF2 onto PF1 - no?
-kw

"Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
news:ugIMIgIuDHA.3744@TK2MSFTNGP11.phx.gbl...
> Kevin:
>
> Your post got me to playing around with Outlook 2002 and folders (not
public
> folders but I think the method should be similar). Here's what I have so
> far.
>
> 1. Open OL 2002 on a client with permissions to both public folders
(called
> PF1 and PF2).
> 2. Create two new personal folders: CopyPF1 and CopyPF2
> 3. Copy the content of the PF1 and PF2 folders into their respective
COPYPF
> folders. You'll be working on the local machine with copies instead of
the
> real PF folder contents (in case this process goes south).
> 4. Now, create another Personal Folder called FinalPF. (This step may
not
> be necessary but it makes things a little cleaner).
> 5. Copy (drag copy) the contents of CopyPF1 into FinalPF.
> 6. Copy (drag copy) the contents of CopyPF2 into FinalPF. At this point,
> OL2002 should respond with a "Duplicate Contact Detected" message and
> default to "Update new information from this contact to the existing one".
> Select "Yes to All". The contents of the two Public Folders should then
> merge.
> 7. Delete the contents of one of the real public folders on the server
(or
> create a new public folder on the server) and copy the contents of the
> FinalPF folder back to it. (Assign permissions as required if a new PF
> folder is created).
>
> This won't give you a comparison of the PFs but it should get you to a
final
> PF folder that has all the contact info from each PF in it.
>
> Have I missed something here? This seems too easy.
>
> --
> Merv Porter [SBS MVP]
> ===================================
> "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> news:OL$FtdCuDHA.424@TK2MSFTNGP11.phx.gbl...
> > Thanks, Dave - there's about 1,000 names in the contact list, which is
why
> I
> > would prefer a semi-automatic method.
> >
> > As to rights with public folders, you have me concerned ... with your
> > statement "there are issues" when mixing permissions on Outlook and the
> > server. Granted, I have seen cases where I could not delete or move a
> public
> > folder from within Outlook (options would be grayed out), even though I
> was
> > the owner. In those instances, I go to ESM and delete or move them.
> >
> > -kw
> >
> > "Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
> > news:uPhz0%23BuDHA.2360@TK2MSFTNGP09.phx.gbl...
> > > I'm sure there's a way to do it programatically, but how about opening
> > each
> > > folder in its own window. Switch the views to "phone list," which is
a
> > > table view, and just compare them visually in two tiled windows. This
> > > shouldn't be much of a job unless there are thousands of contacts.
> > >
> > > A possibly riskier alternative - if one of the folders contains more
> > > contacts than the other, import the smaller folder into the larger,
> > choosing
> > > not to import duplicates. The risk is that if a contact were edited
> most
> > > recently in the smaller folder, those edits will be lost with this
> method.
> > >
> > > I only set permissions using Outlook - there are issues created by
> setting
> > > some permissions in Outlook and others in the file system. Our users
> > don't
> > > have delete rights to the shared contacts folder. Our theory is that
if
> > > someone makes a mistake in editing data, we'll catch that eventually,
> but
> > a
> > > deleted contact could go unnoticed until it's too late. On the rare
> > > occasion when we need to delete one (a duplicate, for example), they
> have
> > to
> > > come to me or the big boss to get something deleted. Our Default is
> > Create,
> > > Read, Edit All, Delete None.
> > >
> > >
> > > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > > news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> > > > someone at one of the offices accidentally dragged and created a
copy
> of
> > a
> > > > public contact folder a while back. So now they have two versions of
> the
> > > > folder. is there an easy way to do a comparison of the contents of
the
> > two
> > > > list of contacts, and identify those that don't match or don't exist
> > > between
> > > > the two?
> > > >
> > > > also, what's the best way to restrict who can create/move/delete
> public
> > > > folders? I assume it's through a combination of admin rights -vs-
> > > directory
> > > > rights -vs- client permissions for each public folder?
> > > >
> > > > thanks!
> > > > kw
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Merv
Tue Dec 02 05:32:24 CST 2003

Yep, the "Update new information" does force an overwrite. Sorry, thought I
was onto something but it doesn't look promising.

--
Merv Porter [SBS MVP]
===================================

"Kevin Weilbacher" <kweilbac@REMOVE_CAPSgte.net.NO_SPAM> wrote in message
news:OdSy2lJuDHA.2136@TK2MSFTNGP10.phx.gbl...
> Merv, you asked if your solution was "too easy" - not sure. But my concern
> using your scenario is this: when I copy PF2 on top of PF1, and it gives
the
> option to "update new information" - it will simply force PF2 version of a
> specific contact on top of the one in PF1.
>
> Also, copying PF1 onto PF2 would probably create a different FinalPF than
> copying PF2 onto PF1 - no?
> -kw
>
> "Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
> news:ugIMIgIuDHA.3744@TK2MSFTNGP11.phx.gbl...
> > Kevin:
> >
> > Your post got me to playing around with Outlook 2002 and folders (not
> public
> > folders but I think the method should be similar). Here's what I have
so
> > far.
> >
> > 1. Open OL 2002 on a client with permissions to both public folders
> (called
> > PF1 and PF2).
> > 2. Create two new personal folders: CopyPF1 and CopyPF2
> > 3. Copy the content of the PF1 and PF2 folders into their respective
> COPYPF
> > folders. You'll be working on the local machine with copies instead of
> the
> > real PF folder contents (in case this process goes south).
> > 4. Now, create another Personal Folder called FinalPF. (This step may
> not
> > be necessary but it makes things a little cleaner).
> > 5. Copy (drag copy) the contents of CopyPF1 into FinalPF.
> > 6. Copy (drag copy) the contents of CopyPF2 into FinalPF. At this
point,
> > OL2002 should respond with a "Duplicate Contact Detected" message and
> > default to "Update new information from this contact to the existing
one".
> > Select "Yes to All". The contents of the two Public Folders should then
> > merge.
> > 7. Delete the contents of one of the real public folders on the server

> (or
> > create a new public folder on the server) and copy the contents of the
> > FinalPF folder back to it. (Assign permissions as required if a new PF
> > folder is created).
> >
> > This won't give you a comparison of the PFs but it should get you to a
> final
> > PF folder that has all the contact info from each PF in it.
> >
> > Have I missed something here? This seems too easy.
> >
> > --
> > Merv Porter [SBS MVP]
> > ===================================
> > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > news:OL$FtdCuDHA.424@TK2MSFTNGP11.phx.gbl...
> > > Thanks, Dave - there's about 1,000 names in the contact list, which is
> why
> > I
> > > would prefer a semi-automatic method.
> > >
> > > As to rights with public folders, you have me concerned ... with your
> > > statement "there are issues" when mixing permissions on Outlook and
the
> > > server. Granted, I have seen cases where I could not delete or move a
> > public
> > > folder from within Outlook (options would be grayed out), even though
I
> > was
> > > the owner. In those instances, I go to ESM and delete or move them.
> > >
> > > -kw
> > >
> > > "Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
> > > news:uPhz0%23BuDHA.2360@TK2MSFTNGP09.phx.gbl...
> > > > I'm sure there's a way to do it programatically, but how about
opening
> > > each
> > > > folder in its own window. Switch the views to "phone list," which
is
> a
> > > > table view, and just compare them visually in two tiled windows.
This
> > > > shouldn't be much of a job unless there are thousands of contacts.
> > > >
> > > > A possibly riskier alternative - if one of the folders contains more
> > > > contacts than the other, import the smaller folder into the larger,
> > > choosing
> > > > not to import duplicates. The risk is that if a contact were edited
> > most
> > > > recently in the smaller folder, those edits will be lost with this
> > method.
> > > >
> > > > I only set permissions using Outlook - there are issues created by
> > setting
> > > > some permissions in Outlook and others in the file system. Our
users
> > > don't
> > > > have delete rights to the shared contacts folder. Our theory is
that
> if
> > > > someone makes a mistake in editing data, we'll catch that
eventually,
> > but
> > > a
> > > > deleted contact could go unnoticed until it's too late. On the rare
> > > > occasion when we need to delete one (a duplicate, for example), they
> > have
> > > to
> > > > come to me or the big boss to get something deleted. Our Default is
> > > Create,
> > > > Read, Edit All, Delete None.
> > > >
> > > >
> > > > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > > > news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> > > > > someone at one of the offices accidentally dragged and created a
> copy
> > of
> > > a
> > > > > public contact folder a while back. So now they have two versions
of
> > the
> > > > > folder. is there an easy way to do a comparison of the contents of
> the
> > > two
> > > > > list of contacts, and identify those that don't match or don't
exist
> > > > between
> > > > > the two?
> > > > >
> > > > > also, what's the best way to restrict who can create/move/delete
> > public
> > > > > folders? I assume it's through a combination of admin rights -vs-
> > > > directory
> > > > > rights -vs- client permissions for each public folder?
> > > > >
> > > > > thanks!
> > > > > kw
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Kevin
Tue Dec 02 05:36:18 CST 2003

Kevin,

Using Import and Export in Outlook you may be able to achieve what you
require as there is an option which enables you to decide what to do with
any duplicate entries found when importing. This process is very easy to
test. If you:-

1. Create a Public Folder called 'Test'
2. Copy the contents of PF1 into folder Test
3. Export the contents of PF2 to a .PST file using Import and Export
4. Import PF2 from the PST file and set the destination to folder 'Test'.
When asked, select "Do not import duplicate items".

Hope this helps

Kevin

"Kevin Weilbacher" <kweilbac@REMOVE_CAPSgte.net.NO_SPAM> wrote in message
news:OdSy2lJuDHA.2136@TK2MSFTNGP10.phx.gbl...
> Merv, you asked if your solution was "too easy" - not sure. But my concern
> using your scenario is this: when I copy PF2 on top of PF1, and it gives
the
> option to "update new information" - it will simply force PF2 version of a
> specific contact on top of the one in PF1.
>
> Also, copying PF1 onto PF2 would probably create a different FinalPF than
> copying PF2 onto PF1 - no?
> -kw
>
> "Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
> news:ugIMIgIuDHA.3744@TK2MSFTNGP11.phx.gbl...
> > Kevin:
> >
> > Your post got me to playing around with Outlook 2002 and folders (not
> public
> > folders but I think the method should be similar). Here's what I have
so
> > far.
> >
> > 1. Open OL 2002 on a client with permissions to both public folders
> (called
> > PF1 and PF2).
> > 2. Create two new personal folders: CopyPF1 and CopyPF2
> > 3. Copy the content of the PF1 and PF2 folders into their respective
> COPYPF
> > folders. You'll be working on the local machine with copies instead of
> the
> > real PF folder contents (in case this process goes south).
> > 4. Now, create another Personal Folder called FinalPF. (This step may
> not
> > be necessary but it makes things a little cleaner).
> > 5. Copy (drag copy) the contents of CopyPF1 into FinalPF.
> > 6. Copy (drag copy) the contents of CopyPF2 into FinalPF. At this
point,
> > OL2002 should respond with a "Duplicate Contact Detected" message and
> > default to "Update new information from this contact to the existing
one".
> > Select "Yes to All". The contents of the two Public Folders should then
> > merge.
> > 7. Delete the contents of one of the real public folders on the server
> (or
> > create a new public folder on the server) and copy the contents of the
> > FinalPF folder back to it. (Assign permissions as required if a new PF
> > folder is created).
> >
> > This won't give you a comparison of the PFs but it should get you to a
> final
> > PF folder that has all the contact info from each PF in it.
> >
> > Have I missed something here? This seems too easy.
> >
> > --
> > Merv Porter [SBS MVP]
> > ===================================
> > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > news:OL$FtdCuDHA.424@TK2MSFTNGP11.phx.gbl...
> > > Thanks, Dave - there's about 1,000 names in the contact list, which is
> why
> > I
> > > would prefer a semi-automatic method.
> > >
> > > As to rights with public folders, you have me concerned ... with your
> > > statement "there are issues" when mixing permissions on Outlook and
the
> > > server. Granted, I have seen cases where I could not delete or move a
> > public
> > > folder from within Outlook (options would be grayed out), even though
I
> > was
> > > the owner. In those instances, I go to ESM and delete or move them.
> > >
> > > -kw
> > >
> > > "Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
> > > news:uPhz0%23BuDHA.2360@TK2MSFTNGP09.phx.gbl...
> > > > I'm sure there's a way to do it programatically, but how about
opening
> > > each
> > > > folder in its own window. Switch the views to "phone list," which
is
> a
> > > > table view, and just compare them visually in two tiled windows.
This
> > > > shouldn't be much of a job unless there are thousands of contacts.
> > > >
> > > > A possibly riskier alternative - if one of the folders contains more
> > > > contacts than the other, import the smaller folder into the larger,
> > > choosing
> > > > not to import duplicates. The risk is that if a contact were edited
> > most
> > > > recently in the smaller folder, those edits will be lost with this
> > method.
> > > >
> > > > I only set permissions using Outlook - there are issues created by
> > setting
> > > > some permissions in Outlook and others in the file system. Our
users
> > > don't
> > > > have delete rights to the shared contacts folder. Our theory is
that
> if
> > > > someone makes a mistake in editing data, we'll catch that
eventually,
> > but
> > > a
> > > > deleted contact could go unnoticed until it's too late. On the rare
> > > > occasion when we need to delete one (a duplicate, for example), they
> > have
> > > to
> > > > come to me or the big boss to get something deleted. Our Default is
> > > Create,
> > > > Read, Edit All, Delete None.
> > > >
> > > >
> > > > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > > > news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> > > > > someone at one of the offices accidentally dragged and created a
> copy
> > of
> > > a
> > > > > public contact folder a while back. So now they have two versions
of
> > the
> > > > > folder. is there an easy way to do a comparison of the contents of
> the
> > > two
> > > > > list of contacts, and identify those that don't match or don't
exist
> > > > between
> > > > > the two?
> > > > >
> > > > > also, what's the best way to restrict who can create/move/delete
> > public
> > > > > folders? I assume it's through a combination of admin rights -vs-
> > > > directory
> > > > > rights -vs- client permissions for each public folder?
> > > > >
> > > > > thanks!
> > > > > kw
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Dave
Tue Dec 02 12:51:00 CST 2003

If you move the contacts from the public folder to a PST or other folder,
you will lose cross references between the contacts (actually, they'll just
stop working). Also, your create and modified dates will be changed. This
may not matter, but I thought I'd mention it just in case.


"Kevin Weilbacher" <kweilbac@REMOVE_CAPSgte.net.NO_SPAM> wrote in message
news:OdSy2lJuDHA.2136@TK2MSFTNGP10.phx.gbl...
> Merv, you asked if your solution was "too easy" - not sure. But my concern
> using your scenario is this: when I copy PF2 on top of PF1, and it gives
the
> option to "update new information" - it will simply force PF2 version of a
> specific contact on top of the one in PF1.
>
> Also, copying PF1 onto PF2 would probably create a different FinalPF than
> copying PF2 onto PF1 - no?
> -kw
>
> "Merv Porter [SBS-MVP]" <mwport@hotmail.com_no_spam> wrote in message
> news:ugIMIgIuDHA.3744@TK2MSFTNGP11.phx.gbl...
> > Kevin:
> >
> > Your post got me to playing around with Outlook 2002 and folders (not
> public
> > folders but I think the method should be similar). Here's what I have
so
> > far.
> >
> > 1. Open OL 2002 on a client with permissions to both public folders
> (called
> > PF1 and PF2).
> > 2. Create two new personal folders: CopyPF1 and CopyPF2
> > 3. Copy the content of the PF1 and PF2 folders into their respective
> COPYPF
> > folders. You'll be working on the local machine with copies instead of
> the
> > real PF folder contents (in case this process goes south).
> > 4. Now, create another Personal Folder called FinalPF. (This step may
> not
> > be necessary but it makes things a little cleaner).
> > 5. Copy (drag copy) the contents of CopyPF1 into FinalPF.
> > 6. Copy (drag copy) the contents of CopyPF2 into FinalPF. At this
point,
> > OL2002 should respond with a "Duplicate Contact Detected" message and
> > default to "Update new information from this contact to the existing
one".
> > Select "Yes to All". The contents of the two Public Folders should then
> > merge.
> > 7. Delete the contents of one of the real public folders on the server
> (or
> > create a new public folder on the server) and copy the contents of the
> > FinalPF folder back to it. (Assign permissions as required if a new PF
> > folder is created).
> >
> > This won't give you a comparison of the PFs but it should get you to a
> final
> > PF folder that has all the contact info from each PF in it.
> >
> > Have I missed something here? This seems too easy.
> >
> > --
> > Merv Porter [SBS MVP]
> > ===================================
> > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > news:OL$FtdCuDHA.424@TK2MSFTNGP11.phx.gbl...
> > > Thanks, Dave - there's about 1,000 names in the contact list, which is
> why
> > I
> > > would prefer a semi-automatic method.
> > >
> > > As to rights with public folders, you have me concerned ... with your
> > > statement "there are issues" when mixing permissions on Outlook and
the
> > > server. Granted, I have seen cases where I could not delete or move a
> > public
> > > folder from within Outlook (options would be grayed out), even though
I
> > was
> > > the owner. In those instances, I go to ESM and delete or move them.
> > >
> > > -kw
> > >
> > > "Dave Nickason" <gwdibble@NOSPAM.frontiernet.net> wrote in message
> > > news:uPhz0%23BuDHA.2360@TK2MSFTNGP09.phx.gbl...
> > > > I'm sure there's a way to do it programatically, but how about
opening
> > > each
> > > > folder in its own window. Switch the views to "phone list," which
is
> a
> > > > table view, and just compare them visually in two tiled windows.
This
> > > > shouldn't be much of a job unless there are thousands of contacts.
> > > >
> > > > A possibly riskier alternative - if one of the folders contains more
> > > > contacts than the other, import the smaller folder into the larger,
> > > choosing
> > > > not to import duplicates. The risk is that if a contact were edited
> > most
> > > > recently in the smaller folder, those edits will be lost with this
> > method.
> > > >
> > > > I only set permissions using Outlook - there are issues created by
> > setting
> > > > some permissions in Outlook and others in the file system. Our
users
> > > don't
> > > > have delete rights to the shared contacts folder. Our theory is
that
> if
> > > > someone makes a mistake in editing data, we'll catch that
eventually,
> > but
> > > a
> > > > deleted contact could go unnoticed until it's too late. On the rare
> > > > occasion when we need to delete one (a duplicate, for example), they
> > have
> > > to
> > > > come to me or the big boss to get something deleted. Our Default is
> > > Create,
> > > > Read, Edit All, Delete None.
> > > >
> > > >
> > > > "Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
> > > > news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> > > > > someone at one of the offices accidentally dragged and created a
> copy
> > of
> > > a
> > > > > public contact folder a while back. So now they have two versions
of
> > the
> > > > > folder. is there an easy way to do a comparison of the contents of
> the
> > > two
> > > > > list of contacts, and identify those that don't match or don't
exist
> > > > between
> > > > > the two?
> > > > >
> > > > > also, what's the best way to restrict who can create/move/delete
> > public
> > > > > folders? I assume it's through a combination of admin rights -vs-
> > > > directory
> > > > > rights -vs- client permissions for each public folder?
> > > > >
> > > > > thanks!
> > > > > kw
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>

Dave
Tue Dec 02 13:08:00 CST 2003

Kevin, check this out...

http://www.sperrysoftware.com/jcContactDuplicatesEliminator.asp

More stuff listed here...

http://www.slipstick.com/addins/contacts.htm#dupes

DS
---------------
That's right >> SBS ROCKS!

"Kevin Weilbacher" <kweilbac@NO_SPAM_gte.net> wrote in message
news:ehtFMLBuDHA.1576@TK2MSFTNGP11.phx.gbl...
> someone at one of the offices accidentally dragged and created a copy of a
> public contact folder a while back. So now they have two versions of the
> folder. is there an easy way to do a comparison of the contents of the two
> list of contacts, and identify those that don't match or don't exist
between
> the two?
>
> also, what's the best way to restrict who can create/move/delete public
> folders? I assume it's through a combination of admin rights -vs-
directory
> rights -vs- client permissions for each public folder?
>
> thanks!
> kw
>
>
>
>

Dave
Tue Dec 02 13:50:34 CST 2003

And this one may do just what you want, will merge body, categories, and is
free...
Don't know about linking issues...
http://www.teamscope.com/otherpro/freeutil.asp#scrubber

Kevin
Tue Dec 02 23:32:54 CST 2003

DS -thanks a million. I did try searching Slipstick and Google previously,
but did not find anything. Guess I better repeat 1st grade on "how to search
using Google"!

:-)
kw

"Dave Stoecker" <david_stoecker@hotCOFFEEmail.com> wrote in message
news:OJBSO2QuDHA.684@TK2MSFTNGP09.phx.gbl...
> And this one may do just what you want, will merge body, categories, and
is
> free...
> Don't know about linking issues...
> http://www.teamscope.com/otherpro/freeutil.asp#scrubber
>
>