Hello, I would like to known if is possible to hook up AMT on remote computers. They are already installed on users's depts and it would take a while to go at one by one doing the configuration manually. Is it possible do that with any agent installed on the computers? I meaning, using a gui software with default password of AMT for example? or a command line?

Thanks so munch.

I recently created a script in hopes of enabling and configuring Intel AMT on all of our machines spanning several remote branches. They already have the Intel Management and Security Client installed, and it's not enabled by default - it's how they came from Dell. My plan was to copy the script to the branch server and it would use psexec to run the script on each specified workstation. In testing the script, I can open the Management and Security Client and verify that the settings appear to be correct, but if I restart and enter the MEBx interface from the bios, it hasn't applied anything - it's still disabled, and hasn't applied the new password or anything from the xml profile that was generated and specified in the script - the client doesn't seem to pass the info to the BIOS level. Do I need to use the Intel® vPro Technology Activator Utility, or is there something else I'm missing?

@echo off
REM This script is intended to deploy a default profile for Intel AMT settings to all AMT-enabled devices on the network
REM This script is intended to be run from the server in the store and target the workstations in the same store
REM Place PsExec.exe (SysInternals), ACU.dll (Intel SCS), ACUConfig.exe (Intel SCS), IntelAMTDefaultProfile.xml, and this script on the store server in C:\Scripts\AMT_Temp prior to running the script
REM The target machine must be configured for a static ip in order for this script to work
echo --------------------Intel AMT Settings Deployment Script v1.0--------------------
echo --------------------------------Last updated: 01/06/2014--------------------------------
ECHO.
:Menu
echo Let's deploy the Intel AMT settings to a remote computer..
echo Enter the IP address or hostname of the store SERVER (this computer) and press ENTER:
SET /P SERVER_ID=
echo Enter the name of a local administrator account on the WORKSTATION that you know the password for.
SET /P ADMIN_USER=
echo Enter the password of the user you chose and press Enter:
SET /P ACCT_PASSWD=
setlocal
echo Enter the IP address or hostname of the WORKSTATION and press ENTER:
SET /P REMOTE_ID=
IF exist "\\%REMOTE_ID%\C$\Program Files (x86)\Intel\Intel(R) Management Engine Components" goto AMTPresent
:AMTPresent
xcopy /f /i \\%SERVER_ID%\C$\Scripts\AMT_Temp \\%REMOTE_ID%\C$\Scripts\AMT_Temp
PsExec.exe \\%REMOTE_ID% /u %ADMIN_USER% /p "%ACCT_PASSWD%""C:\Scripts\AMT_Temp\ACUConfig.exe" /Output File C:\intelamtinstalllog.txt ConfigAMT C:\Scripts\AMT_Temp\IntelAMTDefaultProfile.xml /DecryptionPassword "insertdecryptionpasswordhere" /AbortOnFailure /AdminPassword "admin"
PsExec.exe \\%REMOTE_ID% /u %ADMIN_USER% /p "%ACCT_PASSWD%" rmdir \\%REMOTE_ID%\C$\Scripts\AMT_Temp
echo Done with this machine..
echo Rebooting the machine before moving on..
runas /netonly /user:%REMOTE_ID%\%ADMIN_USER% "shutdown /r /m \\%REMOTE_ID% /t 60 /c \"A computer reboot has been initiated by the IT Department (%USERNAME%) and will take place in 60 seconds. Please save any changes before the reboot.\""
goto Return
IF not exist "\\%REMOTE_ID%\C$\Program Files (x86)\Intel\Intel(R) Management Engine Components" goto AMTNotPresent
:AMTNotPresent
echo This system isn't AMT-enabled. Move on to the next machine on the list..
goto Return
:Return
endlocal
pause
cls
goto Menu

Abstract

Intel sta introducendo il primo processore di 5ª generazione (dal nome in codice Broadwell) con il lancio di tre SKU nella famiglia di processori Intel® Core™ M. Il presente articolo, indirizzato agli sviluppatori, fornisce una visione approfondita del processore SOC multi-core a 64 bit e offre una panoramica delle tecnologie Intel® disponibili, inclusa Grafica Intel® HD 5300.

Caratteristiche principali del processori Intel Core M

La famiglia di processori Intel® Core™ M offre prestazioni migliori in un package più piccolo che richiede un consumo energetico e un sistema di raffreddamento ridotti (ideale per i design sottili e privi di ventola) con una maggiore durata della batteria e include:

• Grafica Intel HD 5300 e Intel® Wireless Display 5.0
• Intel Wireless-AC 7265 e supporto docking wireless (2015) con WiGig
• Tecnologia Intel® Smart Sound
• Tecnologia Intel® Platform Protection e altri sistemi di sicurezza

Riduzione delle dimensioni + Miglioramenti delle prestazioni = Riduzione del consumo energetico e del sistema di raffreddamento

Il processore Intel Core M è il primo ad essere realizzato con la tecnologia a 14 nm. La dimensione del chip è stata ridotta di oltre il 30%, anche se il numero di transistori è aumentato di oltre 300 milioni.

Il processore Intel Core M dispone di un contenitore fisico a consumo energetico ridotto, che produce meno calore. I tre SKU rilasciati nel quarto trimestre del 2014 sono realizzati per funzionare con soli 4,5 watt, che vuol dire che possono funzionare senza ventola!
Questi SKU forniscono ottime prestazioni soprattutto sui fattori di forma ultrasottili (inferiori a 9 mm), inclusi tablet e dispositivi 2 in 1.

Figure 1: Small Low Power Intel Core M Processor Comparisons

Il grafico sul lato sinistro della Figura 1 mostra la diminuzione della potenza dissipata da 18 W  nel 2010 a 4,5 W con il processore  Intel Core M. È una riduzione di 4 voltein 4 anni e una riduzione del 60% dal 2013 Sul lato destro della Figura 1, la comparazione mostra le dimensioni del processore di 4ª generazione Intel® Core™ rispetto al nuovo processore Intel Core M. E nella riduzione del pacchetto del 50%, Intel ha raggiunto una riduzione del 25% nell'area dei componenti.

Più piccolo in tutte le dimensioni del processore Intel Core di 4ª generazione,  il processore Intel Core M fornisce una CPU composta da due core con una cache da 4 MB. Dotato di tecnologia Intel® Hyper-Threading, consente di eseguire quattro thread contemporaneamente. Con tecnologia Intel® TurboBoost 2.0, i processori con frequenza dei core da 0,8 GHz possono raggiungere 2,0 GHz, mentre con frequenza dei core da 1,1, il processore Intel Core M 5Y70 può raggiungere 2,6 GHz.

 

Grazie a 1,3 miliardi di transistori che forniscono CPU, grafica, controller di memoria, audio e connettività in un unico package, non ci sarà alcuna perdita di prestazioni. Di fatto, i test di comparazione con la generazione precedente di processori Intel® Core™ i5-4320Y hanno mostrato miglioramenti significativi delle prestazioni (vedi Figura 3).

Tecnologie energetiche

In questo documento ci sono molte tecnologie Intel utilizzate per mantenere il consumo di energia al minimo. La tecnologia Intel® Turbo Boost 2.0 monitora il consumo energetico che calcola la potenza dei core di processore e grafica e regola l'energia in modo che l'energia e le prestazioni migliorate vengano impiegate dove è necessario. La tecnologia Enhanced Intel SpeedStep® con stati C C0,1,1E, 3 e da 6 a 10 assicura uno stato di inattività a bassissimo consumo energetico. Quando è richiesta maggiore energia, il processore aumenta la tensione per eseguire una rapida transizione. Con Hyper-Threading abilitato, ciò si verifica al livello thread. Il gestore del risparmio energetico è ottimizzato con l'utilizzo di X2 APIC e  PAIR (Power Aware Interrupt Routing) e controlla i core in modo da  non attivare quelli nel "sonno profondo".

