<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Powershell Script to install VUM 6.0? in vSphere Update Manager PowerCLI Discussions</title>
    <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453630#M96</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That 1603 error is kind of a catch-all.&lt;BR /&gt;Did you already try rebooting the target station before doing the install?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 06 Mar 2017 19:54:50 GMT</pubDate>
    <dc:creator>LucD</dc:creator>
    <dc:date>2017-03-06T19:54:50Z</dc:date>
    <item>
      <title>Powershell Script to install VUM 6.0?</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453627#M93</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Anyone ever have success doing an unattended install of VUM 6.0.x via a powershell script?&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;I've been playing around attempting to do this so that I can automate the install using vRO. &amp;nbsp;However, the installation fails with a error: "Error 25085. Setup failed to register VMware vSphere Update Manager extension to VMware vCenter Server: &lt;FQDN of="" server=""&gt;." &lt;/FQDN&gt;&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;&lt;FQDN of="" server=""&gt;Several KBs are listed for this issue: KB1036055 seems to be the one of import - However, for testing we are using a local "administrator@vsphere.local" of the vCSA 6.0. Also, installing the server with the exact same settings / options manually works without issue. The command reference used in powershell is:&lt;/FQDN&gt;&lt;/P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;FQDN of="" server=""&gt;&lt;P&gt;$Command = "/v`"/qr /L*v C:\temp\VUMInstLog.log WARNING_LEVEL=0 VMUM_DATA_DIR=`"$VUM_DATA_DIR`" VCI_DB_SERVER_TYPE=Custom DB_DSN=$VUM_DSN DB_USERNAME=$VUM_DATABASE_USER DB_PASSWORD=$VUM_DATABASE_PASSWORD VC_SERVER_IP=$VCENTER_IP VC_SERVER_PORT=$VCENTER_PORT VC_SERVER_ADMIN_USER=$VCENTER_ADMIN_USER VC_SERVER_ADMIN_PASSWORD=$VCENTER_ADMIN_PASSWORD`""&lt;/P&gt;&lt;P&gt;$string = @()&lt;/P&gt;&lt;P&gt;$string =+= '/L1033'&lt;/P&gt;&lt;P&gt;$string += '/s'&lt;/P&gt;&lt;P&gt;$string += '/w'&lt;/P&gt;&lt;P&gt;$string += $Command&lt;/P&gt;&lt;P&gt;Start-Process -Wait -FilePath c:\temp\VUMInstall\VMware-UpdateManager.exe -ArgumentList $string&lt;/P&gt;&lt;/FQDN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 16:18:28 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453627#M93</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2017-02-17T16:18:28Z</dc:date>
    </item>
    <item>
      <title>Re: Powershell Script to install VUM 6.0?</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453628#M94</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are there any indications in the &lt;SPAN style="color: #666666; font-family: proxima-nova, Arial, sans-serif; font-size: 14px;"&gt;VUMInstLog.log&lt;/SPAN&gt; of what might go wrong?&lt;/P&gt;&lt;P&gt;Or does the install not even get that far?&lt;/P&gt;&lt;P&gt;Did you already try adding the -Verbose switch on the Start-Process cmdlet?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 17:42:37 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453628#M94</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2017-02-17T17:42:37Z</dc:date>
    </item>
    <item>
      <title>Re: Powershell Script to install VUM 6.0?</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453629#M95</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I apologize for failing to get back to you...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It's a very strange thing. It seems to not want complete no matter how we run it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the MSI Installer log, we see:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MSI (s) (DC:80) [TimeStamp]: Executing op: ActionStart(Name=VM_RegisterExtension,Description=Registering Update Manager extension with the VMware vCenter Server ( FDNQ of vCenter:80),)&lt;BR /&gt; Action [Time]: VM_RegisterExtension. Registering Update Manager extension with VMware vCenter Server (vCenter FQDN:80)&lt;BR /&gt; MSI (s) (DC:80) [TimeStamp]: Executing op: CustomActionSchedule(Action=VM_RegisterExtension,ActionType=11265,Source=BinaryData,Target=*******&lt;STRONG&gt;&lt;EM&gt;,CustomActionData=&lt;/EM&gt;&lt;/STRONG&gt;*******)&lt;BR /&gt; MSI (s) (DC:78) [TimeStamp]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI4740.tmp, Entrypoint: VMRegisterExtension&lt;BR /&gt; Error 25085.&lt;STRONG&gt;Setup failed to register VMware vSphere Update Manager extension to VMware vCenter Server:&lt;/STRONG&gt; &lt;EM&gt;(FQDN to vCenter Server).&lt;/EM&gt;&lt;BR /&gt; MSI (s) (DC!14) [TimeStamp]: Product: VMware vSphere Update Manager -- Error 25085.Setup failed to register VMware vSphere Update Manager extension to VMware vCenter SErver: &lt;EM&gt;(FQDN to vCenter Server&lt;/EM&gt;).&lt;/P&gt;&lt;P&gt;CustomAction VM_RegisterExtension returned actualy error code 1603 (Note this may not be 100% accurate if the translation happend insdie sandbox)&lt;BR /&gt; Action ended [Time]: InstallFinalize. Return value 3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I look in the Registrar-log4cpp.log, I see:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[TimeStamp) '' 5668 ALERT] [logUtil, 265] Product = VMware Update Manager, Version = 6.0.0, Build = 454195&lt;BR /&gt; [TimeStamp) '' 5668 INFO] [installerRunVCCommand, 530] [VCSERVER] Loading registrar library&lt;BR /&gt; [TimeStamp) 'Registrar' 5668 INFO] VC server &lt;STRONG&gt;&lt;SPAN&gt;URL &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://:80" rel="nofollow"&gt;http://:80&lt;/A&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;/STRONG&gt;&lt;EM&gt;&amp;lt;---This is exactly how it appears&lt;/EM&gt;&lt;BR /&gt; [TimeStamp) 'Registrar' 5668 ERROR] InvalidArgument error: extension.server.url&lt;BR /&gt; [TimeStamp) '' 5668 INFO] [installerRunVCCommand, 546] [VCSERVER] The extension registration failed&lt;BR /&gt; [TimeStamp) '' 5668 ERROR] [installerRunVCCommand, 549] [VCSERVER] Register extension failed 87&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have checked the inputs by looking at the variables in the powershell script and all looks perfect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Format for DB_USERNAME is domain\user (so it has a \ )&lt;BR /&gt;Format for VC_SERVER_IP is location-businessunit-number (with hyphens in it)&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Mar 2017 19:02:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453629#M95</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2017-03-06T19:02:23Z</dc:date>
    </item>
    <item>
      <title>Re: Powershell Script to install VUM 6.0?</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453630#M96</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;That 1603 error is kind of a catch-all.&lt;BR /&gt;Did you already try rebooting the target station before doing the install?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Mar 2017 19:54:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453630#M96</guid>
      <dc:creator>LucD</dc:creator>
      <dc:date>2017-03-06T19:54:50Z</dc:date>
    </item>
    <item>
      <title>Re: Powershell Script to install VUM 6.0?</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453631#M97</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, the simple answer to that is yes.&amp;nbsp; However, the actually answer is sorta.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, I figure that in testing all of the permutations of installing VUM via PowerShell, it's been installed ~35 times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;That would include reboots in-between installs some of the time, and then full install and running the installer up to just before hitting final install button to start the process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What we've seen so far is that the installer pre-populates fine when not using /qr as an option; an install using the PowerShell script will effectively let you click Next a bunch of times.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;At them moment, it seems that the URL is being messed up when you attempt to automate the install process.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Mar 2017 12:22:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453631#M97</guid>
      <dc:creator>GBartsch</dc:creator>
      <dc:date>2017-03-07T12:22:46Z</dc:date>
    </item>
    <item>
      <title>Re: Powershell Script to install VUM 6.0?</title>
      <link>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453632#M98</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I wrestled with the same issue for a while and discovered that the parameter VMUM_SERVER_SELECT must be specified or you get this error. Although the GUI pre-populates this field when removing the /qr switch, whatever automated method is being used does not.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Jun 2017 08:42:11 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vSphere-Update-Manager-PowerCLI/Powershell-Script-to-install-VUM-6-0/m-p/453632#M98</guid>
      <dc:creator>Frank405</dc:creator>
      <dc:date>2017-06-22T08:42:11Z</dc:date>
    </item>
  </channel>
</rss>

