In creating a group policy login script. All drives are mapping correctly
exept the ones that are wild cards. I thought they were supposed to use the
next available drive letter but they are not working. Any help would be
appreciated....

Mike,

I am not seeing any reference to this anywhere in the literature so
let's make sure that there is not something else that is stopping this
from working. I am sure you have tried this already, but can you
confirm that you can run the command on the workstation itself outside
of the script? How about the batch file?

I just want to rule anything silly out.

Ryan Hanisco

"Mike" <(E-Mail Removed)> wrote in message
news:BC567BE3-777A-462A-8994-(E-Mail Removed):

> In creating a group policy login script. All drives are mapping correctly
> exept the ones that are wild cards. I thought they were supposed to use the
> next available drive letter but they are not working. Any help would be
> appreciated....

yes it did work in a command prompt...

"Ryan Hanisco" wrote:

> Mike,
>
> I am not seeing any reference to this anywhere in the literature so
> let's make sure that there is not something else that is stopping this
> from working. I am sure you have tried this already, but can you
> confirm that you can run the command on the workstation itself outside
> of the script? How about the batch file?
>
> I just want to rule anything silly out.
>
> Ryan Hanisco
>
> "Mike" <(E-Mail Removed)> wrote in message
> news:BC567BE3-777A-462A-8994-(E-Mail Removed):
>
> > In creating a group policy login script. All drives are mapping correctly
> > exept the ones that are wild cards. I thought they were supposed to use the
> > next available drive letter but they are not working. Any help would be
> > appreciated....
>
>

If it worked there as both the batch and at the console, then it has to
be the GPO handoff that is interfering. I would suggest that you change
the GPO settings to show the script as it is running and put a pause in
at the end of it so you can catch the error message.

Also, make sure that this is a user script rather than a computer
script. I have seen cases where commands don't work well if they try
to run before the UI is fully loaded.

Best regards,

Ryan Hanisco

"Mike" <(E-Mail Removed)> wrote in message
news:29EA8F5F-C60B-4BAA-BF06-(E-Mail Removed):

> yes it did work in a command prompt...
>
> "Ryan Hanisco" wrote:
>
>
> > Mike,
> >
> > I am not seeing any reference to this anywhere in the literature so
> > let's make sure that there is not something else that is stopping this
> > from working. I am sure you have tried this already, but can you
> > confirm that you can run the command on the workstation itself outside
> > of the script? How about the batch file?
> >
> > I just want to rule anything silly out.
> >
> > Ryan Hanisco
> >
> > "Mike" <(E-Mail Removed)> wrote in message
> > news:BC567BE3-777A-462A-8994-(E-Mail Removed):
> >
>
> > > In creating a group policy login script. All drives are mapping correctly
> > > exept the ones that are wild cards. I thought they were supposed to use the
> > > next available drive letter but they are not working. Any help would be
> > > appreciated....
> >
>
> >