Hi
Will we be getting the REST API from Fusion in Workstation? It seems to me that having a new API should be supported across the hosted products to enable single codebase for both Workstation and Fusion.
Thanks
Hi
Will we be getting the REST API from Fusion in Workstation? It seems to me that having a new API should be supported across the hosted products to enable single codebase for both Workstation and Fusion.
Thanks
Wil,
Couldn't agree more, in fact, I've got a meeting this afternoon with Fusion PM to talk about some of my feedback while trying out the new REST API, one of which is this very topic
Hi,
If it is connected and pointing to the correct iso file then normally you should be able to select it from Windows Explorer and run "setup" on there so you can start the upgrade.
I take it that you already installed VMware Tools and that it is current?
--
Wil
Hello, I did a clean installation of W98 on VMWARE and it works. Now can tell me how to share a folder between my PC and the W98 virtual machine.
Thank you
Hi William,
Glad to hear you agree.
I would prefer to have the entire REST interface behind some authentication method and yes it would be great if it requires https.
From my point of view that should be mandatory.
Extra work perhaps for people who want to use this interface, but with great powers comes great responsibility.
But that does not mean that having the new API isn't sexy, it is and it does make a lot of things easier.
My mind is bubbling with possibilities, so yes happy that we get an extra API.
--
Wil
Is anyone else having this issue ?
Nope, you're good to go – UEM won't expire, and all features are available.
Hi,
I'm using vRA 7.0. When logging into the vRA console (Workspace One) and remoting into my VM using "connect using VMRC", VMRC launches without any issues by my selections for removable devices, reinstall vmware tools and virtual machine settings are greyed out.
If I log into the vSphere console (6.0), launch VMRC for the same VM, the selections are not greyed out and I could mount a USB drive from the client workstation.
Is there another setting or permission I need to apply within the vRA console?
Hi janasrs,
Is UEM running correctly at logoff? That's when we perform our "undo" actions, which includes removing previously created shortcuts.
The logic at logon just determines whether to create the shortcut or not; we need the logoff counterpart to clean up after ourselves.
Hi,
I tried this too & still have the same error message?
Hi Guys,
i need your help, i am trying to backup my vcenter appliance using bash script but i am facing an issue could related to API, as shown below
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
root@VCSA [ /tmp/CERT ]# sh ./vcpu.sh
{"type":"com.vmware.vapi.std.errors.unauthenticated","value":{"messages":[{"args":[],"default_message":"Authentication required.","id":"com.vmware.vapi.endpoint.method.authentication.required"}]}}Backup job id:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 188 0 188 0 0 3737 0 --:--:-- --:--:-- --:--:-- 3836
Backup job state:
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
your help is highly appreciated
Thanks
I'll be transparent and say that's the goal, but we haven't committed to a timeline yet. The feature is derived from the former AppCatalyst project, but that was never originally designed for Win or Lin, only Mac. So we're definitely interested in doing it, but the work so far was around porting it to Fusion and then we can get to a unified codebase with WS.
It's very encouraging to see your request tho... It's the feature I'm most excited about personally.
That's my #1 ask as well
What's the filename of the ISO?
Hi Phil,
Just to make sure I understand everything correctly:
If you do indeed use folder redirection:
If you are referring to creating a logoff task to clean some things up, I've made an attempt at that. I've created a script to run which first identifies the current shortcuts on the desktop to a text file, then it attempts to delete winscp.lnk and finally, it re-lists the directory contents to files. As shown below, the script shows that only Google Chrome remains when the script is run, but when I log back on the orphaned shortcut is still there.
I also tried disabling the desktop shortcut for winscp before logging back on - just to verify that the shortcut task is not recreating the shortcut during logon. The orphaned shortcut was still there when I logged back on.
Directory of c:\users\username\desktop
07/18/2017 03:13 PM <DIR> .
07/18/2017 03:13 PM <DIR> ..
07/18/2017 03:13 PM 2,247 Google Chrome.lnk
07/18/2017 03:13 PM 1,841 WinSCP.lnk
2 File(s) 4,088 bytes
2 Dir(s) 25,514,774,528 bytes free
Volume in drive C has no label.
Volume Serial Number is BA83-BE3C
Directory of c:\users\username\desktop
07/18/2017 03:14 PM <DIR> .
07/18/2017 03:14 PM <DIR> ..
07/18/2017 03:13 PM 2,247 Google Chrome.lnk
1 File(s) 2,247 bytes
2 Dir(s) 25,514,778,624 bytes free
Hi,
Its :-
Windows 10 Pro 1511 Build 10586.iso
Should the name matter?
No, what I meant was whether UEM itself was running correctly at logoff. Can you provide a FlexEngine log file with the log level set to DEBUG, covering a full session from logon to logoff?
We're currently busy implementing the Identity Firewall feature, so that we can allow access to certain subnets (like management subnets) based on your Active Directory group membership. Now, in theory this works fine. If you're part of "AD Group A", your desktop will become a member of NSX Security Group "AD - Group A", where only AD Group A is included. This Security Group is then used as the source for the distributed firewall rule that allows access to something. So far, so good. However, an administrator may occasionaly need to run an application within their desktop using "Run as administrator". Since NSX is constantly monitoring the Security Event Logs of all the configured domains, NSX will update your current IP address with a different user (expected behaviour perhaps, but not really what we want). All other defined rules now don't apply to the currently logged in user anymore, because NSX saw a different user and has overwritten the user-to-ip mapping.
Again, this is expected behaviour, however...
The user that's being used to login when using Run as administrator is part of a different AD group, which we then added to the same NSX Security Group. However, NSX doesn't "see" this relationship. This might be due to the fact that NSX simply doesn't support multiple logins on one IP address, and therefore it doesn't check if this new user is also part of an AD group that's specified in the same NSX Security Group. So this workaround doesn't work.
Naturally, I opened a Service Request with VMware and they pretty much told me that NSX doesn't support more than one user per IP. However, I refuse to believe that we are the only NSX customer that has run into this issue. I thought that perhaps the good people here at VMTN might have experienced the same issue and found a resolution (either through VMware Support or by using a different method).
Any thoughts?
Thanks!
I know this is a duplicate of this discussion, but that discussion is from 18 months ago and relates to vROps 6.1. I'm wondering if 6.5 or 6.6 has changed this functionality, because I can't seem to find it.
I run a daily report that gets mailed to the managers of our different support groups. The support groups have been instructed to add notes to alerts that can't be closed (for example, if they need to wait for a maintenance window to shutdown a VM for modification), and the managers would like to see the notes in the report to ensure alerts are being followed up on. I don't see anywhere in the Alert attributes the notes, nor do I see a Notes object that could even be included in a View of its own.