Zen Agent and "Workstation Only"?

We're using the Zen 6.5sp2 agent and NO CLIENT in our remote locations.
Users are consistently choosing to login to the local workstation without
authenticating to eDir, which causes obvious difficulties in
package/policy distribution. I would like to do one of two things:
1. Set the Agent to default to Workstation Only = 0 so that the Agent
doesn't remember the last setting -OR-
2. Remove the "Workstation Only" checkbox from the login (I found this reg
key) and then REDUCE the network timeout.
Any suggestions?

I don't have the collection of settings on me but I can get them.
What I did in clientless environments is to enable "PassiveMode" on the
clients so that the MS GUI was shown and not the NWGina.
With the MS Gina, users would just automatically login to E-Dir in the
background through the middle-tier.
There would never even be an option for them to not log into E-dir.
At http://www.zenworks.com there is a Group Policy maintained by Shaun
Pond for the Novell Client that I suspect would also include the
required settings for ZEN as well but I am not sure.
I would check it out. I dont have the link but it should not be hard.
I presume a GP would be an easy way to keep the settings you want.
[email protected] wrote:
>
> We're using the Zen 6.5sp2 agent and NO CLIENT in our remote locations.
> Users are consistently choosing to login to the local workstation
> without authenticating to eDir, which causes obvious difficulties in
> package/policy distribution. I would like to do one of two things:
>
> 1. Set the Agent to default to Workstation Only = 0 so that the Agent
> doesn't remember the last setting -OR-
> 2. Remove the "Workstation Only" checkbox from the login (I found this
> reg key) and then REDUCE the network timeout.
>
> Any suggestions?
Craig Wilson
Novell Product Support Forum Sysop
Master CNE, MCSE 2003, CCN

