ISE 1.1.2 - Customize Agent Package

Similar Questions

• Failed to deploy the agent packages.

  Hello

  I install the Fglam on one of the Sun solaris box, but unable to deploy agent packages on this box, that is to say - could not build an Agent of the packages.

  I'm trying to deployment package JavaEE_5_8_2_5.8.2 - 20121206 - 1602.gar

  Please suggest what measures need to take here?

  Thank you

  Vivek

  Additional and similar issues specified in the support site

  User Account Control problem https://support.software.dell.com/foglight/kb/86955

  Deployment with corrupt files https://support.software.dell.com/foglight/kb/114458

  I hope it's one of these use cases and you can resolve the issue under the KB articles

  https://support.software.Dell.com/Foglight/KB/114458

  Golan

• Is it possible for us to customize a package/costume from Adobe?

  Customize a package of adobe suite to include only those

  Illustrator

  First Pro

  After Effects

  InDesign

  # Available plans are defined in the plans page.  For what you want, your best bet will be to get a comprehensive plan.

  Creative cloud plans

  https://creative.Adobe.com/plans

• ISE - profile of the NAC agent

  Dears

  I want to deploy via GPO NAC agent and I need to create the agent profile, I know how to create on ISE, but how to get the file in xml format which will be distributed?

  You can try to install only a single PC (whether by a manual installation or captive portal). If you have set up rules of posture while ISE then the NAC Agent automatically contacts the ISE server and downloads the last NACAgentcfg.xml.

  Then you can browse the following directory and find the NACAgentcfg.xml file in your PC.

  C:\Program Files (x 86) \Cisco\Cisco NAC Agent

  After that, you can deploy mass agent of the NAC as well as the xml file. Well that is not required to deploy the xml file as a I said, every time, there is a rule of posture the NAC agent will download the last available the ISE Server NACAgentcfg.xml.

  Please rate if this can help.

• How to customize a package after importing to vCO...?

  Dear community,

  Please somebody guide me how to customize and make changes on the package after I imported the packge to my server of vCO.

  I tried a few items, articles and books, I could get no direct nt with no do.

  Appreciated your help.

  If the edition for packaged items feature is disabled in the user interface, it means that the package author has disabled explicitly the user permissions when it exports the package. This is kind of normal for package versions official - usually, the contents of the package has been tested as is, and the author does not want users to make changes.

  If you have the following options:

  • Restore change it (and other) permissions by making changes directly in the database where workflows are stored. It is risky and not supported officially.
  • Duplicate the workflow (s) you want to change. The duplicate copy will be editable you can make your changes.
  • Contact the author of the package and he ask if he is ready to provide you with a copy of the editable content package or if he is ready to make the changes on the settings/content on your behalf.

• HP T610: Devicemanager 4.7 SP3 and SP4 break computer thinclient HPDM agents

  After update for HP Devicemanager 4.7 SP3 (and also SP4), it seems that the agent update task is broken. He pointed out that the update is successful, but the client does connect to Device Manager more. When you use the applet of the control panel HPDM Agent it does report no version number. Displaying the services applet, it seems that the service Agent of HPDM disappeared.

  Looks like the update task is seriously broken. Worse, it is that it does not include a complete agent installation, so how can I reinstall the agent now on the ThinClients?

  Frank

  Hi Chen,

  I had to use the Sysinternals Process Explorer to see what process has the file LIBEAY32. DLL in use, it has not been shown in diskactivity of the resource managers.

  I finally found the culprit! It seems that the Service of Proxy SSL VNC keeps the file open and it is not clogged up by the update agent package. When stop VNC SSL Proxy Service and by applying the agent to update manually then it works fine.

  So I created a group of settings which first disbales the Service of Proxy SSL VNC. Then I send the agent update task. Then the update is done correctly.

  Looks like a problem with the package to update the agent that is not stop or disable the Service of Proxy SSL VNC before replacing files including LIBEAY32. DLL.

  Frank.

