ISE 1.2 and Posture Report Before Login

Hi everyone,
Is it possible for the ISE 1.2 NAC/Posture agent to submit a posture report before user login on a Windows desktop system?
We're trialling ISE 1.2, performing machine based authentication using EAP-TLS/Certificates. On top of this we are also using the posture agent and do not grant access until a 'compliant' posture report is received.
Currently when a desktop powers up the posture status is 'pending' and this does not change until the user logs in, the NAC agent submits a successful posture report. This can take quite a few minutes leaving the user in a state of limbo where they have logged in to the computer but they must wait for the posture report.
I see the NacAgent service runs as system, but the NACAgentUI.exe does not and only starts with the user logs in.
Thanks,
Mark

That is correct, the nac agent is unaware of what policies exist in your ISE design. It's sole purpose is to start when the services allow it to do so and then send the information about the services and AV information it can gather so ISE can make a decision on whether the client is compliant or not compliant, it can then take direction on how to remeidate the client when it fails. There is nothing you can configure from ISE that will allow you to run the nac agent before user login.
In the end when the nac agent makes into the anyconnect secure mobility client you might have hope there since there are some start before login vpn features, but I do not see the nac agent adopting this any time soon. You should however still work with your Cisco Account team on doing some research with the BU on your behalf, this could benefit alot of nac customers.
thanks,
Tarik Admani
*Please rate helpful posts*

