Amazon has released a fix for the instances running Windows Server 2012 R2 that prevent the loss of network connections
this morning, got notification support AWS.
The notice States that the function "Plug and Play Cleanup" from Windows Server 2012 R2, relying on inactive system devices every 30 days, determines the network card EC2 (the only way to access the instance), and as inactive. As a result, the device is removed from the system and the next restart access instance will be lost. If the instance is not lost, to make sure that the instance is not affected by this problem and to prevent disabling of network interfaces using a special edition of a script that can be downloaded here or page describing the problem official website.
The archive is the script itself and the instructions for use. If in short, the instance administrator must run the command:
Article based on information from habrahabr.ru
The notice States that the function "Plug and Play Cleanup" from Windows Server 2012 R2, relying on inactive system devices every 30 days, determines the network card EC2 (the only way to access the instance), and as inactive. As a result, the device is removed from the system and the next restart access instance will be lost. If the instance is not lost, to make sure that the instance is not affected by this problem and to prevent disabling of network interfaces using a special edition of a script that can be downloaded here or page describing the problem official website.
user manual
The archive is the script itself and the instructions for use. If in short, the instance administrator must run the command:
powershell -noprofile -executionpolicy unrestricted -file \RemediateDriverIssue.ps1
If the instance is enabled PSRemoting script can also be executed remotely, however, you need to either turn off the logging (see below), or manually specify the path for log files.
The documentation also shows an example of how to run a script on a series of instances (as-is, as an example):
$creds = (Get-Credential)
$servers = import-csv c:\serverlist.csv
Foreach($server in $servers)
{
echo d | xcopy /S c:\temp \\$server\c$\RemediateDriverIssue
$session = new-pssession -computername $server -credential $creds
invoke-command -session $session -scriptblock {powershell -noprofile -executionpolicy unrestricted -file C:\RemediateDriverIssue.ps1}
}
Available parameters:
the
the - -disableAutoRepair - Boolean, allows you to disable the fix in the automatic mode
the - -force - Boolean, allows you to record keys in the registry even if the script detects that it is not necessary. Default is false.
the - -logPath - a String that specifies the path to write logs: c:\logs\RemediateDriverIssue.log
the - -loggingEnabled - Boolean enables or disables logging. Defaults to true.
Verification script
The output in the shell will display the result of the script.
An example of such output:
the
C:\Users\Administrator>powershell -noprofile -executionpolicy unrestricted -file
RemediateDriverIssue.ps1
20140904_0843:07+00 INFO : scheduled task Disabling Plug and Play Cleanup.
20140904_0843:08+00 INFO : We have disabled the Plug and Play Cleanup scheduled task, please do not re-enable this scheduled task.
20140904_0843:09+00 INFO : This machine was found to be in a non-impacted state.
The same information is duplicated in the log file. In my case the instance was affected, but the network card still has not been removed.
There is a possibility that are affected by this issue and a VPS running Windows Server 2012 R2 and other providers, so I recommend to check for tasks "Plug and Play Cleanup" in task scheduler to disable it if it is there and make sure the network device has not been disabled.
Комментарии
Отправить комментарий