Tutti gli altri componenti hanno migliorato le funzionalità della gestione del consumo energetico che sono incluse nelle loro rispettive sezioni riportate in basso.

Il resto del package

Il package Intel Core M condivide un chip con PCH a basso consumo con una limitazione dei consumi intelligente che supporta PCIe NAND, PCIe 2.0 (12 corsie a x1, x2 o x4) e aggiunge 2 porte USB 2.0 aggiuntive.

Il controller di memoria integrato supporta Intel® Fast Memory Access e Intel® Flex-Memory Access e riduce il consumo di energia utilizzando aggiornamenti automatici condizionati, il controllo dinamico dell'energia e disattivando la memoria di sistema inutilizzata tramite 4 modalità di spegnimento, supportando la RAM DDR3L o LPDDR3 a 1600 o 1333 divisa in 2 canali.

Grafica Intel® HD 5300

Come nuova aggiunta alla famiglia Grafica Intel HD, Grafica Intel HD 5300 inizia da una base di 100 MHz che ha un frequenza dinamica massima di 800 MHz (850 MHz su 5Y70). Con Intel® Quick Sync Video (codifica e post-elaborazione per video e applicazioni con grafica intensiva), la tecnologia Intel® InTru™ 3D, la tecnologia Intel® Clear Video HD e Intel® Flexible Display Interface (Intel® FDI), la Grafica Intel HD 5300 supporta 3 display (eDP/DP/HDMI). Con l'utilizzo del processore della famiglia GT2 (con 189 milioni di transistori), Grafica HD 5300 è dotata di 24 unità di ombreggiatura, 4 TMU e 1 ROP con supporto per DirectX* 11.1+, OpenGL* 4.2, OpenCL^TM 2.0, Shader Model 5.0, e fornisce una risoluzione UltraHD (3840 × 2160) tramite HDMI a 24 Hz.

I test hanno dimostrato che è possibile convertire video HD utilizzando Cyberlink* MediaEsspresso* fino all'80% più velocemente rispetto alla precedente generazione di processori core i5 e che i giochi (3DMark* IceStorm Unlimited v 1.2.) vengono eseguiti con prestazioni fino al 40% più elevate. Eppure, i processori Intel Core M forniscono comunque una durata della batteria di 1,7 ora in più (basata sulla riproduzione di video in locale e una batteria di 35 WHr).

(Tutti i test sono stati effettuati su piattaforme di riferimento Intel con 4 GB Dual Channel LPDDR3-1600 (2× 2 GB) con SSD Intel da 160 GB SSD con Windows 8.1 Update RTM. Il core M utilizzava il BIOS v80.1, mentre il core i5-4302Y (generazione precedente) utilizzava il BIOS WTM137. Entrambe le generazioni utilizzavano il driver Grafica Intel® HD v. 15.36.3650 ed erano dotate di TDP a 4,5 W. Altre impostazioni: Gestione del consumo energetico del sistema: equilibrata, Wireless: attivo e connesso, Dimensioni stimate della batteria: 35 WHr).

È possibile una durata maggiore della batteria, in quanto Grafica Intel HD 5300 dispone di:

• Tecnologia Intel® Display Power Savings (Intel DPST) 6.0, che riduce la retroilluminazione aumentando il contrasto e la luminosità.
• Intel® Automatic Display Brightness, che utilizza un sensore sul pannello anteriore per regolare la luce dell'ambiente.
• Tecnologia Intel® Seamless Display Refresh Rate (SDRRS), che diminuisce la frequenza di aggiornamento quando la batteria è in fase di esaurimento.
• Intel® Rapid Memory Power Management (Intel® RMPM), che permette l'aggiornamento automatico della batteria da stati di alimentazione a basso consumo.
• Rendering grafico in stato C (RC6), che modifica la linea di alimentazione in bassa tensione quando non è in corso alcuna attività.
• Tecnologia Intel® Smart 2D Display (Intel® S2DDT), che riduce la lettura della memoria per l'aggiornamento del display (disponibile solo in modalità single-pipe e non utilizzabile con le applicazioni 3D).
• Tecnologia Intel® Graphics Dynamic Frequency, che aumenta la frequenza e la tensione in base alle esigenze delle prestazioni.

Schede Intel® Wireless-AC7265 di 2^ª generazione

La famiglia di processori Intel Core M introduce anche una WLAN più veloce (le prestazioni migliorano del 15-100%) con un contenitore fisico più piccolo del 70%, utilizzando il fattore di forma M.2 1216.

Rispetto a Intel® Dual Band Wireless-A7260, la AC7265 ha migliorato la qualità di collegamento, è dotato di una copertura più ampia, di supporto per più dispositivi e può trasmettere video a 1080p pur essendo più ecologica del 50% quando inattiva (4 mW) e del 30% quando attiva (8 mW durante la navigazione nel web).

Nota: Intel prevede di introdurre docking wireless con WiGig nella famiglia Intel Core M nel 2015.

Intel® Wireless Display 5

Questa nuova generazione di Intel® Wireless Display (nota come Intel® WiDi) supporta una risoluzione di 1920 × 1080p a 60 fps, un tempo di connessione ridotto (inferiore a 6 secondi) e una latenza di gioco ridotta (inferiore a 65 ms). 

Le tecnologie includono:

• HDCP 2.2
• Scaling adattivo e frame rate
• UoIP per lo schermo touch a più punti tattili o controllo dei gesti
• Intel® Update Manager integrato per semplificare l'aggiornamento dei driver
• Supporto di tutti i formati a schermo intero DX9/DX11 con rilevamento della modalità gioco
• Intel WiDi Remote incluso per la gestione di multifinestre su doppi schermi
• Funzionalità aggiuntive in Intel Pro WiDi, dedicate all'utilizzo nelle sale per conferenze
• DCM (modalità canale differente)
• Schermo per la privacy
• Isolamento WPAN
• Maneggevolezza

Vedere anche Building Intel® WiDi Apps for Ultrabook^TM

Tecnologia Intel® Smart Sound

Con un nuovo DSP I2S più potente integrato nel PCH, la tecnologia Intel Smart Sound (Intel® SST) riduce la potenza della piattaforma con l'offload dei flussi audio elaborandoli dalla CPU host per la decodificazione di MP3/AAC, post-elaborazione Waves* o DTS* e attivazione vocale. Il codec I2S deve essere utilizzato per Intel SST.

Tecnologia di sicurezza che include Intel® Platform Protection

I sistemi con i processori Intel Core M sono dotati di funzioni di sicurezza avanzate, tra cui:

• La tecnologia Intel® Virtualization (Intel® VT-d e Intel® VT-x con EPT) ottimizza l'utilizzo della memoria VM e consente garanzie di QoS
• Standard di crittografia Intel® Advanced Encryption - Nuove istruzioni (Intel® AES-NI) - 6 istruzioni Intel® SSE per la sicurezza ad alte prestazioni
• Intel® Secure Key - Generatore dinamico di cifre casuali
• PCLMULQDQ (moltiplicazione carry-less), utilizzata spesso in crittografia
• OS Guard
• Execute Disable (ND) Bit
• SMEP (Supervisor Mode Execution Protection) e SMAP (Supervisor Mode Access Protection)
• Intel® Device Protection con Boot Guard
• Tecnologia Intel® Active Management v10

Nota: in aggiunta, il processore Intel Core M 5Y70 supporta la tecnologia Intel vPro™, la tecnologia Intel® Trusted Execution (Intel® TXT) e Windows* Instant Go* (nota come Connected Standby).

 

Suggerimenti per gli sviluppatori

 

Considerare le seguenti funzionalità per lo sviluppo di applicazioni per la famiglia di processori Intel Core M.

