[gptalk] Re: Vista in Win2k3 domain - VBS Logon scripts?

  • From: "Darren Mar-Elia" <darren@xxxxxxxxxx>
  • To: <gptalk@xxxxxxxxxxxxx>
  • Date: Mon, 27 Nov 2006 17:15:55 -0800

This is hilarious. They can't possibly think the thousands of orgs that use
logon scripts are going to put up with this? I'm going to bring this up
during our monthly MVP call with the GP product team. There has to be
another way to do this (aside from disabling UAC, of course).


Thanks for tracking this down Michael. Just for curiosity sake, can you post
the scripts referenced below?

 

 

Darren

 

 

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Michael Pietrzak
Sent: Monday, November 27, 2006 5:10 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Vista in Win2k3 domain - VBS Logon scripts?

 

Darren-

 

I just came across this little tidbit in the technet Vista forums. People
seem pretty p.o'd regarding this answer to login scripts in vista. People
seem to be thinking that you now need two scripts to just run one. Any
thoughts on this?

 

Michael

 

 Sorry about the delay. Here's an explanation of what you are seeing and the

official recomendation. 

Explanation for what you are seeing and workaround : 

By default Group policy service executes scripts in an elevated mode. There 
are some scripts like 'Map network drives' that would need to be run in UAP 
mode. In order to launch such scripts in a UAP context from an elevated 
process, you can leverage the Task scheduler API. Here is a sample script: 
Launchapp.wsf 

Usage: cscript launchapp.wsf <AppPath> 


If the user wants to run a GP logon script Script-UAP.wsf and requires it 
to run in UAP context because it is mapping drives for the user then, create

another script Launch-Script-UAP.wsf which will just use the sample script 
above to launch Script-UAP.wsf in UAP mode. Deploy this script as GP logon 
script. 

I'm attaching the LaunchApp sample script too. 

This change will also be communicated via KB, Vista GP document or 
otherwise. 

Let me know if you still have issues. 

Thanks, 
Prashanth 
Vista Remote File Systems. 

 

 

  _____  

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Darren Mar-Elia
Sent: Monday, November 27, 2006 1:06 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Vista in Win2k3 domain - VBS Logon scripts?

Michael-

What happens if you set the logon scripts to run hidden (using policy)?

 

Darren

 

 

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Michael Pietrzak
Sent: Monday, November 27, 2006 1:02 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Vista in Win2k3 domain - VBS Logon scripts?

 

Thanks Darren,

 

I just checked the Minasi boards and couldn't find anything there. I'll keep
googling and trying to see what's going on. I had not yet checked the event
log so perhaps something is in there as well.

 

I should have made my problem more clear. The VBS scripts are logon scripts
that basically map drives. Nothing too fancy.

 

Thanks again! Let's hope there is a solution besides the "will be supported
on Longhorn server group policies".

 

Michael

 

 

  _____  

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Darren Mar-Elia
Sent: Monday, November 27, 2006 12:59 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Vista in Win2k3 domain - VBS Logon scripts?

Michael-

My guess is that this is a UAC issue. I have heard it come up once before
with Vista. Not sure though-I will try to dig some more.

 

 

From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Michael Pietrzak
Sent: Monday, November 27, 2006 12:53 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Vista in Win2k3 domain - VBS Logon scripts?

 

Hello all-

 

I am now running Vista in my windows 2003 domain and one of the first things
I noticed was that my VBS scripts that normally run on XP are no longer
being processed. 

 

Now is the problem stemming from the fact that the script is set in a GPO
and the Vista box can't interpret it or is it a security issue in Vista that
I have to dig through to allow it to run.

 

Thanks guys in advanced for any thoughts.

 

Michael

Other related posts: