Group Policy Drive Mapping

I cannot figure this one... might be simple or missing something.

Running Server 2003 with AD. Joining the domain with XP Pro SP2. I
configured a logon script under the OU containing the user(s) I want to have
the mapped drive using group policy. Its a simple script designed to map one
drive. I've checked all over the place and checked permissions on the script
file itself (added domain users) and I just cant get it to map the drive. I
am not sure where my mistake is, any direction would be appreciated :) I
used the following format.

NET USE z: \\server01\e$ /PERSISTENT:yes (specifics altered)

any thoughts ?

does it work if you manually run the script from your desktop?



"Kelly Armitage" <KellyArmitage@discussions.microsoft.com> wrote in message
news:9E59EFBE-9B0D-4631-A204-BC206CCC7AEE@microsoft.com...
>I cannot figure this one... might be simple or missing something.
>
> Running Server 2003 with AD. Joining the domain with XP Pro SP2. I
> configured a logon script under the OU containing the user(s) I want to
> have
> the mapped drive using group policy. Its a simple script designed to map
> one
> drive. I've checked all over the place and checked permissions on the
> script
> file itself (added domain users) and I just cant get it to map the drive.
> I
> am not sure where my mistake is, any direction would be appreciated :) I
> used the following format.
>
> NET USE z: \\server01\e$ /PERSISTENT:yes (specifics altered)
>
> any thoughts ?

And, Kelly, is the user an admin on the server?
You are trying to map a drive to an administrative share..

Regards,

Austin

"Troy McClure" <n@n.com> wrote in message
news:uxz9TMqDIHA.4712@TK2MSFTNGP04.phx.gbl...
> does it work if you manually run the script from your desktop?
>
>
>
> "Kelly Armitage" <KellyArmitage@discussions.microsoft.com> wrote in
> message news:9E59EFBE-9B0D-4631-A204-BC206CCC7AEE@microsoft.com...
>>I cannot figure this one... might be simple or missing something.
>>
>> Running Server 2003 with AD. Joining the domain with XP Pro SP2. I
>> configured a logon script under the OU containing the user(s) I want to
>> have
>> the mapped drive using group policy. Its a simple script designed to map
>> one
>> drive. I've checked all over the place and checked permissions on the
>> script
>> file itself (added domain users) and I just cant get it to map the drive.
>> I
>> am not sure where my mistake is, any direction would be appreciated :) I
>> used the following format.
>>
>> NET USE z: \\server01\e$ /PERSISTENT:yes (specifics altered)
>>
>> any thoughts ?
>

oh wow yes of course, thanks Austin thats all it was... i created a new share
and changed the script to reflect that... ran gpupdate, logged off and on and
there it was...... previously i had never bothered joining the domain and
had always just mapped the drive FROM Windows XP (righ click my computer ->
map drive) and then specified my domain admin account........... thanks...
it works fine now.... i had a feeling i was missing something simple.....
AWESOME

since u tackled that one so easily, maybe you could answer another one....

on the server (2003 / with AD) i was under the impression i did NOT need a
computer account if the OS was 2000 or newer.... so i deleted the computer
account it had created when i joined the domain, only to realize i could no
longer logon to the domain..... I fixed it easily enough by removing the pc
and re-adding he pc to the domain, but i am wondering, do I have to change my
DC from mixed mode to native mode in order for it NOT to require a computer
account?? Maybe I am not understanding it correctly ... ? The only pc's
joining the domain are XP Pro SP2.... ??? Probably another simple one for
someone more versed in server. (im a newb and do this for a small home
business / webpage / email with 2 accounts)......


If you dont answer... thanks for the last one.... again :D

"Austin Osuide" wrote:

> And, Kelly, is the user an admin on the server?
> You are trying to map a drive to an administrative share..
>
> Regards,
>
> Austin
>
> "Troy McClure" <n@n.com> wrote in message
> news:uxz9TMqDIHA.4712@TK2MSFTNGP04.phx.gbl...
> > does it work if you manually run the script from your desktop?
> >
> >
> >
> > "Kelly Armitage" <KellyArmitage@discussions.microsoft.com> wrote in
> > message news:9E59EFBE-9B0D-4631-A204-BC206CCC7AEE@microsoft.com...
> >>I cannot figure this one... might be simple or missing something.
> >>
> >> Running Server 2003 with AD. Joining the domain with XP Pro SP2. I
> >> configured a logon script under the OU containing the user(s) I want to
> >> have
> >> the mapped drive using group policy. Its a simple script designed to map
> >> one
> >> drive. I've checked all over the place and checked permissions on the
> >> script
> >> file itself (added domain users) and I just cant get it to map the drive.
> >> I
> >> am not sure where my mistake is, any direction would be appreciated :) I
> >> used the following format.
> >>
> >> NET USE z: \\server01\e$ /PERSISTENT:yes (specifics altered)
> >>
> >> any thoughts ?
> >
>
>

Howdie!

Kelly Armitage schrieb:
> oh wow yes of course, thanks Austin thats all it was... i created a new share
> and changed the script to reflect that... ran gpupdate, logged off and on and
> there it was...... previously i had never bothered joining the domain and
> had always just mapped the drive FROM Windows XP (righ click my computer ->
> map drive) and then specified my domain admin account........... thanks...
> it works fine now.... i had a feeling i was missing something simple.....
> AWESOME

In order to log on to the domain, your computers always have to be
joined to the domain. And they always need a computer account in Active
Directory. There is no functional level which could render the computer
accounts useless. If there was no account for the computers, how would
AD know that it's a already domain-joined machine you're attempting to
log in? The computers create a secure channel before communicating with
Domain Controllers and also have a "password" which changes from time to
time. They also need to be sync'ed with the DC's time in order to make
Kerberos' authentication process work. For short - there are many
reasons why there just _needs_ to be a machine account in AD - no matter
what happens.

Remember, you can also create Group Policies linked to OUs where machine
accounts are present - for example Windows Firewall settings.

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.