Apply add-on bundle without Zenworks agent installed?

Hi all,
I've created an add-on image file from a bundle within ZCC, but I can't apply it when imaging a computer. It says it can't find any installed Zenworks agent, and that is true, since it is not part of the base image. Instead it gets installed when Windows boots up.
I found this post that says you can use another add-on image to create an empty directory structure on the computer before you apply the add-on image, thus fooling it to believe the agent is installed.
This doesn't seem to work here, though, maybe because we have 64-bit Windows 7. I changed the directory structure to reflect the C:\Program Files (x86)\ folder, but it doesn't seem to work.
Is there any workaround for this, preferrably without having to install the agent within the base image?
Thanks in advance!
Regards,
Pr

Oh well... this was quite silly. I found the answer myself, and it seems that if you only create an add-on image with empty folders, it will not be created on the workstation (although there was no message to indicate that). But when I put a dummy text file into the \Program Files (x86)\Novell\ZENworks\work folder, the structure was created and I was able to push out the add-on image file afterwards without the agent installed.

Similar Messages

  • ZLM Agent Install Fails - NOTHING_PROVIDES_DEP:

    Hi,
    I am trying to install the zlm agent (ZLM 7.3 IR2) on a SLES 11 box.
    I have extracted the ZLM Server ISO image files, and put it on an NFS server. The client box then mounts the NFS share and I run the command
    ./zlm-install -a -i
    Sometimes the installation goes through fine, but lately I am getting the following errors on the agent install
    Installing Component : ZENworks Agent
    Installing ZENworks Agent | | 0% NOTHING_PROVIDES_DEP: /bin/sh needed by rug-7.3.2.0-0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-utilities-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zmd-tess-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/bash needed by novell-zenworks-install-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/bash needed by novell-zenworks-zmd-settings-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: libxml2 needed by novell-zenworks-zmd-rmagent-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zmd-policymanager-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zmd-policyenforcers-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: libc.so.6 needed by novell-zenworks-x11vnc-0.6.1-2.novell.0.8.i586
    NOTHING_PROVIDES_DEP: libc.so.6 needed by novell-zenworks-tightvnc-1.2.9-6.novell.0.7.i586
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zislnx-7.3.2-0.0.0.i586
    NOTHING_PROVIDES_DEP: libc.so.6()(64bit) needed by zmd-inventory-7.3.2.0-0.0.x86_64
    NOTHING_PROVIDES_DEP: 'gconf2 >= 2.2.1' needed by novell-zenworks-zmd-gconfpolicyenforcers-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by zen-updater-7.3.2-0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zlm-release2-7.3.2-0.0.0.noarch
    DEP_PROVIDERS_NOT_INSTALLABLE: 'novell-zenworks-zislnx >= 7.0.0' needed by novell-zenworks-zmd-imgagent-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zmd-tess-7.3.2-0.0.0.x86_64
    Install of ZENworks Agent failed.
    Install has not completed
    Here is the output from the log file
    26 Mar 2010 13:08:43 INFO Daemon Received signal SIGTERM
    26 Mar 2010 13:08:43 WARN ShutdownManager Preparing to shut down...
    26 Mar 2010 13:08:43 INFO UnixWebServer Unix server stopped
    26 Mar 2010 13:08:44 WARN ShutdownManager Shutting down daemon...
    26 Mar 2010 13:08:44 INFO Daemon Final RSS size is 25708 KB
    26 Mar 2010 13:08:51 INFO Daemon Starting ZMD version 7.3.2
    26 Mar 2010 13:08:51 INFO Daemon Using Mono 1.2.6
    26 Mar 2010 13:08:51 INFO WebCache Expiring cached files...
    26 Mar 2010 13:08:51 INFO KeyManager Loading key whitelist
    26 Mar 2010 13:08:51 INFO Daemon Loading trusted certificates...
    26 Mar 2010 13:08:51 WARN NetworkManagerModule Failed to connect to NetworkManager
    26 Mar 2010 13:08:51 INFO PackageManagementModule Using SAT backend
    26 Mar 2010 13:08:51 INFO RPMBackend Loading installed packages
    26 Mar 2010 13:08:51 INFO RPMBackend Finished loading installed packages
    26 Mar 2010 13:08:51 INFO ModuleLoader Loaded 'NetworkManager' - 'NetworkManager support'
    26 Mar 2010 13:08:51 INFO ModuleLoader Loaded 'Package Management' - 'Package Management module for Linux'
    26 Mar 2010 13:08:51 INFO ModuleLoader Loaded 'ZENworks Server' - 'SOAP methods used by a ZENworks server'
    26 Mar 2010 13:08:51 INFO ModuleLoader Loaded 'XML-RPC interface' - 'Export ZMD public interfaces over XML-RPC'
    26 Mar 2010 13:08:51 INFO ServiceManager Not loading existing services
    26 Mar 2010 13:08:51 WARN Daemon Not starting remote web server
    26 Mar 2010 13:08:51 INFO UnixWebServer Unix server listening for connections.
    26 Mar 2010 13:08:51 INFO DaemonHealth Current RSS size is 18740 KB
    26 Mar 2010 13:09:01 INFO ServiceManager Adding service: file:///mnt/data/packages/edir/sles-11-x86_64
    26 Mar 2010 13:09:02 INFO ServiceManager Successfully added service 'edir'
    26 Mar 2010 13:09:02 INFO ServiceManager Adding service: file:///mnt/data/packages/imaging/sles-11-x86_64
    26 Mar 2010 13:09:02 INFO ServiceManager Successfully added service 'imaging'
    26 Mar 2010 13:09:02 INFO ServiceManager Adding service: file:///mnt/data/packages/server/sles-11-x86_64
    26 Mar 2010 13:09:02 INFO ServiceManager Successfully added service 'server'
    26 Mar 2010 13:09:02 INFO ServiceManager Adding service: file:///mnt/data/packages/mono/sles-11-x86_64
    26 Mar 2010 13:09:02 INFO ServiceManager Successfully added service 'mono'
    26 Mar 2010 13:09:02 INFO ServiceManager Adding service: file:///mnt/data/packages/java/sles-11-x86_64
    26 Mar 2010 13:09:02 INFO ServiceManager Successfully added service 'java'
    26 Mar 2010 13:09:03 INFO ServiceManager Adding service: file:///mnt/data/packages/sles-11-x86_64/sles-11-x86_64
    26 Mar 2010 13:09:03 INFO ServiceManager Successfully added service 'sles-11-x86_64'
    26 Mar 2010 13:09:03 INFO ServiceManager Adding service: file:///mnt/data/packages/runtime-deps/sles-11-x86_64
    26 Mar 2010 13:09:03 INFO ServiceManager Successfully added service 'runtime-deps'
    26 Mar 2010 13:09:03 INFO ServiceManager Adding service: file:///mnt/data/packages/client/sles-11-x86_64
    26 Mar 2010 13:09:03 INFO ServiceManager Successfully added service 'client'
    26 Mar 2010 13:09:07 INFO Progress Progress.Stop Message: NOTHING_PROVIDES_DEP: /bin/sh needed by rug-7.3.2.0-0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-utilities-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zmd-tess-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/bash needed by novell-zenworks-install-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/bash needed by novell-zenworks-zmd-settings-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: libxml2 needed by novell-zenworks-zmd-rmagent-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zmd-policymanager-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zmd-policyenforcers-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: libc.so.6 needed by novell-zenworks-x11vnc-0.6.1-2.novell.0.8.i586
    NOTHING_PROVIDES_DEP: libc.so.6 needed by novell-zenworks-tightvnc-1.2.9-6.novell.0.7.i586
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zislnx-7.3.2-0.0.0.i586
    NOTHING_PROVIDES_DEP: libc.so.6()(64bit) needed by zmd-inventory-7.3.2.0-0.0.x86_64
    NOTHING_PROVIDES_DEP: 'gconf2 >= 2.2.1' needed by novell-zenworks-zmd-gconfpolicyenforcers-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by zen-updater-7.3.2-0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zlm-release2-7.3.2-0.0.0.noarch
    DEP_PROVIDERS_NOT_INSTALLABLE: 'novell-zenworks-zislnx >= 7.0.0' needed by novell-zenworks-zmd-imgagent-7.3.2-0.0.0.x86_64
    NOTHING_PROVIDES_DEP: /bin/sh needed by novell-zenworks-zmd-tess-7.3.2-0.0.0.x86_64
    Those packages deps are installed and I have a SLES 11 repo setup - which works.
    Thanks.

    Hi Rainer,
    Thanks for the response.
    I tried what you said:
    rpm -q --whatprovides /bin/sh
    bash-3.2-147.3
    Including the rebuild, but it didn't work.
    I doubt its an RPM problem, because I can install any other package.
    host-10-121-92-73:/mnt/agent # rpm -aq | grep squid
    yast2-squid-2.17.10-1.32
    host-10-121-92-73:/mnt/agent # zypper in squid
    Loading repository data...
    Reading installed packages...
    Resolving package dependencies...
    The following NEW package is going to be installed:
    squid
    Overall download size: 1.3 M. After the operation, additional 4.4 M will be used.
    Continue? [YES/no]: yes
    Retrieving package squid-2.7.STABLE5-2.3.x86_64 (1/1), 1.3 M (4.4 M unpacked)
    Installing: squid-2.7.STABLE5-2.3 [done]
    Additional rpm output:
    Updating etc/sysconfig/squid...
    host-10-121-92-73:/mnt/agent # rpm -aq | grep squid
    yast2-squid-2.17.10-1.32
    squid-2.7.STABLE5-2.3
    While I was writing this, I tried to install the agent again after that squid rpm install and it appears to be working now.
    It looks like the rebuild didn't do the trick, but install any new RPM sorts it out.
    Thank you very much for the help.

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

  • HT1977 i want to add a app i just purchased to my i phone. nut when i click apply it asks me if i want to remove the rest of my apps.. which i dont.. how can i add the app without deleting my other apps

    i want to add a app i just purchased to my i phone. nut when i click apply it asks me if i want to remove the rest of my apps.. which i dont.. how can i add the app without deleting my other apps

    You can sync an iPhone to only one computer. If you connect it to a different computer (or you have never connected it to a computer) it will delete all iTunes content on the phone and replace it with the iTunes content on the current computer. As Avis says, you can transfer your purchases to the computer you are about to sync to, but only if that computer is authorized to the same account that the content was downloaded under.

  • ZENworks agent update from workstation.

    Hi there,
    Is there a way to get workstations to update themselves automatically with the latest version of the ZENworks agent. (ZCM 11.2.3.a is what we have)
    We have a standard image which has a older version of the ZCM agent on it. Images are pulled down and the workstations are automatically built.
    Various bundles are then installed automatically on the workstations. When we update the image with other changes etc, we will add the new agent to it.
    But until we do that, instead of me having to manually check for all new machines built in the last week / month and then assign the agent update to them,
    is there a process, script, bundle of something that can run on the workstation to update the agent itself to the latest version we have.
    We are using ZCM 11.2.3a and we need to do this without having to manually visit 200-400 machines.
    Thanks
    Mark

    While I (And Microsoft) recommends configuring your Router/Switches to
    pass WOL packets from your trusted WOL Servers (Primaries in this case),
    it is also possible to use WOL Proxies to allow this to happen across
    your subnets.
    There are also some Windows settings that may be necessary to allow WOL
    to work from a deep sleep state. I would recommend researching those as
    well.
    If you are concerned about deploying updates when users are not using
    the devices, WOL is something with which I recommend you become more
    comfortable using.
    On 2/10/2014 8:06 AM, gshaw0 wrote:
    >
    > craig_wilson;2305537 Wrote:
    >> And ask folks to Leave PCs on as well as schedule a WOL task to run for
    >> those missed. Then they should all be ready by start of the next school
    >> day.
    >>
    >>
    >> On 2/9/2014 3:00 AM, Shaun Pond wrote:
    >>> Gshaw0,
    >>>
    >>> I can't say that it will be non-disruptive, no. Can you not schedule
    >>> updates to happen out of hours?
    >>>
    >>
    >>
    >> --
    >> --
    >> Craig Wilson
    >> Novell, Inc
    >>
    >> Any Comments or Posts are only my views and not Novell's
    >> Accuracy Attempted but not guaranteed.
    >
    > 2500 PCs across 5 sites in a couple hundred different rooms, can't
    > guarantee even half of them being on. WOL isn't routed across VLANs so
    > that won't do the trick either, also not had great experiences with it
    > in the past as it seems to rely on machines having had a clean shutdown
    > and the socket not being turned off in between (once that happens WOL
    > doesn't seem to have any effect until the machine gets a clean startup \
    > shutdown cycle)
    >
    >
    Craig Wilson
    Novell, Inc
    Any Comments or Posts are only my views and not Novell's
    Accuracy Attempted but not guarenteed.

  • Search for ZfD Agent install script

    I am looking for a script / batch file for installation of the ZENworks agent without reboot of the workstation.
    I am just updating from ZfD 7 SP1 ir3a to ir4 and if I install it manually and start the ZENworks services after install everything is still operational without reboot.
    However if I install the agent with a ZENworks application package it always needs a reboot to activate the ZENworks services again - especially the Workstation-Manager
    I tried it with pre- and post launch and distribution scripts, and with batch file installation. Everytime when the Workstation-Manager stops the installation ends but the post-scripts and batch processing stops as well. It always requires a reboot to activated the Agent again - or a manual start of the Workstation-Manager service.
    I need to find just a way to call a batch file after the MSIEXEC process finishes in order to perform a "net start Workstation-manager".
    The difference to other invoronments might be, that the Application is assigned to the Workstations instead to the users like in most other environments.
    Thanks for your ideas, Klaus

    Well .... [toot horn]
    This is a link to a script I wrote in AutoIt that I used for many ZfD6 - 7 deployments. Was very successfully in getting the agent out and you run it from the login script.
    Zenworks 4x - 7.x Workstation Agent Automated Deployment - Novell: ZENworks FAQ - Tek-Tips
    I didn't write it to do a removal of the agent, but would be simple enough to be added. On the same forum site, in the Zen FAQ's I also posted the source code for the script I have been using to do ZCM deployments. In it has the code you would need to add to facilitate the uninstall of the agent so you can do a reinstall.
    Originally Posted by Croaker
    You may need put *everything* in a single batch file.
    I.e. app copies the zfdagent.msi to the workstation (it won't work off a
    server, because as soon as you stop the workstation helper/manger, the
    workstation will lose the ability to install from the network)
    Then executes the batch file
    The batch file stops the zenworks services, unloads the NAL (may not be
    necessary, not sure if the msi will do this)
    Batch file then installs the ZFD agent with the noreboot option.
    batch file restarts each service
    Problem will be the batch file really can't re-start the nal correctly.
    Since the batch file will be running under the SYSTEM scope, anything it
    launches will be under that scope too (ie.. the NAL), so when it loads, it
    wouldn't see any user-based apps.
    >>> On 7/1/2009 at 10:36 AM, in message
    <[email protected]>,
    dgibbons<[email protected]> wrote:
    > I would like to echo your question. I have a problem right now in
    > whichupgrading the agents from ZfD 7 SP1 ir3a to ir4 will break the agent
    > andthe only way I can recover is to manually uninstall the agent,
    > rebootand reinstall with ir4. I have not yet been successful in scripting
    > it(but then I am not that smart when it comes to scripting either) so
    > ifanyone has a good solution I too am very much wanting a method
    > thatworks. Thanks
    > Darcy--
    dgibbons--------------------------------------------------------------------
    ----dgibbons's Profile:
    > NOVELL FORUMS - View Profile: a10425 this thread:
    > Search for ZfD Agent install script - NOVELL FORUMS

  • Is it possible to run Posture using ISE 1.2 without NAC Agent provisioning?

    Is it possible to run Posture using ISE 1.2 without NAC Agent provisioning?
    -My customer does not want to push NAC Agent installation on BYOD type of computers (non-managed by the company computers).
    -The requirement is to check for posture only company owned wired, wireless, and VPN connected Windows computers. The rest of the endpoints should be considered as posture incompliant, and limited access to the network should be allowed.
    -No certificates are used.
    -I’ve configured the required posture check, and it all works fine if a PC has NAC Agent manually installed (without ISE Client Provisioning). However, when I use a PC without NAC Agent, it is redirected to Client Provisioning Portal and is stuck there as Client Provisioning is deliberately not configured in ISE.
    -If I remove Posture Remediation Authorization Profile that does URL redirect, the posture does not work.
    -For now I'm testing it on wired endpoints.
    Is there a way to configure ISE to fulfill the listed above requirements?
    Any ideas would be appreciated.
    Thanks,
    Val Rodionov

    Everyone who finds reads this article,
    I'm answering my own quesiton "Is it possible to run Posture using ISE 1.2 without NAC Agent provisioning?"
    The answer is Yes.
    After doing research and configuration testing I came up with a solution, and it works fine for wired and VPN connections. I expect it to work on wireless endpoints as well.
    ISE configuration:
    Posture General Settings - Default Posture Status = NonCompliant
    Client Provisioning Policy - no rules defined
    Posture Policy - configured per requirements
    Client Provisioning (under Administration > Settings) - Enable Provisioning = Enable (it was disabled in my first test)
    Authorization Policies configured as regular posture policies
    The result:
    After successful dot1x authentication posture redirect happens. If the PC does not have NAC Agent preinstalled, the browser is redirected to Client Provisioning Portal and a default ISE message is displayed (ISE is not able to apply and access policy... wait one minute and try to connect again...). At the same time, the endpoint is assigned NonCompliant posture status and proper authorization policy is applied. This is what I wanted to achieve.
    If NAC Agent was preinstalled on the PC, after successful dot1x authentication the NAC Agent pops up and performs posture check. If posture is successful, posture compliant authorization policy is applied. If posture check fails, NonCompliant posture status is assigned and posture non-compliant authorization policy is applied. Which is the expected and needed result.
    The only part that is not perfect it the message displayed to the end-user when posture is about to fail. I did not find a place to change the text of that message. I might need to open TAC case, so this file can be manually found and edited from CLI (root access).
    Best,
    Val Rodionov

  • Opinions... desktop image with or without ZCM agent?

    I'm working on deploying ZCM 10 to my company and was wondering what your opinions are on deployment method for newly ghosted computers (I'm going to use a deploy task for all existing computers). What are the pros/cons of installing the Zen Agent with the ghost image prior to sysprep (we still use ghost for imaging by the way...) versus scripting the install of the agent after the desktop is imaged and entered into the domain?
    I've seen some posts in the forums with people having problems with duplicate GUIDS. I imagine that you have to take some precautions if you install the agent prior to sysprepping the image to avoid this kind of problem.
    The benefit to manully installing or scripting the install after the computer is entered in the domain is you can easily update the agent with the latest version without needing to modify your image.
    Right now our image has the ZFD7 agent pre-installed, but of course that agent is old and has not changed in quite a while. I'm inclined to script the install of the agent instead of including it in the image, but I'd love to hear other opinions or methods.
    Thanks!

    Originally Posted by magic31
    Our script is launched as post sysprep command, there are different actions in there but it would depend on what you are installing modifying.
    The bit to install the ZCM agent is quite straight forward utilizing the REG ADD command, this keeps the screen nice and tidy and only presents a small dialog screen without logging into the desktop.
    Just put something similar in your batch +other things you wish to do and run that as (one of the) post sysprep actions.
    Code:
    REM ZCM 10 agent
    REG ADD %KEY%\02-160 /VE /D "Installing ZCM agent..." /f
    REG ADD %KEY%\02-160 /V 01 /D "C:\Install\ZCM10\PreAgentPkg_Agent.exe -q" /f
    REM ADDING A TIMED PAUSE USING DELAY.EXE TO LET THE ZCM AGENT INSTALL AND REBOOT
    REG ADD %KEY%\02-161 /VE /D "Wating for ZCM agent install to complete.." /f
    REG ADD %KEY%\02-161 /V 01 /D "C:\Install\delayit test.exe 20000" /f
    Where did you get the the delay.exe that you are using from? btw, the script says "delayit text.exe" is that a typo? just wondering, thanks.

  • DPM 2012 Manual Agent Install Fails

    Hello Everyone,
    Using DPM 2012 SP1, I've been stuck on an issue for some time now in trying to get a DPM agent install accomplished on a certain server. The DPM server resides on a parent domain and the server that I am having an issue with is on a child domain. Other servers
    on the child domain have installed the agent without issue when doing it manually.
    Here is the command I use (as an administrator):
    net use X: \\DPMSERVERNAME.parentdomain.com\c$ 
    cd /d X:\Program Files\Microsoft System Center 2012\DPM\DPM\agents\RA\4.1.3465.0\amd64\1033
    DPMAgentInstaller_KB2991995_AMD64.exe dpmservername.parentdomain.com
    The installation proceeds through the Microsoft License Terms, begins to install and then backs out. The error message that is generated states: "DPMAgentinstaller failed with error code = 0X80070643 error says: fatal error during installation"
    In researching the 1708 error within the log file it lead me to the fact that maybe the firewall on the target server was the issue. I
    ran this suggested fix on the target server:
    netsh advfirewall firewall set rule group=\"@FirewallAPI.dll,-29502\" new enable=yes
    netsh advfirewall firewall set rule group=\"@FirewallAPI.dll,-34251\" new enable=yes
    netsh advfirewall firewall add rule name=dpmra dir=in program=\"%PROGRAMFILES%\\Microsoft Data Protection Manager\\DPM\\bin\\DPMRA.exe\" profile=Any action=allow
    netsh advfirewall firewall add rule name=DPMRA_DCOM_135 dir=in action=allow  protocol=TCP localport=135 profile=Any
    The issue still persists.
    The MSDPMAgentinstall log file says the following at the end:
    Property©: Date = 1/7/2015
    Property©: MsiNetAssemblySupport = 4.0.30319.18408
    Property©: MsiWin32AssemblySupport = 6.1.7601.17514
    Property©: MsiRunningElevated = 1
    Property©: Privileged = 1
    Property©: USERNAME = Windows User
    Property©: DATABASE = c:\b1e38ee30069ed00e510\DPMRA.msi
    Property©: OriginalDatabase = c:\b1e38ee30069ed00e510\DPMRA.msi
    Property©: SOURCEDIR = c:\b1e38ee30069ed00e510\
    Property©: VersionHandler = 5.00
    Property©: ROOTDRIVE = c:\
    Property©: EXECUTEACTION = INSTALL
    Property©: ACTION = INSTALL
    Property©: UILevel = 5
    Property©: CostingComplete = 0
    Property©: OutOfDiskSpace = 0
    Property©: OutOfNoRbDiskSpace = 0
    Property©: PrimaryVolumeSpaceAvailable = 0
    Property©: PrimaryVolumeSpaceRequired = 0
    Property©: PrimaryVolumeSpaceRemaining = 0
    MSI © (68:E8) [09:38:14:119]: Note: 1: 1708 
    MSI © (68:E8) [09:38:14:119]: Note: 1: 2205 2:  3: Error 
    MSI © (68:E8) [09:38:14:119]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708 
    MSI © (68:E8) [09:38:14:119]: Note: 1: 2205 2:  3: Error 
    MSI © (68:E8) [09:38:14:119]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 
    MSI © (68:E8) [09:38:14:119]: 吰瞒
    MSI © (68:E8) [09:38:14:119]: 吰瞒
    MSI © (68:E8) [09:38:14:119]: Grabbed execution mutex.
    MSI © (68:E8) [09:38:14:119]: Cleaning up uninstalled install packages, if any exist
    MSI © (68:E8) [09:38:14:119]: MainEngineThread is returning 1603
    === Verbose logging stopped: 1/7/2015  9:38:14 ===
    Any ideas where to turn next?

    I do not have a Program Files\Microsoft System Center 2012\DPM\DPM\ProductionAgents\RA\4.1.3313.0\amd64
    file path on the DPm system.
    Rather Program Files\Microsoft System Center 2012\DPM\DPM\ProtectionAgents\RA\4.1.3313.0\amd64
    Still, I ran the DPMAgentInstaller_x64.exe
    from that file path and the agent did not install.
    Also, on the DPM server I have added the target machine name to the DPMRADmTrustedMachines
    group. I also made sure that the domain service account is in the same group. Still no luck.

  • Scheduler Agent Installed as Service Encrypted Password Change

    All,
    We have a Scheduler Agent installed as a service in Windows Server 2003, SP2. We want to change the password of the Master Repository. When I change the ODI_SECU_ENCODED_PASS in the odiparams.bat file it doesn't reflect this change in the service. I tried looking around in the snpsagent.conf wrapper file to see if the password is stored anywhere but dont' see it. I see it references a file called snpparams.bat, unfortunately I cannot find this file on our machine. If anyone knows how to get the new password to take effect without having to drop the agent and recreate it, thus losing all schedules that we've created, I would greatly appreciate the help.
    Thanks in Advance,
    Josh

    Hi Josh,
    the snpparamens.bat is exactly the same of odiparameter.bat. It had this name when the software was Sunopsis (SNP). Probably you saw the reference at some old document...
    If you drop the service nothing will be loose, just recreate it to get the new parameters. The scheduling list is stored, as everything in the ODI, at the repository, it means that all scheduling orders are at tables. Because of that you need to made a "update scheduler" when create a new scheduling.
    If you are still afraid, just create a new agent at another port (as service) and change the logical agent to it. Update the scheduller list an take a look if everthing is OK.
    After that you can drop the old service.
    Does it make any sense to you?

  • How to create a WMI filter in order to apply to machines that have Skype already installed with deploying a newer version of Skype

    Hi there,
    I was wondering whether anybody could tell me how to create a WMI filter in order to apply to machines that have Skype already installed with deploying a newer version of Skype.
    Your help would be much appreciated.
    Many thanks,
    Timbuctoo

    Hi,
    To create a WMI filter
    1.In the Group Policy Management Console (GPMC) console tree, right-click
    WMI Filters in the forest and domain in which you want to create a WMI filter.
    2.Click
    New .
    3.In the
    New WMI Filter dialog box, type a name for the new WMI Filter in the
    Name box, and type a description of the filter in the Description box.
    4.Click
    Add .
    5.In the
    WMI Query dialog box, either leave the default namespace (root\CIMv2) or enter another namespace by doing one of the following:
    ◦ In the
    Namespace box, type the name of the namespace that you want to use for the WMI query.
    ◦ Click
    Browse , select a namespace from the list, and then click
    OK .
    6.Type a WMI query in the
    Query box, and then click OK .
    7.To add more queries, repeat Steps 4 through 6 to add each query.
    8.After adding all queries, click
    Save .
    In the Query box, type the following WMI query:
    Select * from Win32_Product where Name LIKE “%Skype%”
    Best Regards,
    Erin

  • SCOM agent install fails Error 80070035 - the network path was not found

    I have deployed SCOM 2012 agents to most servers (2008, 2008 R2, 2012, 2012R2) in our estate but some either fail to install or are not monitored. I assume the two problems are related, but for now I am concentrating on the servers that fail completely.
    Installation is from the Discovery Wizard and I have about 20 servers that fail of various server versions.
    So looking at one specific server that is failing to install the agent - a 2008 standard service pack 2
    The firewall in on and file and printer sharing is enabled for domain, remote administration is enabled for domain
    I added a specific rule to allow TCP 5723 and 5724
    DCOM is enabled
    I can Ping the target server from the SCOM server by both name and FQDN - both return the same IP and our DNS server has only one entry for this server
    I can browse to the admin share \\server\C$ from the SCOM Server, using the same account that I specify for the agent install that is a domain admin with rights on this server (and on the other servers the agent
    did install to) and the server has plenty of disk space available
    I am not sure what else to look at so would welcome any ideas
    Thanks

    Hi Petro,
    I have a Agent installation failure cheat sheet, For your error 80070035 it is said to perform a manual installation.
    So i would like to understand which version of SCOM is this ? 2007 R2 or 2012 or 2012 r2 ?
    Also check if your agents have the WMI service started and enabled ?
    Also if yours is a SCOM 2007 R2 do you have a RMS & MS in your management group ? If yes then Pushing the agent installation from MS may cause such issue. So would suggest you push the installation from RMS.
    Also check if your Network connectivity meets the minimum requirement as recommended by SCOM. Below is applicable for Both SCOM 2007 R2 & SCOM 2012 & 2012 R2.
    Component A
    Component B
    Minimum Requirement
    Root management server or management server
    Agent
    64 Kbps
    Root management server or management server
    Agentless
    1024 Kbps
    Root management server or management server
    Database
    256 Kbps
    Also check if you have any Anti virus / Firewall which is blocking the install / communication. If yes disabe or add the "Monitoringhost.exe to the safe list or what your feature is.
    Check if you have another IP assigned to the NIC card and remove it tempraurly andchecl.
    Also post the event logs of the Agents which are in not monitored state for analysis.
    SCOM Agent installation failure error codes
    Error
    Error Code(s)
    Remediation Steps
    The MOM Server could not execute WMI Query "Select * from Win32_Environment where
    NAME='PROCESSOR_ARCHITECTURE'" on computer server.domain.com
    Operation: Agent Install
    Install account: domain\account
    Error Code: 80004005
    Error Description: Unspecified error
    80004005
    1.  Check the PATH environment variable.  If the PATH statement is very long, due to lots of installed third party software - this can
    fail.  Reduce the path by converting any long filename destinations to 8.3, and remove any path statements that are not necessary.
    2.  The cause
    could be corrupted Performance Counters on the target Agent.
    To rebuild all Performance counters including extensible and third party counters in Windows Server 2003, type the following commands at a command
    prompt. Press ENTER after each command.
    cd
    \windows\system32
    lodctr /R
    Note /R is uppercase.
    Windows Server 2003 rebuilds all the counters because it reads all the .ini files in the C:\Windows\inf\009 folder for the English operating system.
    How to manually rebuild Performance Counter Library values
    http://support.microsoft.com/kb/300956
    3.  Manual agent install. 
    The MOM Server could not execute WMI Query "Select * from Win32_OperatingSystem" on
    computer “servername.domain.com”
    Operation: Agent Install
    Install account: DOMAIN\account
    Error Code: 800706BA
    Error Description: The RPC server is unavailable.
    8004100A
    800706BA
    1.  Ensure agent push account has local admin rights
    2.  Firewall is blocking NetBIOS access
    3.  Inspect WMI health and rebuild repository if necessary
    4.  Firewall is blocking ICMP  (Live OneCare)
    5.  DNS incorrect
    The MOM Server failed to open service control manager on computer "servername.domain.com". Access is Denied
    Operation: Agent Install
    Install account: DomainName\User Account
    Error Code: 80070005
    Error Description: Access is denied.
    80070005
    80041002
    1.  Verify SCOM agent push account is in Local Administrators group on target computer.
    2.  On Domain controllers will have to work with AD team to install agent manually if agent push account is not a domain admin.
    Disable McAfee antivirus during push
    The MOM Server failed to open service control manager on computer "servername.domain.com".
    Therefore, the MOM Server cannot complete configuration of agent on the computer.
    Operation: Agent Install
    Install account: DOMAIN\account
    Error Code: 800706BA
    Error Description: The RPC server is unavailable.
    800706BA
    1.  Firewall blocking NetBIOS ports
    2.  DNS resolution issue.  Make sure the agent can ping the MS by NetBIOS and FQDN.  Make sure the MS can ping the agent by NetBIOS
    and FQDN
    3.  Firewall blocking ICMP
    4.  RPC services stopped.
    The MOM Server failed to acquire lock to remote computer servername.domain.com. This means there is already an agent management operation proceeding
    on this computer, please retry the Push Agent operation after some time.
    Operation: Agent Install
    Install account: DOMAIN\account
    Error Code: 80072971
    Error description: Unknown error 0x80072971
    80072971
    This problem occurs if the LockFileTime.txt file is located in the following folder on the remote computer:
    %windir%\422C3AB1-32E0-4411-BF66-A84FEEFCC8E2
    When you install or remove a management agent, the Operations Manager 2007 management server copies temporary files to the remote computer. One
    of these files is named LockFileTime.txt. This lock file is intended to prevent another management server from performing a management agent installation at the same time as the current installation. If the management agent installation is unsuccessful and
    if the management server loses connectivity with the remote computer, the temporary files may not be removed. Therefore, the LockFileTime.txt may remain in the folder on the remote computer. When the management server next tries to perform an agent installation,
    the management server detects the lock file. Therefore, the management agent installation is unsuccessful.
    http://support.microsoft.com/kb/934760/en-us
    The MOM Server detected that the following services on computer "(null);NetLogon" are not running. These services are required for push
    agent installation. To complete this operation, either start the required services on the computer or install the MOM agent manually by using MOMAgent.msi located on the product CD.
    Operation: Agent Install
    Remote Computer Name: servername.domain.com Install account: DOMAIN\account
    Error Code: C000296E
    Error Description: Unknown error 0xC000296E
    C000296E
    1.  Netlogon service is not running.  It must be set to auto/started
    The MOM Server detected that the following services on computer
    "winmgmt;(null)" are not running
    C000296E
    1.  WMI services not running or WMI corrupt
    The MOM Server detected that the Windows Installer service (MSIServer) is disabled on computer "servername.domain.com". This service is
    required for push agent installation. To complete this operation on the computer, either set the MSIServer startup type to "Manual" or "Automatic", or install the MOM agent manually by using MOMAgent.msi located on the product CD.
    Operation: Agent Install
    Install account: DOMAIN\account
    Error Code: C0002976
    Error Description: Unknown error 0xC0002976
    C0002976
    1.  Windows Installer service is not running or set to disabled – set this to manual or auto and start it.
    The Agent Management Operation Agent Install failed for remote computer servername.domain.com.
    Install account: DOMAIN\account
    Error Code: 80070643
    Error Description: Fatal error during installation.
    Microsoft Installer Error Description:
    For more information, see Windows Installer log file "C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameAgentInstall.LOG
    C:\Program Files\System Center Operations Manager 2007\AgentManagement\AgentLogs\servernameMOMAgentMgmt.log" on the Management Server.
    80070643
    1.  Enable the automatic Updates service…. Install the agent – then disable the auto-updates service if desired.
    Call was canceled by the message filter
    80010002
    Install latest SP and retry. One server that failed did not have Service pack installed
    The MOM Server could not find directory \\I.P.\C$\WINDOWS\. Agent will not be installed on computer "name". Please verify the required
    share exists.
    80070006
    1.  Manual agent install
    Possible locking on registry?
    http://www.sysadmintales.com/category/operations-manager/
    Try manual install.
    Verified share does not exist.
    The network path was not found.
    80070035
    1.  Manual agent install
    The Agent Management Operation Agent Install failed for remote computer "name". There is not enough space on the disk.
    80070070
    1.  Free space on install disk
    The MOM Server failed to perform specified operation on computer "name". The semaphore timeout period has expired.
    80070079
    NSlookup failed on server. Possible DNS resolution issue.
    Try adding dnsname to dnssuffix search list.
    The MOM Server could not start the MOMAgentInstaller service on computer "name" in the time.
    8007041D
    80070102
    NSlookup failed on server. Possible DNS resolution issue.
    Verify domain is in suffix search list on management servers.
    The Agent Management Operation Agent Install failed for remote computer "name"
    80070643
    1.  Ensure automatic updates service is started
    2.  Rebuild WMI repository
    3.  DNS resolution issue
    The Agent Management Operation Agent Install failed for remote computer "name". Another installation is already in progress.
    80070652
    Verify not in pending management. If yes, remove and then attempt installation again.
    The MOM Server detected that computer "name" has an unsupported operating system or service pack version
    80072977
    Install latest SP and verify you are installing to Windows system.
    Not discovered
    Agent machine is not a member of domain
    Ping fails
    1.  Server is down
    2.  Server is blocked by firewall
    3.  DNS resolving to wrong IP.
    Fail to resolve machine
    1.  DNS issue
    The MOM Server failed to perform specified operation on computer "name". Not enough server storage…
    8007046A
    1.  This is typically a memory error caused by the remote OS that the agent is being installed on.
    There are currently no logon servers available to service the logon request.
    8007051F
    1.  Possible DNS issue
    This installation package cannot be installed by the Windows Installer service. You must install a Windows service pack that contains a newer version
    of the Windows Installer service.
    8007064D
    1.  Install Windows Installer 3.1
    The network address is invalid
    800706AB
    Possible DNS name resolution issue.
    Tried nslookup on server name and did not get response.
    Verify domain is in suffix search list on management servers.
    The MOM Server failed to perform specified operation on computer servername.domain.com
    80070040
    1.  Ensure agent push account has local admin rights
    The MOM Server detected that the actual NetBIOS name SERVERNAME is not same as the given NetBIOS name provide for remote computer SERVERNAME.domain.com.
    80072979
    1.  Correct DNS/WINS issue.
    2.  Try pushing to NetBIOS name
    Gautam.75801

  • SCCM 2012 SP1 agent install via WSUS

    Hi guys,
    I'm having got an issue when I try installing the agent via WSUS. When I try installing manually everything seems to work.
    Here are the infos from the ccmsetup.log:
    ==========[ ccmsetup started in process 2252 ]========== ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Running on platform X86 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Updated security on object C:\WINDOWS\ccmsetup\cache\. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Launch from folder C:\WINDOWS\SoftwareDistribution\Download\Install\ ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    CcmSetup version: 5.0.7804.1000 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Ccmsetup command line: "C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe"  ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    LSJoinedToADDomain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Local Machine is joined to an AD domain ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    LSGetAssignedSiteFromAD ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    DhcpGetOriginalSubnetMask entry point is supported. ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Begin checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    spNamespace.Open(sNamespacePath), HRESULT=8004100e (e:\nts_sccm_release\sms\framework\ccmutillib\ccmiputil.cpp,1109) ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Finished checking Alternate Network Configuration ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    LSGetADSiteName ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Current AD site of machine is DE-Zeilarn ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Attempting to query AD for assigned site code ccmsetup 08.02.2013 13:45:46 196 (0x00C4)
    Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=2887256160)(MSSMSRangedIPHigh>=2887256160))))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=172.24.8.0)(mSSMSRoamingBoundaries=DE-Zeilarn)(mSSMSSiteCode=XYZ)))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSIsSiteCompatible : Verifying Site Compatibility for <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetSiteVersionFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetSiteVersionFromAD : Attempting to query AD for MPs for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetSiteVersionFromAD : Successfully retrieved version '5.00.7804.1000' for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSIsSiteCompatible : Site Version = '5.00.7804.1000' Site Capabilities = <Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities> ccmsetup 08.02.2013
    13:45:47 196 (0x00C4)
    LSIsSiteVersionCompatible : Site Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSIsSiteCompatible : Site <XYZ> Version '5.00.7804.1000' is compatible. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetAssignedSiteFromAD : Trying to Assign to the Site <XYZ> ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Got site code 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=XYZ))' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    OperationalXml '<ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
    <CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
    Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    HTTP is selected for Client. The current state is 0. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    The MP name retrieved is 'mysccmserver.mydomain.tld' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSL" Version="1"/><Property Name="SSLState" Value="31"/></Capabilities>' ccmsetup 08.02.2013
    13:45:47 196 (0x00C4)
    MP 'mysccmserver.mydomain.tld' is not compatible ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Retrieved 0 MP records from AD for site 'XYZ' ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
    <CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
    Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Security settings: Certificate Issuers =  ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    SslState value: 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Ccmsetup was run without any user parameters specified. Running without registering ccmsetup as a service. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Detected sitecode 'XYZ' from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMHTTPPORT:    80 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMHTTPSPORT:    443 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMHTTPSSTATE:    480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMHTTPSCERTNAME:     ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    FSP:     ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMCERTISSUERS:    CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMFIRSTCERT:    1 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Creating CCMCertStore ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMCERTID:    SMS;FB0F35392A7FF68D2FA9C97D0CD54A3E0057964E ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    No MP or source location has been explicitly specified.  Trying to discover a valid content location... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Looking for MPs from AD... ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Retrieving client operational settings from AD. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Received client operational settings: <ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>448</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers>CN=root-ca</CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F4308201DCA003020102021011B05A5A5C9B0BBA4299C744025DA257300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133303131363138303730375A180F32313132313232343138303730375A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A02820101009855D66E3C7F2CBA9E701E06597B77942120C27D6A4B7FACE3DB214363C20E6AD12BFFB7225A5D9B84A316B6EC20979007CB6FEE71A82D879091A0EEC7E07C7952EDA27ED31C76E63CF8ABA411B8BA79AB8B48B4FA4204085E8836B7F4619A0E29160528C91D205A8C4F1CBDF5C78CC27ED7C5BAA9369E74F7B610C77BAA777E5B31DF65DC562129D26A5C730161D7D1E2946B3953F8923BFE80A812AE2304A8B3701400CE11BF4F1521A693B9624BF25A19AD1A8E56DE9B99793D60CFA4D9B83E4777B169FF33CEF04298AAEECE733AB9A9CCD7380C8073079D95D650434D2FF7AD33AB21A0DAE4EDB64343E94141108F594925BE214933AC9E3BC043FD332F0203010001A33C303A30220603551D11041B301982175649455343434D322E65696E737465696E2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B0500038201010089A4B76FFBF73A0F9872BF2B6C14B7EAFAEDBCDEB2793675048BEA300BADC1E168FE75E6A8207B0BADD5C9FC533F62687DD393DDE8C0E68E1973DE32B9DC85DAF41D2AB62F34AC8C88CF8C02FCCE04695D732317430561D3D0F8C95719AA605D0E68488CAB9B3A98461D19EF9E62FF2F37A8E45CCAFE65E48A46CE48987A41858CE2B7324D5F529E0E3A76DE8374787851C9F7044FBEF89C583CC42717F3BDFDF4E73A64FBE4A2991B32C7C2C30117EFE584111112C39368A4712BBD147934D38B4C4FB9E12A6254969A6DDFFE40DA7D687F42D8528A6F8117028C3F25401D1892574303F6C02E208E4F938429B0AC4DC9F9EDC98B6D40D2EBD9266223D02EBF</SiteSigningCert></SecurityConfiguration><RootSiteCode>XYZ</RootSiteCode><CCM>
    <CommandLine>SMSSITECODE=XYZ</CommandLine> </CCM><FSP> <FSPServer></FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSL" Version="1" /><Property Name="SSLState"
    Value="31" /></Capabilities><Domain Value="mydomain.tld" /><Forest Value="mydomain.tld" /></ClientOperationalSettings>. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Security settings: Http port 80; https port 443; select first cert 1; sslstate 480 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Security settings: Certificate Issuers = CN=root-ca ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    FromAD: command line = SMSSITECODE=XYZ ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetManagementPointsForSiteFromAD ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CCMGetGlobalService(&spService), HRESULT=87d00219 (e:\nts_sccm_release\sms\framework\core\ccmcore\ccmconditions.cpp,39) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    LSGetADForestAndDomainName ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Current AD forest name is mydomain.tld, domain name is mydomain.tld ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Domain joined client is in Intranet ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CMPInfoFromADCache requests are throttled for 00:59:59 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Current directory 'C:\WINDOWS\SoftwareDistribution\Download\Install' is not a valid source location. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    No valid source or MP locations could be identified to download content from. Ccmsetup.exe cannot continue. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    DetermineInstallSource(), HRESULT=80004005 (e:\nts_sccm_release\sms\setup\ccmsetup\ccmsetup.cpp,4426) ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    Failed to parse '"C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe" ' with error 0x80004005 ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
    A Fallback Status Point has not been specified.  Message with STATEID='100' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
    CFSPStateMessage::CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
    A Fallback Status Point has not been specified.  Message with STATEID='307' will not be sent. ccmsetup 08.02.2013 13:45:47 196 (0x00C4)
    CFSPStateMessage::~CFSPStateMessage FSPStateMessage 08.02.2013 13:45:47 196 (0x00C4)
    ParseCommandLine(), HRESULT=80004005
    My boundaries and boundary groups are configured, I can see the objects in the Systems Management Container in AD, but still the agent install via WSUS will not work. Any suggestions?
    Cheers
    Sebastian Bammer

    see my latest post. It looks like a bug in the setup. It selects a certificate but still it presents information that iis on the mp does not accept. Check your iis logs. Manual install works for ssl only sites. I haven't got any other methods yet. I will
    keep you updated.

  • Action "Apply Assigned Imaging Bundle"

    Version: 11.3.1
    I need to run action "Apply Assigned Imaging Bundle" against several devices, is it possible to run this action against a device group? This option is greyed out, but just wanted to know if this can be done via a script or any other way to do this? Finding the device and ticking the box is not the quickest and easiest method when there are 100 devices to find.
    Thanks
    Richard

    #!/bin/bash
    ### Script applyImageDaily.sh
    ### Script read all members of a group, assign and apply image. This script is assign to the ZCM-Server itsself as a linux-script action.
    ### After the execution of this script, a WOL-action to a computer-group(can be another group) start and computers create an image.
    ### To prevent imaging to office start hours, a few minutes after execution of WOL I remove the image bundle from all clients.
    ### With this you can control imaging-actions from ZCC, without using of console
    ### Version 1.1 09.11.2014 10:44 Uhr H.Schoene ###
    ZMANBIN=/usr/bin/zman
    DEVICEROOT="PCs"
    DEVICEGROUP="PC-Gruppen/PCs-Imaging"
    IMAGE="Images/DailyImage"
    # Read all members of group PCs-Imaging, assign and apply Image
    /usr/bin/zman wgm "$DEVICEGROUP" | grep Workstations | awk '{print $1}' | while read line
    do
    DEV=$line
    # Image-Bundle assign
    $ZMANBIN ba device "$IMAGE" "Workstations/$DEVICEROOT/$DEV"
    # Image-Action apply
    $ZMANBIN imaging-apply-assigned-imaging-bundle workstation "$DEVICEROOT/$DEV"
    done

  • How to run java exe files without having to install jre

    Hi all i want to run a java application. i already converted the jar file to exe using Launch4j but the problem is that i want to run the application on other computers without having to install jre. please, is this possible and if yes, how can i do that. Thanks alot in advance

    The Launch4J website should explain how to bundle the JRE. I've not really used it myself though. If you can't get it to work you could try the launcher I use:
    http://www.megaupload.com/?d=FYZAVM77
    which comes with instructions. Or:
    http://sourceforge.net/projects/javaround
    Both of which are really easy to use.

Maybe you are looking for