Re: Vista Logon Script

I cannot possibly deploy Vista until this is fixed either. I've been
really happy with Vista so far, but I just can't believe that this is
even an issue. There should really be a group policy just for drive
mapping.


danshane wrote:
I agree that this "solution" is unwieldy and in fact unacceptable.
Drive mapping via login script is standard practice at hundreds of
organizations, and using Group Policy to do so has always been the
recommended method.

We need a *real* fix for this, not a workaround. I reported this issue
on every build of Vista betas, and still we have no solution. We won't
be upgrading to Vista on our campus until we have a satisfactory means
of performing this simple procedure.

Dan Shane
Network Systems Administrator
Indiana University


taf@xxxxxxxxxxxxxxxx wrote:
There must be a better way. The script works fine when launched
manually after logon. This solution is cumbersome to say the least and
would be a hassle to integrate with XP and 2K machines.


Richard Mueller wrote:
Seems many people report this problem. I found this posted on a Microsoft
Vista help group:
=========
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.
===========
This sounds like a big problem to me. I've never used wsf files myself. More
research needed, but this is crazy.

--
Richard
Microsoft MVP Scripting and ADSI
Hilltop Lab - http://www.rlmueller.net

.

Relevant Pages

  • Re: Writing my 1st VBS "Script Component"
    ... source object is vacated; I always vacate the drived object first. ... In script, though, MS has tried to make it very ... And it's 3.3 product cycles for their Software Assurance racket. ... but it's supported in Vista. ...
    (microsoft.public.scripting.vbscript)
  • Re: CIM_DataFile WQL on Vista
    ... This script finds all specific file ... In vista as an administrator or system, it will not find files on ... Dim WQL, objWMI, colFiles, objFile ...
    (microsoft.public.scripting.vbscript)
  • Re: Vista Datei einlesen
    ... Fehlermeldung kommt keine, im Editor steht nur: ... Content-Type header not found in the script output. ... please use the Run -> Run in Command Prompt menu to run ... Wo soll ich diese in Vista setzen? ...
    (de.comp.lang.perl.misc)
  • Re: Should be trivial, but isnt.
    ... I did what I thought made sense - I had the script insert itself into ... fighting for the file extention (even though I specifically told Vista to ... HKLM or HKCR on a Vista computer, unless you use "Run as Administrator". ... programs fail on Vista. ...
    (microsoft.public.scripting.vbscript)
  • Re: Scripted netwrok drives not appearing
    ... Mapped drives created from an elevated access token will not be visible from ... processes running in limited user token. ... The script launchapp.wsf helps you create mapped drives under limited user ... I'm new to Vista and playing around a bit. ...
    (microsoft.public.windows.vista.general)