• Evaluation of posture transmitted by mistake using Cisco ISE

  Hi all

  I would like to help try to understand why a customer who has not been connected to the network for a little over a month has allowed full network access despite being older than 28 days AV definitions.

  We have 2 mandatory requirements of posture,

  1 Symantec Av MUST be installed

  2. the definitions AV MUST be expired LESS THAN 28 days

  Currently, the machine I have watch the defs AV as being 25 March 2013.

  When I produce the detailed report posture, it shows me even that the two mandatory requirements described above were successfully which means that the endpoint is compliant posture. Clearly this is not the case if...!

  Is there anything else I can check on the ISE to help debug this?

  Mario

  Hello

  You may have two problems:

  1 al ' ISE, you have a set global clients not supported of the NAC Agent (Android, etc.) that specifies what their default state of compliance. If the default setting is "consistent" and you do not have a rule in this customer service or you simply do not have client provisioning rules, any machine that does not fit in the provisioning rule (IE thinks them ISE which is not supported) Gets a consistent event compliance status if NAC Agent is installed and that the rules are not met.

  2. problem of ANC Agent version?

  I saw in the papers that you use NAC 4.9.1.6 agent but the latest NAC Agent recommended to be used with (later) ISE is version 4.9.0.51.

  4.9.1.6 is a version of NAC Appliance and Cisco does not guarantee that is 100% compatible with ISE.

  Check

  http://www.Cisco.com/en/us/docs/security/ISE/1.1.1/compatibility/ise_sdt.html#wp78131

  Cisco NAC Agent Interoperability Between NAC Appliance and Identity Services Engine (ISE)
  Cisco supports different versions of the NAC Agent for integration with  NAC Appliance and ISE. Current releases are developed to work in either  environment, however, interoperability between deployments is not  guaranteed. Therefore, there is no explicit interoperability support for  a given NAC Agent version intended for one environment that will  necessarily work in the other. If you require support for both NAC  Appliance and ISE using a single NAC Agent, be sure to test NAC Agent in  your specific environment to verify compatibility.
  Unless there is a specific defect or feature required for your NAC  Appliance deployment, Cisco recommends deploying the most current agent  certified for your ISE deployment. If an issue arises, Cisco recommends  restricting the NAC Agent's use to its intended environment and  contacting Cisco TAC for assistance. Cisco will be addressing this issue  through the standard Cisco TAC support escalation process, but NAC  Agent interoperability is not guaranteed.
  Cisco is working on an approach to address NAC Agent interoperability testing and support in an upcoming release.
  

• Unable to add agents to Exchange and active directory fglam

  I'm having issues getting the announcement and exchanging cartridges to add new agents. The Exchange and the advertising agent package has been properly deployed. However, when you try to add and configure new agents, errors will prevent the installation of the future.

  I get the following error whenever I try to install Exchange followed 5.6.3.1 agent version.

  "Access error to the mydomain.com with the supplied user name and password: javax.naming.CommunicationException: mydomain.com:389 [root exception is java.net.ConnectException: Connection timed out: connect].

  I confirmed usernames are correct and work passwords and user account has access to connect to Exchange and to perform operations.

  I opened all the ports required by the installation docs and Foglight requirements. The network between the FMS and fglam boxes and Exchange are on opposite sides of a firewall.

  I fear that port 389 is not yet open, and I was wondering if anyone has experience with the exchange connection and agents of the AD through the firewall. If so, what has been your experience?

  Thank you

  A number of things I've noticed in the past:

  1 make sure that the machine/machine virtual fglam is running have enough memory for the fglam create agents.

  2. for AD and exchange please check the release notes for these agents, especially when AD/Exchange running on Windows 2008 R2, there are a lot of prerequisites to allow agents to collect data.

  3. If you did the pre requirements, I saw cases where it took a long time for the system to respond. In these cases what I usually do, is go to administration > dashboard status agent and change the properties of the agents. I give the connection timeout, a very high value (typically, I add a few zeros to the number that is there).

  In addition, if you check the edocs you will see both for AD and Exchange there is a troubleshooting section and a guide to diagnosis remotely.

  http://eDOCS.quest.com/Foglight/565/files/RemoteAccessDiagnostics_Guide.PDF

  There is also support solutions to talk about troubleshooting problems

  https://support.quest.com/SolutionDetail.aspx?ID=SOL76251&PR=Foglight

  https://support.quest.com/SolutionDetail.aspx?ID=SOL74226&PR=Foglight

  https://support.quest.com/SolutionDetail.aspx?ID=SOL70765&PR=Foglight

  If it still does not respond, please open a case of pension.

  Golan

