Drive Mapping using IFMember

[Guest]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Hi,

in my firm we use logon scripts to map drives for users when they logon
using the IFMember resource kit utility. We have one file and print BDC which
processes the logon requests of about 70 users. Recently I've added another
entry into the logon script to map a drive - depending on the group they are
in, which should affect about half the users. This seems to work for some
users and not for others. After checking the problem clients it seems some
days they are ok, and others they have to map the drive manually. After
checking the clients when they have problems it seems that they are using the
correct DC to logon, and are in the correct groups and all the other mappings
appear.

The users usually logon anytime between 8 and 10 in the morning so I dont
think the server is being overloaded by logon requests.

Anyone have any ideas, or how to 'debug' why only some machines are affected
on certain days???

Thanks in advance
Tim

 

[Guest]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Tim,
Where is the logon script running IfMember.exe from? You should probably put
a copy of it in each Netlogon share (if you haven't already).
Jim
"Tim Anderson" <Tim Anderson@discussions.microsoft.com> wrote in message
news:E6070C3C-8E6E-4268-BA25-F93996B45DAC@microsoft.com...
> Hi,
>
> in my firm we use logon scripts to map drives for users when they logon
> using the IFMember resource kit utility. We have one file and print BDC
which
> processes the logon requests of about 70 users. Recently I've added
another
> entry into the logon script to map a drive - depending on the group they
are
> in, which should affect about half the users. This seems to work for some
> users and not for others. After checking the problem clients it seems some
> days they are ok, and others they have to map the drive manually. After
> checking the clients when they have problems it seems that they are using
the
> correct DC to logon, and are in the correct groups and all the other
mappings
> appear.
>
> The users usually logon anytime between 8 and 10 in the morning so I dont
> think the server is being overloaded by logon requests.
>
> Anyone have any ideas, or how to 'debug' why only some machines are
affected
> on certain days???
>
> Thanks in advance
> Tim

 

[Guest]

Archived from groups: microsoft.public.windowsnt.misc (More info?)

Jim,

the logon script is located in the netlogon share on the server. I think
we've narrowed it down to the server we are trying to map to being
overwhelmed by requests. We're modifying our back end system to use a UNC
path.

We've managed to redirect the output of the mapping to a logfile which
proved this.
i.e. net use x: \\servername\share >>%LOGFILE%

The logfile variable was set earlier in the logon script, and created a new
logfile for each PC name...

set LOGFILE=\\servername\share\%COMPUTERNAME%.log

There are probably easier ways of doing this but it worked.

Thanks
Tim


"Jim Van Sickle" wrote:

> Tim,
> Where is the logon script running IfMember.exe from? You should probably put
> a copy of it in each Netlogon share (if you haven't already).
> Jim
> "Tim Anderson" <Tim Anderson@discussions.microsoft.com> wrote in message
> news:E6070C3C-8E6E-4268-BA25-F93996B45DAC@microsoft.com...
> > Hi,
> >
> > in my firm we use logon scripts to map drives for users when they logon
> > using the IFMember resource kit utility. We have one file and print BDC
> which
> > processes the logon requests of about 70 users. Recently I've added
> another
> > entry into the logon script to map a drive - depending on the group they
> are
> > in, which should affect about half the users. This seems to work for some
> > users and not for others. After checking the problem clients it seems some
> > days they are ok, and others they have to map the drive manually. After
> > checking the clients when they have problems it seems that they are using
> the
> > correct DC to logon, and are in the correct groups and all the other
> mappings
> > appear.
> >
> > The users usually logon anytime between 8 and 10 in the morning so I dont
> > think the server is being overloaded by logon requests.
> >
> > Anyone have any ideas, or how to 'debug' why only some machines are
> affected
> > on certain days???
> >
> > Thanks in advance
> > Tim
>
>
>