Installing Agent

Hello All,
We have OEM running on Window. :-(
Our Oracle database 10.1.0.4.0 is running on AIX 5.2.
I need to install Agent on AIX 5.2.
I have downloaded "AIX_Grid_Control_agent_download_10_1_0_4_1.cpio.gz".
Are there any good documentation on "how to install agent on unix box?".
OR some one give me steps to accomplish task.
thanks for any feed back.
Regards,
DN

Hi DN,
I was insttalling AIX_GRID_Control_agent_download_10_1_0_4_1.cpio.gz
after unpack, there was no Disk1 directory. These are the following files and directory after unpack:
-rw-r--r-- 1 oracle dba 1531 Jan 03 05:12 instructions.txt
-rwxr-xr-x 1 oracle dba 15002 Jan 03 05:12 agentDownload.aix.bak
-rw-r--r-- 1 oracle dba 18235 Jan 03 05:14 agent_download.rsp.bak
-rw-r----- 1 oracle dba 753056256 Jan 12 08:22 AIX_Grid_Control_agent_download_10_1_0_4_1.cpio
drwxr-xr-x 5 oracle dba 256 Jan 12 14:25 aix

Similar Messages

Problem installing agent on new database server

Agent11g> ./runInstaller -silent -responseFile /u01/oemAgentStage/linux_x64/response/rac1_additional_agent.rsp
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 150 MB. Actual 12211 MB Passed
Checking swap space: must be greater than 150 MB. Actual 16002 MB Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2011-09-07_04-49-04PM. Please wait ...Agent11g> Warning: Is the following line present in /u01/oemAgentStage/linux_x64/response/rac1_additional_agent.rsp correct?
MYORACLESUPPORT_USERNAME=
Warning: This line is not added to HashMap
Warning: Is the following line present in /u01/oemAgentStage/linux_x64/response/rac1_additional_agent.rsp correct?
MYORACLESUPPORT_PASSWORD=
Warning: This line is not added to HashMap
Warning: Is the following line present in /u01/oemAgentStage/linux_x64/response/rac1_additional_agent.rsp correct?
COLLECTOR_SUPPORTHUB_URL=
Warning: This line is not added to HashMap
*** Check for updates ***
*** Select Installation Type ***
*** Check Prerequisites ***
*** Specify Oracle Management Service Location ***
The specified Management Service on host 192.168.1.51 at port 3872 is unreachable. Check the connection details for the Management Service to ensure that you entered the value for the host name correctly
Response File contents:
OMS_HOST="192.168.1.51"
#OMS_PORT="7799" ORIGINAL
OMS_PORT="3872"
AGENT_REGISTRATION_PASSWORD=Tiger2231
s_agentServiceName="GridAgent"
#Please Don't change the values of these variables
#FROM_LOCATION:<String> Complete path to the products.xml.
#b_upgrade:<Boolean> "whether it is Upgrade or not"
#EM_INSTALL_TYPE:<STRING> install type
FROM_LOCATION="../stage/products.xml"
b_upgrade=false
EM_INSTALL_TYPE="AGENT"
ERROR: Silent Install has failed. Please check the log files for more details.
OMS is up and running.

Re,
did you need install agent form database host ? Did you try deployment from OEMGC ?
We deploy all our agents 11.1 from OEMGC.
*T

Install agent on solaris 10 using agent deploy application?

Hi all,
I have installed 10g grid control on solaris 10 with new repository database on same machine.
The OMS, and agent is running on grid host.
Now I want to add other hosts (targets) into grid. For this, I have to install agent on target hosts. I am using agent deploy application method for installation of agent.
It is giving error
Istall --> Failed
"Pre-Install Script is Not Executed, Install is Failed, Run root.sh is Not Executed, Post-Install Script is Not Executed, Collection of Logs is Success"
version for agent and OMS is 10.2.0.1 and for repository database is 10.1.04
any idea, how to troubleshoot this?

Did you get answer? I had same problem on agent 10.2.0.4 deployment on linux 2.6.9-55.ELsmp.

How to use installed agent?

Hi all,
   EM: 12.1.0.2
   Host: RedHat 6.3 64 bits
   DB: 11.2.0.3
   I have installed successfully the Grid Control 12c on HOST01. I suppose that the installation install all the Grid control 12c binaries and an agent in the host where the repository database is. What i want to know is how to use that installed agent to monitor the repository database? I tried to manually add a target to host HOST01, but an error appears to me saying that an agent is already installed on the machine. How to use that agent to monitor my repository database?
Thanks in advance.

You can discover (add) the repository database target to start monitoring it using the following steps:
- Navigate to Setup > Add Target > Add Targets Manually
- From the Add Targets Manually page, select Add Non-Host Targets Using Guided Process
- From the Target Types drop-down list, select Oracle Database, Listener and Automatic Storage Management
- Click Add Using Guided Discovery
- From the Add Database Instance Target: Specify Host page, select the host where the repository resides, and click Continue
- Follow the process to discover the repository database
Regards,
- Loc

Is there a SCOM install agent for SLES on PPC64?

Is there a SCOM install agent for SLES on PPC64?
Trying to install an agent for SCOM on Suse VM units that are hosted on IBM's power 7 hardware.
While i do see .ppc AIX agent installers I do not see one for SLES on ppc64.
Has anyone installed SCOM on SLES ppc64 or know of a viable agent for the install?

To elaborate a bit, Microsoft definitely does not offer an agent for SLES on PowerPC.  Linux has been ported to a lot of different processor chip architectures, which is great. But Intel x86/x64 is by far the most popular, and it's the only
chip architecture for which Microsoft supplies an agent for monitoring Linux. As you noted, there is an agent for AIX on PowerPC, but AIX is a very different operating system from Linux, and the agent for AIX on PPC will not work on Linux on PowerPC.
I don't see Microsoft doing an agent for Linux on PowerPC. We would need to see a significant business opportunity for that to change.
I would note that the source code for the OpsMgr agent for Linux/UNIX is available at
http://scx.codeplex.com, along with instructions on how to compile and build the agent. Someone with developer skills in C++, compilers, makefiles, etc. could definitely build an agent for SLES on PowerPC.  For
example, I'm aware of someone who has built an agent for Linux running on the IBM S/390 (z-Series) chip architecture running as a guest under zOS and has it working with SC 2012 OpsMgr.   But you would be on your own,
perhaps with help from the community, to make that happen.
Michael Kelley, Lead Program Manager, Open Source Technology Center

Install agent problem on proxy

Hi
i got some problem on install agent process in intranet and no cross any routes.
my agent version is 10.2.0.2 and problem platform are linux and hpux.
i have not check proxy when install agent , and process next step , it's fail on "Oracle configuration manager proxy" window and can't process next step ,and then issue a message "Oracle configuration manager proxy can't established ,please check your network connection and proxy settings ,and try again" ,even i check proxy and setting proxy , it's alse has issue ....
But in another platform windows , it's fine and no proxy check box.
someone have issue like this?

Seems proxy credential are incorrect in Oracle configuration manager proxy screen
Please ,please provide valid proxy credentail or uncheck the check box enable proxy to proceed the agent installation

Where to install agents?

Hi,
I have following architecture:
- Server 1 - ODI installed with option Server
- Client 1 - ODI installed with option Client
- Client 2 - ODI installed with option Client
- Server 2 - Oracle DB installed - ODI Repositories created
- Server 3 - Oracle DB - source system
- Server 4 - MS SQL Server - source system
- Server 5 - Oracle DB installed - target system
I not sure where to install agents for this architecture:
- on Server 1?
or
- on Servers 3 or 4 (source systems)
or
- on Server 5 (target system)
What solution will be the best one in this case?
Thanks in advance!

It is best to install the agent as close to the target as possible. So, in your case it will be on Server 5.
Moreover, since you have only one target, then you have the advantage that you can install only one agent and it works.
Just keep in mind, that while installing the agent on the Server 5,
Server2, server3 and server4 should be visible to Server 5.
To explain more the above statement,
We have Filesystems FS1, FS2 on which the source files are located.
And the agent is located on ORADB1 which is the target Oracle DB. So, the filesystems FS1 and FS2 are visible to the system on which ORADB1 is installed and hence the agent on ORADB1 can also see the filesystems and hence access the files for processing.
HTH

Error applying transforms when trying to install Agent

Several Windows XP machines were experiencing problems that seemed to be associated with the ZENworks agent. I've tried to reinstall the agent using the Install Agent utility but I received the message:
"Workstation <computer name> Failed - Windows error 1624 (Error applying transforms. Verify that the specified transform paths are valid.)"
I tried uninstalling the agent on the local computers and received almost the same message:
"Error applying transforms. Verify that the transform paths are valid."
We are in a Windows Server 2003 environment. ZENworks Desktop Management is running on a NetWare 6.5 server. I just setup Middle Tier Server on a Win 2003 box. It's only the Windows XP machines that are giving me trouble. Distributing the agents to Windows 2000 boxes worked fine.

pbenjamin,
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/ to search the knowledgebase and check the other support options available on that page under "Self Support" and "Support Programs".
- You could also try posting your message again. Make sure it is posted in the correct newsgroup. (http://support.novell.com/forums)
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/

Install agent fail (Agent host must be registered before an agent can be installed or upgraded.)

I got the following error with trying to install agent
# java -jar agent.jar -d /u01/avagent/
Agent host is not registered.
Agent host must be registered before an agent can be installed or upgraded. Agent deployment failed.
database firewall ip address is 10.0.0.10 (for management) and 192.168.0.10 (for traffic source)
auditvault server ip address is 10.0.0.11 (for management)
I have 2 IP address on my DB 10.0.0.9 and 192.168.0.9
when i register host with ip 192.168.0.9 i will get the error
but if i register host with ip 10.0.0.9 installation is fine with no error
i want to monitor audit traffic on 192.168.0.9 interface which is for client to access so i need to register host with ip 192.168.0.9

hi Stefan,
this is expected behaviour, or at least it's better to say : in a multi homed system the choice of the network path that is used is determined by the underlying tcp network,
it doesn matter which path the sqlnet connection from agent to AV server takes as long as it is able to connect. Your statement about 'monitor audit traffic on 192.168.0.9'
does not make sense, the agent / collection framework is the part that fetches audit records from secured targets and has nothing to do with monitoring network traffic since
that part of the functionality is done by the firewall component. Anyway if you want to change the nework path you need to use 'route' and force it,
greetings,
Harm ten Napel

Scom 2012 R2 Convert Manually installed Agents to Remotely managed

Hi
Need to convert manually installed agents to remotely managed.
Found this post :
http://damatisystemcenter.com/2013/01/25/convert-manually-installed-agents-to-remotely-managed/
The last Query converts one agent to remotely managed
How do I do if I want ALL my agents to be converted to remotely ?

Hi,
Setting Agents as Remotely Manageable in SCOM 2012 R2
http://daxsnippets.wordpress.com/2014/04/08/setting-agents-as-remotely-manageable-in-scom-2012-r2/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Install agent while sysman schema already in place...

hello all,
i want to deploy oem agent on a box which has 3 DB(11.2.0.2) running on it. Can i install oem agent(11.1) if one of the DB already has sysman schema in it??
i cannot drop the repositry from the DB....the reason behind is when i run the emca comman it get below error... it turn out that the oracle home is a symbolic link...and i have to drop the link and point to to physical home and re-start the DB.....we do not have down time for this db....so can i install agent with sysman schema already in it ??
Do you wish to continue? [yes(Y)/no(N)]: Y
Nov 15, 2011 4:43:26 PM oracle.sysman.emcp.DatabaseChecks checkDbAvailabilityImpl
WARNING: ORA-01034: ORACLE not available
Nov 15, 2011 4:43:26 PM oracle.sysman.emcp.DatabaseChecks throwDBUnavailableException
SEVERE:
Database instance is unavailable. Fix the ORA error thrown and run EM Configuration Assistant again.
Some of the possible reasons may be :
1) Database may not be up.
2) Database is started setting environment variable ORACLE_HOME with trailing '/'. Reset ORACLE_HOME and bounce the database.
For eg. Database is started setting environment variable ORACLE_HOME=/scratch/db/ . Reset ORACLE_HOME=/scratch/db and bounce the database.