• Custom in the dmg bundle package icons

  Hello

  I created an ant script to create a Setup program for my application JavaFx:

  <?xml version="1.0" encoding="UTF-8"?>
  <project name="app-javafx" default="do-deploy" basedir="." xmlns:fx="javafx:com.sun.javafx.tools.ant">
      <property name="java8.jdk.home" value="/Library/Java/JavaVirtualMachines/jdk1.8.0_11.jdk/Contents/Home" />
      <property name="javafx.tools.ant.jar" value="${java8.jdk.home}/lib/ant-javafx.jar" />
      <target name="init-fx-tasks">
          <taskdef resource="com/sun/javafx/tools/ant/antlib.xml" uri="javafx:com.sun.javafx.tools.ant" classpath="${javafx.tools.ant.jar}" />
      </target>
      <target name="setup-staging-area">
          <delete dir="externalLibs" />
          <delete dir="project" />
          <delete dir="projectRefs" />
  
          <mkdir dir="externalLibs" />
  
          <copy todir="externalLibs">
              <fileset dir="..\lib">
                  <include name="**.jar" />
              </fileset>
          </copy>
  
          <!--LIBRERIE PERSONALIZZATE-->
          <copy todir="externalLibs">
              <fileset dir=".">
                  <include name="**.jar" />
              </fileset>
          </copy>
  
  
          <mkdir dir="project" />
          <copy todir="project">
              <fileset dir="generated-sources">
                  <include name="gfx/**" />
              </fileset>
          </copy>
          <copy todir="project">
              <fileset dir="..\src\main">
                  <include name="resources/**" />
              </fileset>
          </copy>
          <copy todir="project">
              <fileset dir="..\src\main">
                  <include name="java/**" />
              </fileset>
          </copy>
  
          <mkdir dir="projectRefs" />
      </target>
      <target name='do-compile'>
          <delete dir="build" />
          <mkdir dir="build/src" />
          <mkdir dir="build/libs" />
          <mkdir dir="build/classes" />
  
          <!-- Copy project-libs references -->
          <copy todir="build/libs">
              <fileset dir="externalLibs">
                  <include name="**.jar" />
              </fileset>
          </copy>
  
          <!-- Copy project references -->
  
          <!-- Copy project sources itself -->
          <copy todir="build/src">
              <fileset dir="project/gfx">
                  <include name="**/*" />
              </fileset>
          </copy>
          <copy todir="build/src">
              <fileset dir="project/resources">
                  <include name="**/*" />
              </fileset>
          </copy>
          <copy todir="build/src">
              <fileset dir="project/java">
                  <include name="**/*" />
              </fileset>
          </copy>
  
          <javac fork="true" executable="${java8.jdk.home}/bin/javac" includeantruntime="false" source="1.8" target="1.8" srcdir="build/src" destdir="build/classes" encoding="UTF-8">
              <classpath>
                  <fileset dir="build/libs">
                      <include name="*" />
                  </fileset>
                  <filelist>
                      <file name="${java8.jdk.home}/jre/lib/jfxrt.jar" />
                  </filelist>
              </classpath>
          </javac>
  
          <!-- Copy over none Java-Files -->
          <copy todir="build/classes">
              <fileset dir="project/gfx">
                  <exclude name="**/*.java" />
              </fileset>
              <fileset dir="project/resources">
                  <exclude name="**/*.java" />
              </fileset>
              <fileset dir="project/java">
                  <exclude name="**/*.java" />
              </fileset>
          </copy>
  
  
      </target>
      <target name="do-deploy" depends="setup-staging-area, do-compile, init-fx-tasks">
          <delete file="dist" />
          <delete file="deploy" />
      
          <mkdir dir="dist" />
          <mkdir dir="dist/libs" />
  
          <copy todir="dist/libs">
              <fileset dir="externalLibs">
                  <include name="*" />
              </fileset>
          </copy>
  
          <fx:resources id="appRes">
              <fx:fileset dir="dist" includes="app-javafx.jar" />
              <fx:fileset dir="dist" includes="libs/*" />
          </fx:resources>
  
          <fx:application id="fxApplication" name="app" version="3.0" mainClass="it.client.Main" preloaderclass="it.SplashScreenUi" toolkit="fx" />
  
          <fx:jar destfile="dist/app-javafx.jar">
              <fx:application refid="fxApplication" />
              <fileset dir="build/classes">
              </fileset>
              <fx:resources refid="appRes" />
  
  
              <manifest>
                  <attribute name="Implementation-Vendor" value="Vendor" />
                  <attribute name="Implementation-Title" value="app" />
                  <attribute name="Implementation-Version" value="3.0.0" />
              </manifest>
          </fx:jar>
  
  
          <mkdir dir="deploy" />
          <!-- Need to use ${basedir} because somehow the ant task is calculating the directory differently -->
          <fx:deploy outdir="${basedir}/deploy" outfile="app-javafx" nativeBundles="all" height="768" width="1024" verbose="true">
              <fx:info title="app" vendor="Vendor" copyright="Copyright Tutti i diritti riservati" />
              <fx:application refId="fxApplication" />
              <fx:resources refid="appRes" />
  
              <fx:preferences shortcut="true" install="true" menu="true" />
  
              <fx:permissions elevated="true" />
  
  
              <!-- Custom JVM setup for application -->
              <fx:platform>
                  <fx:jvmarg value="-Xmx1024m" />
              </fx:platform>
          </fx:deploy>
      </target>
  </project>
  

  During compilation, I see:

  Using base JDK at: /Library/Java/JavaVirtualMachines/jdk1.8.0_11.jdk
    Using default package resource [Bundle config file] (add package/macosx/Info.plist to the class path to customize)
    Using default package resource [icon] (add package/macosx/app.icns to the class path to customize)
  Creating app bundle: /Users/Utente/Documents/workspaceServer/javafx/target/deploy/bundles/app.app
  Config files are saved to /var/folders/q6/vmt_h0tx3rgdbt_4h2_2f3780000gn/T/build6635061168386632777.fxbundler/macosx. Use them to customize package.
  fxbund
  ler/macosx. Use them to customize package.
  

  So I get files in the temp directory and I copied them to my target of the project directory. Unfortunally javafxbuilder not use to customize the package so I think that the path where I put the files that will not.

  Can you help me?

  Thank you

  Resources are found do sniff classpath: your classpath is missing 'dot '.

  Instead of

  Please try to

  Reference: deployment of JavaFX Applications: Application independent packaging | 2 JavaFX tutorials and Documentation

