Second Post - Logon script error

[Guest]

This is driving me nuts. Now that I have gotten rid of my Win9x clients, I want to invoke the logon script via GPO. I created a simple script (.bat) that maps 4 network drives. I copied the script to the folder of the GPO template \\domain\policies\GUID\User\scripts\logon. The script works but before it runs it gives the following message..

CMD.exe was started with the above path as the curent directory. UNC paths are not supported. Defaulting to Windows directory

What gives? Can anyone help me? Am I missing something simple here or what. Any point in the right direction would be appreciated

Thanks in advance

Gle

 

[Chriss3]

Group Policies are not applied to Pre-Windows2000 Computers. Use the logon
script attribute of the user account instead and place the particular script
in the NETLOGON share.

--
Regards
Christoffer Andersson

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

This is driving me nuts. Now that I have gotten rid of my Win9x clients,

I want to invoke the logon script via GPO. I created a simple script (.bat)
that maps 4 network drives. I copied the script to the folder of the GPO
template \\domain\policies\GUID\User\scripts\logon. The script works but
before it runs it gives the following message...

CMD.exe was started with the above path as the curent directory. UNC

paths are not supported. Defaulting to Windows directory.

What gives? Can anyone help me? Am I missing something simple here or

what. Any point in the right direction would be appreciated.

 

[Herb Martin]

This is driving me nuts. Now that I have gotten rid of my Win9x clients,

I want to invoke the logon script via GPO. I created a simple script (.bat)
that maps 4 network drives. I copied the script to the folder of the GPO
template \\domain\policies\GUID\User\scripts\logon. The script works but
before it runs it gives the following message...

Probably a bad idea -- why not just "Create" the script using the GPEdit
tool,
and paste the contents of the (current pre-built) script into the notepad it
opens;
now you know it will be in the correct location.

CMD.exe was started with the above path as the curent directory. UNC

paths are not supported. Defaulting to Windows directory.

Sounds like you specified the script as a UNC path and you don't want to
do that -- it's a local path on the DC that gets sent to the client which
works
itself out.

What gives? Can anyone help me? Am I missing something simple here or

what. Any point in the right direction would be appreciated.

 

[Guest]

I'm not talking about pre-2000 computers and I don't want to use the user account attribute since that is more work. I want to do this via GPO.

 

[Herb Martin]

My post addressed you (actual) question....

This is driving me nuts. Now that I have gotten rid of my Win9x clients,

I want to invoke the logon script via GPO. I created a simple script (.bat)
that maps 4 network drives. I copied the script to the folder of the GPO
template \\domain\policies\GUID\User\scripts\logon. The script works but
before it runs it gives the following message...

Probably a bad idea -- why not just "Create" the script using the GPEdit
tool,
and paste the contents of the (current pre-built) script into the notepad it
opens;
now you know it will be in the correct location.

CMD.exe was started with the above path as the curent directory. UNC

paths are not supported. Defaulting to Windows directory.

Sounds like you specified the script as a UNC path and you don't want to
do that -- it's a local path on the DC that gets sent to the client which
works
itself out.

What gives? Can anyone help me? Am I missing something simple here or

what. Any point in the right direction would be appreciated.



--
Herb Martin

I'm not talking about pre-2000 computers and I don't want to use the user

account attribute since that is more work. I want to do this via GPO.