For agent u don't need to drop repostory for oms if you have plan to use that database as oms repository then you have to drop the dbconsoler schema, installer check for this.

Manually Installed Agent is not showing up in the Operations Manager Console Under Pending Management.

Hi Community,
I submitted this question because I'm a bit stuck with SCOM 2012 R2, I'll try to explain briefly what is happening right now in my environment, we have a DEV SCOM Deployment in which all the roles are installed in a single server, this servers is a
VMware machine running Windows Server 2008R2.
The Initial installation of the SCOM Operations Manager and all the other components was not performed by me but by a co-worker, unfortunately he doesn't remember much about the initial configuration. So i had to pickup where he left things about a year
ago, neither of us are SCOM experts, and we have almost no previous experience with previous versions of this application.
Now the problem that I'm facing is the following, all the DEV Servers are Domain Controllers and one of the indication within the "Guide for System Center Management Pack for Active Directory for Operations Manager 2012" states the following
Configuration
Supported?
Agent-less monitoring
No
After my first review I notice that our servers were being monitor by agent-less mode and given the above statement from the Operations Guide the only way that we could ever get those domain controllers monitor by SCOM would be by installing the agent on
each server, so I read somewhere (Can't remember where) that in order to install the agents in all the servers I should first remove them from the Agent-less node, which I did. Then I tried to use the discovery wizard to get the agent install in all of them
but it didn't matter how many times I try the servers never show up.
I read in a Tech Net Article that you had to modify the security settings so SCOM would let me decide if I wanted to approve it or not.
--> http://technet.microsoft.com/en-us/library/hh212853.aspx
I performed the suggested steps from the article but still the servers were not showing up, not even if I run the Discovery wizard, so I decided to go and perform the installation manually in a couple of servers I was able to install the agent in one of
the Domain Controllers, I configured the agent to use a service account that has Domain Admin rights. An hour after I installed the agent I went back to the Operations Console Manager and I check under Pending Action but the Server was not showing up. So i
went back to the Internet to try to find out if someone else had experience the same problem, and in one website some mentioned that if the servers were not showing up it was probably because they were still register in the SCOM Database, now I have no idea
of how i can check that or How can i remove them from there to have them available again, but what troubles me the most is that even after i installed the agent manually the server were not being recognize.
I went to the Event Viewer and I found one particular event that caught my attention, see below :
Log Name:      Operations Manager
Source:        Health Service Modules
Date:          6/12/2014 12:48:19 PM
Event ID:      11551
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      MyManagementServer
Description:
Computer verification failure for Machine Name: MyManagementServe is 0x800706BA. The RPC server is unavailable.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Health Service Modules" />
    <EventID Qualifiers="49152">11551</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-06-12T16:48:19.000000000Z" />
    <EventRecordID>1945680</EventRecordID>
    <Channel>Operations Manager</Channel>
    <Computer>MyManagementServer</Computer>
    <Security />
</System>
<EventData>
    <Data>MyManagementServe</Data>
    <Data>0x800706BA</Data>
    <Data>The RPC server is unavailable.</Data>
</EventData>
</Event>
Not sure if this is related to the problem that I'm facing right now, but , I make sure that the RPC Services were running and also the related dependencies too. There's no Firewall enable in any of the servers and DNS seems to be working properly.
Ports 135 / 5723 are open and listening so since I ran out of ideas, I would like to know if some of the experts in this field could perhaps give me some guidelines.
There's one caveat that I haven't mention yet and that is related to SQL, I checked and my user just has read access to SQL i'm not sure if that could affect this but i think is worth mentioning.
My main goal is to have all the servers showing up in the Operations Manager Console.
So thanks all in advance !
Oscar Loria

So you can ping and nslookup from your ms to these agents and vice versa right? I wouldn't do a manual install, I would push the agent from the management server. You can uninstall the agent manually, or use cleanmom to get rid of them. Then
do an install from the console. When you initiate the install from the console (management server), should it run into any issues it will dump out an error which will give you an idea of where the problem may be.
From Holmans post on this:
e 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.
The MOM Server could not execute WMI Query "(null)” 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. If Windows 2008 firewall is enabled, ensure “Remote Administration (RPC)” rule is enabled/allowed. We need port 135 (RPC) and the DCOM port range opened for console push through a firewall.
3. Inspect WMI service, health, and rebuild repository if necessary
4. Firewall is blocking ICMP (Live OneCare)
5. DNS incorrect
http://blogs.technet.com/b/kevinholman/archive/2009/01/27/console-based-agent-deployment-troubleshooting-table.aspx
Regards, Blake Email: mengotto<at>hotmail.com Blog: http://discussitnow.wordpress.com/ If my response was helpful, please mark it as so, if it answered your question, then please also mark it accordingly. Thank you.

Installing agent - "VBScript runtime error" on Windows server

Hi all,
I am installing the agent (10.2.0.2.0) on another one of my Windows Oracle servers - this is about the 10th one I've done, and I am doing it no differently than all the others.
I download the wget.exe utility, put it in the path somewhere (usually put it under e:\oracle\ora92\bin), then download the agentDownload.vbs script from the Grid server. Then, when I issue the command to start the installation:
cscript agentDownload.vbs b e:\oracle m ourserver.ourdomain.com r 4889
and I am getting this error (2 different lines):
e:\oracle
agentDownload.vbs(476, 2) Microsoft VBScript runtime error: Object doesn't support this property or method: 'currentdirectory'
Has anyone ever seen anything like this?
Thanks,
Brad

Whats your defualt directory?
can you try by putting wget in the beggining of windows path variable.

Cannot install agent on 2 2012 Host servers

Hi, i am using SCVMM 2012 SP1 version 3.1.6011.0
i have 2 2012 Datacentre servers, both hyperv hosts, i am unable to install the agent, manually or remotely
i get an error as soon as i run the installer
"There is a problem with this windows installer package. A DLL for this install to completed could not be run. Contatc your support personnel or package vendor"
Visual C++2010 is installed
error from SCVMM
Error (441)
Agent communication is blocked. On SERVER1.company.org, the version of virtualization software or the VMM agent is unsupported.
Recommended Action
Update the agent and virtualization software, and then try the operation again.
it is working fine for all other servers,
any suggestions would be appreciated.
Phil Mason

i have tried the install through the following
msiexec.exe /i vmmAgent.msi /L*V c:\vmmagent_install.log
here is the log
=== Verbose logging started: 10/09/2014 17:01:44 Build type: SHIP UNICODE 5.00.9200.00 Calling process: C:\Windows\system32\msiexec.exe ===
MSI (c) (AC:DC) [17:01:44:132]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (AC:DC) [17:01:44:132]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg
MSI (c) (AC:44) [17:01:44:132]: Resetting cached policy values
MSI (c) (AC:44) [17:01:44:132]: Machine policy value 'Debug' is 0
MSI (c) (AC:44) [17:01:44:132]: ******* RunEngine:
           ******* Product: vmmAgent.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (AC:44) [17:01:44:132]: Machine policy value 'DisableUserInstalls' is 0
MSI (c) (AC:44) [17:01:44:132]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\vmm\vmmAgent.msi' against software restriction policy
MSI (c) (AC:44) [17:01:44:132]: Note: 1: 2262 2: DigitalSignature 3: -2147287038
MSI (c) (AC:44) [17:01:44:132]: SOFTWARE RESTRICTION POLICY: C:\vmm\vmmAgent.msi is not digitally signed
MSI (c) (AC:44) [17:01:44:132]: SOFTWARE RESTRICTION POLICY: C:\vmm\vmmAgent.msi is permitted to run at the 'unrestricted' authorization level.
MSI (c) (AC:44) [17:01:44:163]: Cloaking enabled.
MSI (c) (AC:44) [17:01:44:163]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (AC:44) [17:01:44:163]: End dialog not enabled
MSI (c) (AC:44) [17:01:44:163]: Original package ==> C:\vmm\vmmAgent.msi
MSI (c) (AC:44) [17:01:44:163]: Package we're running from ==> C:\vmm\vmmAgent.msi
MSI (c) (AC:44) [17:01:44:163]: APPCOMPAT: Compatibility mode property overrides found.
MSI (c) (AC:44) [17:01:44:163]: APPCOMPAT: looking for appcompat database entry with ProductCode '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}'.
MSI (c) (AC:44) [17:01:44:163]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (AC:44) [17:01:44:179]: MSCOREE not loaded loading copy from system32
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'TransformsSecure' is 1
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'DisablePatch' is 0
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'AllowLockdownPatch' is 0
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'DisableLUAPatching' is 0
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (c) (AC:44) [17:01:44:179]: APPCOMPAT: looking for appcompat database entry with ProductCode '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}'.
MSI (c) (AC:44) [17:01:44:179]: APPCOMPAT: no matching ProductCode found in database.
MSI (c) (AC:44) [17:01:44:179]: Transforms are not secure.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'c:\vmmagent_install.log'.
MSI (c) (AC:44) [17:01:44:179]: Command Line: CURRENTDIRECTORY=C:\vmm CLIENTUILEVEL=0 CLIENTPROCESSID=13996
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{6A2A3BC7-0C15-472C-BB42-7D879FA490AB}'.
MSI (c) (AC:44) [17:01:44:179]: Product Code passed to Engine.Initialize:           ''
MSI (c) (AC:44) [17:01:44:179]: Product Code from property table before transforms: '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}'
MSI (c) (AC:44) [17:01:44:179]: Product Code from property table after transforms: '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}'
MSI (c) (AC:44) [17:01:44:179]: Product not registered: beginning first-time install
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
MSI (c) (AC:44) [17:01:44:179]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (AC:44) [17:01:44:179]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (AC:44) [17:01:44:179]: Adding new sources is allowed.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: Package name extracted from package path: 'vmmAgent.msi'
MSI (c) (AC:44) [17:01:44:179]: Package to be registered: 'vmmAgent.msi'
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding IsAdminPackage property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'DisableMsi' is 1
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (c) (AC:44) [17:01:44:179]: User policy value 'AlwaysInstallElevated' is 0
MSI (c) (AC:44) [17:01:44:179]: Product installation will be elevated because user is admin and product is being installed per-machine.
MSI (c) (AC:44) [17:01:44:179]: Running product '{DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}' with elevated privileges: Product is assigned.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\vmm'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '13996'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: TRANSFORMS property is now:
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '301'.
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\Favorites
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\Documents
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Recent
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\SendTo
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Templates
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Local
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\Pictures
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Users\datapacremote\Desktop
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (c) (AC:44) [17:01:44:179]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (c) (AC:44) [17:01:44:179]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (c) (AC:44) [17:01:44:179]: MSI_LUA: Setting AdminUser property to 1 because this is the client or the user has already permitted elevation
MSI (c) (AC:44) [17:01:44:179]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (c) (AC:44) [17:01:44:179]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'IT'.
MSI (c) (AC:44) [17:01:44:179]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding COMPANYNAME property. Its value is 'SJOG'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\vmm\vmmAgent.msi'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'C:\vmm\vmmAgent.msi'.
MSI (c) (AC:44) [17:01:44:179]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding SourceDir property. Its value is 'C:\vmm\'.
MSI (c) (AC:44) [17:01:44:179]: PROPERTY CHANGE: Adding SOURCEDIR property. Its value is 'C:\vmm\'.
MSI (c) (AC:DC) [17:01:44:195]: PROPERTY CHANGE: Adding VersionHandler property. Its value is '5.00'.
=== Logging started: 10/09/2014 17:01:44 ===
MSI (c) (AC:44) [17:01:44:195]: Note: 1: 2205 2: 3: PatchPackage
MSI (c) (AC:44) [17:01:44:195]: Machine policy value 'DisableRollback' is 0
MSI (c) (AC:44) [17:01:44:195]: User policy value 'DisableRollback' is 0
MSI (c) (AC:44) [17:01:44:195]: PROPERTY CHANGE: Adding UILevel property. Its value is '5'.
MSI (c) (AC:44) [17:01:44:195]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (c) (AC:44) [17:01:44:195]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
MSI (c) (AC:44) [17:01:44:195]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (c) (AC:44) [17:01:44:195]: Doing action: INSTALL
Action 17:01:44: INSTALL.
Action start 17:01:44: INSTALL.
MSI (c) (AC:44) [17:01:44:195]: UI Sequence table 'InstallUISequence' is present and populated.
MSI (c) (AC:44) [17:01:44:195]: Running UISequence
MSI (c) (AC:44) [17:01:44:195]: PROPERTY CHANGE: Adding EXECUTEACTION property. Its value is 'INSTALL'.
MSI (c) (AC:44) [17:01:44:195]: Doing action: FindRelatedProducts
Action 17:01:44: FindRelatedProducts. Searching for related applications
Action start 17:01:44: FindRelatedProducts.
Action ended 17:01:44: FindRelatedProducts. Return value 1.
MSI (c) (AC:44) [17:01:44:195]: Doing action: PrepareDlg
Action 17:01:44: PrepareDlg.
Action start 17:01:44: PrepareDlg.
Info 2898. For WixUI_Font_Normal textstyle, the system created a 'Tahoma' font, in 0 character set, of 13 pixels height.
Info 2898. For WixUI_Font_Bigger textstyle, the system created a 'Tahoma' font, in 0 character set, of 19 pixels height.
Action 17:01:44: PrepareDlg. Dialog created
Action ended 17:01:44: PrepareDlg. Return value 1.
MSI (c) (AC:44) [17:01:44:195]: Doing action: AppSearch
Action 17:01:44: AppSearch. Searching for installed applications
Action start 17:01:44: AppSearch.
AppSearch: Property: VMMSERVER, Signature: VMMServerRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Server\Setup 3: 2
AppSearch: Property: BITSPORT, Signature: BitsPortRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Agent\Setup 3: 2
AppSearch: Property: WSMANPORT, Signature: WsmanPortRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Agent\Setup 3: 2
AppSearch: Property: NONTRUSTEDMACHINE, Signature: NonTrustedMachineRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Agent\Setup 3: 2
AppSearch: Property: BITSFORCEFILEFLUSH, Signature: BITSForceFileFlushRegistry
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding BITSFORCEFILEFLUSH property. Its value is '#1'.
AppSearch: Property: BITS4, Signature: CheckQMgr
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding BITS4 property. Its value is 'C:\Windows\system32\QMgr.dll'.
AppSearch: Property: FIREWALLENABLED, Signature: FirewallEnabledRegistry
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding FIREWALLENABLED property. Its value is '#0'.
AppSearch: Property: MSIDLL, Signature: CheckMsiDll
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding MSIDLL property. Its value is 'C:\Windows\SysWOW64\msi.dll'.
AppSearch: Property: WINRMSERVICESTARTTYPE, Signature: AgentWinRMStartTypeRegistry
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding WINRMSERVICESTARTTYPE property. Its value is '#2'.
AppSearch: Property: WSMSVC, Signature: CheckWsmSvc
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1322 2:
MSI (c) (AC:44) [17:01:44:210]: PROPERTY CHANGE: Adding WSMSVC property. Its value is 'C:\Windows\SysWOW64\wsmwmipl.dll'.
AppSearch: Property: DMZUSERNAME, Signature: DmzLocalUserRegistry
MSI (c) (AC:44) [17:01:44:210]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft System Center Virtual Machine Manager Agent\Setup 3: 2
Action ended 17:01:44: AppSearch. Return value 1.
MSI (c) (AC:44) [17:01:44:210]: Doing action: LaunchConditions
Action 17:01:44: LaunchConditions. Evaluating launch conditions
Action start 17:01:44: LaunchConditions.
Action ended 17:01:44: LaunchConditions. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Doing action: ValidateProductID
Action 17:01:44: ValidateProductID.
Action start 17:01:44: ValidateProductID.
Action ended 17:01:44: ValidateProductID. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Doing action: CostInitialize
Action 17:01:44: CostInitialize. Computing space requirements
Action start 17:01:44: CostInitialize.
MSI (c) (AC:44) [17:01:44:226]: Machine policy value 'MaxPatchCacheSize' is 10
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding ROOTDRIVE property. Its value is 'C:\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding CostingComplete property. Its value is '0'.
Action ended 17:01:44: CostInitialize. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Doing action: FileCost
Action 17:01:44: FileCost. Computing space requirements
Action start 17:01:44: FileCost.
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: MsiAssembly
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: Class
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: Extension
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: TypeLib
Action ended 17:01:44: FileCost. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Doing action: CostFinalize
Action 17:01:44: CostFinalize. Computing space requirements
Action start 17:01:44: CostFinalize.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding OutOfDiskSpace property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding OutOfNoRbDiskSpace property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceAvailable property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRequired property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding PrimaryVolumeSpaceRemaining property. Its value is '0'.
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: Patch
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: Condition
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding TARGETDIR property. Its value is 'C:\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding MSAppDataFolder property. Its value is 'C:\ProgramData\Microsoft\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding VMMAppDataFolder property. Its value is 'C:\ProgramData\Microsoft\Virtual Machine Manager\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding SYSCENTERDIR property. Its value is 'C:\Program Files\Microsoft System Center 2012\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding INSTALLDIR property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding CREDENTIALEXPORTDIRECTORY property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding AgentBinDir property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding Trace.3812768D_658A_4BB6_9A68_F288BE3E9CF5 property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding SetupDir property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\'.
MSI (c) (AC:44) [17:01:44:226]: PROPERTY CHANGE: Adding SetupHelpDir property. Its value is 'C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\help\'.
MSI (c) (AC:44) [17:01:44:226]: Target path resolution complete. Dumping Directory table...
MSI (c) (AC:44) [17:01:44:226]: Note: target paths subject to change (via custom actions or browsing)
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: TARGETDIR , Object: C:\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: WindowsFolder , Object: C:\Windows\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: CommonAppDataFolder , Object: C:\ProgramData\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: MSAppDataFolder , Object: C:\ProgramData\Microsoft\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: VMMAppDataFolder , Object: C:\ProgramData\Microsoft\Virtual Machine Manager\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: ProgramFiles64Folder , Object: C:\Program Files\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: SYSCENTERDIR , Object: C:\Program Files\Microsoft System Center 2012\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: INSTALLDIR , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: CREDENTIALEXPORTDIRECTORY , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: AgentBinDir , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: Trace.3812768D_658A_4BB6_9A68_F288BE3E9CF5 , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: SetupDir , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\
MSI (c) (AC:44) [17:01:44:226]: Dir (target): Key: SetupHelpDir , Object: C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\help\
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2205 2: 3: MsiAssembly
MSI (c) (AC:44) [17:01:44:226]: Note: 1: 2228 2: 3: MsiAssembly 4: SELECT `MsiAssembly`.`Attributes`, `MsiAssembly`.`File_Application`, `MsiAssembly`.`File_Manifest`, `Component`.`KeyPath` FROM `MsiAssembly`, `Component` WHERE `MsiAssembly`.`Component_`
= `Component`.`Component` AND `MsiAssembly`.`Component_` = ?
Action ended 17:01:44: CostFinalize. Return value 1.
MSI (c) (AC:44) [17:01:44:226]: Skipping action: SetInstallModeRemove (condition is false)
MSI (c) (AC:44) [17:01:44:226]: Doing action: GetAllIPAddresses
Action 17:01:44: GetAllIPAddresses.
Action start 17:01:44: GetAllIPAddresses.
MSI (c) (AC:58) [17:01:44:226]: Invoking remote custom action. DLL: C:\Users\DATAPA~1\AppData\Local\Temp\MSIE02D.tmp, Entrypoint: GetAllIPAddresses
MSI (c) (AC:A0) [17:01:44:226]: Cloaking enabled.
MSI (c) (AC:A0) [17:01:44:226]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (AC:A0) [17:01:44:226]: Connected to service for CA interface.
CustomAction GetAllIPAddresses returned actual error code 1157 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (c) (AC:44) [17:01:44:241]: Note: 1: 1723 2: GetAllIPAddresses 3: GetAllIPAddresses 4: C:\Users\DATAPA~1\AppData\Local\Temp\MSIE02D.tmp
Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor. Action GetAllIPAddresses, entry: GetAllIPAddresses, library: C:\Users\DATAPA~1\AppData\Local\Temp\MSIE02D.tmp
MSI (c) (AC:44) [17:01:46:489]: Product: Microsoft System Center Virtual Machine Manager Agent (x64) -- Error 1723. There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel
or package vendor. Action GetAllIPAddresses, entry: GetAllIPAddresses, library: C:\Users\DATAPA~1\AppData\Local\Temp\MSIE02D.tmp
Action ended 17:01:46: GetAllIPAddresses. Return value 3.
MSI (c) (AC:44) [17:01:46:489]: Doing action: FatalError
Action 17:01:46: FatalError.
Action start 17:01:46: FatalError.
Action 17:01:46: FatalError. Dialog created
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: _RemoveFilePath
MSI (c) (AC:E8) [17:01:46:505]: PROPERTY CHANGE: Modifying CostingComplete property. Its current value is '0'. Its new value: '1'.
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: BindImage
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: ProgId
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: PublishComponent
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: SelfReg
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: Extension
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: Font
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: Shortcut
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: Class
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2205 2: 3: TypeLib
MSI (c) (AC:E8) [17:01:46:505]: Note: 1: 2727 2:
Action ended 17:01:47: FatalError. Return value 2.
Action ended 17:01:47: INSTALL. Return value 3.
MSI (c) (AC:44) [17:01:47:708]: Destroying RemoteAPI object.
MSI (c) (AC:A0) [17:01:47:708]: Custom Action Manager thread ending.
Property(C): DiskPrompt = Microsoft System Center Virtual Machine Manager Agent (x64) Installation [1]
Property(C): UpgradeCode = {87827097-A5CB-4E4F-BB18-76A7B9CC25A2}
Property(C): BITSPORT = 443
Property(C): WSMANPORT = 5985
Property(C): NONTRUSTEDMACHINE = 0
Property(C): BITSFORCEFILEFLUSH = #1
Property(C): BITS4 = C:\Windows\system32\QMgr.dll
Property(C): FIREWALLENABLED = #0
Property(C): MSIDLL = C:\Windows\SysWOW64\msi.dll
Property(C): WINRMSERVICESTARTTYPE = #2
Property(C): WSMSVC = C:\Windows\SysWOW64\wsmwmipl.dll
Property(C): IPAddressChoice = (no choice)
Property(C): INSTALLDIR = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\
Property(C): SetupHelpDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\help\
Property(C): SetupDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\
Property(C): AgentBinDir = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\
Property(C): VMMAppDataFolder = C:\ProgramData\Microsoft\Virtual Machine Manager\
Property(C): CREDENTIALEXPORTDIRECTORY = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\
Property(C): LicenseAccepted = 0
Property(C): DistinguishedNameOption = 0
Property(C): WIXUI_INSTALLDIR = INSTALLDIR
Property(C): WixUIRMOption = UseRM
Property(C): ARPNOREPAIR = 1
Property(C): ALLUSERS = 1
Property(C): CreateUser = **********
Property(C): WixUI_InstallMode = InstallComplete
Property(C): SYSCENTERDIR = C:\Program Files\Microsoft System Center 2012\
Property(C): ProgramFiles64Folder = C:\Program Files\
Property(C): TARGETDIR = C:\
Property(C): MSAppDataFolder = C:\ProgramData\Microsoft\
Property(C): CommonAppDataFolder = C:\ProgramData\
Property(C): SourceDir = C:\vmm\
Property(C): VersionNT = 602
Property(C): Privileged = 1
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductCode = {DA9CF191-5E6A-4F96-98AD-9DB99BE611C0}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Microsoft System Center Virtual Machine Manager Agent (x64)
Property(C): ProductVersion = 3.1.6011.0
Property(C): INSTALLLEVEL = 100
Property(C): ARPCONTACT = Microsoft Corporation
Property(C): ARPPRODUCTICON = ProductIcon
Property(C): ARPHELPLINK =
http://go.microsoft.com/fwlink/?LinkId=68951
Property(C): HostRegSubKey = Microsoft System Center Virtual Machine Manager Agent
Property(C): MofFileName = VMMAgent.mof
Property(C): WmiNamespace = scvmm
Property(C): AgentServiceName = SCVMMAgent
Property(C): AgentExeName = vmmAgent.exe
Property(C): AgentFirewallRuleName = VMMAgent
Property(C): BitsPortName = HTTPS
Property(C): WSMANMINVERSION = 5.2.3790.2984
Property(C): DISTINGUISHEDNAMEOPTION = 0
Property(C): IPADDRESSCHOICE = 0
Property(C): DefaultUIFont = WixUI_Font_Normal
Property(C): WixUI_Mode = InstallDir
Property(C): WIXUI_CREDENTIALEXPORTDIR = CREDENTIALEXPORTDIRECTORY
Property(C): WixUI_LicenseAgreementDlg_Next = InstallDirDlg
Property(C): WixUI_LicenseAgreementDlg_Back = WelcomeDlg
Property(C): WixUI_VMMCredentialDirectoryDlg_NextTrusted = VMMPortSettingDlg
Property(C): WixUI_VMMCredentialDirectoryDlg_NextNonTrusted = VMMDNSelectionDlg
Property(C): WixUI_VMMCredentialDirectoryDlg_Back = InstallDirDlg
Property(C): WixUI_VMMCredentialDirectoryDlg_Change = BrowseDlg
Property(C): WixUI_VMMDNSelectionDlg_Next = VMMPortSettingDlg
Property(C): WixUI_VMMDNSelectionDlg_Back = VMMCredentialDirectoryDlg
Property(C): WixUI_VMMPortSettingDlg_Next = VerifyReadyDlg
Property(C): WixUI_VMMPortSettingDlg_Back = VMMCredentialDirectoryDlg
Property(C): IPADDRESS0 = (address 1 N/A)
Property(C): IPADDRESS1 = (address 2 N/A)
Property(C): IPADDRESS2 = (address 3 N/A)
Property(C): IPADDRESS3 = (address 4 N/A)
Property(C): IPADDRESS4 = (address 5 N/A)
Property(C): IPADDRESS5 = (address 6 N/A)
Property(C): IPADDRESS6 = (address 7 N/A)
Property(C): IPADDRESS7 = (address 8 N/A)
Property(C): ErrorDialog = ErrorDlg
Property(C): SecureCustomProperties = ANYVERSION
Property(C): MsiHiddenProperties = CreateUser;DMZPASSWORD
Property(C): Trace.3812768D_658A_4BB6_9A68_F288BE3E9CF5 = C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\Trace\
Property(C): MsiLogFileLocation = c:\vmmagent_install.log
Property(C): PackageCode = {6A2A3BC7-0C15-472C-BB42-7D879FA490AB}
Property(C): ProductState = -1
Property(C): PackagecodeChanging = 1
Property(C): IsAdminPackage = 1
Property(C): CURRENTDIRECTORY = C:\vmm
Property(C): CLIENTUILEVEL = 0
Property(C): CLIENTPROCESSID = 13996
Property(C): MsiSystemRebootPending = 1
Property(C): VersionDatabase = 301
Property(C): VersionMsi = 5.00
Property(C): VersionNT64 = 602
Property(C): WindowsBuild = 9200
Property(C): ServicePackLevel = 0
Property(C): ServicePackLevelMinor = 0
Property(C): MsiNTProductType = 3
Property(C): MsiNTSuiteDataCenter = 1
Property(C): WindowsFolder = C:\Windows\
Property(C): WindowsVolume = C:\
Property(C): System64Folder = C:\Windows\system32\
Property(C): SystemFolder = C:\Windows\SysWOW64\
Property(C): RemoteAdminTS = 1
Property(C): TempFolder = C:\Users\DATAPA~1\AppData\Local\Temp\
Property(C): ProgramFilesFolder = C:\Program Files (x86)\
Property(C): CommonFilesFolder = C:\Program Files (x86)\Common Files\
Property(C): CommonFiles64Folder = C:\Program Files\Common Files\
Property(C): AppDataFolder = C:\Users\datapacremote\AppData\Roaming\
Property(C): FavoritesFolder = C:\Users\datapacremote\Favorites\
Property(C): NetHoodFolder = C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
Property(C): PersonalFolder = C:\Users\datapacremote\Documents\
Property(C): PrintHoodFolder = C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
Property(C): RecentFolder = C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\Recent\
Property(C): SendToFolder = C:\Users\datapacremote\AppData\Roaming\Microsoft\Windows\SendTo\
Property(C): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
Property(C): LocalAppDataFolder = C:\Users\datapacremote\AppData\Local\
Property(C): MyPicturesFolder = C:\Users\datapacremote\Pictures\
Property(C): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
Property(C): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
Property(C): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
Property(C): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
Property(C): DesktopFolder = C:\Users\Public\Desktop\
Property(C): FontsFolder = C:\Windows\Fonts\
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): MsiAMD64 = 6
Property(C): Msix64 = 6
Property(C): Intel = 6
Property(C): PhysicalMemory = 131037
Property(C): VirtualMemory = 89588
Property(C): AdminUser = 1
Property(C): MsiTrueAdminUser = 1
Property(C): LogonUser = datapacremote
Property(C): UserSID = S-1-5-21-4197612004-1255000048-2282055192-13349
Property(C): UserLanguageID = 6153
Property(C): ComputerName = SERVERSAN1
Property(C): SystemLanguageID = 6153
Property(C): ScreenX = 1364
Property(C): ScreenY = 706
Property(C): CaptionHeight = 23
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): TextInternalLeading = 3
Property(C): ColorBits = 32
Property(C): TTCSupport = 1
Property(C): Time = 17:01:47
Property(C): Date = 10/09/2014
Property(C): MsiNetAssemblySupport = 4.0.30319.17929
Property(C): MsiWin32AssemblySupport = 6.2.9200.16384
Property(C): RedirectedDllSupport = 2
Property(C): MsiRunningElevated = 1
Property(C): USERNAME = IT
Property(C): COMPANYNAME = SJOG
Property(C): DATABASE = C:\vmm\vmmAgent.msi
Property(C): OriginalDatabase = C:\vmm\vmmAgent.msi
Property(C): SOURCEDIR = C:\vmm\
Property(C): VersionHandler = 5.00
Property(C): UILevel = 5
Property(C): ACTION = INSTALL
Property(C): EXECUTEACTION = INSTALL
Property(C): ROOTDRIVE = C:\
Property(C): CostingComplete = 1
Property(C): OutOfDiskSpace = 0
Property(C): OutOfNoRbDiskSpace = 0
Property(C): PrimaryVolumeSpaceAvailable = 0
Property(C): PrimaryVolumeSpaceRequired = 0
Property(C): PrimaryVolumeSpaceRemaining = 0
=== Logging stopped: 10/09/2014 17:01:47 ===
MSI (c) (AC:44) [17:01:47:724]: Windows Installer installed the product. Product Name: Microsoft System Center Virtual Machine Manager Agent (x64). Product Version: 3.1.6011.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success
or error status: 1603.
MSI (c) (AC:44) [17:01:47:724]: Grabbed execution mutex.
MSI (c) (AC:44) [17:01:47:724]: Cleaning up uninstalled install packages, if any exist
MSI (c) (AC:44) [17:01:47:724]: MainEngineThread is returning 1603
=== Verbose logging stopped: 10/09/2014 17:01:47 ===
Phil Mason

Installing agent as a non-root user?

Trying to install OEM agent on Solaris, from the OMS server, I get the following error when setting up the SSH Named Credentials.
"The agent installation cannot be performed as a root user. Ensure the user name in the Named Credential is set to a non-root user."
Does that mean I have to go around to all of my clients and create a special user just to run the OEM agent?
What are other people doing for this?

Well, we have thousands of servers and only a couple that have Oracle on them.
I went ahead and created an "oemagent" user, in group dba.
Then I gave it ALL permissions in sudoers.
I then had to run some SSH script on the OMS server that set up SSH configuration variables to talk to the client.
Then created an agent deployment directory (since you have to give it an empty directory to install to).
Then created an oraInventory directory and made the owner "oemagent" and group owner "dba".
Then I was able to deploy.
So it seems that, in order to deploy an agent to maintain a configuration on my clients...I have to write a script that will initialize the client first. So much for OEM taking care of all the provisioning/management!

Installing Agent

Similar Messages

Maybe you are looking for