• Thinapped IE 7 - How to customize (home page, security zone, proxy settings,...)

  Hello

  I virtualized copy of IE 7 and it's working properly (thanks guys here in this community) but I need to customize this package with different internet settings for the homepage and the intranet zone instance. then rebuild the package and got the portable version.

  Thanks in advance.

  Here are the steps to follow:

  1. on a clean machine, open IE 7 ThinApp and make all the customizations that are saved in the sandbox

  2. to aid SBmerge utility, merge the contents of the sandbox again in the ThinApp

  For steps on SBmerge, take a look here:

  Simple steps for using SBMERGE | VMware ThinApp Blog - Articles from VMware

  Video HOWTO: using sbmerge for updating a ThinApp project. | VMware ThinApp Blog - Articles from VMware

• Icons of drop-in customized for packaging stand-alone application on Mac OS x

  I can't add icons customized to a standalone package built on MacOSX.
  
  JDK1.7.0_06 with JavaFX 2.2.
  
  Directory structure:
  TestFX
  -bin
  -(update of class files)
  -build
  -Test.jar
  -deploy
  -package
  -macosx
  -Test.icns
  -Test - volume.icns
  
  From the Terminal:
  CD TestFX
  deploy - native - title "TestApp" - seller 'James Clément' - description "Quick Test Application" appclass - edu.marshall.denvir.tests.fx.TestFX - width 400 - height 400 - name 'Test' - outdir javafxpackager - deploy - Test - build srcdir - v outfile
  
  This creates the natives and DMG packages and they work, but there is no custom icons for file DMG installer or .app (just gray coffee cup icon).
  
  Here is the result. What confuses me is the 4th line and similar, with 'add package/macosx/Test.icns to the classpath to customize. " This file is relative to the current directory, but for some reason any is not picked up. If I switch to Windows (via VMWare) and add some windows/Test.ico in the package and run the same command, the custom .ico file is recognized.
  
  Looking for price for type = all = any format
  Prepare the Info.plist file: /var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/macosx/Info.plist
  Using the default package [config file] resource (add package/macosx/Info.plist to the classpath to customize)
  Using the default package resource (add package/macosx/Test.icns to the classpath to customize) [icon]
  Creation bundle app: /Users/jdenvir/Documents/workspace/TestFX/deploy/bundles/Test.app
  Running [rm,-f, Users/jdenvir/Documents/workspace/TestFX/deploy/bundles/Test.app/Contents/PlugIns/jdk1.7.0_06.jdk/Contents/MacOS/libjli.dylib]
  Running [ln,-s... / Home/jre/lib/jli/libjli.dylib,.] in deploy/bundles/Test.app/Contents/PlugIns/jdk1.7.0_06.jdk/Contents/MacOS
  Configuration files are saved in var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/macosx. Use them to customize the package.
  Package building for Test DMG
  Prepare the Info.plist file: /var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/macosx/Info.plist
  Using the default package [config file] resource (add package/macosx/Info.plist to the classpath to customize)
  Using the default package resource (add package/macosx/Test.icns to the classpath to customize) [icon]
  Running [ln,-s... / Home/jre/lib/jli/libjli.dylib,.] in /var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/images/dmg.image/Test.app/Contents/PlugIns/jdk1.7.0_06.jdk/Contents/MacOS
  Configuration files are saved in var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/macosx. Use them to customize the package.
  Using the default package [dmg background] resource (add package/macosx/Test-background.png to the classpath to customize)
  Using the default package [volume icon] resource (add package/macosx/Test-volume.icns to the classpath to customize)
  Using the default package resource [script to run after the application image is filled] (add package/macosx/Test-post-image.sh to the classpath to customize)
  Preparation of installation dmg: /var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/macosx/Test-dmg-setup.scpt
  Using the default package [DMG configuration script] resource (add package/macosx/Test-dmg-setup.scpt to the classpath to customize)
  DMG file creation: /Users/jdenvir/Documents/workspace/TestFX/deploy/bundles/Test.dmg
  Running [usr/bin/hdiutil create - quiet, - srcfolder, var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/images/dmg.image, - volname, Test, - ov, var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/images/Test-tmp.dmg -, format, UDRW]
  Running [usr/bin/hdiutil, attach, var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/images/Test-tmp.dmg, - quiet -, mountroot, var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/images]
  Running [osascript, var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/macosx/Test-dmg-setup.scpt]
  Running [developer/tools/then-a, C, var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/images/Test]
  Running [usr/bin/hdiutil detach,-quiet, var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/images/Test]
  Running [usr/bin/hdiutil, convert, var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/images/Test-tmp.dmg,-calme,-UDZO, - o, format Users/jdenvir/Documents/workspace/TestFX/deploy/bundles/Test.dmg]
  Installer DMG of Test result: /Users/jdenvir/Documents/workspace/TestFX/deploy/bundles/Test.dmg
  Configuration files are saved in var/folders/sd/8_vhkpzj539bxcjgp27wb75r0000gn/T/build6438886407189596362.fxbundler/macosx. Use them to customize the package.

  It is indeed a bug in utility javafxpackager introduced towards the end of the release. It has impact on Mac and Linux
  You can fix it on your copy of the javafxlauncher - edit
  /Library/Java/JavaVirtualMachines/JDK1.7.0_06.JDK/contents/home/bin/javafxpackager
  and
  replace
  classpath="$javafx_home/lib/Ant-JavaFX.jar".
  with the following line
  classpath=".:$javafx_home/lib/Ant-JavaFX.jar".

  I'll make sure that this problem is fixed in point 2.2.2.

