Dear all,
I have the exactly the same problem installing the VMware vCenter 5.1.0b on Microsoft Windows 2012 either upgrade from ver 5.0 or fresh install. I was search around Google and VMware portal but I do not see any official document or website talked about vCenter 5.1.0x does not support Microsoft Windows 2012.
Any I have no issue on vCenter 5.0 running on Windows 2012 and vCenter 5.1.0b on Windows 2008 R2.
Any feedback are welcome
Hi every one
I am using vsphere ESXi 5.1 and now want to install the web access service. I found that it is required to use vmware command line interface. Then I installed the CLI and it is now in this location of my system: C:\Program Files\VMware\VMware vSphere CLI
I moved to the bin folder as it is instructed in this article. Now I want to check the status ans run the vmware web access service but when I try to run the command (service vmware-webAccess status AND service vmware-webAccess start) I get the error ('service' is not recognized as an internal or external command)
can any one help me to solve this issue
best regards
This "support" person doesn't seem to know anything about the product. You want to install WS - not VMware Tools - which obviously you could not install if you can't intstall WS adn create a VM. (A small sidenote here - actually vmware-install.pl IS used to iinstall ll VMware Tools - in a Linux guest). RHEL Linux is sulpported for WS 9 at least from version 2 to version 6.
Myself I would just say to the guy (who will never give his name) that you want to escalte the problem to his supervisor. Then if his supervisor is still overseas tell him you need to escalate the problem/question to his supervisor in the US. If her balks then call the corporate number and work your way around the phone tree. What I always say here is don't speak to tech support - speak to sales.
The whole question of out-sourcing to faraway land is almost criminal (I readched a support person in India whe I called up my State Tax return people and wanted my SSN - did not give it of course - then said the question t was a software problem!).
I can't say more since its a problem of saving bucks. Your time means nothing to the company.
BTW I have run into the gtk problem on some installs and could not solve it. You can try to force a cli install (I can't give the instructions without a further search on Google or using this forum search <not recommends IMHO>. But you will probably have the same problem when you try to bring up WS GUI>
Yes, you seem to be on the wrong chapter. Can you please what you are trying to do? What kind of app are you trying to publish?
I have 40 + vms in Protection group, Since its need is to map the unresolve device to recovery site. Do powercli has commands regarding this.
Thanks
--A
What is the size of the virtual hard disk itself? Go into the VM settings (without trying to start the VM). If the disk is larger than 19 GB (a distinct possibility for a server) you may just want to move it to removable disk and move it back when you've cleanit D: Look for a swap file or hibernation file. ( Windows may be warning of low disk space - is this the case??
Also it looks like you've confused two threads you started. This causes great confusion for anyone replying.
If I'm not not mistaken this "help" text from VMware goes back to version 5.5! And yes the GUI for VMware Tools was promised "real soon now" in TP2. Doesn't seem difficult to code - but then again I'm not privy to the code. 
the real problem is that once you start the VM does not recognize the operating system. OS not found. Why?
I'M able to take the remote session.now need to invoke powershell script for remote installation of Vcenter5.1.For SSO installation we’ve written logic somewhat like this:
$username = "Administrator"
$password = "crt@123"
$Server = "10.211.34.2"
$secstr = New-Object -TypeName System.Security.SecureString
$password.ToCharArray() | ForEach-Object {$secstr.AppendChar($_)}
$cred = new-object -typename System.Management.Automation.PSCredential -argumentlist $username, $secstr
$session=New-PSsession -Computername $Server -Credential $cred
Invoke-Command -Session $session -ScriptBlock {&"c:\batch_files\inventory.bat"}
In above code we’re taking username and password from xml file. It is taking remote session successfully & on local m/c ‘s console it is showing contents of the bat file and get stucked there only. We searched for Remote installation of bat file commands they are using ‘Invoke-Command’ only. But in our case neither the installation get started nor it is showing error.
Calling NetApp users... Any real-world experience/examples of where a NetApp back-end really excelled over the regular VMWare features on cheaper storage? Examples of where the regular VMWare tools fell short and NetApp filled in would be great.
Unfortunately there are no SRM cmdlets in PowerCLI.
But it can be possible to write a PowerCLI script to perform what you want to accomplish.
Can you provide some more practical details of what you want to do ?
Yes we have, working through it was Support now......though its gone surprisingly quiet in the last 24 hours..
Doesn't make me any wiser I'm afraid.
Perhaps the PowerCLI Dev Team can come up with an explanation, and perhaps a solution.
Hi MarchYang,
I have the same problem here. Did you figure it out? Please advise me if you have a solution.
I have created protection group ,which has 40+vms.
Now I have to map the unresolved devices to recovery site such as datacenter, resource pool and network information for all 40 vms. All 40 vms has same datacenter,resource pool and network.
Unresolve device mapping from protection site to recovery site.
Thanks
-A
Still facing the same issue..
Here are my system details and can anyone provide with the exact command to deploy ovf
My vcenter ndcame is "WIN-1VPBHEDRE5"
My datacenter name is "dc1"
My ESXi host is "10.110.209.214"
I did a little bit more testing...
I'm sure that there is a bug on the VMware side. You can set the first boot device, when you just specify a single device in the list, e.g. an ethernet device with its corresponding deviceKey. But when you specify a list of devices it doesn't work as it's supposed to. It just ignores some devices or there might be a problem with the order of the "Removable devices", that you cannot set at all.
In my case, I want the boot order to be 'CDROM, network, hard disk'. By doing that in one ReconfigureVM Task, it doesn't work. As a workaround, you can do that by using three ReconfigureVM tasks, where you enter the devices in a reverse order. (So 'hard disk' first, then you put 'network' on top and last, but not least the CDROM on top of that.
Perhaps a stupid question, but have you enabled Horizon management on your ThinApp packages?
The ThinApp packages must live in separate folders on your ThinApp repository.
Martin Felker wrote: Also it looks like you've confused two threads you started. This causes great confusion for anyone replying.
The only one greatly confused here is you! All KaL4 did in a thread he originally started and was resolved in Jan was to ask me if the .vmx configuration file I provided him was the cause of the current issue, which of course it's not, and then asked me why I though the error (of this thread) was being caused. It certainly made more sense to provide the answer here. I referenced the original thread since André had already provided an adequate simliar answer and I didn't want it to look like I was just butting in.
The bottom line is since the space is reclaimed upon Host reboot Ka4L needs to ascertain what explicitly and specifically is consuming that space and once that is known it can be properly dealt with. He has already been told by André and I what utilities can aid in uncovering that! 
Perhaps I'm still misunderstanding, but if I completely prevent the laptop from suspending, it just keeps running until the battery dies a couple hours later, at which point the laptop automatically shuts down and I lose all unsaved data. When I plug in the laptop and boot up the VMs again, they complain about Windows shutting down incorrectly and ask me if I want to start in Safe Mode. That's it.