• Con la tecnologia Intel SpeedStep, utilizzare l'istruzione MWAIT e i sotto-stati per la maggior parte delle transizioni degli stati di alimentazione; per gli stati C1/C1E utilizzare l'istruzione HLT. Per ulteriori informazioni sugli stati C dei core, consultare il Volume 1 della scheda informativa di Intel Core M.

• Estensioni di sincronizzazione transazionale Intel® - Le nuove istruzioni (Intel® TSX-NI) forniscono la capacità al lock a grana fine solo durante la programmazione di lock a grana grossa. Consultare Riferimento per la programmazione di estensioni dei set di istruzioni dell'architettura Intel®..

• Una nuova istruzione Intel® AVX2 instruzione, Floating Point fused Multiply Add (FMA), aiuterà con il rilevamento dei volti e altre applicazioni di calcolo complesse.

• Assicurarsi di ottimizzare le applicazioni per il touch. Consultare la Guida allo sviluppo di interfacce touch di dispositivi e tablet Ultrabook™ con Windows,  Sviluppo con le interfacce naturali desktop API per gli sviluppatori, e Gestione dell'input touch nelle applicazioni per Windows* 8.

• Ottimizzare le applicazioni per l'input dei sensori inclusi il GPS, la bussola, giroscopio, l'accelerometro e la luce ambientale. Utilizzando la tecnologia Intel® RealSense™ e le API dei sensori di Windows per 8.1 (consultare  Guida allo sviluppo dei sensori per Ultrabook™ e tablet con Windows* 8 e Rilevamento dei sensori per Ultrabook™ su Windows* 8).

Altra documentazione e strumenti utili di Intel:

• SDK Intel® RealSense™ 2014
• Guida per lo sviluppo di Grafica Intel®
• SDK Intel® Media
• Intel® Graphics Performance Analyzers (Intel® GPA)
• Intel® Advanced Vector Extensions  (Intel® AVX)
• Manuali per lo sviluppo di architetture di software Intel® 64 e IA-32
• Elenco degli strumenti per lo sviluppo di software Intel
• Ulteriori informazioni sui processori Intel Core M

Informazioni sull'autore

Colleen Culbertson è un ingegnere di applicazioni per piattaforme nella Developer Relations Division, autore di articoli e di un blog nell'Intel® Developer Zone.

I test e le valutazioni sulle prestazioni vengono calcolati usando sistemi e/o componenti specifici e forniscono un'indicazione approssimativa delle prestazioni dei prodotti Intel misurate durante tali test. Qualsiasi differenza nell’hardware del sistema, nella progettazione del software o nella configurazione potrebbe influire sulle prestazioni effettive. Gli acquirenti sono tenuti a consultare altre fonti di informazioni per valutare le prestazioni dei sistemi o dei componenti che intendono acquistare. Per ulteriori informazioni sui test delle prestazioni dei prodotti Intel, visitare la pagina sulle Limitazioni dei benchmark delle prestazioni Intel..

Intel può apportare modifiche alle specifiche e alle descrizioni dei prodotti in qualsiasi momento e senza preavviso

Hi,

I have a working (demo) server with Intel AMT (version 9.0.31, bios version 1107, current setup mode is enterprise and TLS security is working). I am using the manageability director tool (v0.1.33).

