Ошибка сценарий входа 1130

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 mgmtInstallsMicrosoftTeams

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)MicrosoftTeams"

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
    }
}

Event ID 1130 — Group Policy Scripts Processing

Updated: September 21, 2007

Applies To: Windows Server 2008

During Group Policy processing, the Scripts client-side extension is responsible for launching not only computer startup and shutdown scripts but also user logon and logoff scripts.

Event Details

Resolve
Correct a scripts extension failure

Possible resolutions include:

• Logon and logoff scripts: Ensure the user has the proper file permissions to read and run the script. Users must have the Read and Execute NTFS permission. If the script is located on a network share, the user must also have Read share permissions.
• Startup and shutdown scripts: Ensure the computer account has the proper file permissions to read and run the script. Computers must have the Read and Execute NTFS permission. If the script is located on a network share, the computer must also have Read share permissions.
• Verify the user or computer can start the script from %SystemRoot%system32 folder.

Verify

Group Policy applies during computer startup and user logon. Afterward, Group Policy applies every 90 to 120 minutes. Events appearing in the event log may not reflect the most current state of Group Policy. Therefore, you should always refresh Group Policy to determine if Group Policy is working correctly.

To refresh Group Policy on a specific computer:

1. Open the Start menu. Click All Programs and then click Accessories.
2. Click Command Prompt.
3. In the command prompt window, type gpupdate and then press ENTER.
4. When the gpupdate command completes, open the Event Viewer.

Group Policy is working correctly if the last Group Policy event to appear in the System event log has one of the following event IDs:

• 1500
• 1501
• 1502
• 1503

Related Management Information

Group Policy Scripts Processing

Group Policy Infrastructure