Similar Messages

  • GDM displays only a black screen and a cursor, before login screen

    I'm using the xf86-video-ati driver for an R9 270, and GDM (v3.16.1.1) only shows a black screen with cursor. I can run TWM fine with startx, and I've got 2 displays attached via DVI.
    Here's my Xorg.0.log:
    [ 2.743]
    X.Org X Server 1.17.1
    Release Date: 2015-02-10
    [ 2.743] X Protocol Version 11, Revision 0
    [ 2.743] Build Operating System: Linux 3.19.2-1-ARCH x86_64
    [ 2.743] Current Operating System: Linux spitfire 3.19.3-3-ARCH #1 SMP PREEMPT Wed Apr 8 14:10:00 CEST 2015 x86_64
    [ 2.743] Kernel command line: initrd=\initramfs-linux.img root=/dev/sda2 rw nomodeset
    [ 2.743] Build Date: 14 April 2015 10:34:18AM
    [ 2.743]
    [ 2.743] Current version of pixman: 0.32.6
    [ 2.743] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 2.743] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 2.743] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Apr 29 02:52:10 2015
    [ 2.744] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 2.744] (==) No Layout section. Using the first Screen section.
    [ 2.745] (==) No screen section available. Using defaults.
    [ 2.745] (**) |-->Screen "Default Screen Section" (0)
    [ 2.745] (**) | |-->Monitor "<default monitor>"
    [ 2.745] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 2.745] (==) Automatically adding devices
    [ 2.745] (==) Automatically enabling devices
    [ 2.745] (==) Automatically adding GPU devices
    [ 2.748] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 2.748] Entry deleted from font path.
    [ 2.748] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 2.748] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 2.748] Entry deleted from font path.
    [ 2.752] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/100dpi/,
    /usr/share/fonts/75dpi/
    [ 2.752] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 2.752] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 2.753] (II) Loader magic: 0x815d80
    [ 2.753] (II) Module ABI versions:
    [ 2.753] X.Org ANSI C Emulation: 0.4
    [ 2.753] X.Org Video Driver: 19.0
    [ 2.753] X.Org XInput driver : 21.0
    [ 2.753] X.Org Server Extension : 9.0
    [ 2.754] (II) systemd-logind: took control of session /org/freedesktop/login1/session/c2
    [ 2.754] (--) PCI:*(0:1:0:0) 1002:6811:1458:226c rev 0, Mem @ 0xd0000000/268435456, 0xefe00000/262144, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072
    [ 2.754] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 2.755] (II) LoadModule: "glx"
    [ 2.755] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 2.758] (II) Module glx: vendor="X.Org Foundation"
    [ 2.758] compiled for 1.17.1, module version = 1.0.0
    [ 2.758] ABI class: X.Org Server Extension, version 9.0
    [ 2.758] (==) AIGLX enabled
    [ 2.758] (==) Matched ati as autoconfigured driver 0
    [ 2.758] (==) Matched modesetting as autoconfigured driver 1
    [ 2.758] (==) Matched fbdev as autoconfigured driver 2
    [ 2.758] (==) Matched vesa as autoconfigured driver 3
    [ 2.758] (==) Assigned the driver to the xf86ConfigLayout
    [ 2.758] (II) LoadModule: "ati"
    [ 2.758] (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so
    [ 2.758] (II) Module ati: vendor="X.Org Foundation"
    [ 2.758] compiled for 1.17.0, module version = 7.5.0
    [ 2.758] Module class: X.Org Video Driver
    [ 2.758] ABI class: X.Org Video Driver, version 19.0
    [ 2.758] (II) LoadModule: "radeon"
    [ 2.758] (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so
    [ 2.761] (II) Module radeon: vendor="X.Org Foundation"
    [ 2.761] compiled for 1.17.0, module version = 7.5.0
    [ 2.761] Module class: X.Org Video Driver
    [ 2.761] ABI class: X.Org Video Driver, version 19.0
    [ 2.761] (II) LoadModule: "modesetting"
    [ 2.761] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
    [ 2.761] (II) Module modesetting: vendor="X.Org Foundation"
    [ 2.761] compiled for 1.17.1, module version = 1.17.1
    [ 2.761] Module class: X.Org Video Driver
    [ 2.761] ABI class: X.Org Video Driver, version 19.0
    [ 2.761] (II) LoadModule: "fbdev"
    [ 2.761] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
    [ 2.762] (II) Module fbdev: vendor="X.Org Foundation"
    [ 2.762] compiled for 1.17.0, module version = 0.4.4
    [ 2.762] Module class: X.Org Video Driver
    [ 2.762] ABI class: X.Org Video Driver, version 19.0
    [ 2.762] (II) LoadModule: "vesa"
    [ 2.762] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    [ 2.762] (II) Module vesa: vendor="X.Org Foundation"
    [ 2.762] compiled for 1.17.0, module version = 2.3.2
    [ 2.762] Module class: X.Org Video Driver
    [ 2.762] ABI class: X.Org Video Driver, version 19.0
    [ 2.762] (II) RADEON: Driver for ATI Radeon chipsets:
    ATI Radeon Mobility X600 (M24) 3150 (PCIE), ATI FireMV 2400 (PCI),
    ATI Radeon Mobility X300 (M24) 3152 (PCIE),
    ATI FireGL M24 GL 3154 (PCIE), ATI FireMV 2400 3155 (PCI),
    ATI Radeon X600 (RV380) 3E50 (PCIE),
    ATI FireGL V3200 (RV380) 3E54 (PCIE), ATI Radeon IGP320 (A3) 4136,
    ATI Radeon IGP330/340/350 (A4) 4137, ATI Radeon 9500 AD (AGP),
    ATI Radeon 9500 AE (AGP), ATI Radeon 9600TX AF (AGP),
    ATI FireGL Z1 AG (AGP), ATI Radeon 9800SE AH (AGP),
    ATI Radeon 9800 AI (AGP), ATI Radeon 9800 AJ (AGP),
    ATI FireGL X2 AK (AGP), ATI Radeon 9600 AP (AGP),
    ATI Radeon 9600SE AQ (AGP), ATI Radeon 9600XT AR (AGP),
    ATI Radeon 9600 AS (AGP), ATI FireGL T2 AT (AGP), ATI Radeon 9650,
    ATI FireGL RV360 AV (AGP), ATI Radeon 7000 IGP (A4+) 4237,
    ATI Radeon 8500 AIW BB (AGP), ATI Radeon IGP320M (U1) 4336,
    ATI Radeon IGP330M/340M/350M (U2) 4337,
    ATI Radeon Mobility 7000 IGP 4437, ATI Radeon 9000/PRO If (AGP/PCI),
    ATI Radeon 9000 Ig (AGP/PCI), ATI Radeon X800 (R420) JH (AGP),
    ATI Radeon X800PRO (R420) JI (AGP),
    ATI Radeon X800SE (R420) JJ (AGP), ATI Radeon X800 (R420) JK (AGP),
    ATI Radeon X800 (R420) JL (AGP), ATI FireGL X3 (R420) JM (AGP),
    ATI Radeon Mobility 9800 (M18) JN (AGP),
    ATI Radeon X800 SE (R420) (AGP), ATI Radeon X800XT (R420) JP (AGP),
    ATI Radeon X800 VE (R420) JT (AGP), ATI Radeon X850 (R480) (AGP),
    ATI Radeon X850 XT (R480) (AGP), ATI Radeon X850 SE (R480) (AGP),
    ATI Radeon X850 PRO (R480) (AGP), ATI Radeon X850 XT PE (R480) (AGP),
    ATI Radeon Mobility M7 LW (AGP),
    ATI Mobility FireGL 7800 M7 LX (AGP),
    ATI Radeon Mobility M6 LY (AGP), ATI Radeon Mobility M6 LZ (AGP),
    ATI FireGL Mobility 9000 (M9) Ld (AGP),
    ATI Radeon Mobility 9000 (M9) Lf (AGP),
    ATI Radeon Mobility 9000 (M9) Lg (AGP), ATI FireMV 2400 PCI,
    ATI Radeon 9700 Pro ND (AGP), ATI Radeon 9700/9500Pro NE (AGP),
    ATI Radeon 9600TX NF (AGP), ATI FireGL X1 NG (AGP),
    ATI Radeon 9800PRO NH (AGP), ATI Radeon 9800 NI (AGP),
    ATI FireGL X2 NK (AGP), ATI Radeon 9800XT NJ (AGP),
    ATI Radeon Mobility 9600/9700 (M10/M11) NP (AGP),
    ATI Radeon Mobility 9600 (M10) NQ (AGP),
    ATI Radeon Mobility 9600 (M11) NR (AGP),
    ATI Radeon Mobility 9600 (M10) NS (AGP),
    ATI FireGL Mobility T2 (M10) NT (AGP),
    ATI FireGL Mobility T2e (M11) NV (AGP), ATI Radeon QD (AGP),
    ATI Radeon QE (AGP), ATI Radeon QF (AGP), ATI Radeon QG (AGP),
    ATI FireGL 8700/8800 QH (AGP), ATI Radeon 8500 QL (AGP),
    ATI Radeon 9100 QM (AGP), ATI Radeon 7500 QW (AGP/PCI),
    ATI Radeon 7500 QX (AGP/PCI), ATI Radeon VE/7000 QY (AGP/PCI),
    ATI Radeon VE/7000 QZ (AGP/PCI), ATI ES1000 515E (PCI),
    ATI Radeon Mobility X300 (M22) 5460 (PCIE),
    ATI Radeon Mobility X600 SE (M24C) 5462 (PCIE),
    ATI FireGL M22 GL 5464 (PCIE), ATI Radeon X800 (R423) UH (PCIE),
    ATI Radeon X800PRO (R423) UI (PCIE),
    ATI Radeon X800LE (R423) UJ (PCIE),
    ATI Radeon X800SE (R423) UK (PCIE),
    ATI Radeon X800 XTP (R430) (PCIE), ATI Radeon X800 XL (R430) (PCIE),
    ATI Radeon X800 SE (R430) (PCIE), ATI Radeon X800 (R430) (PCIE),
    ATI FireGL V7100 (R423) (PCIE), ATI FireGL V5100 (R423) UQ (PCIE),
    ATI FireGL unknown (R423) UR (PCIE),
    ATI FireGL unknown (R423) UT (PCIE),
    ATI Mobility FireGL V5000 (M26) (PCIE),
    ATI Mobility FireGL V5000 (M26) (PCIE),
    ATI Mobility Radeon X700 XL (M26) (PCIE),
    ATI Mobility Radeon X700 (M26) (PCIE),
    ATI Mobility Radeon X700 (M26) (PCIE),
    ATI Radeon X550XTX 5657 (PCIE), ATI Radeon 9100 IGP (A5) 5834,
    ATI Radeon Mobility 9100 IGP (U3) 5835,
    ATI Radeon XPRESS 200 5954 (PCIE),
    ATI Radeon XPRESS 200M 5955 (PCIE), ATI Radeon 9250 5960 (AGP),
    ATI Radeon 9200 5961 (AGP), ATI Radeon 9200 5962 (AGP),
    ATI Radeon 9200SE 5964 (AGP), ATI FireMV 2200 (PCI),
    ATI ES1000 5969 (PCI), ATI Radeon XPRESS 200 5974 (PCIE),
    ATI Radeon XPRESS 200M 5975 (PCIE),
    ATI Radeon XPRESS 200 5A41 (PCIE),
    ATI Radeon XPRESS 200M 5A42 (PCIE),
    ATI Radeon XPRESS 200 5A61 (PCIE),
    ATI Radeon XPRESS 200M 5A62 (PCIE),
    ATI Radeon X300 (RV370) 5B60 (PCIE),
    ATI Radeon X600 (RV370) 5B62 (PCIE),
    ATI Radeon X550 (RV370) 5B63 (PCIE),
    ATI FireGL V3100 (RV370) 5B64 (PCIE),
    ATI FireMV 2200 PCIE (RV370) 5B65 (PCIE),
    ATI Radeon Mobility 9200 (M9+) 5C61 (AGP),
    ATI Radeon Mobility 9200 (M9+) 5C63 (AGP),
    ATI Mobility Radeon X800 XT (M28) (PCIE),
    ATI Mobility FireGL V5100 (M28) (PCIE),
    ATI Mobility Radeon X800 (M28) (PCIE), ATI Radeon X850 5D4C (PCIE),
    ATI Radeon X850 XT PE (R480) (PCIE),
    ATI Radeon X850 SE (R480) (PCIE), ATI Radeon X850 PRO (R480) (PCIE),
    ATI unknown Radeon / FireGL (R480) 5D50 (PCIE),
    ATI Radeon X850 XT (R480) (PCIE),
    ATI Radeon X800XT (R423) 5D57 (PCIE),
    ATI FireGL V5000 (RV410) (PCIE), ATI Radeon X700 XT (RV410) (PCIE),
    ATI Radeon X700 PRO (RV410) (PCIE),
    ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X700 (RV410) (PCIE),
    ATI Radeon X700 SE (RV410) (PCIE), ATI Radeon X1800,
    ATI Mobility Radeon X1800 XT, ATI Mobility Radeon X1800,
    ATI Mobility FireGL V7200, ATI FireGL V7200, ATI FireGL V5300,
    ATI Mobility FireGL V7100, ATI Radeon X1800, ATI Radeon X1800,
    ATI Radeon X1800, ATI Radeon X1800, ATI Radeon X1800,
    ATI FireGL V7300, ATI FireGL V7350, ATI Radeon X1600, ATI RV505,
    ATI Radeon X1300/X1550, ATI Radeon X1550, ATI M54-GL,
    ATI Mobility Radeon X1400, ATI Radeon X1300/X1550,
    ATI Radeon X1550 64-bit, ATI Mobility Radeon X1300,
    ATI Mobility Radeon X1300, ATI Mobility Radeon X1300,
    ATI Mobility Radeon X1300, ATI Radeon X1300, ATI Radeon X1300,
    ATI RV505, ATI RV505, ATI FireGL V3300, ATI FireGL V3350,
    ATI Radeon X1300, ATI Radeon X1550 64-bit, ATI Radeon X1300/X1550,
    ATI Radeon X1600, ATI Radeon X1300/X1550, ATI Mobility Radeon X1450,
    ATI Radeon X1300/X1550, ATI Mobility Radeon X2300,
    ATI Mobility Radeon X2300, ATI Mobility Radeon X1350,
    ATI Mobility Radeon X1350, ATI Mobility Radeon X1450,
    ATI Radeon X1300, ATI Radeon X1550, ATI Mobility Radeon X1350,
    ATI FireMV 2250, ATI Radeon X1550 64-bit, ATI Radeon X1600,
    ATI Radeon X1650, ATI Radeon X1600, ATI Radeon X1600,
    ATI Mobility FireGL V5200, ATI Mobility Radeon X1600,
    ATI Radeon X1650, ATI Radeon X1650, ATI Radeon X1600,
    ATI Radeon X1300 XT/X1600 Pro, ATI FireGL V3400,
    ATI Mobility FireGL V5250, ATI Mobility Radeon X1700,
    ATI Mobility Radeon X1700 XT, ATI FireGL V5200,
    ATI Mobility Radeon X1700, ATI Radeon X2300HD,
    ATI Mobility Radeon HD 2300, ATI Mobility Radeon HD 2300,
    ATI Radeon X1950, ATI Radeon X1900, ATI Radeon X1950,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI Radeon X1900, ATI Radeon X1900, ATI Radeon X1900,
    ATI AMD Stream Processor, ATI Radeon X1900, ATI Radeon X1950,
    ATI RV560, ATI RV560, ATI Mobility Radeon X1900, ATI RV560,
    ATI Radeon X1950 GT, ATI RV570, ATI RV570, ATI FireGL V7400,
    ATI RV560, ATI Radeon X1650, ATI Radeon X1650, ATI RV560,
    ATI Radeon 9100 PRO IGP 7834, ATI Radeon Mobility 9200 IGP 7835,
    ATI Radeon X1200, ATI Radeon X1200, ATI Radeon X1200,
    ATI Radeon X1200, ATI Radeon X1200, ATI RS740, ATI RS740M, ATI RS740,
    ATI RS740M, ATI Radeon HD 2900 XT, ATI Radeon HD 2900 XT,
    ATI Radeon HD 2900 XT, ATI Radeon HD 2900 Pro, ATI Radeon HD 2900 GT,
    ATI FireGL V8650, ATI FireGL V8600, ATI FireGL V7600,
    ATI Radeon 4800 Series, ATI Radeon HD 4870 x2,
    ATI Radeon 4800 Series, ATI Radeon HD 4850 x2,
    ATI FirePro V8750 (FireGL), ATI FirePro V7760 (FireGL),
    ATI Mobility RADEON HD 4850, ATI Mobility RADEON HD 4850 X2,
    ATI Radeon 4800 Series, ATI FirePro RV770, AMD FireStream 9270,
    AMD FireStream 9250, ATI FirePro V8700 (FireGL),
    ATI Mobility RADEON HD 4870, ATI Mobility RADEON M98,
    ATI Mobility RADEON HD 4870, ATI Radeon 4800 Series,
    ATI Radeon 4800 Series, ATI FirePro M7750, ATI M98, ATI M98, ATI M98,
    ATI Mobility Radeon HD 4650, ATI Radeon RV730 (AGP),
    ATI Mobility Radeon HD 4670, ATI FirePro M5750,
    ATI Mobility Radeon HD 4670, ATI Radeon RV730 (AGP),
    ATI RV730XT [Radeon HD 4670], ATI RADEON E4600,
    ATI Radeon HD 4600 Series, ATI RV730 PRO [Radeon HD 4650],
    ATI FirePro V7750 (FireGL), ATI FirePro V5700 (FireGL),
    ATI FirePro V3750 (FireGL), ATI Mobility Radeon HD 4830,
    ATI Mobility Radeon HD 4850, ATI FirePro M7740, ATI RV740,
    ATI Radeon HD 4770, ATI Radeon HD 4700 Series, ATI Radeon HD 4770,
    ATI FirePro M5750, ATI RV610, ATI Radeon HD 2400 XT,
    ATI Radeon HD 2400 Pro, ATI Radeon HD 2400 PRO AGP, ATI FireGL V4000,
    ATI RV610, ATI Radeon HD 2350, ATI Mobility Radeon HD 2400 XT,
    ATI Mobility Radeon HD 2400, ATI RADEON E2400, ATI RV610,
    ATI FireMV 2260, ATI RV670, ATI Radeon HD3870,
    ATI Mobility Radeon HD 3850, ATI Radeon HD3850,
    ATI Mobility Radeon HD 3850 X2, ATI RV670,
    ATI Mobility Radeon HD 3870, ATI Mobility Radeon HD 3870 X2,
    ATI Radeon HD3870 X2, ATI FireGL V7700, ATI Radeon HD3850,
    ATI Radeon HD3690, AMD Firestream 9170, ATI Radeon HD 4550,
    ATI Radeon RV710, ATI Radeon RV710, ATI Radeon RV710,
    ATI Radeon HD 4350, ATI Mobility Radeon 4300 Series,
    ATI Mobility Radeon 4500 Series, ATI Mobility Radeon 4500 Series,
    ATI FirePro RG220, ATI Mobility Radeon 4330, ATI RV630,
    ATI Mobility Radeon HD 2600, ATI Mobility Radeon HD 2600 XT,
    ATI Radeon HD 2600 XT AGP, ATI Radeon HD 2600 Pro AGP,
    ATI Radeon HD 2600 XT, ATI Radeon HD 2600 Pro, ATI Gemini RV630,
    ATI Gemini Mobility Radeon HD 2600 XT, ATI FireGL V5600,
    ATI FireGL V3600, ATI Radeon HD 2600 LE,
    ATI Mobility FireGL Graphics Processor, ATI Radeon HD 3470,
    ATI Mobility Radeon HD 3430, ATI Mobility Radeon HD 3400 Series,
    ATI Radeon HD 3450, ATI Radeon HD 3450, ATI Radeon HD 3430,
    ATI Radeon HD 3450, ATI FirePro V3700, ATI FireMV 2450,
    ATI FireMV 2260, ATI FireMV 2260, ATI Radeon HD 3600 Series,
    ATI Radeon HD 3650 AGP, ATI Radeon HD 3600 PRO,
    ATI Radeon HD 3600 XT, ATI Radeon HD 3600 PRO,
    ATI Mobility Radeon HD 3650, ATI Mobility Radeon HD 3670,
    ATI Mobility FireGL V5700, ATI Mobility FireGL V5725,
    ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
    ATI Radeon HD 3200 Graphics, ATI Radeon 3100 Graphics,
    ATI Radeon HD 3300 Graphics, ATI Radeon HD 3200 Graphics,
    ATI Radeon 3000 Graphics, SUMO, SUMO, SUMO2, SUMO2, SUMO2, SUMO2,
    SUMO, SUMO, SUMO2, SUMO, SUMO, SUMO, SUMO, SUMO, ATI Radeon HD 4200,
    ATI Radeon 4100, ATI Mobility Radeon HD 4200,
    ATI Mobility Radeon 4100, ATI Radeon HD 4290, ATI Radeon HD 4250,
    AMD Radeon HD 6310 Graphics, AMD Radeon HD 6310 Graphics,
    AMD Radeon HD 6250 Graphics, AMD Radeon HD 6250 Graphics,
    AMD Radeon HD 6300 Series Graphics,
    AMD Radeon HD 6200 Series Graphics, PALM, PALM, PALM, CYPRESS,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, AMD Firestream 9370,
    AMD Firestream 9350, ATI Radeon HD 5800 Series,
    ATI Radeon HD 5800 Series, ATI Radeon HD 5800 Series,
    ATI Radeon HD 5800 Series, ATI Radeon HD 5900 Series,
    ATI Radeon HD 5900 Series, ATI Mobility Radeon HD 5800 Series,
    ATI Mobility Radeon HD 5800 Series,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI Mobility Radeon HD 5800 Series, ATI Radeon HD 5700 Series,
    ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
    ATI Radeon HD 5700 Series, ATI Radeon HD 6700 Series,
    ATI Mobility Radeon HD 5000 Series,
    ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon HD 5570,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, ATI Radeon HD 5670,
    ATI Radeon HD 5570, ATI Radeon HD 5500 Series, REDWOOD,
    ATI Mobility Radeon HD 5000 Series,
    ATI Mobility Radeon HD 5000 Series, ATI Mobility Radeon Graphics,
    ATI Mobility Radeon Graphics, CEDAR,
    ATI FirePro (FireGL) Graphics Adapter,
    ATI FirePro (FireGL) Graphics Adapter, ATI FirePro 2270, CEDAR,
    ATI Radeon HD 5450, CEDAR, CEDAR, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
    CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN, CAYMAN,
    AMD Radeon HD 6900 Series, AMD Radeon HD 6900 Series, CAYMAN, CAYMAN,
    CAYMAN, AMD Radeon HD 6900M Series, Mobility Radeon HD 6000 Series,
    BARTS, BARTS, Mobility Radeon HD 6000 Series,
    Mobility Radeon HD 6000 Series, BARTS, BARTS, BARTS, BARTS,
    AMD Radeon HD 6800 Series, AMD Radeon HD 6800 Series,
    AMD Radeon HD 6700 Series, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS, TURKS,
    CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS,
    CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, CAICOS, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, ARUBA,
    ARUBA, ARUBA, ARUBA, ARUBA, ARUBA, TAHITI, TAHITI, TAHITI, TAHITI,
    TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI, TAHITI,
    TAHITI, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
    PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN, PITCAIRN,
    VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
    VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE, VERDE,
    VERDE, VERDE, VERDE, VERDE, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND,
    OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND, OLAND,
    HAINAN, HAINAN, HAINAN, HAINAN, HAINAN, HAINAN, BONAIRE, BONAIRE,
    BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE, BONAIRE,
    BONAIRE, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
    KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI, KABINI,
    KABINI, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS,
    MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS, MULLINS,
    MULLINS, MULLINS, MULLINS, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
    KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
    KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI, KAVERI,
    KAVERI, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII, HAWAII,
    HAWAII, HAWAII, HAWAII, HAWAII, HAWAII
    [ 2.776] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
    [ 2.776] (II) FBDEV: driver for framebuffer: fbdev
    [ 2.776] (II) VESA: driver for VESA chipsets: vesa
    [ 2.776] (++) using VT number 1
    [ 2.776] (II) [KMS] drm report modesetting isn't supported.
    [ 2.776] (EE) open /dev/dri/card0: No such file or directory
    [ 2.776] (WW) Falling back to old probe method for modesetting
    [ 2.776] (EE) open /dev/dri/card0: No such file or directory
    [ 2.776] (II) Loading sub module "fbdevhw"
    [ 2.776] (II) LoadModule: "fbdevhw"
    [ 2.776] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so
    [ 2.777] (II) Module fbdevhw: vendor="X.Org Foundation"
    [ 2.777] compiled for 1.17.1, module version = 0.0.2
    [ 2.777] ABI class: X.Org Video Driver, version 19.0
    [ 2.777] (**) FBDEV(2): claimed PCI slot 1@0:0:0
    [ 2.777] (II) FBDEV(2): using default device
    [ 2.777] (WW) Falling back to old probe method for vesa
    [ 2.777] (EE) Screen 0 deleted because of no matching config section.
    [ 2.777] (II) UnloadModule: "radeon"
    [ 2.777] (EE) Screen 0 deleted because of no matching config section.
    [ 2.777] (II) UnloadModule: "modesetting"
    [ 2.777] (II) FBDEV(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 2.777] (==) FBDEV(0): Depth 24, (==) framebuffer bpp 32
    [ 2.777] (==) FBDEV(0): RGB weight 888
    [ 2.777] (==) FBDEV(0): Default visual is TrueColor
    [ 2.777] (==) FBDEV(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 2.777] (II) FBDEV(0): hardware: EFI VGA (video memory: 3072kB)
    [ 2.777] (II) FBDEV(0): checking modes against framebuffer device...
    [ 2.777] (II) FBDEV(0): checking modes against monitor...
    [ 2.777] (--) FBDEV(0): Virtual size is 1024x768 (pitch 1024)
    [ 2.777] (**) FBDEV(0): Built-in mode "current": 78.7 MHz, 59.9 kHz, 75.7 Hz
    [ 2.777] (II) FBDEV(0): Modeline "current"x0.0 78.65 1024 1056 1184 1312 768 772 776 792 -hsync -vsync -csync (59.9 kHz b)
    [ 2.777] (==) FBDEV(0): DPI set to (96, 96)
    [ 2.777] (II) Loading sub module "fb"
    [ 2.777] (II) LoadModule: "fb"
    [ 2.777] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 2.778] (II) Module fb: vendor="X.Org Foundation"
    [ 2.778] compiled for 1.17.1, module version = 1.0.0
    [ 2.778] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2.778] (**) FBDEV(0): using shadow framebuffer
    [ 2.778] (II) Loading sub module "shadow"
    [ 2.778] (II) LoadModule: "shadow"
    [ 2.778] (II) Loading /usr/lib/xorg/modules/libshadow.so
    [ 2.779] (II) Module shadow: vendor="X.Org Foundation"
    [ 2.779] compiled for 1.17.1, module version = 1.1.0
    [ 2.779] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 2.779] (II) UnloadModule: "vesa"
    [ 2.779] (II) Unloading vesa
    [ 2.779] (==) Depth 24 pixmap format is 32 bpp
    [ 2.779] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    [ 2.781] (==) FBDEV(0): Backing store enabled
    [ 2.782] (==) FBDEV(0): DPMS enabled
    [ 2.782] (==) RandR enabled
    [ 2.786] (II) AIGLX: Screen 0 is not DRI2 capable
    [ 2.786] (EE) AIGLX: reverting to software rendering
    [ 2.874] (II) AIGLX: Loaded and initialized swrast
    [ 2.874] (II) GLX: Initialized DRISWRAST GL provider for screen 0
    [ 2.932] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 2.932] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2.932] (**) Power Button: Applying InputClass "libinput keyboard catchall"
    [ 2.932] (II) LoadModule: "libinput"
    [ 2.932] (II) Loading /usr/lib/xorg/modules/input/libinput_drv.so
    [ 2.933] (II) Module libinput: vendor="X.Org Foundation"
    [ 2.933] compiled for 1.17.1, module version = 0.9.0
    [ 2.933] Module class: X.Org XInput Driver
    [ 2.933] ABI class: X.Org XInput driver, version 21.0
    [ 2.933] (II) systemd-logind: got fd for /dev/input/event2 13:66 fd 14 paused 0
    [ 2.933] (II) Using input driver 'libinput' for 'Power Button'
    [ 2.933] (**) Power Button: always reports core events
    [ 2.933] (**) Option "Device" "/dev/input/event2"
    [ 2.934] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
    [ 2.934] (II) input device 'Power Button', /dev/input/event2 is a keyboard
    [ 2.934] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input4/event2"
    [ 2.934] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 2.934] (II) input device 'Power Button', /dev/input/event2 is tagged by udev as: Keyboard
    [ 2.934] (II) input device 'Power Button', /dev/input/event2 is a keyboard
    [ 2.934] (II) config/udev: Adding input device Power Button (/dev/input/event0)
    [ 2.934] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 2.934] (**) Power Button: Applying InputClass "libinput keyboard catchall"
    [ 2.934] (II) systemd-logind: got fd for /dev/input/event0 13:64 fd 17 paused 0
    [ 2.934] (II) Using input driver 'libinput' for 'Power Button'
    [ 2.934] (**) Power Button: always reports core events
    [ 2.934] (**) Option "Device" "/dev/input/event0"
    [ 2.934] (II) input device 'Power Button', /dev/input/event0 is tagged by udev as: Keyboard
    [ 2.934] (II) input device 'Power Button', /dev/input/event0 is a keyboard
    [ 2.934] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event0"
    [ 2.934] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 2.935] (II) input device 'Power Button', /dev/input/event0 is tagged by udev as: Keyboard
    [ 2.935] (II) input device 'Power Button', /dev/input/event0 is a keyboard
    [ 2.935] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
    [ 2.935] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 2.935] (**) Sleep Button: Applying InputClass "libinput keyboard catchall"
    [ 2.935] (II) systemd-logind: got fd for /dev/input/event1 13:65 fd 18 paused 0
    [ 2.935] (II) Using input driver 'libinput' for 'Sleep Button'
    [ 2.935] (**) Sleep Button: always reports core events
    [ 2.935] (**) Option "Device" "/dev/input/event1"
    [ 2.935] (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
    [ 2.935] (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
    [ 2.935] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input3/event1"
    [ 2.935] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
    [ 2.935] (II) input device 'Sleep Button', /dev/input/event1 is tagged by udev as: Keyboard
    [ 2.935] (II) input device 'Sleep Button', /dev/input/event1 is a keyboard
    [ 2.935] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=8 (/dev/input/event7)
    [ 2.935] (II) No input driver specified, ignoring this device.
    [ 2.935] (II) This device may have been added with another device file.
    [ 2.936] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=9 (/dev/input/event8)
    [ 2.936] (II) No input driver specified, ignoring this device.
    [ 2.936] (II) This device may have been added with another device file.
    [ 2.936] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=10 (/dev/input/event9)
    [ 2.936] (II) No input driver specified, ignoring this device.
    [ 2.936] (II) This device may have been added with another device file.
    [ 2.936] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=11 (/dev/input/event12)
    [ 2.936] (II) No input driver specified, ignoring this device.
    [ 2.936] (II) This device may have been added with another device file.
    [ 2.936] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=3 (/dev/input/event5)
    [ 2.936] (II) No input driver specified, ignoring this device.
    [ 2.936] (II) This device may have been added with another device file.
    [ 2.936] (II) config/udev: Adding input device HDA ATI HDMI HDMI/DP,pcm=7 (/dev/input/event6)
    [ 2.936] (II) No input driver specified, ignoring this device.
    [ 2.936] (II) This device may have been added with another device file.
    [ 2.936] (II) config/udev: Adding input device LOGITECH G110 G-keys (/dev/input/event4)
    [ 2.936] (**) LOGITECH G110 G-keys: Applying InputClass "evdev keyboard catchall"
    [ 2.936] (**) LOGITECH G110 G-keys: Applying InputClass "libinput keyboard catchall"
    [ 2.936] (II) systemd-logind: got fd for /dev/input/event4 13:68 fd 19 paused 0
    [ 2.936] (II) Using input driver 'libinput' for 'LOGITECH G110 G-keys'
    [ 2.936] (**) LOGITECH G110 G-keys: always reports core events
    [ 2.936] (**) Option "Device" "/dev/input/event4"
    [ 2.937] (II) input device 'LOGITECH G110 G-keys', /dev/input/event4 is tagged by udev as: Keyboard
    [ 2.937] (II) input device 'LOGITECH G110 G-keys', /dev/input/event4 is a keyboard
    [ 2.937] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-11/3-11.1/3-11.1:1.0/0003:046D:C22B.0001/input/input7/event4"
    [ 2.937] (II) XINPUT: Adding extended input device "LOGITECH G110 G-keys" (type: KEYBOARD, id 9)
    [ 2.937] (II) input device 'LOGITECH G110 G-keys', /dev/input/event4 is tagged by udev as: Keyboard
    [ 2.937] (II) input device 'LOGITECH G110 G-keys', /dev/input/event4 is a keyboard
    [ 2.937] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event10)
    [ 2.937] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
    [ 2.937] (**) Gaming Keyboard G110: Applying InputClass "libinput keyboard catchall"
    [ 2.937] (II) systemd-logind: got fd for /dev/input/event10 13:74 fd 20 paused 0
    [ 2.937] (II) Using input driver 'libinput' for 'Gaming Keyboard G110'
    [ 2.937] (**) Gaming Keyboard G110: always reports core events
    [ 2.937] (**) Option "Device" "/dev/input/event10"
    [ 2.937] (II) input device 'Gaming Keyboard G110', /dev/input/event10 is tagged by udev as: Keyboard
    [ 2.937] (II) input device 'Gaming Keyboard G110', /dev/input/event10 is a keyboard
    [ 2.937] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-11/3-11.3/3-11.3:1.0/0003:046D:C22A.0002/input/input22/event10"
    [ 2.937] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 10)
    [ 2.938] (II) input device 'Gaming Keyboard G110', /dev/input/event10 is tagged by udev as: Keyboard
    [ 2.938] (II) input device 'Gaming Keyboard G110', /dev/input/event10 is a keyboard
    [ 2.938] (II) config/udev: Adding input device Gaming Keyboard G110 (/dev/input/event20)
    [ 2.938] (**) Gaming Keyboard G110: Applying InputClass "evdev keyboard catchall"
    [ 2.938] (**) Gaming Keyboard G110: Applying InputClass "libinput keyboard catchall"
    [ 2.938] (II) systemd-logind: got fd for /dev/input/event20 13:84 fd 21 paused 0
    [ 2.938] (II) Using input driver 'libinput' for 'Gaming Keyboard G110'
    [ 2.938] (**) Gaming Keyboard G110: always reports core events
    [ 2.938] (**) Option "Device" "/dev/input/event20"
    [ 2.938] (II) input device 'Gaming Keyboard G110', /dev/input/event20 is tagged by udev as: Keyboard
    [ 2.938] (II) input device 'Gaming Keyboard G110', /dev/input/event20 is a keyboard
    [ 2.938] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-11/3-11.3/3-11.3:1.1/0003:046D:C22A.0003/input/input23/event20"
    [ 2.938] (II) XINPUT: Adding extended input device "Gaming Keyboard G110" (type: KEYBOARD, id 11)
    [ 2.938] (II) input device 'Gaming Keyboard G110', /dev/input/event20 is tagged by udev as: Keyboard
    [ 2.938] (II) input device 'Gaming Keyboard G110', /dev/input/event20 is a keyboard
    [ 2.939] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event21)
    [ 2.939] (**) Logitech USB Receiver: Applying InputClass "evdev pointer catchall"
    [ 2.939] (**) Logitech USB Receiver: Applying InputClass "libinput pointer catchall"
    [ 2.990] (II) systemd-logind: got fd for /dev/input/event21 13:85 fd 22 paused 0
    [ 2.990] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
    [ 2.990] (**) Logitech USB Receiver: always reports core events
    [ 2.990] (**) Option "Device" "/dev/input/event21"
    [ 2.990] (II) input device 'Logitech USB Receiver', /dev/input/event21 is tagged by udev as: Mouse
    [ 2.990] (II) input device 'Logitech USB Receiver', /dev/input/event21 is a pointer caps
    [ 2.990] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-11/3-11.4/3-11.4:1.0/0003:046D:C52F.0004/input/input24/event21"
    [ 2.990] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 12)
    [ 2.990] (**) Option "AccelerationScheme" "none"
    [ 2.990] (**) Logitech USB Receiver: (accel) selected scheme none/0
    [ 2.990] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
    [ 2.990] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
    [ 2.990] (II) input device 'Logitech USB Receiver', /dev/input/event21 is tagged by udev as: Mouse
    [ 2.990] (II) input device 'Logitech USB Receiver', /dev/input/event21 is a pointer caps
    [ 2.990] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/mouse0)
    [ 2.990] (II) No input driver specified, ignoring this device.
    [ 2.990] (II) This device may have been added with another device file.
    [ 2.990] (II) config/udev: Adding input device Logitech USB Receiver (/dev/input/event22)
    [ 2.990] (**) Logitech USB Receiver: Applying InputClass "evdev keyboard catchall"
    [ 2.990] (**) Logitech USB Receiver: Applying InputClass "libinput keyboard catchall"
    [ 2.991] (II) systemd-logind: got fd for /dev/input/event22 13:86 fd 23 paused 0
    [ 2.991] (II) Using input driver 'libinput' for 'Logitech USB Receiver'
    [ 2.991] (**) Logitech USB Receiver: always reports core events
    [ 2.991] (**) Option "Device" "/dev/input/event22"
    [ 2.991] (II) input device 'Logitech USB Receiver', /dev/input/event22 is tagged by udev as: Keyboard
    [ 2.991] (II) input device 'Logitech USB Receiver', /dev/input/event22 is a keyboard
    [ 2.991] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb3/3-11/3-11.4/3-11.4:1.1/0003:046D:C52F.0005/input/input25/event22"
    [ 2.991] (II) XINPUT: Adding extended input device "Logitech USB Receiver" (type: MOUSE, id 13)
    [ 2.991] (**) Option "AccelerationScheme" "none"
    [ 2.991] (**) Logitech USB Receiver: (accel) selected scheme none/0
    [ 2.991] (**) Logitech USB Receiver: (accel) acceleration factor: 2.000
    [ 2.991] (**) Logitech USB Receiver: (accel) acceleration threshold: 4
    [ 2.991] (II) input device 'Logitech USB Receiver', /dev/input/event22 is tagged by udev as: Keyboard
    [ 2.991] (II) input device 'Logitech USB Receiver', /dev/input/event22 is a keyboard
    [ 2.991] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event11)
    [ 2.991] (II) No input driver specified, ignoring this device.
    [ 2.991] (II) This device may have been added with another device file.
    [ 2.992] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event13)
    [ 2.992] (II) No input driver specified, ignoring this device.
    [ 2.992] (II) This device may have been added with another device file.
    [ 2.992] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event14)
    [ 2.992] (II) No input driver specified, ignoring this device.
    [ 2.992] (II) This device may have been added with another device file.
    [ 2.992] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event15)
    [ 2.992] (II) No input driver specified, ignoring this device.
    [ 2.992] (II) This device may have been added with another device file.
    [ 2.992] (II) config/udev: Adding input device HDA Intel PCH Line Out Front (/dev/input/event16)
    [ 2.992] (II) No input driver specified, ignoring this device.
    [ 2.992] (II) This device may have been added with another device file.
    [ 2.992] (II) config/udev: Adding input device HDA Intel PCH Line Out Surround (/dev/input/event17)
    [ 2.992] (II) No input driver specified, ignoring this device.
    [ 2.992] (II) This device may have been added with another device file.
    [ 2.992] (II) config/udev: Adding input device HDA Intel PCH Line Out CLFE (/dev/input/event18)
    [ 2.992] (II) No input driver specified, ignoring this device.
    [ 2.992] (II) This device may have been added with another device file.
    [ 2.992] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event19)
    [ 2.992] (II) No input driver specified, ignoring this device.
    [ 2.992] (II) This device may have been added with another device file.
    [ 2.992] (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    [ 2.992] (II) No input driver specified, ignoring this device.
    [ 2.992] (II) This device may have been added with another device file.
    [ 2.993] (EE) FBDEV(0): FBIOBLANK: Invalid argument
    Output of lshw -c video:
    *-display
    description: VGA compatible controller
    product: Curacao PRO [Radeon R9 270]
    vendor: Advanced Micro Devices, Inc. [AMD/ATI]
    physical id: 0
    bus info: pci@0000:01:00.0
    version: 00
    width: 64 bits
    clock: 33MHz
    capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
    configuration: driver=radeon latency=0
    resources: irq:29 memory:d0000000-dfffffff memory:efe00000-efe3ffff ioport:e000(size=256) memory:efe40000-efe5ffff
    And the output of systemctl status gdm:
    ● gdm.service - GNOME Display Manager
    Loaded: loaded (/usr/lib/systemd/system/gdm.service; enabled; vendor preset: disabled)
    Active: active (running) since Wed 2015-04-29 03:30:42 AEST; 15min ago
    Main PID: 289 (gdm)
    CGroup: /system.slice/gdm.service
    └─289 /usr/bin/gdm
    Apr 29 03:30:42 spitfire systemd[1]: Starting GNOME Display Manager...
    Apr 29 03:30:42 spitfire systemd[1]: Started GNOME Display Manager.
    Apr 29 03:30:45 spitfire gdm[289]: GdmDisplay: display lasted 2.980133 seconds
    Apr 29 03:30:45 spitfire gdm[289]: Child process -311 was already dead.
    Apr 29 03:30:45 spitfire gdm[289]: Child process 303 was already dead.
    Apr 29 03:30:45 spitfire gdm[289]: Unable to kill session worker process
    Apr 29 03:30:45 spitfire gdm[289]: Child process 303 was already dead.
    Apr 29 03:30:45 spitfire gdm[289]: Unable to kill session worker process
    I don't know where the GDM logs are located, as the /var/log/gdm folder is empty. Newbie problems.
    If there are other logs that would help, please tell me and I'll add them. Thanks.
    Last edited by The6P4C (2015-04-28 09:53:14)

    The first is the audio codec, which is WM Std at 44.1kHz. WVP2 is the video codec and I have not heard of it. Nor seen it playback in QT assisted by Flip4mac so it may be unplayable.
    There are always listed one audio codec and one video codec in that box assuming there are audio and video in the clip, e.g. AAC 256 bit (audio) and H264 Simple Profile (video) in an iPod clip.
    Ooh bad news, from another source:
    +"It seems that the Flip4Mac WMV Player, which should provide the missing Windows Media support for Mac users (as endorsed by Microsoft) does not support all Windows Media codecs, namely *it refuses to play content encoded with the Windows Media Video 9 Image v2 (WVP2) codec.* "+

  • ISE with dot1x and Posture deployment in pararrel with certain users

    Hi,
    We want to deploy ISE in sequencial order, meaning that I will initially have all users authenticate/authorized with dot1x/MAB etc, then only on certain locations or users to have posture condition validation/verification while others not.
    Can someone please advise whether this approach is possible, as far I understand, once you have posture policies in place as authorization rule it will hit all the users. This may be possible where you can match the switch or the location as a seperate condition, but if all users are spread/mixed we just need to find a simple way how to do it or whether it is not possible..?

    We have modified the attached policy on rule 04 and 05 (from top) and add a new condition Device locationEqual "Switch1".According to this rule any user connected to Switch1 only do the posture and same user PCconnect any other switch (other than switch1), it should do only the dot1x/MAB (rule 1-3). But in our case user PC connect any other switch than switch1, it hit the ISE default policy(not included in this attachement) and also it pop-ups the NAC agent and do the posturing. Questions-why the PC/user is not hitting rule 1-3 and goes to default rule-why the PC/user is doing posture where there's no posture rule hitting.
    Hi,
    First of all, I would assume you configured the PC for machine or user authentication.
    So, when a user connects to the network using other switch but not switch1, it will get 2 hits:
    1. Computer authentication - this PC is part of Domain Computers
    2. Default rule - because you configured (domain) user authentication for dot1x requests that are received only from switch1!
    You haven't specified a rule for domain users alone (with no location condition) and with no posture.
    You have to add something like this:
    1. dot1x + Domain PC
    2. dot1x + Domain User + location + preposture
    3. dot1x + Domain User + location + posture compliant
    4. dot1x + Domain User (and no posture condition)
    To answer your second question, event though you 've excepted a certain user from posture, if NAC Agent is installed, it will popup and it will say that you're compliant, so practically it isn't doing posture
    (http://www.cisco.com/en/US/docs/security/ise/1.1/user_guide/ise_pos_pol.html)
    Generating a Posture Requirement The run-time services requests for the posture requirement for the  endpoint by looking up at the role to which the user belongs to and the  operating system on the client. If you do not have a policy associated  with the role, then the run-time services communicate to the NAC Agent  with an empty requirement. If you have a policy associated with the  role, then the run-time services run through the posture policies  through one or more requirements associated with the policies and for  each requirement through one or more conditions.
    If you want to rollout for posture, you could use exception rules (check the top section of authorization rules) or you could do only posture audit for your rules so that everyone can get network access event though they're not compliant.

  • Lately I have been getting a rectangular screen titled Login Setting, with my Username and Password and asking me to Login.  This screen shows up on opening the computer and has never been seen before the last month or so.

    Lately I have been getting a rectangular screen titled Login Setting, with my Username and Password and asking me to Login.  This screen shows up on opening the computer and has never been seen before the last month or so.  It has one box titled Login Credentials with a username and password field and a second box titled Login Status at the bottom where it says "Profile not found" in red.   I've never seen this before and ignoring it does not effect any operations.   Is this legitimate or some kind of identity fishing?

    Hello,
    Have you done the recent Security updates?
    Is this from Sleep or on bootup?
    Timing is about right for the FlashBack attack.
    Disable Java in your Browser settings, not JavaScript.
    http://support.apple.com/kb/HT5241?viewlocale=en_US
    http://support.google.com/chrome/bin/answer.py?hl=en-GB&answer=142064
    http://support.mozilla.org/en-US/kb/How%20to%20turn%20off%20Java%20applets
    Flashback - Detect and remove the uprising Mac OS X Trojan...
    http://www.mac-and-i.net/2012/04/flashback-detect-and-remove-uprising.html
    In order to avoid detection, the installer will first look for the presence of some antivirus tools and other utilities that might be present on a power user's system, which according to F-Secure include the following:
    /Library/Little Snitch
    /Developer/Applications/Xcode.app/Contents/MacOS/Xcode
    /Applications/VirusBarrier X6.app
    /Applications/iAntiVirus/iAntiVirus.app
    /Applications/avast!.app
    /Applications/ClamXav.app
    /Applications/HTTPScoop.app
    /Applications/Packet Peeper.app
    If these tools are found, then the malware deletes itself in an attempt to prevent detection by those who have the means and capability to do so. Many malware programs use this behavior, as was seen in others such as the Tsunami malware bot.
    http://reviews.cnet.com/8301-13727_7-57410096-263/how-to-remove-the-flashback-ma lware-from-os-x/
    http://x704.net/bbs/viewtopic.php?f=8&t=5844&p=70660#p70660
    The most current flashback removal instructions are F-Secure's Trojan-Downloader:OSX/Flashback.K.
    https://www.securelist.com/en/blog/208193454/Flashfake_Removal_Tool_and_online_c hecking_site
    More bad news...
    https://www.securelist.com/en/blog/208193467/SabPub_Mac_OS_X_Backdoor_Java_Explo its_Targeted_Attacks_and_Possible_APT_link

  • ISE 1.3 and Windows Posture Web Agent

    Hello,
    I am running ISE 1.3 and have an issue running the Posture Web Agent. The client authenticates and gets redirected to the client provisioning portal but get the following message
    Detecting if Web Agent is installed and running gets ticked and then it keeps rolling at scanning your device. Open Web Agent to check the current status of the system scan and update your system as instructed.
    See attached screen shot

    is this issue specific to particular groups of clients/OS type... if using Windows 8, Internet Explorer 10 has two modes: Desktop and Metro. In Metro mode, the ActiveX plugins are restricted. You cannot download the Cisco NAC Agent in Metro mode. You must switch to Desktop mode, ensure ActiveX controls are enabled, and then launch Internet Explorer to download the Cisco NAC Agent. (If users are still not able to download Cisco NAC agent, check and enable “compatibility mode.”)

  • 'Hierarchy Based Login' and 'Direct Reports' field in Dim - Position table

    Hello -
    I am trying to build a "My Team's" report, which basically shows the logged in Managers ( and his subordinates) revenues rolled up by default. Then the manager needs to drilldown on his name and see revenues grouped by his direct reports. I am using OBIEE 10G. In the out of the box RPD, there are two fields in the BMM layer called 'Hierarchy Based Login' and 'Direct Reports'.
    1. The 'Hierarchy based Login' field uses the INDEXCOL method to get relevant column from the W_POSITION_DH table based on the the Logged in users hierarchy level (the hierarchy level is stored in a session variable (HIER_LEVEL). This session variable works fine and i have tested the SQL)
    2. The 'Direct Reports' is using the same INDEXCOL method, just that it uses the formula HIER_LEVEL - 1. This works fine as well.
    The issue i am facing is neither of these out-of-the-box fields are assigned to the Position dimension (the position dimension also exists OOTB).
    So basically, i am able to create a manager and his direct subordinate report, but without any drill functionality.
    I am trying to get the report to drill all the way down to the bottom most level of the heirarchy.
    Any help to get this working is much appreciated

    What i meant was neither of these out-of-the box fields are assigned to a Dimension Hierarchy ( there is a hierarchy called 'Position' that already exists out-of-the box). Other fields in the 'Dim-Position' table are assigned to a level in this position hierarchy, except these two. I guess what i am trying to achieve is to dynamically assign the hierarchy level based on the users Hierachy level in W_POSITION_DH table.
    Thanks for spending time to look into my issue

  • Report server running in integrated mode , but cannot deploy reports again and again prompts for login

    Report server running in integrated mode , but cannot deploy reports again and again prompts for login
    Nur Mondal

    Hello,
    How are you deploying the reports? Via Visual Studio, Report builder or manually uploading RDL files?
    Paul
    Paul Mather | Twitter |
    http://pwmather.wordpress.com | CPS

  • Customized Email Content for Firefighter login and Log report

    Hi Experts,
    Is it possible to customize the email content (subject as well as body) for Firefoghter login and log report notifications. This is required on GRC AC 5.3 SP10.
    Thanks
    Davinder

    No, D P. You can not customize FF emails. They are hard coded in the ABAP programs.
    Alpesh

  • Wireless active and connected before login

    Hi,
    I have been trying to get wireless connected before I login into my Mac in order to be autheticated by Active Directory.
    As the MAC didn't come with an integrated LAN port i am only able to use the wireless connection.
    Thank you

    I'm trying to figure this out as well. I may have another step in the solution for you.
    In the network preference pane of system preferences click on Airport on the left.
    Click Advanced...
    Click on 802.1x at the top.
    Click the plus sign and then click Add Login Window Profile.
    This should allow you to create a 802.1x profile that will pre-authenticate with your Directory Service. (I'm working with Active Directory) I have left the username and password blank in the profile so that the user will be the one authenticating.
    My problem now is that it seems to pre-authenticate 802.1x for me but it says that the server's certificate is invalid. If I set 802.1x up for an individual user I can 'Always Trust' the certificate but I don't know how to do it at login.
    I'm testing this on a MacBook running 10.5.6

  • GT70 2PC – Software testing and performance report.

    It is so excited here again. Currently, my first/only object after work is playing Titanfall.
    I intended to share another performance testing today. But I didn’t. I found there are too many great open box posts on different forums. Therefore, I decide to dig the MSI software compatibility and do a touring. What can I say? I’m Mr.Curiosity who really desires to know every built-in application in system. That is why I share this article with you, my friends. I would like to discuss with everybody who is interested in MSI software. Of course, I have some performance reports for you, too. Please also remind me if you find any typo/wrong in this post. Thanks in advance.  
    1. MSI Boot Configure
        This is the first software which pops up immediately. It is thoughtful design because we can choose enter the [Windows 8.1 metro] or [desktop] by ourselves now. I give it two thumbs up!!!
    Select your favorite boot configuration and press [OK]. If we want it work immdiately, we can logout the system and re-login again.
    2.   MSI Remind Manager
    Honestly, I didn’t know what it is in the beginning. The cute robot shows every time when I login the system. I found this is a reminder for product registration. Good, I would like to have best MSI support and warranty for my lovely GT70 2PC. But don’t worry, if you don’t want to get this message again, you just need to select the right option and close it.
    3.   Synaptics TouchPad
    This is a driver for mouse. [Mouse property] will show if we do the double clicks on TouchPad icon in tray. You can choose enable/disable internal pointing device when external pointing device is attached. This is brilliant. A tough guy (like me…HA! HA!) didn’t like to play game with touchpad. Because the character in game will be weak and slow if I control it by touchpad. Of course, I need the external mouse all the time and don’t want the interference from touchpad.
    4.   System Control Manager (SCM)
    We can enable/disable the WLAN/BT/camera devices by SCM. Besides, it can control the display brightness, volume, screen on/off and ECO. ECO is special mode for gaming watching movie.  
    5.   Sound Blaster CINEMA
    Sound Blaster CINEMA is come from an old school audio company – CREATIVE. The software can adjust the surround sound easily. We also can adjust 5.1/7.1 surround sound for the internal speakers and external headphone. That is great, isn’t it?
    Besides, we can also adjust CRYSTALIZER/BASS/SMART VOLUME/digital output by ourselves.
    6.   Killer Network Manager
    This is a major feature of MSI NB.
    In Killer Network Manager, we can set the network priority for each of applications and we also can abandon the connection from malicious software.
    [Performance] shows current status of network. We can find out which application occupied the most greedy resources by it.
    [Network -> Test Network Speed] will detect the network environment automatically. Furthermore, it will adjust the priority for applications.
    [Killer Ethernet] show the LAN connection info.
    [Killer Wireless] show the router info.
    7.   SteelSeries Engine
    This is another major feature of MSI NB
    If we do the right click on icon in tray, the menu will show following list. We can select [Launch SteelSeries Firmware Update Tool], [Updates]…and so on.
    If we select the [Settings]. It can help us change default language and set application auto running when system power on.
    I.   Buttons
    Double click to open the SteelSeries Engine. I think it can set 4 different keyboard settings for each of profiles. And it can switch by FN+1~4.
    [Keypress Marc] can record what you input. And [Record Delays ] can modify the delay time. HA! No game can block us anymore. Please remember to press the [SAVE] for your setting
    [Launch Application] can launch any application immediately. I suggest to set the cold key for this function.
    Here is example. I use [PgUp] to quick start the 3D Mark11. See, it will pop up when I pressed [PgUp].
    It is simple to use [TextMarco] set our own phrase. Now I become a quick speaker in my team. One key, only one key can help me to type a lot of words.
    Are you tired to press some keys that you never want to touch in game (Like WIN KEY)? It is not the problem now.  [Disable Key] will do the favor and disable any key which you hate.
    II.   [Colors] can change the color of backlight keyboard. Also, you can set different modes (Gaming/Audio…etc) on it.
    We can change the color zone. There is not only 4 or 5 colors. The engine provides thousands of colors for us. [Audio mode] is the coolest. It will change colors by itself when we play music by speakers. I like to dance with my keyboard.
    III.   We can select different languages by [Settings].
    IV.   [Properties] can save our hard works of settings reliably.
    V.   If you want to defeat your competitors, it is important to know your enemy. However, It is more important to know yourself. [Statistics] can help us observe which keys are most popular by our fingers.
    Right click on [Profile]. It can modify/export/import/delete the profiles.
    Mouse can use the same kind of settings as keyboard.
    DPI setting for mouse.
    Save files.
    We can record the mouse, too.
    8.   Norton
    Norton Internet Security: Anti-Virus software, MSI provides 60 days for free.
    Norton Online Backup: Online data backup software, MSI provides 30 days for free.
    Norton Anti-Theft: Anti-Theft software, MSI provides 30 days for free.
    If you like Norton’s products, you can buy it online.
    If you don’t, I believe we can uninstall it directly.
    So, the decision is ours.
    Introduction from Norton official website
    9.   Dragon Gaming Center
    I.   System Monitor:
    It can monitor CPU/GPU loading and temperature. We also can find the network speed and fan speed in it.  
    II.   Utility:
    You can set your favorite apps in [Add new Utility].
    E.g. I added a [MSI Afterburner]. Click [Open] to build the link. Do you feel familiar with something? Exactly, [Launch Application] of [SteelSeries Engine] can do this, too.
    III.   Instant Play:
    We can define [Fn+F4] to enable the quick start. But there is more secret.
    We can also use [Browse] to assign the game which we want.  
    Click the icon of game and [Fn+F4] will be ready. We can only use 1 program at once.  
    I usually change the brightness, volume and mouse sensitive before the game. As you know, every games are different. It is sweet because we can use  [Apply Setting] to do this.
    I can’t believe it. We also can find the clock feature in it. How convenient it is!
    IV.   Hybrid Power is another MSI feature.
    It can provide the power by AC adapter and battery in the same time. We can monitor the status in here.
    10. BurnRecovery
    It can create the recovery CD/DVD/USB for MSI NB.
    Here can select Recovery disc/USB/ISO.
    I will make a ISO file first.
    We can select where to put the ISO.
    Creating the recovery file...
    Finish!
    Open the folder and we can find 4 ISO files in it.
    Well…[BurnRecovery Help] provide the details spec.
    In my opinion, everyone should create their own recovery image. You will need it in one day.
    11. Battery Calibration
    This is software for battery calibration. In order to keep our battery good, we should do the calibration every three months. Don’t forget to plug-in the AC adapter and battery during the process..
    Press [Start] to begin the process. It will make the battery fully charged first.
    Then, it will empty the battery like this.
    System will shut down after the empty process. At last, fully charged again. It will take 4~5 hrs to complete the process.
    12. MSI Dragoon Army /MSI Facebook /Web site /YouTube
    Those are MSI forums/Facebook/official website/YouTube and links.
    [MSI Dragoon Army] is the official forum for MSI. We can find NB, MB and AIO info in it.
    Facebook Quick Link for many countries of world.
    MSI official website
    YouTube channel of MSI.
    13. Super-Charger
    There is no message when I click this app at the first time. But when I attached my IPAD, it pops up the [Super-Charger]. It is amazing because IPAD can’t be charge by this USB port. As far as I know, the USB 3.0 only provides maximum 900mA for its device. IPAD will need 2.1A for charge process. I have no idea how MSI NB make IPAD charging okay.
    14. XSplit GameCaster
    This is one of important features. I saw many different first class gaming machines this year. All of them have the broadcast software. (Like PS4, Xbos ONE)
    It can switch the default language after we login.
    Twitch/YouTube / Facebook/ Twitter/Google+ can be used by [Accounts]. It is easy to start the live show.
    We can modify the resolution and use twitch by [Setting]
    We can configure FPS/CPU loading/where to show on display by [Status label].
    Hotkey configuration.
    Videos storage.
    Press [Ctrl+Tab] to call Gamecaster in game. And we can twitch or modify setting. I will provide my gaming video for you later.
    15. Power DVD
    This is a famous video player. Also, it can support BD format.
    We can use the [Setting] to change our language.
    We can change 5 times for default country .
    It is glad that I’ve finished the introduction of GT70 software.
    Performance report:
    Um…Now is late at night. I should go to my lovely bed.  Following is the testing report for the reference.
    1.   FurMark
    1920*1080, 15 minutes.
    2.   AIDA 64
    CPU and GPU stress testing, 30 minutes.
    3. 3D Mark 11
    4. 3DMark Vantage
    5.   3DMark 2013
    6.   Heaven Benchmark 4.0
    7.   CINBENCH 11.5
    8.   FINAL FANTASY XIV Benchmark
    9.   PCMARK 7
    10.   HD Tune Pro  5.50
    11.   AS SSD Benchmark
    12.   Crystal Disk Mark
    I didn’t forget my promise. Here is my gaming videos
    http://youtu.be/tCd5Lnj2U0I

    Editors' Choice Award. Good job MSI !!
    http://www.computershopper.com/laptops/reviews/msi-gt70-dominator-893#review-body

  • UCCX 7.0.1SR5 to 8.0 upgrade while also adding LDAP integration for CUCM - what happens to agents and Historical Reporting data?

    Current State:
    •    I have a customer running CUCM 6.1 and UCCX 7.01SR5.  Currently their CUCM is *NOT* LDAP integrated and using local accounts only.  UCCX is AXL integrated to CUCM as usual and is pulling users from CUCM and using CUCM for login validation for CAD.
    •    The local user accounts in CUCM currently match the naming format in active directory (John Smith in CUCM is jsmith and John Smith is jsmith in AD)
    Goal:
    •    Upgrade software versions and migrate to new hardware for UCCX
    •    LDAP integrate the CUCM users
    Desired Future State and Proposed Upgrade Method
    Using the UCCX Pre Upgrade Tool (PUT), backup the current UCCX 7.01 server. 
    Then during a weekend maintenance window……
    •    Upgrade the CUCM cluster from 6.1 to 8.0 in 2 step process
    •    Integrate the CUCM cluster to corporate active directory (LDAP) - sync the same users that were present before, associate with physical phones, select the same ACD/UCCX line under the users settings as before
    •    Then build UCCX 8.0 server on new hardware and stop at the initial setup stage
    •    Restore the data from the UCCX PUT tool
    •    Continue setup per documentation
    At this point does UCCX see these agents as the same as they were before?
    Is the historical reporting data the same with regards to agent John Smith (local CUCM user) from last week and agent John Smith (LDAP imported CUCM user) from this week ?
    I have the feeling that UCCX will see the agents as different almost as if there is a unique identifier that's used in addition to the simple user name.
    We can simplify this question along these lines
    Starting at the beginning with CUCM 6.1 (local users) and UCCX 7.01.  Let's say the customer decided to LDAP integrate the CUCM users and not upgrade any software. 
    If I follow the same steps with re-associating the users to devices and selecting the ACD/UCCX extension, what happens? 
    I would guess that UCCX would see all the users it knew about get deleted (making them inactive agents) and the see a whole group of new agents get created.
    What would historical reporting show in this case?  A set of old agents and a set of new agents treated differently?
    Has anyone run into this before?
    Is my goal possible while keeping the agent configuration and HR data as it was before?

    I was doing some more research looking at the DB schema for UCCX 8.
    Looking at the Resource table in UCCX, it looks like there is primary key that represents each user.
    My question, is this key replicated from CUCM or created locally when the user is imported into UCCX?
    How does UCCX determine if user account jsmith in CUCM, when it’s a local account, is different than user account jsmith in CUCM that is LDAP imported?
    Would it be possible (with TAC's help most likely) to edit this field back to the previous values so that AQM and historical reporting would think the user accounts are the same?
    Database table name: Resource
    The Unified CCX system creates a new record in the Resource table when the Unified CCX system retrieves agent information from the Unified CM.
    A Resource record contains information about the resource (agent). One such record exists for each active and inactive resource. When a resource is deleted, the old record is flagged as inactive; when a resource is updated, a new record is created and the old one is flagged as inactive.

  • ISE 1.3 and NAC

    I have a customer running 5508 WLCs across the estate, and I'm retrofitting IEEE802.1x authentication for the corporate WLAN, and WebAuth for the Guest WLAN...they have PSK at the moment :(
    They have AD and are showing great interest in ISE and NAC, so my immediate thoughts are to integrate ISE with AD, and use ISE as the RADIUS server for .1x on the WLC. Then use the WLC and ISE to do WebAuth for Guest...This is all standard stuff, but it gives the background.
    Now we get to the interesting bit...they want to run BYOD. They are involved in financial markets, so the BYOD needs to be tightly controlled. They are asking about ISE coupled with NAC, but I'm not convinced I need NAC since the arrival of ISE1.3. Obviously, I will be looking at three (min) SSIDs, namely corporate, guest and BYOD, all logically separate. I don't need anything that ISE 1.2 can't support on corporate and guest, but BYOD needs full profiling and either barring or device remediation before access to the net.
    Has anyone got any comments or suggestions? Is ISE 1.3 sufficiently NAC-like that I don't need it any more, or if that's not the case, what additional benefits does it bring that ISE can't support
    Thanks for any advice/comments/experiences
    Jim

    Hi Jim-
    Version 1.3 offers a built-in PKI and vastly improved guest services experience. The internal PKI is nice if the customer doesn't have an PKI solution in place. Keep in mind though that the internal ISE PKI can only issue certificates to BYOD devices that were on-boarded via the ISE BYOD "flow" So you cannot use the ISE PKI to issue certs to domain computers.
    With regards to NAC: You will have to clarify exactly what is needed here. If you needed to perform "posture assessment" then ISE can do it for Windows and OSX based machines. You can check for things like: A/V, A/S, Firewall Status, Windows Patches, etc. If you want to perform posture on mobile devices then you will need to integrate ISE with an MDM (Mobile Device Management) solution such as: Airwatch, Mobile Iron, Maas360, etc. ISE can query the MDM for things like: Is the device protected with a PIN, is the device rooted, is the device encrypted, etc.
    I hope this helps!
    Thank you for rating helpful posts!

  • Cisco ISE Vs Cisco Anyconnect Posture module with Advanced Endpoint Protection

    We are planning to use cisco Anyconnect posture module with Adv Endpoint protection to examine the VPN users- This can check whether they a antivirus/anti spyware software installed on their work station and can force to update def file if its older than specified number of days, it can also check the firewall status on their workstation and enable if its not already.This can detect keylogger and emulation softwares also.
    Do we get any additional advantages in using ISE compared to Anyconnect posture module ......
    Siddhartha       

    These are good questions. We had them last year before we decided to purchase ISE, specifically for our VPN users.
    I will be watching this thread to see what kind of responses you get.
    As of right now, I can verify the ISE can indeed check if specific Anti-Virus is installed (i.e., your corporate AntiVirus), or if ANY (supported by Cisco within ISE) antivirus is installed, and it can force an update process for the AV if it detects that the DAT files are older than a admin specified amount of time.
    Our issue at the moment (if you haven't searched the forums) is ISE detected the proper WSUS updates are indeed installed on the users systems and allowing the users system to talk to our internal WSUS server.
    We are now wondering if the Advanced Endpoint licensing on the ASA would have been a better way to go.
    Wishing you luck in finding your answers for us all.
    Dirk

  • ISE 802.1x and Windows Logoff

    Hi Guys,
    i have a ISE works fine using 802.1x but we have a strange behavior when the client just logoff the windows machine, after the client login again, the machine does not authenticate and stuck as a message " not possible to authenticate". Then I need to take off the cable machine and put again, after this everything works fine.
    This happens just using logoff windows.
    could someone help me about it?
    thanks a lot

    Hi Rik,
    I am using this configuration.
    interface GigabitEthernet3/33
    switchport access vlan 22
    switchport mode access
    switchport voice vlan 23
    ip access-group ACL-DEFAULT in
    logging event link-status
    authentication event fail action next-method
    authentication host-mode multi-domain
    authentication order dot1x mab
    authentication priority dot1x mab
    authentication port-control auto
    authentication violation restrict
    mab
    snmp trap mac-notification change added
    snmp trap mac-notification change removed
    dot1x pae authenticator
    dot1x timeout tx-period 10
    qos trust device cisco-phone
    spanning-tree portfast
    spanning-tree bpduguard enable
    service-policy input AutoQos-4.0-Cisco-Phone-Input-Policy
    service-policy output AutoQos-4.0-Output-Policy
    the client are using the NAC Agent the way to perform a posture.
    If i take off the cable and put again, everything works fine, but if the client try to logoff and after a time login again, the NIC Card can not be authenticated.
    thanks a lot

  • Untrusted apps are not allowed to connect to or launch Window Server before login.

    I'm getting this with the Citrix Receiver uninstaller from the command line... but not on all Mountain Lion 10.8.5 systems.  Googling turns up a lot of ideas about a problem with the app or in pre/post-flight scripts, but since it works on some, I wonder.  What is the mechanism that generates this error?  I'm guessing there's some setting or condition that exists on one system that isn't true on the other.  How do I find out?
    Sep 25 10:55:21 palms sudo[74325]:  joliver : TTY=ttys000 ; PWD=/Users/joliver ; USER=root ; COMMAND=/Volumes/Citrix Receiver/Uninstall Citrix Receiver.app/Contents/MacOS/Uninstall Citrix Receiver --nogui
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: 3891612: (connect_and_check) Untrusted apps are not allowed to connect to or launch Window Server before login.
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorFailure: This user is not allowed access to the window system right now.
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: _RegisterApplication(), FAILED TO establish the default connection to the WindowServer, _CGSDefaultConnection() is NULL.
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: CGSGetEventPort: Invalid connection
    Sep 25 10:55:21 --- last message repeated 3 times ---
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: CGSRegisterConnectionNotifyProc called with invalid connection
    Sep 25 10:55:21 --- last message repeated 2 times ---
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: CGSGetDockRect: Invalid connection
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: CGSGetCurrentDisplayMode: Invalid display 0x00000000
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: CGSGetCurrentCursorLocation: Invalid connection
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: CGSGetDisplayBounds: Invalid display 0x00000000
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: CGSGetCurrentCursorLocation: Invalid connection
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: CGSGetDisplayBounds: Invalid display 0x00000000
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: CGSGetCurrentCursorLocation: Invalid connection
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: CGSGetDisplayBounds: Invalid display 0x00000000
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: CGSGetCurrentCursorLocation: Invalid connection
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: CGSGetDisplayBounds: Invalid display 0x00000000
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: CGSGetEventPort: Invalid connection
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: CGSSetConnectionProperty: Invalid connection
    Sep 25 10:55:21 palms Uninstall Citrix Receiver[74326]: kCGErrorInvalidConnection: Error enabling suspendResume handling

    Contact Wacom. Unless they have updated drivers there is no workaround.
    Update or remove Quicksilver.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

Maybe you are looking for

  • How to get old data in to infocube

    hai gurus,    good morning, today i got one error that one of the report in the CATS is not showing the data, i gone that particular INFOCUBE  and observed the requests, iam searching for the information of a particular employee   here is the example

  • How to extract HRM master data from R/3 into LDIF file?

    Recently I have been asked to provide an extract from our R/3 system with some Human Resource master data. The extract has to be in the LDIF format (LDAP data interchange format). It is needed to import into a DirX metahub solution from Siemens. How

  • Hard disk details

    Hi friends, How to find out the hard disk number the real one through java. tell me ......... thanks in advance selvin

  • Am I qualify to join Mountain Lion if I purchased Lion through Mac App Store lately in early July

    I purchased the Mac OS X Lion through Mac App Store in early July. Am I qualify to join the Up-to-date program for Mountain Lion? If yes, how is this be done?

  • CCMS monitor configuration

    Hello Experts., Without use of BASIS Solution manager, is that possible to configure CCMS monitoring tool directly on SAP BI for monitoring the same.. or is there any option with ABAP coding  we can monitor ? BR, ANI