/build/static/layout/Breadcrumb_cap_w.png
11/30/2018 222 views

Deploying a Windows 10 scripted install, I am able to run our scripted install that points to a network share.  The batch file we're using to install the software maps the drive to J: and then starts the install process with 'start /wait <command>'.  On the 1803 ISO it works fine and never prompts to run the software installer.  When I change the ISO in the scripted install to the 1809 ISO (the latest one from MS, re-released at the end of November 2018 and the first release in October) it stops and prompts us to 'Run' the software.  Essentially, it appears that UAC does not get turned off on the 1809 ISO, but does on the 1803 ISO.  Has anyone had a similar issue with 1809?  It appears to work on local packages, but not on software that is installing from a network drive. Thanks in advance.

4 Comments   [ + ] Show comments

Comments

  • Please clarify if this is a Scripted Install (KACE Systems Deployment Appliance)

    OR

    If this is a Managed Install (KACE Systems Management Appliance).

    If that is a post installation task (KACE SDA), then you could should be able to see if the UAC task succeeded or not. Make sure you are NOT joined to a domain when running that task since GPO policies will enforce changes and permissions, disrupting the KACE SDA engine.
  • This is a post installation task from the KACE Systems Deployment Appliance. According to the progress log, the "Capture and Disable UAC" task was successful.
    • then it is disabled, 99% guaranteed, You can save this as .VBS file, and create a new Windows Script post install task , this task will show a Message Box with the UAC value 1 or 0. You can run this task before running yours...


      dim bExists
      ssig="Unable to open registry key"

      set wshShell= Wscript.CreateObject("WScript.Shell")
      strKey = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA"
      on error resume next
      present = WshShell.RegRead(strKey)
      if err.number<>0 then
      if right(strKey,1)="\" then 'strKey is a registry key
      if instr(1,err.description,ssig,1)<>0 then
      bExists=true
      else
      bExists=false
      end if
      else 'strKey is a registry valuename
      bExists=false
      end if
      err.clear
      else
      bExists=true
      end if
      on error goto 0
      if bExists=vbFalse then
      wscript.echo strKey & " does not exist."
      else
      wscript.echo strKey & " exists."
      MsgBox "UAC Value is: " & present, 30, "1 is ON, 0 is OFF"


      end if
      • After running the .VBS file, it returns "EnableLUA exists".
  • Made one change, try again, but if you click OK, it should show if UAC is 1 or 0, EnableLUA is the key that controls UAC:

    dim bExists
    ssig="Unable to open registry key"

    set wshShell= Wscript.CreateObject("WScript.Shell")
    strKey = "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\EnableLUA"
    on error resume next
    present = WshShell.RegRead(strKey)
    if err.number<>0 then
    if right(strKey,1)="\" then 'strKey is a registry key
    if instr(1,err.description,ssig,1)<>0 then
    bExists=true
    else
    bExists=false
    end if
    else 'strKey is a registry valuename
    bExists=false
    end if
    err.clear
    else
    bExists=true
    end if
    on error goto 0
    if bExists=vbFalse then
    wscript.echo strKey & " does not exist."
    else

    MsgBox "UAC Value is: " & present, 30, "1 is ON, 0 is OFF"


    end if
    • UAC Value is: 0
      • then UAC is OFF, maybe this is a permissions issue, better use your local drive or build an application post install task in the Library to install the software
    • The post install task I am using is already an application post install task. It runs a .bat file that maps the drive and then installs AutoCAD from that drive.
  • Maybe have your task copy the installer locally first, then run the installer from the local drive?
    • I could do that, but it's AutoCAD and is about 35GB and would take FOREVER to copy, and then install.... Plus, it works fine installing from the network drive if I use 1803 instead of 1809???
      • Yeah, didn't realize it was a large copy.
      • Probably an issue with mapped drives\paths with the actual 1809 build, see:

        https://www.reddit.com/r/sysadmin/comments/9wscz1/mapped_network_drives_dont_work_in_windows_10/

        and

        https://support.microsoft.com/en-us/help/4471218/mapped-network-drive-may-fail-to-reconnect-in-windows-10-version-1809

        and

        https://community.spiceworks.com/topic/2175391-1809-is-back-with-mapped-network-drives-bugs
      • That was what I was thinking but wanted to see if anyone else had run into this issue. Thank you all for your help!!
    • No problem. Thank you for your suggestion!

All Answers

1

Channeler is probably right that it is a problem simply with 1809 and how it handles (or mishandles) mapped drives.  It appears that UAC indeed does get turned off, and local installs work without fail, so this problem only seems to exist on the post install tasks that map a network drive.

Answered 11/30/2018 by: indyram44
White Belt