• Can I specify the package 'root' library?

  Can I specify the package 'root' library (currently apparently logged in as 'components') so that the generated code has the names of package reasonable i.e. 'com.adobe.buttons.HelloWorldButton' rather than 'components. HelloWorldButton ".

  Hi Graeme,

  Not from the inside, Flash Catalyst.  However, if you take your project in Flash Builder, you will be able to customize the package names here.

  Best,
  Tanya

• Foglight delpoyment

  Hello

  Can anyone send me please the documents of a simple way to install the fglam, the deployment of the agent package, and the agent of JavaEE deployment.

  Thank you

  Vivek

  What version of the agent Manager and JavaEE do you use?

  All the documentation is available online: http://edocs.quest.com/

• Installation of 32-bit Comp for cartridges of the BONE

  Someone at - it actually install agents 32bits on centoS 6.x x 64 yet?

  Seems that RPM don't install US 32-bit versions while the x 64 bit exist.

  "package glibc - 2.12 - 1.80.el6.x86_64 (which is newer than the glibc - 2.12 - 1.7.el6.i686) is already installed.

  Does anyone have a solution to this?

  What cartridges you trying to install? What is a custom package or packages Quest?

  Is there a particular reason you want to install a 32-bit to a 64 bit OS agent?

  If the agent package is not listed in the list of deployment you will probably need to check the "Show packages for all platforms:" when you try to deploy the agent package, so you can see other packages. In a foglight environment packages displayed corresponds to the architecture (64-bit fglam 64 bit Windows 2008 OS packages won't be visible from only a fglam running on windows 2008), if you want to deploy another packet that does not match the OS you should check the "packages for all platforms show: ' and it will show all of the cartridges that are available (even if they do not match the OS).

  If it is somehow a redeployment, you may need to delete the file already deployed because under agent manager in the target environment and redeploy.

  I hope this helps.

  Golan

• CSA 6.01 - kit-list

  Hello dear experts and users, I hope someone can help me. I can't open the kit list on the homepage of the APF-Server (CSA_MC) of any client. I see the message "error: address xxx is not allowed access to the Cisco Security Agent kit list.» My solution is to log in to the CSA server to the remote host and to install the kit in the menu "system or Agent packages. It's not so comfortable...
  I went from the CSA Agent from the server to find the great, but I don't have a missconfigure of the Agent is not the solution.

  Thanks a lot if someone has a good answer, greetings...

  You may put in some addresses in the dialog™ concerning what addresses can register with the™, I think that it blocks access to agent so kits without logging it is.