Gpo ошибка 1130 - Решение и исправление самых разных ошибок на TopOshibok.ru

I have a powershell script I am trying to execute and I have placed it inside a GPO under Computer Configuration\Policies\Windows Settings\Scripts\Startup. I receive and Event 1130 Error in the System log on the target PC with the a listing of the network
share the script is contained, \\domain.com\SysVol\domain.com\Policies \{GUID}\Machine. I have made certain that the machine, authenticated users, domain computers all have at least read and execute permissions. Although, when I go to run the script directly
from the path above after logon, I get Access is denied.

Other settings I have tried to get this script to run:

Under System/Group Policy, «Configure Environment preference extension policy processing»= Enabled with «Allow processing across slow network connection» also enabled as well as «Process even if group policy objects have not changed»
is enabled.

«Configure Network Options preference extension policy processing» is «Enabled»

«Configure Logon Script Delay» = Enabled and set to 0

Under System\Logon, «Always wait for the network at computer startup and logon» = Enabled

Under Windows Components/Windows Powershell, «Turn on Script Execution» with Execution Policy set to «Allow local scripts and remote signed scripts».

How do I correct the error so as to allow logon.

Источник

Hello Spiceheads.

Our organization is currently working on rolling out Teams org-wide to replace Skype for Business, and part of that process involves me setting up a Group Policy to install Teams remotely to everyone’s computers. I was originally going to simply deploy the .msi file for the Teams machine-wide installer, but then after some research, I discovered that only installs Teams for users signing into a PC for the first time, which wouldn’t help me at all right now, since I need it installed for everyone on their existing machine. So, I did some more digging and found a handy PowerShell script that runs the regular .exe installer from a specified network share, after checking if Teams is already installed.

So, I placed the .exe installer in a network share that’s open to all authenticated users, added the powershell script as a Logon (user) script to a GPO linked to a test OU (with a test user and computer in it), and then ran logged off the computer and logged back in as the test user. It didn’t install Teams, so I checked Event Viewer and found an error. «Logon script failed», with an Event ID of 1130 and ErrorDescription of «Incorrect Function» I’ve been doing some Googling and found several other posts, including on Spiceworks, that reported similar issues, but none helped me fix my issue. I already double-checked the file permissions on the script and the .exe, so that’s not the problem. I was also able to run the PowerShell script manually and it worked just fine, it’s just won’t run automatically via GP. I did check the Execution Policy for PowerShell, and it says it’s Unrestricted, so that shouldn’t be the issue either.

The script is stored in the default \\<domain>\SysVol\<domain>\Policies\<policy>\User\Scripts\Logon folder, and the .exe is stored in our company share directory. I specified «-SourcePath \\<path>\» for the script in GP; I tried with both the DNS name and the IP address, neither worked.

Script: https://gallery.technet.microsoft.com/scriptcenter/Install-Teams-Desktop-b1ffd424 Opens a new window

Script author’s blog post with instructions:

https://practical365.com/collaboration/teams/deploying-microsoft-teams-desktop-client/ Opens a new window

Script code:

Powershell

<#
.SYNOPSIS
Install-MicrosoftTeams.ps1 - Microsoft Teams Desktop Client Deployment Script

.DESCRIPTION 
This PowerShell script will silently install the Microsoft Teams desktop client.

The Teams client installer can be downloaded from Microsoft:
https://teams.microsoft.com/downloads

.PARAMETER SourcePath
Specifies the source path for the Microsoft Teams installer.


.EXAMPLE
.\Install-MicrosoftTeams.ps1 -Source \\mgmt\Installs\MicrosoftTeams

Installs the Microsoft Teams client from the Installs share on the server MGMT.

.NOTES
Written by: Paul Cunningham

Find me on:

* My Blog:	http://paulcunningham.me
* Twitter:	https://twitter.com/paulcunningham
* LinkedIn:	http://au.linkedin.com/in/cunninghamp
* Github:	https://github.com/cunninghamp

For more Office 365 tips, tricks and news
check out Practical 365.

* Website:	http://practical365.com
* Twitter:	http://twitter.com/practical365

Change Log
V1.00, 15/03/2017 - Initial version
#>

#requires -version 4


[CmdletBinding()]
param (

	[Parameter(Mandatory=$true)]
	[string]$SourcePath

)


