Server core OS installations are not supported. Horizon Connection Server 7.1 requires "Server with Desktop Experience" versions of:
- Windows Server 2008 R2
- Windows Server 2012 R2
- Windows Server 2016
Mark
Server core OS installations are not supported. Horizon Connection Server 7.1 requires "Server with Desktop Experience" versions of:
Mark
Welcome to the Community,
yes, to both questions.
You can use whichever image you want (VMware, or a vender OEM image). The vendor images usually contain additional drivers and/or tools which support their hardware. In fact, for some hardware models you even need to use the vendor's OEM image to make ESXi work.
It's up to you whether you are going to use vCenter Server. You can manage the host separately, if you don't want/need the features which come with vCenter Server.
André
make sure each component (switch and NIC) is set to 9000, if any component is set to 1500 you will get a flag.
I can't check all vmx files, however they are in the proper datastore. I'm able to retrieve all the datastores and trace the vmx files using the path. It's accurate.
Yeah, being a newbie at VMware I didn't realize what I'd done. So, to cut this short, I couldn't wait for an answer so I deleted the VM and all files related. I'm starting from scratch which is not a big deal. I did migrate properly, and that's when I saw what appeared to me to be using double the space, one in each store. I'll never know, or I'm just missing something, but I've move on. Thanks for responding.
I may ping you depending on what I hear back from my emc distributor.
Storage VMotion should do the job for you. New Inventory name of the vm should reflect for VM folder and all the file after SVmotion
Renaming a virtual machine and its files in VMware ESXi and ESX (1029513) | VMware KB
If you found this or any other answer helpful, please consider the use of the Helpful to award points.
Best Regards,
Deepak Koshal
CNE|CLA|CWMA|VCP4|VCP5|CCAH
Please do either way - this will help us bring you guys (our end users) a better experience.
Breaking the licenses, and assigning them to more than 3 host may certainly be possible from a technical point of view, but it violates the EULA.
from https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/products/vsphere/vmware-vsphere-vsom-pricing-whitepape… (page 7)
VMware vSphere Essentials Kits are all-in-one solutions for small environments (up to three hosts with two CPUs each) ...
André
Prerequisites:
1. vCenter Server instance is added in vRO using an administrator user account with full privileges (using the "Share a unique session" option while adding vCenter Server instance) on vCenter Server and full permissions in vRO.
2. The "vmuser" has fewer privileges e.g. the default "Virtual machine user (sample)” role on the vCenter Server and View, Inspect, Execute permissions in vRO.
Scenario:
The “vmuser” executes the vCenter Server workflow “Create simple virtual machine”.
The workflow execution completes successfully creating the specified virtual machine. However, the operations are executed in the context of the service account i.e. the administrator user account with full privileges used for adding the vCenter Server in vRO. Note that the “vmuser” has no permission to create a virtual machine and with execute permission in vRO the restricted user created a virtual machine.
Also observed that the Initiator reported in the Recent Tasks vs. More Tasks in vSphere Web Client are different.
What options are available if I want to execute the vRO workflow/operations in the context of the “vmuser” – the user that initiated the vRO Workflow instead of the service account used for adding the vCenter Server in vRO?
Appreciate your thoughts, suggestions, comments on this.
I think of few options:
1. Plug-in for vRO with Custom Workflows
2. Leverage vRO REST API retrieving vRO user, workflow/operation details and check against the vCenter Server privileges for the vRO user for allowing/disallowing the vRO workflow/operation.
Needing to upgrade a Vcenter 5.5 (installed on Windows Server) to 6.5. I would like to just upgrade the Vcenter in place. That part seems easy. This also has VMware View tied to it. Will this break? I have several 5.5 hosts that we are also migrating away from. I 3 new hosts with 6.5 installed, but as you know my current Vcenter will not manage them until the upgrade. Can I upgrade to 6.5 manage current 5.5 and 6.5 hosts, do the migration and then down the old hosts?
I've got two VCSAs at 6.5 build 5705665. When I run the following, I get the error noted below:
Connect-VIServer vcsa1.blah.local
Connect-VIServer vcsa2.blah.local
$VCTags = Get-TagAssignment -Server vcsa1.blah.local
Name Port User
---- ---- ----
vcsa1.blah.local 443 BLAH\user
vcsa2.blah.local 443 BLAH\user
Get-TagAssignment : 6/22/2017 1:55:51 PM Get-TagAssignment Sequence contains more than one matching element
At line:4 char:12
+ $VCBTags = Get-TagAssignment -Server vcsa1.blah.local
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [Get-TagAssignment], CisException
+ FullyQualifiedErrorId : VMware.VimAutomation.ViCore.Impl.V1.Service.Tagging.Cis.TaggingServiceCisImpl.GetTagAssignment.Error,VMware.VimAutomation.ViCore.Cmdlets.C
ommands.Tagging.GetTagAssignment
I can disconnect from vcsa2 and run the Get-TagAssignment cmdlet successfully against vcsa1. The error only occurs when simultaneously connected to these two servers. I have one other 6.5 build 5705665 VCSA and any combination with it and the other two doesn't result in the error. I also have some 5.5 vCenters on Windows and can't reproduce the error with any combination of those and 6.5 servers.
I've reproduced from Windows Server 2012 R2 (PowerShell 4.0, PowerCLI 6.5R1) and Windows Server 2016 (PowerShell 5.1, PowerCLI 6.5.1).
Can anyone else reproduce this?
Message was edited by: dbailey12
Awesome! Happy to help and thanks for marking answered.
Hi,
While you could try and install Workstation 8, perhaps just changing the virtual hardware of your old RH7.2 VM to an older compatibility level helps?
The virtual hardware might just contain parts that are too new for RH7.2 to be recognized. We're talking about an OS from 2001 after all.
Try virtual hardware version 6 or 7.
FWIW, on Workstation 12 you can change the virtual hardware version with the virtual machine shut down (not suspended) via:
- Right click on the VM in the library
- Manage -> Change Hardware compatibility
- You'll get a wizard
- Next
- From the drop down select "Workstation 6.5 - 7.x"
- Next
- Clone if you want to preserve the original VM, alter if you're OK with changing the VM itself
- Next
- Close
Try again.
--
Wil
Hello Adiel/Danko,
Quite puzzling that 'esxcli storage core path list' lists the devices, possibly the devices are disconnecting/detaching during boot?
Can you attach the boot log located here /var/log/boot.gz ?
Please check if these paths are active via the Web Client:
Host > Configure > Storage Adapters > Select the vSAN controller > Paths
Bob
-o- If you found this comment useful please click the 'Helpful' button and/or select as 'Answer' if you consider it so, please ask follow-up questions if you have any -o-
Has anyone come up with a good solution for this? The KB articles referenced did not help. It seems like a complete waste of time to have to restart servers until you get them up in the correct order. There has to be something that can be scripted differently.
I added some debugging lines in the 2nd part of the script (attached).
What does this show (i don't need all the output, just some representative loops through the 2nd part of the script).
Thanks for the additional info, JohnTwilley.
UEM isn't doing anything special w.r.t. accessing or locking files. It just asks Windows to enumerate files from a folder, read files, write files, etc, without doing anything special.
Do you also get the error when you add the Entity parameter, referring to one or more specific VIObjects?
Hi,
here's the readme file for the current Firmware for QLE2562 HBA's.
Multi-boot image for 8Gb HBAs (Read Me)
The Firmware Version of your adapter is 7.04.00, latest available is 8.01.02.