View Full Version : Help Desk Password Resets
DavidM
January 6th 04, 09:11 PM
Hello --
We have a bunch of standalone W2K machines with many local accounts. These
accounts cannot reside on our ActiveDirectory domain and therefore must stay
local.
We're shifting responsibility of administrating users for unlocking accounts
or resetting user passwords from our Tech Support department who maintain
the servers, to our Customer Support department who handle customer calls.
What is the best way for me to allow non-Admin level customer support folks
to unlock or reset local accounts on a few standalone servers? The Customer
Support folks typically never access these servers directly for anything.
SO no drive mappings or logins.
Is there third party products that allow this via a web console?
I do not want to make all my customer support folks Admins to each local
box; nor have the extra burdon of creating more local accounts for the 25+
customer support personnel.
For audit purposes, using a single account for all customer support folks is
not an option.
Furthermore, I do not wish to allow customer support to login, as this will
create a new profile folder locally for each user. Thus take more space on
the server needlessly.
Any ideas, help, or comments would be appreciated.
--
http://www.micro-mess.com
http://www.va-mustang.com
If you wish to reply to me personally, please remove
the "underline" from . The is done to avoid SPAM!
David H. Lipman
January 6th 04, 09:12 PM
So do you have to cross-post this to WinXP and NT4 News Groups ?
Dave
pcbutts1
January 6th 04, 09:12 PM
Do You?
--
The best live web video on the internet http://www.seedsv.com/webdemo.htm
Sharpvision simply the best http://www.seedsv.com
"David H. Lipman" > wrote in message
...
> So do you have to cross-post this to WinXP and NT4 News Groups ?
>
> Dave
>
>
pcbutts1
January 6th 04, 09:12 PM
Create a separate group just for customer support with rights to reset
passwords, add that group to the local machines and have the customer
service folks use net use or user manager to reset them. No access to the
server is needed.
--
The best live web video on the internet http://www.seedsv.com/webdemo.htm
Sharpvision simply the best http://www.seedsv.com
"DavidM" > wrote in message
news:c7KHb.63863$VB2.123845@attbi_s51...
> Hello --
>
> We have a bunch of standalone W2K machines with many local accounts.
These
> accounts cannot reside on our ActiveDirectory domain and therefore must
stay
> local.
>
> We're shifting responsibility of administrating users for unlocking
accounts
> or resetting user passwords from our Tech Support department who maintain
> the servers, to our Customer Support department who handle customer calls.
>
> What is the best way for me to allow non-Admin level customer support
folks
> to unlock or reset local accounts on a few standalone servers? The
Customer
> Support folks typically never access these servers directly for anything.
> SO no drive mappings or logins.
>
> Is there third party products that allow this via a web console?
>
> I do not want to make all my customer support folks Admins to each local
> box; nor have the extra burdon of creating more local accounts for the 25+
> customer support personnel.
>
> For audit purposes, using a single account for all customer support folks
is
> not an option.
>
> Furthermore, I do not wish to allow customer support to login, as this
will
> create a new profile folder locally for each user. Thus take more space
on
> the server needlessly.
>
> Any ideas, help, or comments would be appreciated.
>
>
> --
> http://www.micro-mess.com
> http://www.va-mustang.com
> If you wish to reply to me personally, please remove
> the "underline" from . The is done to avoid SPAM!
>
>
"David H. Lipman" > wrote in message
...
> So do you have to cross-post this to WinXP and NT4 News Groups ?
What is your problem?
1. Cross-posting is preferable to multi-posting
(ref. http://www.google.com/search?q=cross-posting+multi-posting)
2. None of the groups crossposted to are NT4-specific. They all have
'windowsnt' in the name, which means the NT family or kernal, of which XP is
a part (NT 5.1).
David H. Lipman
January 6th 04, 09:12 PM
The News Groups that contain 'windowsnt' were named PRIOR to Win2K and WinXP therefore
'windowsnt' is NT4 and you won't find a News Group called NT4.
The question was on Win2K AD and it ONLY needed to be posted in a Win2K News Group. It did
not have to be cross-posted.
Dave
"<>" > wrote in message
...
| "David H. Lipman" > wrote in message
| ...
| > So do you have to cross-post this to WinXP and NT4 News Groups ?
|
| What is your problem?
|
| 1. Cross-posting is preferable to multi-posting
| (ref. http://www.google.com/search?q=cross-posting+multi-posting)
|
| 2. None of the groups crossposted to are NT4-specific. They all have
| 'windowsnt' in the name, which means the NT family or kernal, of which XP is
| a part (NT 5.1).
|
|
Brian Desmond [MVP]
January 6th 04, 09:13 PM
How about offering a solution to the question, guys? While it is a little
much to crosspost to that many groups, it's not hurting anything. The
WindowsNT tree was meant for NT4, as there are win2000 groups and
windows.server groups (general Nt4 - 2003, though mostly 2003).
As for the question, my recommendation would be to construct an application
from which the CS reps would select the probem machine, the problem user,
and then the action to take, and have the application do the actual work.
You'd have to audit in a database or something, as the app will need local
admin rights on all the machines.
--
--
Brian Desmond
Windows Server MVP
Http://www.briandesmond.com
"DavidM" > wrote in message
news:c7KHb.63863$VB2.123845@attbi_s51...
> Hello --
>
> We have a bunch of standalone W2K machines with many local accounts.
These
> accounts cannot reside on our ActiveDirectory domain and therefore must
stay
> local.
>
> We're shifting responsibility of administrating users for unlocking
accounts
> or resetting user passwords from our Tech Support department who maintain
> the servers, to our Customer Support department who handle customer calls.
>
> What is the best way for me to allow non-Admin level customer support
folks
> to unlock or reset local accounts on a few standalone servers? The
Customer
> Support folks typically never access these servers directly for anything.
> SO no drive mappings or logins.
>
> Is there third party products that allow this via a web console?
>
> I do not want to make all my customer support folks Admins to each local
> box; nor have the extra burdon of creating more local accounts for the 25+
> customer support personnel.
>
> For audit purposes, using a single account for all customer support folks
is
> not an option.
>
> Furthermore, I do not wish to allow customer support to login, as this
will
> create a new profile folder locally for each user. Thus take more space
on
> the server needlessly.
>
> Any ideas, help, or comments would be appreciated.
>
>
> --
> http://www.micro-mess.com
> http://www.va-mustang.com
> If you wish to reply to me personally, please remove
> the "underline" from . The is done to avoid SPAM!
>
>
DavidM
January 6th 04, 09:30 PM
Thank you, Brian. Your recommended solution sounded like what I was
thinking would need to be done. I was not sure if there were some third
party applications that could be purchased which would do the same thing.
As far the everyone ranting about me cross-posting, I intentually did it
since I did not know there was a Win2000 group. I looked for W2K and did
not see it. At least my cross post would show replies from any groups. It
was interesting to see how everyone complained about the incorrect group and
offered no solution. They wasted more bandwidth than me and they
cross-posted all their replies. Go figure.
Anyway -- thanks again for your help. It's nice to see the group does have
those who respond professional.
Thanks again.
http://www.micro-mess.com
http://www.va-mustang.com
If you wish to reply to me personally, please remove
the "underline" from . The is done to avoid SPAM!
"Brian Desmond [MVP]" > wrote in message
...
> How about offering a solution to the question, guys? While it is a little
> much to crosspost to that many groups, it's not hurting anything. The
> WindowsNT tree was meant for NT4, as there are win2000 groups and
> windows.server groups (general Nt4 - 2003, though mostly 2003).
>
> As for the question, my recommendation would be to construct an
application
> from which the CS reps would select the probem machine, the problem user,
> and then the action to take, and have the application do the actual work.
> You'd have to audit in a database or something, as the app will need local
> admin rights on all the machines.
>
> --
> --
> Brian Desmond
> Windows Server MVP
>
>
> Http://www.briandesmond.com
>
>
> "DavidM" > wrote in message
> news:c7KHb.63863$VB2.123845@attbi_s51...
> > Hello --
> >
> > We have a bunch of standalone W2K machines with many local accounts.
> These
> > accounts cannot reside on our ActiveDirectory domain and therefore must
> stay
> > local.
> >
> > We're shifting responsibility of administrating users for unlocking
> accounts
> > or resetting user passwords from our Tech Support department who
maintain
> > the servers, to our Customer Support department who handle customer
calls.
> >
> > What is the best way for me to allow non-Admin level customer support
> folks
> > to unlock or reset local accounts on a few standalone servers? The
> Customer
> > Support folks typically never access these servers directly for
anything.
> > SO no drive mappings or logins.
> >
> > Is there third party products that allow this via a web console?
> >
> > I do not want to make all my customer support folks Admins to each local
> > box; nor have the extra burdon of creating more local accounts for the
25+
> > customer support personnel.
> >
> > For audit purposes, using a single account for all customer support
folks
> is
> > not an option.
> >
> > Furthermore, I do not wish to allow customer support to login, as this
> will
> > create a new profile folder locally for each user. Thus take more space
> on
> > the server needlessly.
> >
> > Any ideas, help, or comments would be appreciated.
> >
> >
> > --
> > http://www.micro-mess.com
> > http://www.va-mustang.com
> > If you wish to reply to me personally, please remove
> > the "underline" from . The is done to avoid SPAM!
> >
> >
>
>
Brian Desmond [MVP]
January 6th 04, 09:31 PM
There is probably an application out there that would do this. I don't know
of one. It's something that I could write in an hour or so. Not any rocket
science to it.
--
--
Brian Desmond
Windows Server MVP
Http://www.briandesmond.com
"DavidM" > wrote in message
news:5b6Ib.72814$VB2.143590@attbi_s51...
> Thank you, Brian. Your recommended solution sounded like what I was
> thinking would need to be done. I was not sure if there were some third
> party applications that could be purchased which would do the same thing.
>
> As far the everyone ranting about me cross-posting, I intentually did it
> since I did not know there was a Win2000 group. I looked for W2K and did
> not see it. At least my cross post would show replies from any groups.
It
> was interesting to see how everyone complained about the incorrect group
and
> offered no solution. They wasted more bandwidth than me and they
> cross-posted all their replies. Go figure.
>
> Anyway -- thanks again for your help. It's nice to see the group does
have
> those who respond professional.
>
> Thanks again.
>
> http://www.micro-mess.com
> http://www.va-mustang.com
> If you wish to reply to me personally, please remove
> the "underline" from . The is done to avoid SPAM!
>
> "Brian Desmond [MVP]" > wrote in message
> ...
> > How about offering a solution to the question, guys? While it is a
little
> > much to crosspost to that many groups, it's not hurting anything. The
> > WindowsNT tree was meant for NT4, as there are win2000 groups and
> > windows.server groups (general Nt4 - 2003, though mostly 2003).
> >
> > As for the question, my recommendation would be to construct an
> application
> > from which the CS reps would select the probem machine, the problem
user,
> > and then the action to take, and have the application do the actual
work.
> > You'd have to audit in a database or something, as the app will need
local
> > admin rights on all the machines.
> >
> > --
> > --
> > Brian Desmond
> > Windows Server MVP
> >
> >
> > Http://www.briandesmond.com
> >
> >
> > "DavidM" > wrote in message
> > news:c7KHb.63863$VB2.123845@attbi_s51...
> > > Hello --
> > >
> > > We have a bunch of standalone W2K machines with many local accounts.
> > These
> > > accounts cannot reside on our ActiveDirectory domain and therefore
must
> > stay
> > > local.
> > >
> > > We're shifting responsibility of administrating users for unlocking
> > accounts
> > > or resetting user passwords from our Tech Support department who
> maintain
> > > the servers, to our Customer Support department who handle customer
> calls.
> > >
> > > What is the best way for me to allow non-Admin level customer support
> > folks
> > > to unlock or reset local accounts on a few standalone servers? The
> > Customer
> > > Support folks typically never access these servers directly for
> anything.
> > > SO no drive mappings or logins.
> > >
> > > Is there third party products that allow this via a web console?
> > >
> > > I do not want to make all my customer support folks Admins to each
local
> > > box; nor have the extra burdon of creating more local accounts for the
> 25+
> > > customer support personnel.
> > >
> > > For audit purposes, using a single account for all customer support
> folks
> > is
> > > not an option.
> > >
> > > Furthermore, I do not wish to allow customer support to login, as this
> > will
> > > create a new profile folder locally for each user. Thus take more
space
> > on
> > > the server needlessly.
> > >
> > > Any ideas, help, or comments would be appreciated.
> > >
> > >
> > > --
> > > http://www.micro-mess.com
> > > http://www.va-mustang.com
> > > If you wish to reply to me personally, please remove
> > > the "underline" from . The is done to avoid SPAM!
> > >
> > >
> >
> >
>
>
pcbutts1
January 7th 04, 11:28 PM
Dude on the 2000 server CD in the Support\Tools folder you will find the
setup.exe that will install the windows 2000 resource kit. That kit contains
a nice little program called User Manager. That is all you need. More info
here
http://support.microsoft.com/?kbid=237995
--
The best live web video on the internet http://www.seedsv.com/webdemo.htm
Sharpvision simply the best http://www.seedsv.com
"DavidM" > wrote in message
news:5b6Ib.72814$VB2.143590@attbi_s51...
> Thank you, Brian. Your recommended solution sounded like what I was
> thinking would need to be done. I was not sure if there were some third
> party applications that could be purchased which would do the same thing.
>
> As far the everyone ranting about me cross-posting, I intentually did it
> since I did not know there was a Win2000 group. I looked for W2K and did
> not see it. At least my cross post would show replies from any groups.
It
> was interesting to see how everyone complained about the incorrect group
and
> offered no solution. They wasted more bandwidth than me and they
> cross-posted all their replies. Go figure.
>
> Anyway -- thanks again for your help. It's nice to see the group does
have
> those who respond professional.
>
> Thanks again.
>
> http://www.micro-mess.com
> http://www.va-mustang.com
> If you wish to reply to me personally, please remove
> the "underline" from . The is done to avoid SPAM!
>
> "Brian Desmond [MVP]" > wrote in message
> ...
> > How about offering a solution to the question, guys? While it is a
little
> > much to crosspost to that many groups, it's not hurting anything. The
> > WindowsNT tree was meant for NT4, as there are win2000 groups and
> > windows.server groups (general Nt4 - 2003, though mostly 2003).
> >
> > As for the question, my recommendation would be to construct an
> application
> > from which the CS reps would select the probem machine, the problem
user,
> > and then the action to take, and have the application do the actual
work.
> > You'd have to audit in a database or something, as the app will need
local
> > admin rights on all the machines.
> >
> > --
> > --
> > Brian Desmond
> > Windows Server MVP
> >
> >
> > Http://www.briandesmond.com
> >
> >
> > "DavidM" > wrote in message
> > news:c7KHb.63863$VB2.123845@attbi_s51...
> > > Hello --
> > >
> > > We have a bunch of standalone W2K machines with many local accounts.
> > These
> > > accounts cannot reside on our ActiveDirectory domain and therefore
must
> > stay
> > > local.
> > >
> > > We're shifting responsibility of administrating users for unlocking
> > accounts
> > > or resetting user passwords from our Tech Support department who
> maintain
> > > the servers, to our Customer Support department who handle customer
> calls.
> > >
> > > What is the best way for me to allow non-Admin level customer support
> > folks
> > > to unlock or reset local accounts on a few standalone servers? The
> > Customer
> > > Support folks typically never access these servers directly for
> anything.
> > > SO no drive mappings or logins.
> > >
> > > Is there third party products that allow this via a web console?
> > >
> > > I do not want to make all my customer support folks Admins to each
local
> > > box; nor have the extra burdon of creating more local accounts for the
> 25+
> > > customer support personnel.
> > >
> > > For audit purposes, using a single account for all customer support
> folks
> > is
> > > not an option.
> > >
> > > Furthermore, I do not wish to allow customer support to login, as this
> > will
> > > create a new profile folder locally for each user. Thus take more
space
> > on
> > > the server needlessly.
> > >
> > > Any ideas, help, or comments would be appreciated.
> > >
> > >
> > > --
> > > http://www.micro-mess.com
> > > http://www.va-mustang.com
> > > If you wish to reply to me personally, please remove
> > > the "underline" from . The is done to avoid SPAM!
> > >
> > >
> >
> >
>
>
Brian Desmond [MVP]
January 7th 04, 11:39 PM
NT User Manager, I believe? Using that isn't recommended in an AD, and I
don't know if it will even work if you're not an admin/account op.
--
--
Brian Desmond
Windows Server MVP
Http://www.briandesmond.com
"pcbutts1" > wrote in message
link.net...
> Dude on the 2000 server CD in the Support\Tools folder you will find the
> setup.exe that will install the windows 2000 resource kit. That kit
contains
> a nice little program called User Manager. That is all you need. More info
> here
> http://support.microsoft.com/?kbid=237995
>
>
> --
>
>
> The best live web video on the internet http://www.seedsv.com/webdemo.htm
> Sharpvision simply the best http://www.seedsv.com
>
>
>
> "DavidM" > wrote in message
> news:5b6Ib.72814$VB2.143590@attbi_s51...
> > Thank you, Brian. Your recommended solution sounded like what I was
> > thinking would need to be done. I was not sure if there were some third
> > party applications that could be purchased which would do the same
thing.
> >
> > As far the everyone ranting about me cross-posting, I intentually did it
> > since I did not know there was a Win2000 group. I looked for W2K and
did
> > not see it. At least my cross post would show replies from any groups.
> It
> > was interesting to see how everyone complained about the incorrect group
> and
> > offered no solution. They wasted more bandwidth than me and they
> > cross-posted all their replies. Go figure.
> >
> > Anyway -- thanks again for your help. It's nice to see the group does
> have
> > those who respond professional.
> >
> > Thanks again.
> >
> > http://www.micro-mess.com
> > http://www.va-mustang.com
> > If you wish to reply to me personally, please remove
> > the "underline" from . The is done to avoid SPAM!
> >
> > "Brian Desmond [MVP]" > wrote in message
> > ...
> > > How about offering a solution to the question, guys? While it is a
> little
> > > much to crosspost to that many groups, it's not hurting anything. The
> > > WindowsNT tree was meant for NT4, as there are win2000 groups and
> > > windows.server groups (general Nt4 - 2003, though mostly 2003).
> > >
> > > As for the question, my recommendation would be to construct an
> > application
> > > from which the CS reps would select the probem machine, the problem
> user,
> > > and then the action to take, and have the application do the actual
> work.
> > > You'd have to audit in a database or something, as the app will need
> local
> > > admin rights on all the machines.
> > >
> > > --
> > > --
> > > Brian Desmond
> > > Windows Server MVP
> > >
> > >
> > > Http://www.briandesmond.com
> > >
> > >
> > > "DavidM" > wrote in message
> > > news:c7KHb.63863$VB2.123845@attbi_s51...
> > > > Hello --
> > > >
> > > > We have a bunch of standalone W2K machines with many local accounts.
> > > These
> > > > accounts cannot reside on our ActiveDirectory domain and therefore
> must
> > > stay
> > > > local.
> > > >
> > > > We're shifting responsibility of administrating users for unlocking
> > > accounts
> > > > or resetting user passwords from our Tech Support department who
> > maintain
> > > > the servers, to our Customer Support department who handle customer
> > calls.
> > > >
> > > > What is the best way for me to allow non-Admin level customer
support
> > > folks
> > > > to unlock or reset local accounts on a few standalone servers? The
> > > Customer
> > > > Support folks typically never access these servers directly for
> > anything.
> > > > SO no drive mappings or logins.
> > > >
> > > > Is there third party products that allow this via a web console?
> > > >
> > > > I do not want to make all my customer support folks Admins to each
> local
> > > > box; nor have the extra burdon of creating more local accounts for
the
> > 25+
> > > > customer support personnel.
> > > >
> > > > For audit purposes, using a single account for all customer support
> > folks
> > > is
> > > > not an option.
> > > >
> > > > Furthermore, I do not wish to allow customer support to login, as
this
> > > will
> > > > create a new profile folder locally for each user. Thus take more
> space
> > > on
> > > > the server needlessly.
> > > >
> > > > Any ideas, help, or comments would be appreciated.
> > > >
> > > >
> > > > --
> > > > http://www.micro-mess.com
> > > > http://www.va-mustang.com
> > > > If you wish to reply to me personally, please remove
> > > > the "underline" from . The is done to avoid SPAM!
> > > >
> > > >
> > >
> > >
> >
> >
>
>
pcbutts1
January 7th 04, 11:45 PM
Yes it works, been using it for years on AD. The users (cs reps) must have
the correct permissions. We have it installed locally on our workstations
and we are all part of the Domain Admins group. We use it to reset users
password who log into the domain and in conjunction with Net Use for users
who login locally. We use the version included with win2000 server, the NT
version does not work.
--
The best live web video on the internet http://www.seedsv.com/webdemo.htm
Sharpvision simply the best http://www.seedsv.com
"Brian Desmond [MVP]" > wrote in message
...
> NT User Manager, I believe? Using that isn't recommended in an AD, and I
> don't know if it will even work if you're not an admin/account op.
>
> --
> --
> Brian Desmond
> Windows Server MVP
>
>
> Http://www.briandesmond.com
>
>
> "pcbutts1" > wrote in message
> link.net...
> > Dude on the 2000 server CD in the Support\Tools folder you will find the
> > setup.exe that will install the windows 2000 resource kit. That kit
> contains
> > a nice little program called User Manager. That is all you need. More
info
> > here
> > http://support.microsoft.com/?kbid=237995
> >
> >
> > --
> >
> >
> > The best live web video on the internet
http://www.seedsv.com/webdemo.htm
> > Sharpvision simply the best http://www.seedsv.com
> >
> >
> >
> > "DavidM" > wrote in message
> > news:5b6Ib.72814$VB2.143590@attbi_s51...
> > > Thank you, Brian. Your recommended solution sounded like what I was
> > > thinking would need to be done. I was not sure if there were some
third
> > > party applications that could be purchased which would do the same
> thing.
> > >
> > > As far the everyone ranting about me cross-posting, I intentually did
it
> > > since I did not know there was a Win2000 group. I looked for W2K and
> did
> > > not see it. At least my cross post would show replies from any
groups.
> > It
> > > was interesting to see how everyone complained about the incorrect
group
> > and
> > > offered no solution. They wasted more bandwidth than me and they
> > > cross-posted all their replies. Go figure.
> > >
> > > Anyway -- thanks again for your help. It's nice to see the group does
> > have
> > > those who respond professional.
> > >
> > > Thanks again.
> > >
> > > http://www.micro-mess.com
> > > http://www.va-mustang.com
> > > If you wish to reply to me personally, please remove
> > > the "underline" from . The is done to avoid SPAM!
> > >
> > > "Brian Desmond [MVP]" > wrote in message
> > > ...
> > > > How about offering a solution to the question, guys? While it is a
> > little
> > > > much to crosspost to that many groups, it's not hurting anything.
The
> > > > WindowsNT tree was meant for NT4, as there are win2000 groups and
> > > > windows.server groups (general Nt4 - 2003, though mostly 2003).
> > > >
> > > > As for the question, my recommendation would be to construct an
> > > application
> > > > from which the CS reps would select the probem machine, the problem
> > user,
> > > > and then the action to take, and have the application do the actual
> > work.
> > > > You'd have to audit in a database or something, as the app will need
> > local
> > > > admin rights on all the machines.
> > > >
> > > > --
> > > > --
> > > > Brian Desmond
> > > > Windows Server MVP
> > > >
> > > >
> > > > Http://www.briandesmond.com
> > > >
> > > >
> > > > "DavidM" > wrote in message
> > > > news:c7KHb.63863$VB2.123845@attbi_s51...
> > > > > Hello --
> > > > >
> > > > > We have a bunch of standalone W2K machines with many local
accounts.
> > > > These
> > > > > accounts cannot reside on our ActiveDirectory domain and therefore
> > must
> > > > stay
> > > > > local.
> > > > >
> > > > > We're shifting responsibility of administrating users for
unlocking
> > > > accounts
> > > > > or resetting user passwords from our Tech Support department who
> > > maintain
> > > > > the servers, to our Customer Support department who handle
customer
> > > calls.
> > > > >
> > > > > What is the best way for me to allow non-Admin level customer
> support
> > > > folks
> > > > > to unlock or reset local accounts on a few standalone servers?
The
> > > > Customer
> > > > > Support folks typically never access these servers directly for
> > > anything.
> > > > > SO no drive mappings or logins.
> > > > >
> > > > > Is there third party products that allow this via a web console?
> > > > >
> > > > > I do not want to make all my customer support folks Admins to each
> > local
> > > > > box; nor have the extra burdon of creating more local accounts for
> the
> > > 25+
> > > > > customer support personnel.
> > > > >
> > > > > For audit purposes, using a single account for all customer
support
> > > folks
> > > > is
> > > > > not an option.
> > > > >
> > > > > Furthermore, I do not wish to allow customer support to login, as
> this
> > > > will
> > > > > create a new profile folder locally for each user. Thus take more
> > space
> > > > on
> > > > > the server needlessly.
> > > > >
> > > > > Any ideas, help, or comments would be appreciated.
> > > > >
> > > > >
> > > > > --
> > > > > http://www.micro-mess.com
> > > > > http://www.va-mustang.com
> > > > > If you wish to reply to me personally, please remove
> > > > > the "underline" from . The is done to avoid
SPAM!
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
vBulletin® v3.6.4, Copyright ©2000-2012, Jelsoft Enterprises Ltd.