I've not seen this before myself, but perhaps this KB article helps? "Datastore conflicts with an existing datastore in the datacenter that has the same URL" error in vCenter Server (79623) (vmware....
See more...
I've not seen this before myself, but perhaps this KB article helps? "Datastore conflicts with an existing datastore in the datacenter that has the same URL" error in vCenter Server (79623) (vmware.com)
Here is the PowerShell sample, including HTML styling to match your requirements (for example, embedding the report in a SharePoint site); ## ------------ ## HTML STYLING ## ------------ ...
See more...
Here is the PowerShell sample, including HTML styling to match your requirements (for example, embedding the report in a SharePoint site); ## ------------ ## HTML STYLING ## ------------ $head = @" <style type="text/css"> table { font-family: Calibri; font-size:13px; color:#333333; border-width: 1px; border-color: #CCCCCC; border-collapse: collapse; padding-left: 5px; } th { font-size:13px; border-width: 1px; padding: 5px; border-style: solid; border-color: #CCCCCC; background-color: #223C76; color:#ffffff; text-align: left; } td { border-width: 1px; padding: 5px; border-style: solid; border-color: #CCCCCC; } h1 { font-family: Calibri; font-size:24px; color: #9b1b1f; } p.smallheader { font-family: Calibri; font-size:13px; color: #223C76; } p.footer { font-family: Calibri; font-size:12px; color:#223C76; } tr:nth-child(odd) { background-color: #f2f2f2; } </style> “@ ## Share path to output HTML results $Path = '\\share' ## Path to CSV data that will be processed into HTML $Final = Import-Csv -Path '\\share\Report.csv' ## Add some content before your HTML table $Pre = '<h1>VM List Report</h1>' $Pre += '<p class="smallheader">For any queries with this data, please contact <a href="mailto:jon@jonmunday.net">Jon Munday</a>.</p>' $Pre += '<p class="smallheader"> [' + $Final.Count + ' objects found] - <a href="\\share\Report.csv">Export CSV</a> | Report generated: ' + (Get-Date -Format 'dd/MM/yy HH:mm:ss') + '</p>' ## Add some content after your HTML table $Post = '<p class="footer">Report generated: ' + (Get-Date -Format 'dd/MM/yy HH:mm:ss') + '</p>' ## Create the HTML using the custom styling, pre and post content $Final | ConvertTo-Html -title 'VM List'-Head $head -PreContent $Pre -PostContent $Post | Out-File "$Path\Report.html" -Confirm:$false #-Append
Ok, I've resolved this ... and boy do I feel like a dork. It turns out that in my haste to deploy the VM, I only gave it 2GB RAM ... as soon as I increase this to 8GB it works perfectly. Here ...
See more...
Ok, I've resolved this ... and boy do I feel like a dork. It turns out that in my haste to deploy the VM, I only gave it 2GB RAM ... as soon as I increase this to 8GB it works perfectly. Here is the VM with 2GB; And now with 8GB;
Here you go; VMware vSphere 5: Private Cloud Computing, Server and Data Center Virtualization Name: megaraid_sas-06.801.52.00-1096283.zip Release Date: 2013-04-17 Build Number: 1096283
I'm sure there are more elegant ways of doing this, but this should work for you; $metrics = 'cpu.usage.average', 'mem.usage.average' $start = (Get-Date).AddDays(-1) $vmList = Get-Content -P...
See more...
I'm sure there are more elegant ways of doing this, but this should work for you; $metrics = 'cpu.usage.average', 'mem.usage.average' $start = (Get-Date).AddDays(-1) $vmList = Get-Content -Path C:\_temp\VMs.txt $MyCol = @() $Results = @() foreach ($vm in $vmList) { Get-Stat -Entity $vm -Stat $metrics -Start $start | Group-Object -Property Entity | ForEach-Object -Process { $MyCol = '' | Select-Object -Property VM, Date, CPU, Memory $MyCol.VM = $_.Group[0].Entity.Name $MyCol.Date = $_.Group[0].Timestamp.Date $MyCol.CPU = $_.Group | Where-Object -FilterScript { $_.MetricId -eq $metrics[0] } | Measure-Object -Average -Property Value | Select-Object -ExpandProperty Average $MyCol.Memory = $_.Group | Where-Object -FilterScript { $_.MetricId -eq $metrics[1] } | Measure-Object -Average -Property Value | Select-Object -ExpandProperty Average } $Results += $MyCol } $Results | Export-Csv -Path C:\_temp\vm-resource-report.csv -NoTypeInformation -UseCulture
That's the first of two steps required. Once the disk has been extended from 40 to 50GB, logon to the Windows 2008 R2 server, open disk manager (may require a rescan), then simply select the C:\ ...
See more...
That's the first of two steps required. Once the disk has been extended from 40 to 50GB, logon to the Windows 2008 R2 server, open disk manager (may require a rescan), then simply select the C:\ and extend this. The process will be identical across the various vSphere versions, so being on 5.5 now doesn't change anything. Cheers, Jon
I'm not sure if there is a hard limit to the number of times you can upgrade, but upgrading from ESXi 4.1 to 5.1 and then to 5.5 is supported and will work (I just tested this in my lab). For ...
See more...
I'm not sure if there is a hard limit to the number of times you can upgrade, but upgrading from ESXi 4.1 to 5.1 and then to 5.5 is supported and will work (I just tested this in my lab). For reference, here are the relevant KB articles; VMware KB: Methods for upgrading to ESXi 5.5 Supported Upgrades to ESXi 5.5.x Cheers, Jon
Hi Paul, Could you clarify what you mean by;
The problem is that it created a new partition rather than increasing the size of the original
A) Do you mean you edited the VM and added a s...
See more...
Hi Paul, Could you clarify what you mean by;
The problem is that it created a new partition rather than increasing the size of the original
A) Do you mean you edited the VM and added a second disk rather than increasing the size of the original? or; B) Did you increase the size of the original disk and create a new partition in this free space? Either way, the issue should be simple to resolve; A) Delete the second disk that you don't need, increase the size of the original. Then from the OS disk manager, rescan the disks and extend C:\ into the free space. B) Delete the partition that you don't need. Then from the OS disk manager, extend C:\ into the free space. Cheers, Jon
Use views rather than repeatedly running Get-VM, see reference; Get-View - vSphere PowerCLI Cmdlets Reference Also, make sure you are running latest version of PowerShell as this makes a huge...
See more...
Use views rather than repeatedly running Get-VM, see reference; Get-View - vSphere PowerCLI Cmdlets Reference Also, make sure you are running latest version of PowerShell as this makes a huge difference to speed. Cheers, Jon
Yes, that's correct. I have recently finished upgrading heaps of standalone ESXi 4.1 hosts (with local storage only) to 5.1 and all have been successful. The same process applies to 5.5, so yo...
See more...
Yes, that's correct. I have recently finished upgrading heaps of standalone ESXi 4.1 hosts (with local storage only) to 5.1 and all have been successful. The same process applies to 5.5, so you shouldn't have a problem with preserving the VMFS datastores (and all VM's).
Since you in a domain, are there any group policies restricting your access? Perhaps you could use diskpart to verify if the disk is in read only mode? My Disk is Read-only, Help! - Ask the C...
See more...
Since you in a domain, are there any group policies restricting your access? Perhaps you could use diskpart to verify if the disk is in read only mode? My Disk is Read-only, Help! - Ask the Core Team - Site Home - TechNet Blogs
Perhaps the best course of action would be to push back on the security recommendations and log a support call with VMware to confirm the impact of closing this down ... I'm always reluctant to m...
See more...
Perhaps the best course of action would be to push back on the security recommendations and log a support call with VMware to confirm the impact of closing this down ... I'm always reluctant to make changes that I don't fully understand. In this case, security cant explain why they want this closed down and you don't know the impact to production if you do close it down. Cheers, Jon
With Windows Server 2008 R2 and above I am in favor of system manged pagefiles - the OS is extremely efficient at managing this without manual intervention. Here is another interesting article...
See more...
With Windows Server 2008 R2 and above I am in favor of system manged pagefiles - the OS is extremely efficient at managing this without manual intervention. Here is another interesting article which might help you decide ... http://technet.microsoft.com/en-us/magazine/ff382717.aspx Cheers, Jon
The W2012 dedupe should work without any issues - this is a native OS feature that is not restricted by hardware type (VM or physical). With regards to how this performs with backups etc. I guess...
See more...
The W2012 dedupe should work without any issues - this is a native OS feature that is not restricted by hardware type (VM or physical). With regards to how this performs with backups etc. I guess the simple answer is to test this in your own environment. Cheers, Jon
Hi, Welcome to the Communities. Here is some background on VMFS block sizes and their restrictions; VMware KB: Block size limitations of a VMFS datastore VMware KB: Frequently Asked Quest...
See more...
Hi, Welcome to the Communities. Here is some background on VMFS block sizes and their restrictions; VMware KB: Block size limitations of a VMFS datastore VMware KB: Frequently Asked Questions on VMware vSphere 5.x for VMFS-5 Remember, when upgrading from an earlier VMFS version, the block size is preserved. Newly provisioned VMFS-5 datastores have a unified 1MB block size. Cheers, Jon
What performance information are you after that you can't get from the native vSphere client or ESXTOP? The basic metrics that you should be look at are CPU, RAM, Network and Disk (latency, th...
See more...
What performance information are you after that you can't get from the native vSphere client or ESXTOP? The basic metrics that you should be look at are CPU, RAM, Network and Disk (latency, throughput and IOPS). Cheers, Jon
Looks like the guy solved it using dump and syslog collector; VKUMO | Configure coredump &#038; syslog server on diskless ESXi 5.1 Now open up PuTTY connect your host, login as root and r...
See more...
Looks like the guy solved it using dump and syslog collector; VKUMO | Configure coredump &#038; syslog server on diskless ESXi 5.1 Now open up PuTTY connect your host, login as root and run the commands: # esxcli system coredump network set --interface-name vmk0 --server-ipv4 10xx.xx.xx.xx --server-port 6500 replacing 10xx.xx.xx.xx with your core dump server. Enable the new setting: # esxcli system coredump network set --enable true That’s it, no more warning on your host and when creating a Host Profile for deployment of more hosts these settings will be inherited.