Similar Messages

  • Zen agent on Windows server?

    Hello,
    Can the Zen agent and it's components be installed on a Windows 2003 server? I'm looking to use the DLU functionality with the Novell client.
    Thanks,
    Tom

    Tom,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
    - Check all of the other support tools and options available at
    http://support.novell.com.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://support.novell.com/forums)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://support.novell.com/forums/faq_general.html
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • Some computers download and install the two approved updates, others only download Windows Update Agent and not the approved updates.

    Some computers download and install the two approved updates, others only download Windows Update Agent and not the approved updates.

    UN-successful Windows Update Log:
    2014-05-07 09:33:56:180
    1036 e70
    Misc ===========  Logging initialized (build: 7.6.7600.256, tz: -0400)  ===========
    2014-05-07 09:33:56:220
    1036 e70
    Misc  = Process: C:\Windows\system32\svchost.exe
    2014-05-07 09:33:56:221
    1036 e70
    Misc  = Module: c:\windows\system32\wuaueng.dll
    2014-05-07 09:33:56:180
    1036 e70
    Service *************
    2014-05-07 09:33:56:221
    1036 e70
    Service ** START **  Service: Service startup
    2014-05-07 09:33:56:222
    1036 e70
    Service *********
    2014-05-07 09:33:56:544
    1036 e70
    Agent  * WU client version 7.6.7600.256
    2014-05-07 09:33:56:545
    1036 e70
    Agent  * Base directory: C:\Windows\SoftwareDistribution
    2014-05-07 09:33:56:546
    1036 e70
    Agent  * Access type: No proxy
    2014-05-07 09:33:56:547
    1036 e70
    Agent  * Network state: Connected
    2014-05-07 09:33:57:315
    1036 e70
    Setup Service restarting after SelfUpdate
    2014-05-07 09:33:57:545
    1036 e70
    Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-05-07 09:33:57:592
    1036 e70
    Report CWERReporter::Init succeeded
    2014-05-07 09:33:58:326
    1036 e70
    Report ***********  Report: Initializing static reporting data  ***********
    2014-05-07 09:33:58:376
    1036 e70
    Report  * OS Version = 6.1.7601.1.0.65792
    2014-05-07 09:33:58:376
    1036 e70
    Report  * OS Product Type = 0x00000030
    2014-05-07 09:33:58:394
    1036 e70
    Report  * Computer Brand = Hewlett-Packard
    2014-05-07 09:33:58:444
    1036 e70
    Report  * Computer Model = HP Compaq 4000 Pro SFF PC
    2014-05-07 09:33:58:455
    1036 e70
    Report  * Bios Revision = 786H7 v02.00
    2014-05-07 09:33:58:504
    1036 e70
    Report  * Bios Name = Default System BIOS
    2014-05-07 09:33:58:554
    1036 e70
    Report  * Bios Release Date = 2011-01-31T00:00:00
    2014-05-07 09:33:58:554
    1036 e70
    Report  * Locale ID = 1033
    2014-05-07 09:34:03:562
    1036 f08
    Report REPORT EVENT: {082D455B-6E51-4238-A997-1D27D9214A72}
    2014-05-07 09:33:58:565-0400 1
    199 101
    {0011B9ED-9189-4D58-BE25-FA2F13FC3D6C}
    1 240005
    SelfUpdate Success
    Content Install Installation successful and restart required for the following update: Windows Update Aux
    2014-05-07 09:34:03:614
    1036 f08
    Report CWERReporter finishing event handling. (00000000)
    2014-05-07 09:34:42:049
    1036 e70
    Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-05-07 09:34:42:049
    1036 e70
    Agent ***********  Agent: Initializing global settings cache  ***********
    2014-05-07 09:34:42:049
    1036 e70
    Agent  * WSUS server: http://csd26.csd.local:80
    2014-05-07 09:34:42:049
    1036 e70
    Agent  * WSUS status server: http://csd26.csd.local:80
    2014-05-07 09:34:42:049
    1036 e70
    Agent  * Target group: CO
    2014-05-07 09:34:42:049
    1036 e70
    Agent  * Windows Update access disabled: No
    2014-05-07 09:34:42:063
    1036 e70
    DnldMgr Download manager restoring 0 downloads
    2014-05-07 09:34:42:089
    1036 e70
    AU ###########  AU: Initializing Automatic Updates  ###########
    2014-05-07 09:34:42:089
    1036 e70
    AU AU setting next detection timeout to 2014-05-07 13:34:42
    2014-05-07 09:34:42:090
    1036 e70
    AU AU setting next sqm report timeout to 2014-05-07 13:34:42
    2014-05-07 09:34:42:090
    1036 e70
    AU  # WSUS server: http://csd26.csd.local:80
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Detection frequency: 22
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Target group: CO
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Approval type: Scheduled (Policy)
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Scheduled install day/time: Every day at 3:00
    2014-05-07 09:34:42:090
    1036 e70
    AU  # Auto-install minor updates: Yes (User preference)
    2014-05-07 09:34:42:105
    1036 e70
    AU Initializing featured updates
    2014-05-07 09:34:42:116
    1036 e70
    AU Found 0 cached featured updates
    2014-05-07 09:34:42:116
    1036 e70
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:34:42:117
    1036 e70
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:34:42:117
    1036 e70
    AU AU finished delayed initialization
    2014-05-07 09:34:42:117
    1036 e70
    AU AU setting next sqm report timeout to 2014-05-08 13:34:42
    2014-05-07 09:34:42:117
    1036 e70
    AU #############
    2014-05-07 09:34:42:117
    1036 e70
    AU ## START ##  AU: Search for updates
    2014-05-07 09:34:42:117
    1036 e70
    AU #########
    2014-05-07 09:34:42:291
    1036 e70
    AU <<## SUBMITTED ## AU: Search for updates [CallId = {5AA2F00A-8964-4543-A740-EC45C5FD5752}]
    2014-05-07 09:34:42:341
    1036 f08
    Agent *************
    2014-05-07 09:34:42:341
    1036 f08
    Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-05-07 09:34:42:341
    1036 f08
    Agent *********
    2014-05-07 09:34:42:341
    1036 f08
    Agent  * Online = Yes; Ignore download priority = No
    2014-05-07 09:34:42:341
    1036 f08
    Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0
    and DeploymentAction='Uninstallation' and RebootRequired=1"
    2014-05-07 09:34:42:341
    1036 f08
    Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2014-05-07 09:34:42:341
    1036 f08
    Agent  * Search Scope = {Machine}
    2014-05-07 09:34:42:341
    1036 f08
    Setup Checking for agent SelfUpdate
    2014-05-07 09:34:42:342
    1036 f08
    Setup Client version: Core: 7.6.7600.256  Aux: 7.6.7600.256
    2014-05-07 09:34:42:349
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-05-07 09:34:42:392
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:669
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
    2014-05-07 09:34:44:676
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:754
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-05-07 09:34:44:777
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:781
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
    2014-05-07 09:34:44:788
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:837
    1036 f08
    Setup Determining whether a new setup handler needs to be downloaded
    2014-05-07 09:34:44:855
    1036 f08
    Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
    2014-05-07 09:34:44:862
    1036 f08
    Misc Microsoft signed: Yes
    2014-05-07 09:34:44:862
    1036 f08
    Misc WARNING: Digital Signatures on file C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe are not trusted: Error 0x800b0001
    2014-05-07 09:34:44:862
    1036 f08
    Setup WARNING: Trust verification failed for WuSetupV.exe. It will be deleted and downloaded, error = 0x800B0001
    2014-05-07 09:34:44:863
    1036 f08
    Setup SelfUpdate handler update required: Current version: 7.6.7600.256, required version: 7.6.7600.256
    2014-05-07 09:34:44:873
    1036 f08
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-05-07 09:34:44:932
    1036 f08
    Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-05-07 09:34:44:933
    1036 f08
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-05-07 09:34:45:048
    1036 f08
    Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-05-07 09:34:45:048
    1036 f08
    Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256"
    2014-05-07 09:34:45:234
    1036 f08
    Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.6.7600.256" is already installed.
    2014-05-07 09:34:45:235
    1036 f08
    Setup SelfUpdate check completed.  SelfUpdate is NOT required.
    2014-05-07 09:34:48:415
    1036 f08
    PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2014-05-07 09:34:48:415
    1036 f08
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://csd26.csd.local:80/ClientWebService/client.asmx
    2014-05-07 09:34:48:424
    1036 f08
    PT WARNING: Cached cookie has expired or new PID is available
    2014-05-07 09:34:48:424
    1036 f08
    PT Initializing simple targeting cookie, clientId = 97287ab2-5824-44d2-bf93-8a98da659f77, target group = CO, DNS name = c18714.csd.local
    2014-05-07 09:34:48:424
    1036 f08
    PT  Server URL = http://csd26.csd.local:80/SimpleAuthWebService/SimpleAuth.asmx
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING: SOAP Fault: 0x00012c
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     faultstring:Fault occurred
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     ErrorCode:ConfigChanged(2)
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     Message:(null)
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2014-05-07 09:34:48:454
    1036 f08
    PT WARNING:     ID:cb5babad-3a1d-4e6b-946e-736ed4746e3f
    2014-05-07 09:34:48:464
    1036 f08
    PT WARNING: Cached cookie has expired or new PID is available
    2014-05-07 09:34:48:464
    1036 f08
    PT Initializing simple targeting cookie, clientId = 97287ab2-5824-44d2-bf93-8a98da659f77, target group = CO, DNS name = c18714.csd.local
    2014-05-07 09:34:48:464
    1036 f08
    PT  Server URL = http://csd26.csd.local:80/SimpleAuthWebService/SimpleAuth.asmx
    2014-05-07 09:35:06:497
    1036 e70
    AU Forced install timer expired for scheduled install
    2014-05-07 09:35:06:497
    1036 e70
    AU UpdateDownloadProperties: 0 download(s) are still in progress.
    2014-05-07 09:35:06:497
    1036 e70
    AU Setting AU scheduled install time to 2014-05-08 07:00:00
    2014-05-07 09:35:06:498
    1036 e70
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:35:14:236
    1036 f08
    PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2014-05-07 09:35:14:236
    1036 f08
    PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://csd26.csd.local:80/ClientWebService/client.asmx
    2014-05-07 09:35:20:118
    1036 f08
    Agent  * Found 0 updates and 79 categories in search; evaluated appl. rules of 859 out of 1494 deployed entities
    2014-05-07 09:35:20:194
    1036 f08
    Agent *********
    2014-05-07 09:35:20:194
    1036 f08
    Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2014-05-07 09:35:20:194
    1036 f08
    Agent *************
    2014-05-07 09:35:20:209
    1036 f08
    Report CWERReporter finishing event handling. (00000000)
    2014-05-07 09:35:20:209
    1036 f08
    Report CWERReporter finishing event handling. (00000000)
    2014-05-07 09:35:20:209
    1036 bb8
    AU >>##  RESUMED  ## AU: Search for updates [CallId = {5AA2F00A-8964-4543-A740-EC45C5FD5752}]
    2014-05-07 09:35:20:209
    1036 bb8
    AU  # 0 updates detected
    2014-05-07 09:35:20:209
    1036 bb8
    AU #########
    2014-05-07 09:35:20:209
    1036 bb8
    AU ##  END  ##  AU: Search for updates [CallId = {5AA2F00A-8964-4543-A740-EC45C5FD5752}]
    2014-05-07 09:35:20:209
    1036 bb8
    AU #############
    2014-05-07 09:35:20:210
    1036 bb8
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:35:20:210
    1036 bb8
    AU Featured notifications is disabled.
    2014-05-07 09:35:20:211
    1036 bb8
    AU AU setting next detection timeout to 2014-05-08 11:19:46
    2014-05-07 09:35:20:211
    1036 bb8
    AU Setting AU scheduled install time to 2014-05-08 07:00:00
    2014-05-07 09:35:20:212
    1036 bb8
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:35:20:212
    1036 bb8
    AU Successfully wrote event for AU health state:0
    2014-05-07 09:35:25:183
    1036 f08
    Report REPORT EVENT: {C1B39107-F517-4477-AAE3-9B1F1D6002BF}
    2014-05-07 09:35:20:193-0400 1
    147 101
    {00000000-0000-0000-0000-000000000000}
    0 0 AutomaticUpdates
    Success Software Synchronization
    Windows Update Client successfully detected 0 updates.
    2014-05-07 09:35:25:183
    1036 f08
    Report REPORT EVENT: {669B9537-BB71-4190-BA58-A97F725AE4D8}
    2014-05-07 09:35:20:194-0400 1
    156 101
    {00000000-0000-0000-0000-000000000000}
    0 0 AutomaticUpdates
    Success Pre-Deployment Check
    Reporting client status.
    2014-05-07 09:35:25:184
    1036 f08
    Report CWERReporter finishing event handling. (00000000)
    2014-05-07 09:37:32:440
    1036 f08
    Report Uploading 3 events using cached cookie, reporting URL = http://csd26.csd.local:80/ReportingWebService/ReportingWebService.asmx
    2014-05-07 09:37:32:454
    1036 f08
    Report Reporter successfully uploaded 3 events.

  • Adobe Acrobat 7.0.0, ZEN AO and .MSP files

    I'm currently having the following problem...
    I've got two ZEN AO's. One for Adobe Acrobat 7.0 Professional and one for
    Adobe Acrobat 7.0 Standard. I've added the latest Adobe Acrobat 7.0.5 .msp
    (Windows Installer Patch) file to it's respective ZEN AO and incremented the
    AO version number. On my test workstations that are cleanly imaged I
    associate and install either Adobe Acrobat 7.0 ZEN AO and neither object
    applies the 7.0.5 msp during the initial installation of the object/package.
    What gives? I've noticed that during the last part of the installation when
    it looks like it's applying the .msp I see "gibberish" in the text field
    right above the progress bar of the ZEN "Distributing blah blah blah" dialog
    box. I can launch Adobe and verify that the patch has not been applied. I
    can then verify (via NAL in myapps.html) the application and the patch
    applies as expected (I can verify that by launching the application). A new
    install of these objects/packages should include the patch should it not?
    Also if the application was previously installed by this "same" AO (only the
    patch has been added and the version number incremented) and I "install" the
    application (keep in mind it's already installed) NAL / Windows Installer
    goes through the routine of installation and then appears to apply the .msp,
    again I notice the gibberish in the text field right above the progress bar
    of the ZEN "Distributing blah blah blah" dialog box. I can then verify the
    application and the patch applies as expected (again, I can verify that by
    launching the application). What is up with this? I can't believe after
    roughly fifteen agent releases (I say fifteen based on the # of releases on
    the agent release TID) that Novell can't get this basic functionality right.
    Windows 2000 SP4 Update Rollup 1 (including all updates)
    Windows XP SP2 (including all updates)
    Novell Client 4.9 SP1 (including all updates)
    ZEN Agent IR5 and ZEN Agent IR6
    Bryan

    Bryan,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Do a search of our knowledgebase at http://support.novell.com/search/kb_index.jsp
    - Check all of the other support tools and options available at
    http://support.novell.com.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://support.novell.com/forums)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://support.novell.com/forums/faq_general.html
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

  • ZEN Agent install without admin rights

    Hi all,
    Sorry to re-visit something I've seen a number of posts on, but I can't
    seem to get things to work as I've been lead to believe they should. We
    have a handful of systems that do not have any instance of the ZEN agent
    installed, a mix of NT and XP (odd, I know). We are attempting to create
    an automated process that will establish whether the agent is on the
    system and if it is not, install it. Seems pretty straight forward and
    I've been referencing the following suggestions. There are a number of
    posts in the forums as well, but these were the most relevant.
    http://www.novell.com/coolsolutions/trench/3490.html
    http://support.novell.com/cgi-bin/se...?/10085696.htm
    http://www.novell.com/coolsolutions/trench/3383.html
    http://support.novell.com/cgi-bin/se...?/10073212.htm
    The problem is, despite what these instructions say, we cannot install the
    agent without having local admin rights. All the batch files are in
    place, and work, but ultimately the install fails. I've seen work arounds
    for any OS later than NT, but its important that every system have the
    agent.
    I've tried almost everything suggested in the links above but I am
    primarily pursuing the batch file approach as detailed in...
    http://support.novell.com/cgi-bin/se...?/10085696.htm
    At what point are rights elevated such that the install can complete in an
    NT environment?
    I am sure I'm forgetting some relevant details, so humor me please.
    Thanks in advance.
    Mike

    I forgot that RunAs does not come with NT. ( It's available as an add-on,
    but even that needs admin rights to install.)
    Try PSExec from http://www.sysinternals.com, but I believe that will not
    work either, but worth a shot.
    Another outside shot is to push the "AlwaysInstallElevated" MSI installer
    registry keys via a batch file.
    Unfortunately, I doubt your logged on user has the rights to do this
    either..............
    You may be stuck manually visiting and installing manually.
    Craig Wilson
    Novell Product Support Forum Sysop
    Master CNE, MCSE 2003, CCNA
    Editor - http://www.ithowto.com
    (Seeking Full-Time Expert? Drop me a note :> )
    <[email protected]> wrote in message
    news:[email protected]...
    > There's no domain to work with. The only admin account available is on
    > the local PC. I've seen options using Runas or even CPAU.exe but neither
    > are available with Windows NT.
    >
    > We are copying the relevant files to a directory on the PC before
    > beginning the install. To this point, network access has not been an
    > issue.
    >
    > The batch file dictates the install run in the background so I don't see
    > it happening, but the problem seems to come down to not having
    > administrative rights on the PC. If I launch the .MSI manually it gives
    > me an error referencing rights. If I'm logged on as an administrator the
    > install completes exactly as it should.
    >
    > Thanks for the reply. I look forward to any suggestions you may have.
    >
    >
    >> There are lots of scripts, but you need to have some ID that is a local
    >> admin. ( If the PC is on a Domain, then a Domain Admin account works
    >> great.)
    >> Additionally, network access may be lost when running this script, so
    >> copying the agent local before the install may help.
    >>
    >> Where do you hit a snag? Starting the install as the alernate user?
    >> Finding an Admin account? Determining if the agent is installed?
    >>
    >> --
    >> Craig Wilson
    >> Novell Product Support Forum Sysop
    >> Master CNE, MCSE 2003, CCNA
    >>
    >> Editor - http://www.ithowto.com
    >>
    >> (Seeking Full-Time Expert? Drop me a note :> )
    >>
    >>
    >> <[email protected]> wrote in message
    >> news:[email protected]...
    >> > Hi all,
    >> >
    >> > Sorry to re-visit something I've seen a number of posts on, but I can't
    >> > seem to get things to work as I've been lead to believe they should.
    > We
    >> > have a handful of systems that do not have any instance of the ZEN
    > agent
    >> > installed, a mix of NT and XP (odd, I know). We are attempting to
    > create
    >> > an automated process that will establish whether the agent is on the
    >> > system and if it is not, install it. Seems pretty straight forward and
    >> > I've been referencing the following suggestions. There are a number of
    >> > posts in the forums as well, but these were the most relevant.
    >> >
    >> > http://www.novell.com/coolsolutions/trench/3490.html
    >> > http://support.novell.com/cgi-bin/se...?/10085696.htm
    >> > http://www.novell.com/coolsolutions/trench/3383.html
    >> > http://support.novell.com/cgi-bin/se...?/10073212.htm
    >> >
    >> > The problem is, despite what these instructions say, we cannot install
    > the
    >> > agent without having local admin rights. All the batch files are in
    >> > place, and work, but ultimately the install fails. I've seen work
    > arounds
    >> > for any OS later than NT, but its important that every system have the
    >> > agent.
    >> >
    >> > I've tried almost everything suggested in the links above but I am
    >> > primarily pursuing the batch file approach as detailed in...
    >> > http://support.novell.com/cgi-bin/se...?/10085696.htm
    >> >
    >> > At what point are rights elevated such that the install can complete
    > in an
    >> > NT environment?
    >> >
    >> > I am sure I'm forgetting some relevant details, so humor me please.
    >> > Thanks in advance.
    >> >
    >> > Mike
    >>
    >>
    >

  • NAC Agent and NSP provisioning with ISE 1.1.1

    I am trying to get all workstations (OSX and Windows) to install both the Native Supplicant Wizard and NAC Agent during the On-boarding process.
    I am currently using the default guest portal in ISE.
    The environment has been setup using a Dual SSID design.
    At the moment, devices can connect to the provisioning SSID and get CWA. Device registration works, the portal runs the NSP setup which correctly sets up the network adapter.
    The problem is the portal never attempts to install the NAC Agent.
    The client provisioning policy has a separate policies for wireless/wired as well as OS. Each policy applies both a NSP and NAC Agent configuration. It appears the guest portal only checks the NSP configuration and not the NAC Agent config.
    Any ideas?

    Just so i understand this correctly you are using both a client provisioning portal and a native supplicant provisoning portal tied into seperate authz policies.
    With that out of the way are you checking to see if the client is compliant in the client provisioning portal policy.
    Let me know if you have the following configured (example windows OS), this is assuming that the endpoint is statically assigned to RegisteredDevices after native suppliant provisioning.
    Rule 0 (endpoint group = RegisteredDevice) AND (AD:Domain user and authentication method:x509 and posturestatus:COMPLIANT) = Permit Access
    Rule 1 (endpoint group = RegisteredDevice) AND (AD:domain user AND authentication method:x509[if you deployed certs in the native supp condition] AND workstation NOT EQUAL:COMPLIANT) RESULT client provisioning portal.
    Rule 2 (endpoint group = Workstation) AND (AD:Domain User AND authentication mehod using mschapv2) RESULT windows provisioning portal
    Hope that helps,
    Tarik Admani
    *Please rate helpful posts*

  • Remote agent crashing workstation

    Hi,
    I have always installed the remote control agent on my workstations.
    However when I intall it on the latest ones, they computers will just be
    getting to the windows desktop and then reboot, sometimes after
    bluescreen. Remove remote control agent and all is find. Winxp pro, zen
    4.
    Thanks
    Dave

    > On Sat, 20 Aug 2005 02:26:45 GMT, [email protected] wrote:
    >
    > > I have always installed the remote control agent on my workstations.
    > > However when I intall it on the latest ones, they computers will just
    be
    > > getting to the windows desktop and then reboot, sometimes after
    > > bluescreen. Remove remote control agent and all is find.
    >
    > which agent? try the latest agent, try the latest graphic card drivers,
    try
    > without installing the mirror driver
    > --
    >
    > Marcus Breiden
    It is the latest zen 4 agent.
    >
    > Please change -- to - to mail me.
    > The content of this mail is my private and personal opinion.
    > http://www.edu-magic.net

  • 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.

  • How to get lauchctl daemons/agents to run only once a day

    How do you get a daemons/agents to run only once a day regardless of the error code of the .sh you are running?
    (not I'm not looking for run once or run on reboot. I want a job to run at 3am every day and it has several bash commands in it. Regardless of the returns by any of the commands in the script, I only want this to run once - NO RESPAWN).

    Ok still not working.. here is the plist
    the .sh file does file processing and then uploads xml files to my server and should run once a day. Here I have it running at 11:45am. It completes and then runs again and again and again.
    The plist is placed in LaunchAgents and loaded with $launchctl load com.iclassicnu.crontabtest.plist
    ideas?
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>label</key>
    <string>com.iclassicnu.crontabtest</string>
    <key>ProgramArguments</key>
    <array>
    <string>/Users/dan/Desktop/iClassicNu/Idea/Forexite/ForexUpdate.sh</string>
    </array>
    <key>WorkingDirectory</key>
    <string>/Users/dan/Desktop/iClassicNu/Idea/Forexite</string>
    <key>OnDemand</key>
    <false/>
    <key>Nice</key>
    <integer>1</integer>
    <key>StartCalendarInterval</key>
    <dict>
    <key>Hour</key>
    <integer>11</integer>
    <key>Minute</key>
    <integer>45</integer>
    </dict>
    <key>StandardErrorPath</key>
    <string>/Users/dan/tmp/icnTest1.err</string>
    <key>StandardOutPath</key>
    <string>/Users/dan/tmp/icnTest1.out</string>
    </dict>
    </plist>

  • Domain Agents and E6900 with multiple NICs.

    Hello,
    I have some issues configuring Sun management Center 3.6 (and 3.6.1) on a network with this characteristics:
    2 x E6900 (with 2 Domains each one)
    1 x v210
    The Server Component of Sun Management Center is installed on the v210. In this machine are installed the Platform Agents of the 2 System Controllers of the 2 E6900.
    Each domain has installed de Sun Management Center Agent.
    The network configuration of the Domains is this:
    Each domain has 3 NIC on 3 different network interfaces, and each NIC has its own hostname. One of this NIC is destinated to the administration network to be used for the Sun Management Center. This nic, as I said before, has its own hostname but it its different of the nodename (the node name is the same as the public interface of the domain, not the administration interface).
    The Domains does not use DNS, and the information included on the /etc/hosts is related to local NICs and the NICs of the other Domains, but anyone contains the NIC of the admin interface of other domain nor the NIC of the v210.
    The v210 does not has DNS neither, and has only their own information on /etc/hosts.
    All Domains has Solaris 9, and v210 has Solaris 10.
    Basically the problem is:
    "The Domain Agents cannot communicate with SunMC Server", when I manually add each agent. The discovery process doesn't work neither.
    I checked the domain-config.x of one domain and it shows:
    agent = {
    agentServer = "venwas1"
    logicalAddressMode = "ip"
    snmpPort = "1161"
    "venwas1" is the hostname of the public interface, nor the administration interface.
    I changed the value for the hostname of the administration interface with no success; then changed for the ip address of the administration interface; and no success neither.
    The default platform agent works, but does not appers with the corrent icon on the SunMC console. Its appears like a folder icon, and the documentation said that the Platform Agents is represented with a specific Icon.
    Please, anyone can help me ?
    Thanks in advance.

    Hi Alejandro,
    I checked the domain-config.x of one domain and it
    shows:
    agent = {
    agentServer = "venwas1"
    logicalAddressMode = "ip"
    snmpPort = "1161"
    nwas1" is the hostname of the public interface, nor
    the administration interface.
    I changed the value for the hostname of the
    administration interface with no success; then
    changed for the ip address of the administration
    interface; and no success neither.If you just change the hostname or IP, but don't do anything else, it won't work as the Agent has already created security keys for that old entry and needs to be reseeded. Change the entry to the IP that's on the same network as your SunMC Server, then run this command on the Agent while it's turned off:
    /opt/SUNWsymon/sbin/es-run base-usm-seed.sh -s <SEED> -c agent
    ..replacing <SEED> with the same seed/password you used on your SunMC Server. Then start the Agent back up, wait for it a couple minutes, and try to make an icon for it again.
    The default platform agent works, but does not appers
    with the corrent icon on the SunMC console. Its
    appears like a folder icon, and the documentation
    said that the Platform Agents is represented with a
    specific Icon.If the icon is incorrect then your SunMC Server is missing some files (or you've found a bug). You'll want all these addons installed on your Server:
    Dynamic Reconfiguration for Sun Fire High-End and Midrange Systems
    Sun Fire Midrange Systems Platform Administration
    Sun Fire Midrange Systems Domain Administration
    If you think you may be missing some (look in /var/opt/SUNWsymon/install/install.[timestamp] to see how you answered questions during your last install) you can run /opt/SUNWsymon/sbin/es-inst again and point it to your distribution media and it will only ask about packages that may be missing. If you do end up adding in some of the Midrange addons then a simple Console restart should refresh your Platform icons.
    Regards,
    [email protected]
    http://www.HalcyonInc.com

  • Mapping del credere agent and consignment stockist in sap sd

    Dear Gurus
    My client has trading business with IOCL company acted as a del credere agent and consignment stockist. Generally, IOCL sending the material our company go down. we do the business with the customers and we are paying the amount to the IOCL in advance and we are taking the money from the customer. For doing this business we are getting from the IOCL. we are also maintaining RG23D register. Our go downs are registered as depot. But we are not selling the material directly, please tell me how can we map this scenario.
    Regards
    thirupathi

    hi,
    Sales office is termed as an internal organisation element in SAP. ie:- Its a representation of the company at a specified geography.
    The distributor is always a customer for the business. The operations of the distributor are completely different from the company. Hence, mapping distributor as a sales office is completely ruled out.
    The distributors can be taken as a DISTRIBUTION CHANNEL in the org structure.
    All the distributors are created as customers in a specific sales area.
    Secondary sales is a business activity happening from the distributor to the dealer.
    So, in any business automation(not only SAP) we need not automate this activity.
    This would be automated by the distributors. We can only frame business regulations in domain for the secondary sales but not automate it.
    Reward if helpful.
    regards,
    sriram

  • ZenWorks Agent and Java 1.7

    I am working to use ZenWorks to patch all of our SLES/RedHat servers and I am having issues on the very first client I am trying to set up. When I try to install the agent, using either the complete or network install .bin, I run into the following error....
    Cmd: '/bin/sh /opt/novell/zenworks/stage/installJava.sh INSTALL_JRE'
    Exiting with error code -1.
    Exiting with error code 255.
    I realize that this is because my server already has JDK7 installed on it. The servers that I need ZenWorks to patch are production servers which require an updated java (and by updated, I require Java 7 - not the most up to date Java 6). I cannot simply uninstall JDK7 to allow the Zen Agent Installer to install the old JRE without breaking production servers. I found TID 7010783, but it does not quite solve my problem.
    Any help that can be offered is appreciated!

    Ahilton,
    look at the "cause" section of the TID "Prior to 11.3, the ZENworks xplat agent has problems with jre 1.7 due to new security features in the jre", is that a clue?
    Shaun Pond

  • Manual Zen agent removal

    I am trying to upgrade my Zen agent install from Zen 6.5sp2 agent to Zen
    7sp1 agent. There appears to be a problem with my current install of the Zen
    6.5 agent that prevents the install from automatically removing it pryor to
    the Zen 7 install. I have tried uninstalling the 6.5 agent manually through
    add/remove programs but the uninstall fails.
    My question is this....
    How do I remove the Zen 6.5 agent manually so that all traces are gone from
    my machine? Thanks...
    Mike

    Rolf Lidvall wrote:
    >> How do I remove the Zen 6.5 agent manually so that all traces are gone
    >> from my machine? Thanks...
    >
    > It's not easy doing that manually because it's installed
    > with MSI-technology. The safest way is to use this tool,
    > download link is in the document:
    > "Windows Installer CleanUp Utility"
    > http://support.microsoft.com/kb/290301
    That tool doesn't remove zen-agent. It just can remove installer
    configuration for it. In order to really remove agent you should use
    msiexec /X package.msi or msiexec /X{package_GUID}. In Zen 6.5 case that
    would be MsiExec.exe /X{51E7C053-8ED5-4BB8-AEA7-69AECED4A282} (or
    something like that. Right line can be found in
    /HKLM/Software/Microsoft/Windows/CurrentVersion/Uninstall) .
    Cleaning installer configuration might help solving
    installation/uninstallation problems though, so if those above lines
    don't work, then use CleanUP utility and try again.
    Timo Pietil

  • Access Manager Policy Agent and Oracle AS

    Hi,
    my system uses Oracle Application Server. The security dept use Sun Access Manager. I need to integrate the security of the Oracle system with the policy agent. Where this gets a little confusing is that one of my developers tells me that this is difficult to implement and that Sun arent planning on supporting the Oracle AS in future.
    What I would like is some clarification from the horses mouth so to speak. In particular is it possible to integrate the policy agent and Oracle AS, and are Sun committed to supporting and developing for this.
    Thanks,
    Andy.

    "Where this gets a little confusing is that one of my developers tells me that this is difficult to implement"
    "it is NOT an implementation but an integration ! difficult ? why ?"
    "and that Sun arent planning on supporting the Oracle AS in future."
    There is a PA 2.2 for Oracle 10g ! It is the latest version(2.2 I mean). I don't see any reasons why Sun should not continue. But it is ONLY my point of view...
    "What I would like is some clarification from the horses mouth so to speak. In particular is it possible to integrate the policy agent and Oracle AS, and are Sun committed to supporting and developing for this."
    Of course it is possible because you can find the PA that will integrate your Oracle AS with a Sun AM.
    1) Please read the documentation.
    http://docs.sun.com/app/docs/coll/1322.1
    Download the one for Oracle and read also the user guide.
    PA are very easy to integrate if you know what you do... Espec. und. the AM auth and sso... If you can be helped by a AM guy from your comp. it is welcome... It is a j2ee agent and of course the PA will make what is necessary to redirect you to AM at login time and later to auth. your request...2)
    2) Download the soft and do the job :-)
    Product Downloads
    Sun Java System Access Manager Policy Agent 2.2 for Oracle Application Server 10g
    http://www.sun.com/download/products.xml?id=455d52ed
    I did plenty of int. with Sun/Bea/Tomcat AS(don't forget there are also webserver agents like Apache PA) with AM and it is not a big deal. Not Oracle, but it is an AS and I don't see why it should be difficult...
    Hope this helps a bit.

  • New Agent and Image-safe Data

    Just built new images and used the latest agent from May 24,
    2010/ZDM7SP1IR4HP4 (Agent v7.0.173.100324) - it appears that this new
    agent is not respecting a specified Restore Mask. I'm basing this on the
    observation that freshly imaged machines are retaining the previous
    computer name as stored in the image-safe data - I use my own routine
    for naming that runs during mini-setup, which is why I have a restore
    mask in place.
    I've confirmed that the proper restore mask is set both in the ziswin
    gui and in the registry (HKLM\Novell\ZENworks\ZISWin Do Not Restore
    Mask, REG_DWORD). Setting the ziswin mode to "Disable" resolves the
    behaviour and naming conforms to my routine. I tested on another machine
    and with the Agent in "Restore" mode the history reports the status as
    "Successful...restore mask was 0x00000020". This mask is incorrect and
    specifies only the "Windows SID" as the data not to restore.
    I'll forward this to Novell...curious if anyone else has seen this
    behaviour.

    jd,
    It appears that in the past few days you have not received a response to your
    posting. That concerns us, and has triggered this automated reply.
    Has your problem been resolved? If not, you might try one of the following options:
    - Visit http://support.novell.com and search the knowledgebase and/or check all
    the other self support options and support programs available.
    - You could also try posting your message again. Make sure it is posted in the
    correct newsgroup. (http://forums.novell.com)
    Be sure to read the forum FAQ about what to expect in the way of responses:
    http://forums.novell.com/faq.php
    If this is a reply to a duplicate posting, please ignore and accept our apologies
    and rest assured we will issue a stern reprimand to our posting bot.
    Good luck!
    Your Novell Product Support Forums Team
    http://support.novell.com/forums/

Maybe you are looking for