When
users
run
e/pop,
they
appear
to
replace
each
other
in
the
e/pop
Directory
view.
This
problem
is
most
noticeable
in
the
e/pop
client
when
e/pop
is
deployed
to a
small
group
of
users
and
the
e/pop
server
viewer
shows new
users
connecting
to
the
e/pop
server
but
the
number
of
users
in
the
e/pop
Directory
remain
the
same.
The
main
reason
this
condition
exist
in
e/pop
is
because
of
one
of
the
following.
1.
The
e/pop
administrator
installed
e/pop
on
one
computer,
connects
to
the
e/pop
server
and
copied
the
entire
e/pop client
folder
to
other
computers.
2.
The
e/pop
administrator
uses
a
software
distribution
utility
like
'Ghost',
SMS,
or
WinInstall
and
creates
a
software
distribution
package
and
distributes
the
package
to
all
users
on
the
network.
3.
The
e/pop
administrator
copied
the
e/pop
client
folder
from
a
computer
where
e/pop
was
installed
and
placed
the
copied
folder
on a
network
share.
The
administrator
then
ran a
batch
file
to
copy
the
e/pop
folder
from
the
network
share
to
workstations.
In
all
situations,
the
e/pop client
folder
contained
a
set
of
myidentity.idx
and
myidentity.dat
database
files that
belonged
to
the
original
user
and cause
e/pop
users
to
overlap
each
other
in
the
Directory.
To
better
understand
this
issue,
you
must
first
understand
how
e/pop
automatically
create
accounts
on
the
e/pop
server.
When
e/pop
starts
for
the
first
time,
it
automatically
generates
a
unique
ID
for
the
user.
This
unique
ID
is
referred
to
as a
user's
UID
and
it
is a
32
alpha
numeric
value.
The
UID
acts
just
like
a
unique
index
in a
database.
After
the
UID
is
created,
e/pop
automatically
creates
a
set
of
database
files
called
the
myidentity.idx
and
myidentity.dat
files
and
stores
the
UID
in
it.
In
addition
to
storing
the
UID,
e/pop
also
stores
other
information
for
the
user
like
the
user's ID,
current
IP
address,
and
date
and
time
when
e/pop
started.
Each
time
thereafter
e/pop
edits
the
information
in
the
myidentity
database
like
the
date
and
time
and
other
relevant
information.
The
updated
information
is
then
sent
to
the
e/pop
server
and
the
server
relays
the
updated
status
to
other
e/pop
users.
The
best
way
to
fix
this
issue
is
to
delete
the
myidentity.idx
and
myidentity.dat
files
on
all
computers
or
only
delete
the
myidentity
files
on
computers
that
exhibit
the
problem.
If
you
are
using
Ghost
or
any
software
distribution
utility,
you
must
remove
the
myidentity.*
files
from
the
computer
image
or
software
distribution
package.
Please
refer
to
the
documentation
for your
utility
to
complete
this
process.
Note:
The
batch
command
to
delete
the
myidentity
files
is
the
DOS
'del'
command.
Place
this
command
in
the
batch
file
so
it
deletes
the
myidentity
files
in
the
e/pop
folder.
Example:
-----
start
of
batch
file
-----
del
c: \
"program
files"
\
wiredred
\
epop
\
myide*.*
-----
end
of
batch
file
-----