function DoInstall {

    $Installer = "$($SourcePath)\Teams_windows_x64.exe"

    If (!(Test-Path $Installer)) {
        throw "Unable to locate Microsoft Teams client installer at $($installer)"
    }

    Write-Host "Attempting to install Microsoft Teams client"

    try {
        $process = Start-Process -FilePath "$Installer" -ArgumentList "-s" -Wait -PassThru -ErrorAction STOP

        if ($process.ExitCode -eq 0)
        {
            Write-Host -ForegroundColor Green "Microsoft Teams setup started without error."
        }
        else
        {
            Write-Warning "Installer exit code  $($process.ExitCode)."
        }
    }
    catch {
        Write-Warning $_.Exception.Message
    }

}

#Check if Office is already installed, as indicated by presence of registry key
$installpath = "$($env:LOCALAPPDATA)\Microsoft\Teams"

if (-not(Test-Path "$($installpath)\Update.exe")) {
    DoInstall
}
else {
    if (Test-Path "$($installpath)\.dead") {
        Write-Host "Teams was previously installed but has been uninstalled. Will reinstall."
        DoInstall
    }
}

It also looks like the script author is a Spicehead, so I tagged him as well (maybe? I think it’s the same person).

Источник

Remove From My Forums

Question
Hello All,

I’m trying to apply the following computer startup script

I’ve set up the following powershell script to disable NetBIOS
```
$adapters=(gwmi win32_networkadapterconfiguration)
Foreach ($adapter in $adapters){
  Write-Host $adapter
  $adapter.settcpipnetbios(2)
  }
```
The script works fine locally. I added a schedule task under the SYSTEM account and it ran with no problems. It only fails in the computer startup via GPO
This is the error I’m receiving via event viewer
```
 EventData 

  SupportInfo1 900986720 
  SupportInfo2 90 
  ErrorCode 267 
  ErrorDescription The directory name is invalid.  
  ScriptType 0 
  GPODisplayName Computer Starup Script - Disable NetBIOS over TCP/IP 
  GPOFileSystemPath \\HERP\SysVol\DERP\Policies\{GUID}\Machine 
  GPOScriptCommandString Disable_NetBIOS_over_TCPIP.ps1 
```
Any help would be appreciated.
extra info. I’m testing this GPO on a windows 8.1 machine. This script works fine on a server 2008, server 2012, and server 2012 R2

Answers

Hi Stephen,

Based on the description, where is the startup script stored? Please double make sure that the computer account in question has enough permissions to access the script.

Regarding Event ID 1130, the following article can be referred to for more information.

Event ID 1130 — Group Policy Scripts Processing

https://technet.microsoft.com/en-us/library/dd392581(v=ws.10).aspx

Best regards,

Frank Shen

Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
- Marked as answer by
  
  Monday, July 13, 2015 2:20 AM

Источник

Hello all,

I am trying to write a Powershell script that I can use in the GPO to install applications/change settings on Admin level. I already have a posh script installing on User level sitting in a user GPO — User config — windows settings — scripts — logon. Here just dropping the script in the browse section(GPO GUID) and everything works fine.

Now using a test script just to create a file via the computer config section of the same GPO will not allow me to run the script. I am testing on a domain computer and the GPO has domain computer security filtering. The computer can also clearly see the GPO in the RSoP query, but the script never runs — no last run time

Event viewer drops ID 1130 errors. I believe the location of the policy cant be reached. Looking at the folder …\policies{GUID}\machine from within the user account obviously tells me the same which makes sense, because only «domain computer» can access this. But the Computer itself should have visibility to apply the logon script, right? and the browser section on the logon page can clearly access this folder too.

Источник

Today troubleshooting SCCM GPO client push issue. Manually execute the batch script from local machine working fine, but it not working from GPO.

First, check RSoP to ensure the GPO is deployed to the machine. ✅

Second, check Event Log and found error below:

Event Log ID : 1130

Source : GroupPolicy

Error : Startup script failed

Error Description : Access is denied

The root cause for this is access denied from the client machine to the Installer shared folder.

After granted permission Authenticated Users – Read & execute to the folder, it work again ! ✅

This post first appeared on Ben’s System Center Experience. Read the original article.

Источник

Question

Answers