Now I want to introduce Agent Authentication, as to authenticate remote users before they are allowed to remote control this demo server. I start by adjusting the security profile (to TLS Security + Agent Authentication, using the same self signed certificates used for the TLS security), but when trying to push this to the AMT box (by 'Set this profile on computers...") I get a message box (see attached) full with error messages, the first one being 'the request failed with HTTP status 404: not found'.

Any tips / hints or further 'how to' guides for me to read?

Much appreciated,

Chris

Remote Screen Blanking (RSB) is a feature introduced in Intel Active Management Technology (AMT) version 10.0 to help with those situations where you want the display of a client system to be off while remote operations are being performed on it. Prime candidates would be publically visible systems like digital signage, kiosks, and Automated Teller Machines but other systems within an enterprise may benefit from this feature too. RSB only affects the display and does not block any local user input like mouse, keyboard, touchscreen, or power button. Scenarios where patches are being installed, IDE-redirection sessions are in progress, or BIOS settings are being changed would typically be better if not displayed to the public or an unknown audience. RSB provides the curtain for an IT administrator to perform remote operations with discretion.

Before you get started using RSB, there are some prerequisites that must be met:

• Must have Intel AMT version 10.0 or later

• User Consent must be Off on the client

• Must be Enabled before use

• Must be allowed in the firmware

The first three items can be controlled by an administrator via software but the last one is controlled by the system manufacturer. The Intel AMT version number can be queried via API. User Consent is always needed for systems configured in Client Control Mode and optional in Admin Control mode. To be able to utilize RSB the system must be configured into Admin Control Mode with User Consent disabled. Finally you can use an API to Enable RSB. If enabling RSB fails with an Internal Processing error then most likely it is not available in the firmware installed on that system by the OEM.

Once you have satisfied the prerequisites you can incorporate RSB into your usages. The class IPS_ScreenConfigurationService provides the interface for controlling the feature via one method and three properties.

The properties:

• EnabledState – read/write property that allows you to query and enable or disable the state of RSB.

• CurrentState – read only property that provides the current state of an RSB session as either open/blanking or closed/not-blanking.

• RemainingConsecutiveRebootsNum – read only property that indicates the number of reboots that remain that will allow the blanking to persist. The initial value is set in the SetSesssionState method. If this number is 0 then a reboot will cause the blanking session to stop and the display to be shown again. The value can also be 1 through 3 which would allow a blanking session to continue during a reboot, which is useful for scenarios that require a reboot like Boot-to-BIOS or IDE-Redirection. Note that this works with resets only, a shutdown or hibernate will cancel a blanking session and reset this value to 0. Putting the system in Connected Standby will not change any RSB settings.

The method:

• SetSessionState – takes two parameters to allow you to turn screen blanking On or Off and set a value for the number of reboots that it will persist.

The PowerShell script below provides snippets of code that show how to utilize the RSB feature. For information on running PowerShell scripts with the Intel vPro module please refer to the AMT SDK and related documentation.

After establishing a connection (note: you will need to enter the proper credentials and machine address for your client system), the script checks the version of AMT which must be 10.0 or greater to have the feature. It then checks if User Consent is required on the system, which must be false for RSB to work.

Next there is a section that reports the current properties of RSB on the client. If the feature is not enabled, then it will enable it. The other properties are queried to show the current Blanking state and the number of reboots for which the current session will persist.

The final section illustrates how to start a screen blanking session that would persist through two reboots. It then pauses for 20 seconds and stops the screen blanking session.

# Begin flow template

Import-Module 'IntelvPro'

########################################

#   Create a Wsman Connection Object   #

########################################

$wsmanConnectionObject = new-object 'Intel.Management.Wsman.WsmanConnection'

$wsmanConnectionObject.Username = "admin"

$wsmanConnectionObject.Password = "**********"

$wsmanConnectionObject.Address = "http://" + "192.168.10.108" + ":16992/wsman"

########################################

function GetCoreVersion

{

    $softwareIdentityRef = $wsmanConnectionObject.NewReference("SELECT * FROM CIM_SoftwareIdentity WHERE InstanceID='AMT FW Core Version'")

    $softwareIdentityInstance = $softwareIdentityRef.Get()

    $versionString = $softwareIdentityInstance.GetProperty("VersionString")

    return $versionString

}

########## Check the pre-requisites ##########

#Check the AMT version; Need AMT 10 or greater for Remote Screen Blanking

Write-Host "AMT version is: "  $(GetCoreVersion)

#Check if User Consent is required; Remote Screen Blanking will not operate when User Consent is required

$optInServiceRef = $wsmanConnectionObject.NewReference("SELECT * FROM IPS_OptInService WHERE Name='Intel(r) AMT OptIn Service'")

$optInServiceInstance = $optInServiceRef.Get()

$optInRequired = $optInServiceInstance.GetProperty("OptInRequired")

Write-Host "User Consent Required: "  $OptInRequired

########## Report the current properties and enable if needed ##########

#Read the configuration settings for Remote Screen Blanking which are in the class IPS_ScreenConfigurationService

$screenPropRef = $wsmanConnectionObject.NewReference("SELECT * FROM IPS_ScreenConfigurationService")

$screenPropInstance = $screenPropRef.Get()

#Check if Remote Screen Blanking is enabled; If it is not, then set it to enabled

$enabledState = $screenPropInstance.GetProperty("EnabledState")

Write-Host "Enabled state: "  $enabledState

If ($enabledState.ToString() -eq "0")

{

    Write-Host "Remote Screen Blanking was not enabled, so enabling it now"

    $screenPropInstance.SetProperty("EnabledState", "1")

    $screenPropRef.Put($screenPropInstance)

}

#Check if the screen is currently being blanked

$screenState = $screenPropInstance.GetProperty("CurrentState")

Write-Host "Screen state is (0=Not Blanked, 1=Blanked): "  $screenState

#Check how many reboots can occur while maintaining an actively blanked screen

$rebootsRemaining = $screenPropInstance.GetProperty("RemainingConsecutiveRebootsNum")

Write-Host "Remaining reboots: "  $rebootsRemaining

########## Blank the screen, pause, then un-blank the screen ##########

#Start blanking the screen with 2 reboots allowed, wait for 30 seconds, then stop blanking

$screenPropRef = $wsmanConnectionObject.NewReference("SELECT * FROM IPS_ScreenConfigurationService")

$screenPropInstance = $screenPropRef.Get()

$inputObject = $screenPropRef.CreateMethodInput("SetSessionState")

$inputObject.SetProperty("SessionState", "1")

$inputObject.SetProperty("ConsecutiveRebootsNum", "2")

$outputObject = $screenPropRef.InvokeMethod($inputObject)

$returnValue = $outputObject.GetProperty("ReturnValue")

Write-Host "Blank the screen. Return (0 = success):   "  $returnValue

Start-Sleep -s 20

$inputObject.SetProperty("SessionState", "0")

$inputObject.SetProperty("ConsecutiveRebootsNum", "0")

$outputObject = $screenPropRef.InvokeMethod($inputObject)

$returnValue = $outputObject.GetProperty("ReturnValue")

Write-Host "Stop blanking the screen. Return (0 = success): "  $returnValue

########################################

Remove-Module 'IntelvPro'

# End flow template

Hello world!

           I've hooked up computer client to use the Intel ATM feature, but I am getting the error message "Failed to access resource IPS_KVMRedirectionSettingData, check user permissions." when I try to get I remotely via VNC Viewer Plus.

1. I created the xml profile with information below.
   1. Created helpdesk user on Access Control List, Redirection, PT Administration, Hardware Asset and Remote Control Enabled.
   2. System Settings
      1. Management interface to enable: Web UI, Serial Over Lan, IDE Redirection and KVM Redirection  all enabled and RFB password for KVM Sessions field filled.
2. Network and other settings
   1. User the following password for all systems field filled.\
3.   I applied the xml on my computer client with this command line:  ACUConfig.exe /verbose /lowsecurity configAMT Noaddoptions.xml /decryptionpassword p@ssw0rd
4. I am able to access the computer via web http://computername16992/logon.htm, but I am not able to get it remotely via VNC.

Computer information:

Dell 7010

Intel AMT Version 8.1.20

Please Help me out.

Thanks so much.

Hello experts, have anybody got an idea or practice on machine list export and import in xml format, on vPro Platform Solution Manager?

The wireless networking capabilities were extended in the 6.0 release of Intel® AMT to include the following:

• Automatic synchronization of wireless profiles from the host operating system


• Support for remote access over wireless


• Control over host connectivity during Intel® AMT redirection.

 For more details please refer to the documentation in the new Intel® AMT SDK including the CIM Elements. There is also some history on profiles, configuring and enabling.

 Sync or Swim

 Intel® AMT 6.0 can be configured to synchronize wireless profiles between the Host Connection Manager and the Manageability Engine (ME). This feature can be enabled or disabled during configuration. When enabled, the currently connected profile is automatically pushed to the ME for use out of band.

There are two types of profiles defined by Intel® PROSet for use with AMT, Admin and User, and both can be synchronized. Admin profiles (a.k.a. IT profiles) are those defined and set by IT administrators and typically used inside an enterprise network environment. User profiles are those created by the system’s end user typically for connecting to a network outside the corporate enterprise (e.g. home network). Up to sixteen Admin and eight User profiles can be synchronized. 

The Intel® PROSet API service and the Intel ® AMT Local Manageability Service (LMS) are required for the synchronization to work.

 Help with No Wire 

Starting with Intel® AMT 6.0 the Remote Access usages can now be done over wireless. So mobile clients that are connected to a wireless network outside the corporate environment can now perform operations like Fast Call for Help to get connected back to their IT help desk when they have issues that need assistance. This includes support for the new KVM Remote Control feature that allows help desk personnel to diagnose and repair blue screens and other tough issues.
 
Down but Not Out 

When the host operating system is up it controls the wireless connection which provides the channel for calls to AMT. This poses a problem for AMT operations that perform a reset (i.e. Serial-Over-LAN, IDE-Redirection, KVM Remote Control) because once the host OS is down the AMT connection is lost. Prior to Intel® AMT 6.0 the ME took control of the connection before a redirection session to avoid possible disconnect if there was a reset. Now there is the option to let the host operating system maintain the connection with a redirection session to support usages that will not perform a reset like use of KVM Remote Control to see the current host operating system environment.

Let Me Connect 

Intel® AMT supports a variety of authentication and encryption types for its wireless connections. But there are several constraints to keep in mind. Only Infrastructure network types are supported by Intel® AMT, not Ad-hoc/peer-to-peer. User profiles can be configured with WEP or no encryption and cannot be added to the ME via the AMT API. Admin profiles must be TKIP or CCMP with WPA or higher security and can be added to the ME via the AMT API. And as mentioned previously, 802.1x profiles are not automatically synchronized.

 Here is a table that shows the possible security settings for AMT wireless profiles. 

 Wired Equivalency Privacy (WEP)

Temporal Key Integrity Protocol (TKIP)

Counter Mode with Cipher Block Chaining Message Authentication Code Protocol (CCMP) a.k.a. Advanced Encryption Standard (AES)

Wi-Fi Protected Access (WPA)

Wi-Fi Protected Access Version 2 (WPA2)  a.k.a. Robust secure Network (RSN)

Pre-Shared Key (PSK)

Hello,

I installed Ubuntu Server 64bit 12.10 on a Dell Poweredge T20 and wanted to run it headless, but I ran into the following problem, that when no monitor was attached, or if you send the system into standby and wake it up again, the screen is black if connected via VNC. I found this old thread: https://software.intel.com/en-us/forums/topic/279956 where it was suggested to add "nomodeset" to GRUB config, which I did, and it seemed to work at first. I now got a VNC signal too after standby wakeup, but now the mouse/keyboard doesnt work anymore. The video picture still works, because I can see the time changing on my Ubuntu desktop, but the VNC doesnt accept any mouse nor keyboard input anymore. When I reboot, the issue is gone, but the moment I do the same, send the system into standby via pm-suspend, wake it up again via WOL, it's broken. I also noticed, that the nomodeset option results in the video driver not working anymore correctly (with hardware acceleration), because I see large CPU consumption of "Compiz" and X server.

Greetings. I have  a question - can I manage of bios password on laptops and pc's (with intel AMT) in our company  through  powershell script\c# ?

Thanks.

Today, the MeshCentral team is very proud to be announcing something that is absolutely revolutionary in remote computer management. We had to make the announcement today because it was going to leak out anytime and this project was so secret we told absolutely no-one, including our own management about it. We are announcing MeshCentral Drone Enabled Remote Management Technology Enabled by IoT (or “MCDERMTEIoT” for short). Using the location technology already built into Mesh, along with the all new Mesh Drone Server, we will enable remote management like you, literary, could never have seen before.

In the coming months, with MCDERMTEIoT, if the mesh agent is unable to fix a problem remotely, you will be able to dispatch a set of drones to fly over to the remote computer and fix it completely at a distance. You will even have a drone fly over with a USB key and perform remote activation. Because just having a drone plug in a USB key will probably not fix most problems, micro-drones will be deployed to type on the keyboard (standard US keyboard only for the first version). We use peer-to-peer mesh technology to have drones cooperate, making tasks like typing “FORMAT C:” or push the reset button easy, and even more complicated tasks like using 3 drones to press CTRL-ALT-DEL. Drones will also be able to knock at the door before entering a building… so it’s friendly remote management service all the way.

MCDERMTEIoT will enable completely new usages for desktop, mobile and IoT devices in a way that has not been thought of even 24 hours ago. We look forward to having Meshcentral enabled with drones change the world of computing. Remote Management is only the start, we fully expect that the same technology will be enhanced so Meshcentral could be used to setup your home network, fix light bulbs or find left socks hidden behind the dryer.

Happy April 1st!
Ylian Saint-Hilaire
info.meshcentral.com
Meshcentral on Twitter

Meshcentral combined with the power of drones allows for revolutionary remote
computer management. Plenty of interesting use cases can now be solved.

The Meshcentral team is dedicated to bringing the latest in remote computer management.
This hot shot team can dream up and do just about anything.

• Download the Intel AMT SDK
• Intel® AMT SDK Documentation
• Follow Gael on Twitter: @GaelHof

If you have an Intel AMT system and cannot figure out why you are getting error messages when trying to make API calls related to certain Intel AMT features, you may have a system that support Intel Standard Manageability.

You can use WS-Management commands to detect your platform's capabilities. See the Discovery Sample in the Intel AMT SDK located at <SDKRoot>\Windows\Intel_AMT\Samples\Discovery for an example.  Also, messages displayed by these platforms in the MEBx and the WebUI indicate Intel Standard Manageability, instead of Intel AMT.

So what is Standard Manageability? Standard Manageability systems come with a subset of Intel AMT available features.  Standard Manageability are not branded as Intel vPro. These systems are upgradeable to the full Intel AMT version capabilities.

The Standard Manageability SKU was introduced with Intel AMT Release 5.0. The following Intel AMT features are NOT included or supported on platforms with this SKU:

Аннотация

Корпорация Intel представляет первый из процессоров пятого поколения (Broadwell), выпуская три модели семейства Intel^® Core™ M. Эта статья, предназначенная для разработчиков, описывает этот 64-разрядный многоядерный процессор с архитектурой «система на кристалле» и описывает реализованные в нем технологии Intel^®, включая Intel^® HD Graphics 5300.

Основные характеристики процессоров Intel Core M

Семейство процессоров Intel^® Core™ M отличается более высокой производительностью при более компактных размерах, сниженных требованиях к электропитанию и охлаждению (что отлично подходит для тонких устройств без вентиляторов), а также более длительной работе от аккумуляторов. Процессоры поддерживают следующие технологии:

• Intel HD5300 Graphics и Intel® Wireless Display 5.0;
• Intel Wireless-AC 7265 и поддержка беспроводной стыковки (в 2015 г.) с помощью WiGig;
• технология Intel® Smart Sound;
• технология Intel® Platform Protection и другие средства безопасности.

Уменьшение размера + повышение производительности = снижение требований к электропитанию и охлаждению

Intel Core M — первые процессоры, которые будут изготавливаться на основе 14-микронной технологии. Размер кремниевого кристалла удалось сократить более чем на 30 %, хотя количество транзисторов увеличилось более чем на 300 миллионов.  Процессоры Intel Core M отличаются сниженной потребляемой мощностью и выделяют меньше тепла. У трех моделей этого семейства, выпуск которых начался в IV квартале 2014 года, тепловая мощность составляет всего 4,5 Вт. Это означает, что для охлаждения этих процессоров не нужен вентилятор. Эти процессоры позволят добиться высокой производительности в самых тонких устройствах (толщиной менее 9 мм), включая планшеты и трансформеры.

Рисунок 1. Сравнение процессоров Intel Core M с пониженным потреблением электроэнергии

На графике слева на рис. 1 показано снижение тепловой мощности с 18 Вт в 2010 году до 4,5 Вт в процессоре Intel Core M. Это четырехкратное снижение за 4 года и снижение на 60 % по сравнению с 2013 годом. Справа на рис. 1 показано сравнение размеров процессора Intel® Core™ 4-го поколения с новым процессором Intel Core M. За счет уменьшения площади процессора примерно на 50 % удалось уменьшить место, занимаемое процессором на плате, примерно на 25 %.

Процессоры Intel Core M по своим габаритным размерам меньше  процессоров Intel Core 4-го поколения.   При этом двумя ядрам Intel Core M предоставляется кэш объемом 4 МБ. За счет технологии гиперпоточности гипертрединга Intel® поддерживается одновременное выполнение четырех потоков. Благодаря технологии Intel® Turbo Boost 2.0 частота ядер может повышаться с 0,8 ГГц до 2 ГГц, а у процессоров Intel Core M 5Y70 — с 1,1 ГГц до 2,6 ГГц.

 

В едином кристалле с 1,3 млрд транзисторов реализованы ЦП, ГП, контроллер памяти, звуковой контроллер и сетевые интерфейсы, поэтому не следует ожидать снижения производительности. Более того, сравнение с процессором предыдущего поколения Intel^® Core™ i5-4320Y показало значительный прирост производительности.

Технология электропитания

Повсюду в этом документе упоминаются многочисленные технологии Intel, предназначенные для снижения электропитания. Технология Intel® Turbo Boost 2.0 включает модуль отслеживания электропитания, вычисляющий мощность ядер ЦП и ГП, а также модуль управления электропитанием, направляющий электроэнергию туда, где она нужна.  Расширенная технология Intel SpeedStep®с поддержкой C-состояний C0, 1, 1E, 3 и 6—10 обеспечивает наименьшее потребление электропитания в состоянии бездействия. Если требуется увеличить вычислительную мощность, процессор повышает напряжение для быстрого переключения. При включенном гипертрединге это переключение происходит на уровне потоков. Обработка прерываний оптимизирована с точки зрения  электропитания за счет применения X2 APIC и PAIR (маршрутизация прерываний с учетом электропитания): состояние ядер проверяется, чтобы избежать пробуждения ядер, находящихся в состоянии глубокого сна.

В прочих компонентах также улучшены возможности управления электропитанием, об этом
см. в соответствующих разделах ниже.

Прочие компоненты

На одном кристалле Intel Core M расположен также узел контроллера платформы PCH с интеллектуальным управлением электропитанием, поддерживающий PCIe NAND, PCIe 2.0 (12 каналов x1,x2 или x4) и два дополнительных порта USB 2.0.

Интегрированный контроллер памяти поддерживает технологии Intel^® Fast Memory Access и Intel^®
Flex-Memory Access. Экономия электроэнергии обеспечивается с помощью таких решений, как условное самообновление, динамическое понижение напряжения и отключение неиспользуемой системной памяти посредством четырех отключаемых модулей. Поддерживается оперативная память DDR3L или LPDDR3 частотой 1600 МГц или 1333 МГц, разделенная на 2 канала.

Intel^® HD Graphics 5300

Новый компонент семейства Intel HD Graphics, графический процессор Intel HD Graphics 5300, работает с начальной базовой частотой 100 МГц, которая динамически повышается до 800 МГц (850 МГц в модели 5Y70).  Отметим поддержку технологий Intel^® Quick Sync Video (кодирование и пост-обработка мультимедиа и приложений с интенсивной нагрузкой на графическую подсистему), Intel^® In Tru™ 3D, Intel^® Clear Video HD, а также Intel^® Flexible Display Interface (Intel^® FDI). ГП Intel HD Graphics 5300 поддерживает подключение трех экранов (интерфейсы eDP/DP/HDMI).  В HD Graphics 5300 используется процессор GT2 этого семейства (189 млн транзисторов), в нем содержится 24 шейдерных модуля, 4 модуля наложения текстур и 1 модуль вывода отрисованного изображения. Поддерживаются DirectX* 11.1 и более поздних версий,  OpenGL* 4.2, OpenCL^TM 2.0, Shader Model 5.0. Графический процессор способен выдавать изображение с разрешением вплоть до UltraHD (3840 x 2160) по интерфейсу HDMI при 24 Гц.

Тестирование показало, что преобразование видео высокой четкости с помощью Cyberlink*MediaEsspresso* выполнялось на 80 %
быстрее, чем на процессоре Core i5                предыдущего поколения, а скорость в играх     (3DMark* IceStorm Unlimited v 1.2.) увеличилась
на 40 %. При этом система с процессором Intel
Core M проработала от аккумулятора на 1,7 ч дольше (при локальном воспроизведении видео и аккумуляторе 35 Вт-ч).

(Все тесты проведены на эталонных платформах Intel с 4 ГБ двухканальной памяти LPDDR3-1600 (2 модуля по 2 ГБ) с твердотельным накопителем Intel объемом 160 ГБ с операционной системой Windows 8.1. В системе с процессором Core M использовался BIOS версии 80.1, в системе с процессором Core i5-4302Y (предыдущего поколения) — BIOS версии WTM137. В обеих системах использовался драйвер Intel^® HD Graphics версии 15.36.3650, а тепловая мощность составляла 4,5 Вт. Другие параметры: системная политика управления электропитанием: сбалансированная, адаптер беспроводной сети: включен, емкостью аккумулятора: 35 Вт-ч).

Дополнительное время работы от аккумулятора обеспечивается следующими возможностями Intel HD Graphics 5300.

• Технология Intel^® Display Power Savings (Intel DPST) 6.0, снижающая уровень подсветки при одновременном увеличении контрастности и яркости.
• Технология Intel^®  Automatic Display Brightness, использующая датчик на передней панели устройства для регулировки яркости экрана в соответствии с уровнем освещения.
• Технология Intel^® SDRRS (Seamless Display Refresh Rate), снижающая частоту обновления экрана при низком уровне заряда аккумулятора.
• Технология Intel^® Rapid Memory Power Management  (Intel^® RMPM), обеспечивающая автоматическое обновление памяти из состояний с пониженным потреблением электроэнергии
• С-состояние модуля отрисовки графики (RC6), снижающее напряжение шины питания при отсутствии нагрузки.
• Технология Intel^® Smart 2D Display (Intel^® S2DDT), уменьшающая количество операций чтения из памяти для обновления отображения (работает только в одноконвейерном режиме, непригодна для использования с трехмерными приложениями).
• Технология Intel^® Graphics Dynamic Frequency, динамически увеличивающая частоту и напряжение ГП при необходимости.

Беспроводной адаптер Intel^® Wireless-AC7265  2-го поколения

В семействе процессоров Intel Core M также реализованы более скоростные адаптеры WLAN (производительность повышена на 15—100 %)при сниженных на 70 % габаритах за счет использования типоразмера M.2 1216. По сравнению с двухдиапазонным адаптером Intel® Wireless-A7260, у AC7265 значительно повышена надежность каналов, расширено покрытие, поддерживается больше одновременно подключенных устройств и есть возможность потоковой передачи видео с разрешением 1080p. При этом новый беспроводной адаптер расходует на 50 % меньше электроэнергии в состоянии бездействия (4 мВт) и на 30 % при работе (8 мВт при просмотре веб-страниц).

Примечание. Корпорация Intel планирует внедрить возможность беспроводной стыковки с помощью WiGig в семейство Intel Core M в 2015 году.

Intel^®WirelessDisplay 5

Новое поколение технологии Intel^® Wireless Display (Intel^® WiDi) поддерживает разрешение 1920 x 1080p при 60 кадрах в секунду, ускоренное подключение (не более 6 секунд) и сниженные задержки в играх (не более 65 мс). 

Поддерживаемые технологии

• HDCP 2.2
• Адаптивное масштабирование и кадровая скорость
• UoIP: многоточечный сенсорный экран и управление жестами
• Встроенный диспетчер Intel® Update Manager для удобного обновления драйверов
• Поддержка всех полноэкранных игровых форматов DX9/DX11 с определением игрового режима
• В комплект входит программное обеспечение Intel WiDi Remote для управления несколькими окнами при одновременном выводе изображения на два экрана
• Дополнительные функции Intel Pro WiDi, предназначенные для использования в конференц-залах
• DCM (режим раздельных каналов)
• Экран конфиденциальности
• Изоляция WPAN
• Управляемость

См. также «Создание Intel WiDi приложений для ультрабуков^TM».

Технология Intel® Smart Sound

В узел контроллера платформы РСН интегрирован новый, более мощный цифровой сигнальный процессор I2S. Технология Intel Smart Sound (Intel^® SST) снижает потребление электроэнергии за счет разгрузки ЦП системы: сигнальный процессор берет на себя задачи по обработке звука и поддерживает декодирование MP3/AAC, пост-обработку Waves* и DTS*, а также пробуждение по голосовой команде.  Для Intel SST необходимо использовать кодек I2S.

Безопасность, включая технологию Intel^® Platform Protection

Системы с процессорами Intel Core M оснащаются расширенными возможностями безопасности, включая следующие.

• Технология виртуализации Intel^® (Intel^® VT-d и Intel^® VT-x с EPT ) — оптимизация использования памяти виртуальными машинами, поддержка гарантий качества обслуживания
• Инструкции Intel^® AES-NI (Intel^® Advanced Encryption Standards — New Instructions) — 6 инструкций Intel^® SSE для высокопроизводительного шифрования
• Intel^® Secure Key — динамический генератор случайных чисел
• PCLMULQDQ (половинное умножение) — часто используется в шифровании
• Защита ОС
• Отключение бита выполнения (ND)
• SMEP (защита выполнения в режиме супервизора) и SMAP (защита доступа в режиме супервизора)
• Защита устройств Intel^®с Boot Guard
• Intel^® Active Management Technology v10

Процессоры Intel Core M 5Y70 также поддерживают технологии Intel vPro™, Intel^® Trusted Execution (Intel^® TXT) и Windows* Instant Go* (ранее Connected Standby)

Рекомендации для разработчиков

Рассмотрите возможность применения следующих компонентов и вызовов при разработке приложений для процессоров семейства Intel Core M.

• При использовании технологии Intel SpeedStep используйте инструкцию MWAIT и подчиненные состояния для большинства переключений между режимами электропитания, но для состояний C1/C1E используйте инструкцию HLT. Дополнительные сведения о C-состояниях ядер см. в «Семейство процессоров Intel Core M, справочник, том 1».
   
• Расширения Intel® Transactional Sychronization Extensions — New Instructions (Intel® TSX-NI) предоставляют возможность точной настройки блокировок, программируя только грубые блокировки. См. справочник по программированию расширений набора инструкций архитектуры Intel®..
   
• Новая инструкция в наборе Intel® AVX2, AVX2 instruction, синтезированное умножение и сложение значений с плавающей запятой (FMA), полезна при распознавании лиц и в других задачах с интенсивной вычислительной нагрузкой.

• Применяйте оптимизацию приложений сенсорного управления. См. статьи «Руководство по сенсорному управлению для разработчиков: ультрабуки и планшеты», «Разработка с использованием API классического интерфейса»,  «Обработка сенсорного ввода в приложениях для Windows* 8».

• • Оптимизация приложений для датчиков, включая GPS, компас, гироскоп, акселерометр и датчик освещения. Применяйте технологию Intel® RealSense™ и интерфейсы API датчиков для Windows 8.1 (см. «  Руководство по разработке для датчиков на ультрабуках и планшетах под управлением Windows* 8» и «Обнаружение датчиков ультрабуков в Windows* 8»

Прочая документация Intel и полезные инструменты

• Intel® RealSense™ 2014 SDK
• Руководство для разработчиков по Intel® Graphics
• Intel® Media SDK
• Intel® Graphics Performance Analyzers (Intel® GPA) (Intel® GPA)
• Intel® Advanced Vector Extensions (Intel® AVX)(Intel® AVX)
• Руководства разработчиков программного обеспечения по архитектурам Intel® 64 и IA-32
• Список средств для разработки программного обеспечения
• Дополнительные сведения о процессорах Intel Core M

Об авторе

Коллин Калбертсон (Colleen Culbertson) работает в должности инженера по разработке приложений для платформ в отделе Developer Relations Division. Он является автором ряда статей и регулярных публикаций в блоге на портале Intel® Developer Zone.

Тесты и оценки производительности проводятся на определенных компьютерных системах и компонентах и соответствуют приблизительной производительности продуктов Intel в этих тестах. Любые отличия в оборудовании системы и в программном обеспечении или конфигурации могут повлиять на фактическую производительность. При выборе приобретаемых продуктов следует обращаться к другой информации и тестам производительности. Дополнительные сведения о тестах производительности и о производительности продуктов Intel см. на сайте Ограничения тестов производительности Intel.

Примечания

ИНФОРМАЦИЯ В ДАННОМ ДОКУМЕНТЕ ПРИВЕДЕНА ТОЛЬКО В ОТНОШЕНИИ ПРОДУКТОВ INTEL. ДАННЫЙ ДОКУМЕНТ НЕ ПРЕДОСТАВЛЯЕТ ЯВНОЙ ИЛИ ПОДРАЗУМЕВАЕМОЙ ЛИЦЕНЗИИ, ЛИШЕНИЯ ПРАВА ВОЗРАЖЕНИЯ ИЛИ ИНЫХ ПРАВ НА ИНТЕЛЛЕКТУАЛЬНУЮ СОБСТВЕННОСТЬ. КРОМЕ СЛУЧАЕВ, УКАЗАННЫХ В УСЛОВИЯХ И ПРАВИЛАХ ПРОДАЖИ ТАКИХ ПРОДУКТОВ, INTEL НЕ НЕСЕТ НИКАКОЙ ОТВЕТСТВЕННОСТИ И ОТКАЗЫВАЕТСЯ ОТ ЯВНЫХ ИЛИ ПОДРАЗУМЕВАЕМЫХ ГАРАНТИЙ В ОТНОШЕНИИ ПРОДАЖИ И/ИЛИ ИСПОЛЬЗОВАНИЯ СВОИХ ПРОДУКТОВ, ВКЛЮЧАЯ ОТВЕТСТВЕННОСТЬ ИЛИ ГАРАНТИИ ОТНОСИТЕЛЬНО ИХ ПРИГОДНОСТИ ДЛЯ ОПРЕДЕЛЕННОЙ ЦЕЛИ, ОБЕСПЕЧЕНИЯ ПРИБЫЛИ ИЛИ НАРУШЕНИЯ КАКИХ-ЛИБО ПАТЕНТОВ, АВТОРСКИХ ПРАВ ИЛИ ИНЫХ ПРАВ НА ИНТЕЛЛЕКТУАЛЬНУЮ СОБСТВЕННОСТЬ.

КРОМЕ СЛУЧАЕВ, СОГЛАСОВАННЫХ INTEL В ПИСЬМЕННОЙ ФОРМЕ, ПРОДУКТЫ INTEL НЕ ПРЕДНАЗНАЧЕНЫ ДЛЯ ИСПОЛЬЗОВАНИЯ В СИТУАЦИЯХ, КОГДА ИХ НЕИСПРАВНОСТЬ МОЖЕТ ПРИВЕСТИ К ТРАВМАМ ИЛИ ЛЕТАЛЬНОМУ ИСХОДУ.

Корпорация Intel оставляет за собой право вносить изменения в технические характеристики и описания своих продуктов без предварительного уведомления. Проектировщики не должны полагаться на отсутствующие характеристики, а также характеристики с пометками «зарезервировано» или «не определено». Эти характеристики резервируются Intel для будущего использования, поэтому отсутствие конфликтов совместимости для них не гарантируется. Информация в данном документе может быть изменена без предварительного уведомления. Не используйте эту информацию в окончательном варианте дизайна.

Продукты, описанные в данном документе, могут содержать ошибки и неточности, из-за чего реальные характеристики продуктов могут отличаться от приведенных здесь. Уже выявленные ошибки могут быть предоставлены по запросу.

Перед размещением заказа получите последние версии спецификаций в региональном офисе продаж Intel или у местного дистрибьютора.

Копии документов с порядковым номером, ссылки на которые содержатся в этом документе, а также другую литературу Intel можно получить, позвонив по телефону 1-800-548-4725 либо на сайте:http://www.intel.com/design/literature.htm

Программное обеспечение и нагрузки, использованные в тестах производительности, могли быть оптимизированы для достижения высокой производительности на микропроцессорах Intel. Тесты производительности, такие как SYSmark* и MobileMark*, проводятся на определенных компьютерных системах, компонентах, программах, операциях и функциях. Любые изменения любого из этих элементов могут привести к изменению результатов. При выборе приобретаемых продуктов следует обращаться к другой информации и тестам производительности, в том числе к тестам производительности определенного продукта в сочетании с другими продуктами.

Intel, эмблема Intel, Intel Core, Intel SpeedStep, InTru, Intel RealSense и Ultrabook являются товарными знаками корпорации Intel в США и в других странах.

© Intel Corporation, 2014. Все права защищены.

* Прочие наименования и товарные знаки могут быть собственностью третьих лиц.

OpenCL и эмблема OpenCL являются товарными знаками Apple Inc и используются с разрешения Khronos.

The date/time used by Intel® Active Management Technology (AMT) is maintained by a protected real time clock (PRTC) running within the Manageability Engine.

 Clock Usage

The clock is used for a variety of reasons in AMT including date/time checks required for TLS and Kerberos usage, timestamps for events and logging, and maintaining alarms for the Alarm Clock feature.

 Setting the Clock

The clock can be set in a few ways, dependent on how AMT was provisioned. 

1. In  systems with AMT version 7.0 or earlier, you can set it manually (locally) through the Manageability Engine BIOS Extensions (MEBx) via “Intel® AMT Configuration > Set PRTC”.
2. Synchronize to a server’s time remotely through the API. The WS-Management class AMT_TimeSynchronizationService does this with the two calls GetLowAccuracyTimeSynch and SetHighAccuracyTimeSynch. The clock has to be set remotely during Enterprise mode configuration on systems prior to AMT 6.0 or the configuration will not succeed. For AMT 6.0 and later, the clock does not need to be remotely configured in order to complete provisioning to Enterprise mode, as long as TLS/Kerberos are not enabled; In this case the clock will be synchronized to the BIOS clock.
3. The clock is automatically synchronized at boot time with the local BIOS clock for AMT 5.0 or earlier systems configured in Small Business (SMB) and for AMT version 6.0 or greater configured manually.

If the clock is being synchronized with the BIOS clock you should keep in mind that Microsoft Windows will typically set the BIOS to the local time being kept by the operating system (see The Old New Thing). I believe Unix/Linux systems normally set the BIOS clock to Coordinated Universal Time (UTC).

In the Zone

The clock used by AMT does not maintain knowledge of time zone. So it would be a good idea to maintain knowledge of how the clock has been/is being set and what the local time is for that system. This is important when setting the Alarm Clock or reading timestamps in the usages mentioned above.

 

If you have extended Active Directory (AD) for use with your AMT clients and Kerberos authentication, you may have issues connecting to the AMT WebUI for those machines when using Internet Explorer (IE). This is related to authentication settings.

If you experience this problem, you can first try another browser (e.g. Firefox) to see if you can connect to the WebUI. If successful, then you can try the following configurations in your IE settings.

• Tools > Internet options > Security > Custom level > User Authentication > Logon – Prompt for user name and password

• Tools > Internet options > Advanced > Security – Enable Integrated Windows Authentication

 

Have you ever been working and had a patch come down from your IT department that you had to install now. Or how about a virus scan that brought your machine to a crawl in the middle of your work. If so, you may wish your IT department would use AMT Alarm Clock, a feature released in the 5.1 version of Intel Active Management Technology (AMT).

This feature provides the ability for a remote management console to schedule clients to wake themselves up from any sleep state (even off) at a specific date/time or on a recurring basis. And the wake can occur even if the system does not have network connectivity (which distinguishes this feature from WOL or AMT's existing remote power control).

The original implementation provided a single alarm, but starting in AMT 8.0 five new alarms were added for greater flexibility. Multiple alarms allow a single user to schedule different activities or allow multiple users to utilize the feature. It is important to note that the original single alarm uses a different API from the additional five alarms; please refer to the documentation.

With this new feature you can:

• Allow autonomous tasks to run at scheduled times
• Improve productivity and compliance by scheduling compute intensive tasks for off normal working hours
• Save network bandwidth when waking many machines

Once the system is awake a local agent can perform a scheduled task. The tasks to perform can be communicated to the agent in advance, or can be written to the 3rd Party Data Store for reading when the system is powered up by the Alarm Clock.

When the AMT Alarm Clock wakes the system it writes an entry to the event log stating that the system was powered up by AMT and indicates the prior sleep state of the system. The local agent can read this entry to find out which sleep state to return the system when it is finished with its tasks. Also added in AMT 8.0 was the Reason For Last Boot call which will tell if the system was booted due to the AMT Alarm Clock, an AMT Power Control, or other. If it is 'other', the User may have booted the system, in which case you should consider if the planned actions will interfere with work they may be doing.

Keep in mind that the AMT Management Engine (ME) must have a power policy set that will make it be On when the alarm is supposed to run. For example, if the ME is only configured to be On in S3 it won't be available to wake the system from S5.

To find out more please check out the samples and documentation in the AMT SDK.
 

For all of you Java developers out there that have be searching for tools to help with your Intel® Active Management Technology solutions, your search is over. I’d like to introduce you to the Intel® WS-Management Java Client Library, available for download here.

This download contains source code for a library that can be used to make WS-Management calls to Intel® AMT devices. Also included are code samples that demonstrate how to use the library to interact with many AMT features and documentation on the library & samples.

 Key Features

• Allows Intel® AMT development in Java environments


• 100% pure Java (no JNI or native code wrapping)


• Supports Digest and Kerberos authentication


• Library is packaged in a single .jar file with JavaDocs


• Supports JDK5 and newer (JDK6 required for native Kerberos support)

 

 Getting Started

Just include IntelWsmanLib.jar in your class path and you can start calling the API.  I wrote a few of the samples in the download using the NetBeans Integrated Development Environment. But you can use any Java capable environment as long as you include the jar file. Relevant objects are found in the intel.management.wsman Java package.

The library is WS-Management compliant and not AMT specific or even AMT version specific. There are no WSDL files, XSD files, or MOF files needed.

 Writing Code

Here are some snippets to give you an idea of how the code looks.

First create a connection to a WS-Management Service as follows:

        import intel.management.wsman.*;

        connection = WsmanConnection.createConnection(<url>);

Then use the resulting connection object to perform WS-Transfer, WS-Enumeration, or WS-Eventing operations using either digest or Kerberos credentials.

 For example, to get the AMT host name:

        ManagedReference ref = connection.newReference(“AMT_GeneralSettings”);

        ManagedInstance inst = ref.get();

        inst.GetProperty(“HostName”);

Take a look at the sample code included in the download for more details.

Please post to our forum any questions, comments or feedback.

Audit Log (also known as Access Monitor) is an feature introduced in AMT 4.0 that provides a place to record events and introduces a new type of user called Auditor.

Key features of the Audit Log are:

• Auditor user type that cannot be removed or altered by the Administrator


• Policy based events that are selected by the Auditor to be logged


• Configurable alerts associated with the logged events


• Unprovisioning requires collaboration between Auditor and Administrator

Typical usage will start with an Administrator enabling auditing and establishing the Auditor account (after this, the Auditor cannot be affected by the Administrator). There can only be one Auditor on a system at a time. The Auditor will then set policies that define which events will be logged and which will produce alerts. The audit log can be read by any AMT user with General Info permissions. The Auditor will keep track of the audit log and periodically clean it out (this is important because when the log becomes full it will prevent any new critical AMT events from occurring). To shut off auditing, the Auditor must configure the system for unprovisioning, which will then allow the Administrator to disable auditing.

Roll Over

The initial implementation of Audit Log did not allow the log to roll over. To ensure the Auditor had a chance to see all the events flagged as "critical", these events would not be allowed to run when the log was full. This was a security feature to ensure that a sneaky admin (or other user with sufficient privilege) would not be able to perform some improper activity and slip it by the Auditor because the log was full. However, this also created a situation where systems could be prevented from getting managed properly due to events being blocked by a full audit log.  If something happened to the Auditor (or group of people with Auditor permissions) that prevented them from cleaning the log, it could easily become full and block critical events. So starting with AMT 5.1, the feature was updated to provide a choice to users on how to configure their implementation of Access Monitor to allow the log to roll over when full. The following policies can now be set by the Auditor:

• No Roll Over: When full, critical events will fail and others won't be logged

• Roll Over: When full, overwrite the oldest

• Restricted Roll Over: Only overwrite if oldest are past given date

Security Monitoring by Default

Using the log to monitor for security reasons became popular aside from the auditing capability. Starting with AMT 8.0 the log is enabled by default with all Administrators having Auditor rights. By default several events will be logged and available for viewing. The original use of auditing can still be initiated by defining an Auditor.

Reference

To learn more about Audit Log, please downloadthe latest AMT SDK, read the documentation and try the sample. The sample provides code to run a fairly comprehensive API test as well as examples to enable auditing, manipulate the audit policy, manipulate the audit log, view the audit log, clear the audit log, unprovision auditing, add an auditor, and cleanup the sample stuff from your system. When building the sample be sure to view the readme. I found out that I needed to install a root certificate on my management console system to be able to successfully run all the samples.

If you would like to be able to keep track of things happening on your AMT system, independent of your Administrator, you probably want to use the Audit Log feature.

하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노하나카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 아라비안카지노

엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노엠카지노 ♣♣♣【ＡNＨ8９9、c0ℳ】♣♣♣ 엠카지노