GBartsch's Posts

Interestingly, I've recently run into this myself.  Were you able to figure out what the issue was? In my case, the customer created the certificates using OpenSSL, just as we would for vRA ... See more...
Interestingly, I've recently run into this myself.  Were you able to figure out what the issue was? In my case, the customer created the certificates using OpenSSL, just as we would for vRA 6.2.5, and they were signed by a RedHat CA.  During the post-install configuration / validation, we had no issues at all. Everything was flawless. However, when attempting to hit the vRO Control Center web, we get the same error you see above.  vRA itself, as opposed to embedded vRO, doesn't appear to have ANY issues with the certificates supplied and signed by the external CA. (...and they are the same cert, with all of the Subject Alternative Names [SANs] for the vRA appliances, etc.) What is this issue caused by?
So, We have a bunch of vCenter server appliances deployed. When we install them, they are configured to turn on syslogging and include the VPXD.log (which is turned off by default by VMware). ... See more...
So, We have a bunch of vCenter server appliances deployed. When we install them, they are configured to turn on syslogging and include the VPXD.log (which is turned off by default by VMware). When we have that level of syslogging enabled, and in general syslogging enabled, the vCenters all tend to crash - even the vCenters with almost to objects in their inventory. We had assumed that it was just the infrastructure, but this happens even with you put the vCenter on a host that ONLY has the vCenter server on it! (12 cores, 192GB of RAM, and only a vCenter server 6.0) The storage is not awesome, but we used an aggregate for testing of 98 disks  / 13000 IOPS (SAS 10k - NetApp - iSCSI), and still had the issue. 1) Why is syslogging crushing these vCenters? 2) How to we determine where we were getting slammed? (Assuming that this is performance related...?) Any thoughts would be helpful. GB
So, To add to this:  I'm currently working at a client site and we are having similar symptoms. - VPXD (Virtual Center Server Service) crashes - Core dumps start appearing in the /storage/... See more...
So, To add to this:  I'm currently working at a client site and we are having similar symptoms. - VPXD (Virtual Center Server Service) crashes - Core dumps start appearing in the /storage/core mount point on the vCenter Appliance - 503 Errors begin to occure attempting to connect to the Web Client or thorugh vRO The only two extensions installed on the vCenter Appliance are the NetApp VSC 6.2.1P1 and Update Manager. vCenter is patched to 6.0U3b.  (We have two with the issue, and one was updated to 6U3b and the other was clean installed to 6U3b.) We do have the LogInsight and EPOPs agents installed, but they don't directly installed into the vCenter (I believe). Has anyone else had issues with the NetApp Virtual Storage Console (VSC) and vCenter 6.0U3b? GB
Well, the simple answer to that is yes.  However, the actually answer is sorta. So, I figure that in testing all of the permutations of installing VUM via PowerShell, it's been installed ~35 t... See more...
Well, the simple answer to that is yes.  However, the actually answer is sorta. So, I figure that in testing all of the permutations of installing VUM via PowerShell, it's been installed ~35 times. 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. 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. At them moment, it seems that the URL is being messed up when you attempt to automate the install process.
I too am very curious as to if adding baseline groups is available in version 6.0 of the PowerCLI module for VUM. Anyone got an answer to this? If not possible in PowerCLI, can it be done u... See more...
I too am very curious as to if adding baseline groups is available in version 6.0 of the PowerCLI module for VUM. Anyone got an answer to this? If not possible in PowerCLI, can it be done using another method? vRO?
I apologize for failing to get back to you... It's a very strange thing. It seems to not want complete no matter how we run it. In the MSI Installer log, we see: MSI (s) (DC:80) [TimeSta... See more...
I apologize for failing to get back to you... It's a very strange thing. It seems to not want complete no matter how we run it. In the MSI Installer log, we see: 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),) Action [Time]: VM_RegisterExtension. Registering Update Manager extension with VMware vCenter Server (vCenter FQDN:80) MSI (s) (DC:80) [TimeStamp]: Executing op: CustomActionSchedule(Action=VM_RegisterExtension,ActionType=11265,Source=BinaryData,Target=*******,CustomActionData=*******) MSI (s) (DC:78) [TimeStamp]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI4740.tmp, Entrypoint: VMRegisterExtension Error 25085.Setup failed to register VMware vSphere Update Manager extension to VMware vCenter Server: (FQDN to vCenter Server). 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: (FQDN to vCenter Server). CustomAction VM_RegisterExtension returned actualy error code 1603 (Note this may not be 100% accurate if the translation happend insdie sandbox) Action ended [Time]: InstallFinalize. Return value 3. When I look in the Registrar-log4cpp.log, I see: [TimeStamp) '' 5668 ALERT] [logUtil, 265] Product = VMware Update Manager, Version = 6.0.0, Build = 454195 [TimeStamp) '' 5668 INFO] [installerRunVCCommand, 530] [VCSERVER] Loading registrar library [TimeStamp) 'Registrar' 5668 INFO] VC server URL http://:80 <---This is exactly how it appears [TimeStamp) 'Registrar' 5668 ERROR] InvalidArgument error: extension.server.url [TimeStamp) '' 5668 INFO] [installerRunVCCommand, 546] [VCSERVER] The extension registration failed [TimeStamp) '' 5668 ERROR] [installerRunVCCommand, 549] [VCSERVER] Register extension failed 87 I have checked the inputs by looking at the variables in the powershell script and all looks perfect. Format for DB_USERNAME is domain\user (so it has a \ ) Format for VC_SERVER_IP is location-businessunit-number (with hyphens in it)
So, the inital question is simple: Have you ever successfully installed Update Manager 6.0x using PowerShell? I'm attempting to automate a VUM install using vRA/vRO, and the easiest way to do ... See more...
So, the inital question is simple: Have you ever successfully installed Update Manager 6.0x using PowerShell? I'm attempting to automate a VUM install using vRA/vRO, and the easiest way to do this is to use a powershell script. However, when we attempt an unattended install using a powershell script (www.vtagion.com...stallation-vum/) to setup VUM 6 under Windows 2012R2 / SQL Server 2012, we get an error and the installation fails. [Error 25085.Setup failed to register VMware vCenter Update Manager extension] Of course, the error does ot meet the crieteria set forth in the only KB we found related to the error message (KB1036055) - It seems that the error is a symptom, but not caused by the issue related in KB1036055. The command we're building in power shell uses this format: $Command = "/V" /qr /L*v C:\temp\vmvci.log WARNING_LEVEL=0 VMUM_DATA_DIR="$VUM_DATA_DIR" VCI_DB_SERVER_TYPE=Custom VCI_FORMAT_DB=1 DB_DSN=$DSN DB_USERNAME=$DatabaseUser DB_PASSWORD=$DatabasePass VC_SERVER_IP=$vCenterFDQN VC_SERVER_PORT=$port VC_SERVER_ADMIN_USER=$vCenterAdmin VC_SERVER_ADMIN_PASSWORD=$vCenterAdmin_Pass"" Note: The whole thing is escaped for powershell, and the Data Dir especially because it can have spaces. The only difference is if you want to make a pre-answered install,  you remove the /qr. Then you get all of the options in manual install for VUM pre-populated, and the installing person clicks Next a bunch of times. (It's actually pretty neat in a 1990s kinda way. ) The install logs shows us this (the server name has been removed): 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),) Action [Time]: VM_RegisterExtension. Registering Update Manager extension with VMware vCenter Server (vCenter FQDN:80) MSI (s) (DC:80) [TimeStamp]: Executing op: CustomActionSchedule(Action=VM_RegisterExtension,ActionType=11265,Source=BinaryData,Target=*******,CustomActionData=*******) MSI (s) (DC:78) [TimeStamp]: Invoking remote custom action. DLL: C:\WINDOWS\Installer\MSI4740.tmp, Entrypoint: VMRegisterExtension Error 25085.Setup failed to register VMware vSphere Update Manager extension to VMware vCenter Server: (FQDN to vCenter Server). 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: (FQDN to vCenter Server). If we run the install semi-manually, that is we remove /qr from the $Command above and click next alot, the install works without issue. (...but it's not unattended / automated) Thoughts?
Anyone ever have success doing an unattended install of VUM 6.0.x via a powershell script? I've been playing around attempting to do this so that I can automate the install using vRO.  However, ... See more...
Anyone ever have success doing an unattended install of VUM 6.0.x via a powershell script? I've been playing around attempting to do this so that I can automate the install using vRO.  However, the installation fails with a error: "Error 25085. Setup failed to register VMware vSphere Update Manager extension to VMware vCenter Server: ." 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:   $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`"" $string = @() $string =+= '/L1033' $string += '/s' $string += '/w' $string += $Command Start-Process -Wait -FilePath c:\temp\VUMInstall\VMware-UpdateManager.exe -ArgumentList $string
Thank you! I did forget one important question that I had regarding this... a follow-up, per se: When importing packages with the same name and/or version numbers, but different content (ex... See more...
Thank you! I did forget one important question that I had regarding this... a follow-up, per se: When importing packages with the same name and/or version numbers, but different content (ex. modified scriptable task, but the version was never updated), does vRO use something other than version control numbers to determine if the element needs to be updated?  (e.g. CRC, hash, etc.) Thank you. GB
Ok, So I was at a customer today and they had two workflow packages to setup Compute for their environment... The two packages were the same exported package from vRO, and the versioning on... See more...
Ok, So I was at a customer today and they had two workflow packages to setup Compute for their environment... The two packages were the same exported package from vRO, and the versioning on the sub-components (various elements) were the same. Obvoiusly, not a best practice. My question is this: What is the best way (and quickest way) to tell the differences between two export vRO packages when the versions on all of the components inside are the SAME, but the actual scripting / constants / etc. are not? [In other words, they've been not updating versions as they've been changing things like scripting elements, and so on. -ugh-] GB
So I actually like that... I'm writing a workflow where I don't care to get ALL of the Resource Pools, but just those at the same level I'm checking. The interesting part is that I can use ... See more...
So I actually like that... I'm writing a workflow where I don't care to get ALL of the Resource Pools, but just those at the same level I'm checking. The interesting part is that I can use #3 to do that, which is pretty helpful if you don't care of there are other pools with the same name nested up other resource pools. (In other words: I want to only see whats directly under Resources, and if the pool I want does not exist at the top-level, create it.  [Even if there are pools nested under other top-level pools.]) I think you may have helped me with this annoying issue.