Thanks, I was kind of thinking that may be the case. But being able to the get the temp directory path is definitely helpful and gives me something to work with. jonathan
vRO v8.5.1 I've uploaded a PowerShell file to Resources with the intention to use the WF 'Copy file from vCO to guest' to be able to run the PS locally on the OS. But I can't seem to find the path ...
See more...
vRO v8.5.1 I've uploaded a PowerShell file to Resources with the intention to use the WF 'Copy file from vCO to guest' to be able to run the PS locally on the OS. But I can't seem to find the path to the file in resources. I just keep getting errors like: java.io.FileNotFoundException: test.ps1 (No such file or directory) (Workflow:Copy file from vCO to guest / Scriptable task (item1)#13) I've tried various paths like: /web-root/test.ps1, /resources/test.ps1, /resources/web-root/test.ps1 Anyone know what this path should be? Thanks! jonathan
I had opened an SR and referenced this thread. Support has told me that this has been identified and engineering is working on it. Hopefully, they have a fix soon.
Same here. Thought it was IAAS choking. Rebooted the environment a couple of times. No luck. The Submit and Cancel buttons seem to render off page. This is for standard and custom forms. I ...
See more...
Same here. Thought it was IAAS choking. Rebooted the environment a couple of times. No luck. The Submit and Cancel buttons seem to render off page. This is for standard and custom forms. I had a Chrome install that didn't auto update yet and the buttons rendered fine. Then I looked at the version and Chrome updated. Then the buttons disappeared. Confirmed on a fresh deployment of Win 10 and new installation of Chrome. This worked fine yesterday afternoon and then stopped working last night. Works fine in Firefox! Chrome: 75.0.3770.80 vRA: 7.5.0 Build 10053500 Windows 7 and 10 with current patches.
Here are the quick and dirty functions I'm using as a workaround. There is no error checking. vRO-StartSession : pass in a credential for the CredSsp connection to itself. it will return a s...
See more...
Here are the quick and dirty functions I'm using as a workaround. There is no error checking. vRO-StartSession : pass in a credential for the CredSsp connection to itself. it will return a session id that is used to pass to the other functions. mainly this is for speed so the connection to vCenter doesnt need to be constantly opened. vRO-StopSession : pass in the session id from StartSession. vRO-GetTag : get listing of tags with Category and Name. This will not return a valid Tag object vRO-NewTagAssignment : pass in a VM name, tag category, tag name to assign a tag to a vm. vRO-GetTagAssignment : pass in VM name to get listing of tags assigned to VM. This will not return a valid Tag object. vRO-GetTaggedVMs : pass in category and name to get a listing of VMs that have that tag assigned. This will not return valid VM objects. vRO-RemoveTagAssignment : pass in VM name and tag category/name to remove that tag from the VM. Pretty much just open a session and keep that variable to pass to the other functions. Then close the session when done. These are pretty specific to our needs, so some customizing may be needed. But it should be a good starting point.
Is this a change in 6.5? And/or is '-Authentication Credssp' now a valid parameter on Connect-ViServer? it's throwing an error for me. I'm using Invoke-Command with credssp in other parts of ...
See more...
Is this a change in 6.5? And/or is '-Authentication Credssp' now a valid parameter on Connect-ViServer? it's throwing an error for me. I'm using Invoke-Command with credssp in other parts of the scripts without issue. These vRA -> vRO -> PowerShell Plugin -> ScriptHost -> PowerShell scripts worked fine when the PS connected to a 6.0 vCenter. It broke when the vCenter was upgraded to 6.5. That's pretty definitive as to what the problem is. I even built another fresh scripthost and pointed it to a legacy 6.0 vCenter and the very same script once again worked normally. And then to the 6.5 host and it broke. As to what is and isn't working. Connect-ViServer is and continues to work normally and Get-VM and Get-Cluster and all the other cmdlets continue to work as expected with the exception of the tagging related cmdlets. Those throw the errors documented above. Is it true (mentioned above) that the backend processes of tagging has changed in 6.5? This would lead us to believe that this is indeed a bug. Personally, until someone can tell me that they got this scenario to work in their environment I consider this a bug. (vRO/PowerShell that does a Connect-ViServer, Get-VM, Get-Tag) I've worked around it with some functions that wrap the tagging calls in invoke-command -authentication credssp sessions. So at least my vRO environment is functional again. It's slower, but functional.
I got my Tag replacement functions functional and am retrofitting our scheduled script tasks as well as the vRO invoked scripts. Interesting side note, Get-Vm -Tag $TagObj works now. At least...
See more...
I got my Tag replacement functions functional and am retrofitting our scheduled script tasks as well as the vRO invoked scripts. Interesting side note, Get-Vm -Tag $TagObj works now. At least it does in the Invoke-Command scriptblock using Credssp. I will be putting in an SR for this eventually. I'll update this thread if anything comes of it. I expect a fair amount of pushback since it's vRO/PowerShell. Thanks for everyone's input! Jonathan
My biggest red flag for this is that it was working in vCenter 6.0 and then stopped working in 6.5. All things being the same, something changed in vCenter and how tagging works now. And it's j...
See more...
My biggest red flag for this is that it was working in vCenter 6.0 and then stopped working in 6.5. All things being the same, something changed in vCenter and how tagging works now. And it's just the tagging functions in PowerCLI/vRO. Everything else works as it did in 6.0. I've hard coded domain credentials as well as SSO creds. Same error. WinRM is setup and functional and used elsewhere in the script/workflows. Credssp is also being used elsewhere without issue. There is no parameter in Get-Tag to use Credssp authentication. There really shouldn't be a need for it. The domain service account and both server AD objects are set for delegation. (didn't need this before 6.5) Unless someone can verify that Get-Tag is working in a Powershell script called from the PowerShell plugin in vRO, I'm considering this a bug as I'm out of ideas and things to update/upgrade. I did manage to wrap Get-Tag in a Invoke-Command using Credssp on localhost. And that worked. It's a bit of a pain and a kludge, but it's working. I'm now creating a set of functions to replace the native tag cmdlets that work with a persistent pssession and Credssp.
Get-Tag has always worked from a PS console. It's just when vRO kicks off the script in the scripthost that Get-Tag errors out. FWIW, I updated the PS plugin to .13 and the error remains.
Uninstalled PowerCLI and did a Install-Module on the scripthost. It loaded and now reports: 6.5.2.6234650. Still sad panda. Same error message. Going to try the plugin update as soon as I g...
See more...
Uninstalled PowerCLI and did a Install-Module on the scripthost. It loaded and now reports: 6.5.2.6234650. Still sad panda. Same error message. Going to try the plugin update as soon as I get a window in vRA.
PowerCLI is 6.5.0.234. (before and after the vSphere 6.5 upgrade) Didn't know there was an update for the PS plugin. I'll give it a shot. I don't have high hopes though. Seems like a bug i...
See more...
PowerCLI is 6.5.0.234. (before and after the vSphere 6.5 upgrade) Didn't know there was an update for the PS plugin. I'll give it a shot. I don't have high hopes though. Seems like a bug in the PowerCLI cmdlet and how tagging works now. I thought I read a post that tagging changed fundamentally in the backend.
vCenter 6.5d and e (tested with single VCSA/PSCA and three linked VCSA and external PSCA) vRO 7.2.0.4629841 (built-in service in vRA 7.2.0.4659752, PS plugin @ 1.0.11) PS script host tested wit...
See more...
vCenter 6.5d and e (tested with single VCSA/PSCA and three linked VCSA and external PSCA) vRO 7.2.0.4629841 (built-in service in vRA 7.2.0.4659752, PS plugin @ 1.0.11) PS script host tested with Windows 2008R2 and 2016 (connected with HTTPS, WinRM, shared session, Kerboros, and a domain cert) Test script as follows: Import-Module vmware.VimAutomation.core Connect-VIServer -Server 'vcenter.company.loc' -User 'domain\account' -Password 'password' $TagList = Get-Tag Which results in: PowerShellInvocationError: Errors found while executing script Get-Tag : 8/8/2017 9:37:46 PM Get-Tag vSphere single sign-on failed for connection '/VIServer=domain\account@vcenter.company.loc:443/'. Future operations which require single sign-on on this connection will fail. The underlying cause was: The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation. That all being said... this worked prior to our upgrade to 6.5 from 6.0. (and still does work to a 6.0 vCenter) If I change the server name to a 6.0 vCenter in the connection string it works as expected. 6.5 vCenter.... errors. What changed in the upgrade? Does anyone think an vRO update to 7.3 would help?