Shoganator's Posts

Well in that case you should take a look at the log files. Use this KB article to identify the location of your web client service logs: http://kb.vmware.com/selfservice/microsites/search.do?l... See more...
Well in that case you should take a look at the log files. Use this KB article to identify the location of your web client service logs: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004090 Then you should troubleshoot if the problem is not immediately obvious from looking at log files. Use this KB article to help troubleshoot: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2011485 Hope that helps!
Could be a file in use error - FileIOFault to me sounds like a file is in use and is locked. Generally when doing a P2V you should try to stop any services that would normally be doing work on... See more...
Could be a file in use error - FileIOFault to me sounds like a file is in use and is locked. Generally when doing a P2V you should try to stop any services that would normally be doing work on a day to day basis. Take a look through services.msc, identify any non-critical to Windows services, stop them, mark them as disabled, reboot, and then try the P2V process again. Don't forget to re-enable and start your services again once the P2V is complete! You could also try removing the shares temporarily if you suspect them to be causing the issue. (Take a look at open file sessions in your compmgmt.msc MMC to see if any files are being access remotely too).
You'll need to provide more information than that to get help! What else did you try? Have you ensured the web client service is started? Are you using the vCenter Appliance or Windows version? I... See more...
You'll need to provide more information than that to get help! What else did you try? Have you ensured the web client service is started? Are you using the vCenter Appliance or Windows version? If the service is started, have you tried looking at log files? To me it sounds like the service may not be running. Have you tried opening a the vsphere web client locally in a web browser on the machine that runs the web client server to rule out firewall and networking issues?
Hi Nick, I believe the answer is no, it will not take into account the replica already on the "DR" side. As far as I can see, vMotion and vSphere replication are not "aware" of each other for ... See more...
Hi Nick, I believe the answer is no, it will not take into account the replica already on the "DR" side. As far as I can see, vMotion and vSphere replication are not "aware" of each other for this purpose. I did read through the vSphere replication tech paper by @vmKen over here, and did not see any mention of this either. Replicas should be treated just as these - replicas. Hence them being kept separate to other VMs, so when you vMotion the original VM to another Host / Site that contains the replica, they will still be kept separate - original VM, and replica. Hope that helps! Cheers, Sean
Ok, spent quite a bit of time trying to get this working but I wasn't having much luck. I need to be in a clear frame of mind to get this working nicely. Unfortunately I am bogged down with work ... See more...
Ok, spent quite a bit of time trying to get this working but I wasn't having much luck. I need to be in a clear frame of mind to get this working nicely. Unfortunately I am bogged down with work at the moment and have little time outside of work to do this either, so the best I can do for you now is adding the ProvisionedGB figure you wanted: http://dl.dropbox.com/u/450727/scripts/Datastore-Report/datastore-report_01.ps1 That will give you that bit. As for: FreeSpaceinGB AllocationPercent Those are already included in the original script! As I mentioned, you need to install VIProperties - go to the post I linked you to, follow the install instructions, and make sure that the VIProperties module is loaded when the script calls "Import VIProperties" at the start. That will give you the free space percent. If you want to work out the used/allocated Percent, just simply minus the Free percent from 100% and add that into another column in the table. If I had more time I would happily work on this, but right now life is a bit hectic for me
Hi, For the missing percent - did you install LucD's VIProperties? Grab them here and follow instructions to install them where you are running the script - http://www.lucd.info/viproperties/ ... See more...
Hi, For the missing percent - did you install LucD's VIProperties? Grab them here and follow instructions to install them where you are running the script - http://www.lucd.info/viproperties/ that should sort out the missing percent issue for you Make sure the VIProperties are loaded in your PowerCLI environment where you run the script! I'll take a look at adding your requirements to the script I originally did over the weekend when I get a chance (hopefully I can!)
Hi sydq, I know this is an old post, but I noticed traffic to my ESXi Backup / Restore utility coming in from this thread so I came to check it out To run the utility, you just need to l... See more...
Hi sydq, I know this is an old post, but I noticed traffic to my ESXi Backup / Restore utility coming in from this thread so I came to check it out To run the utility, you just need to launch the script from a PowerCLI prompt. The problem you are most probably having is that you are launching via normal PowerShell, which does not have the relevant modules loaded by default. Run VMware PowerCLI 5.0.1 and then type in the name of the file from there - i.e. C:\Downloads > .\nameofutilityfile.ps1 Don't forget to "unblock" the file once downloaded (right click it and choose properties). I can see that launching it manually from PowerCLI is a bit of a pain, so I'll look into getting it "compiled" into an executable file instead - that would probably help a bit with making it user-friendly You can download the latest version of the ESXi 5.0 Backup and Restore GUI from here: http://www.shogan.co.uk/?p=1095 Cheers, Sean
Brian, Great post - thanks for that. Just what I was looking for. I was thinking along similiar lines with regard to presenting the RDMs back to the new VM - as it would be a service down and ... See more...
Brian, Great post - thanks for that. Just what I was looking for. I was thinking along similiar lines with regard to presenting the RDMs back to the new VM - as it would be a service down and there would be time constraints with regard to how long it can be down for. It's really helpful to discuss things like this as you always tend to get discussions about the pros and cons - like your example of backups and snapshots on physical mode RDMs Thanks again for your input, much appreciated. Cheers, Sean
Hi all, I have never had the situation where I need to virtualise a system which has fairly large data disks which are presented via SAN LUNs. I am hoping to get some views/ideas as to the pro... See more...
Hi all, I have never had the situation where I need to virtualise a system which has fairly large data disks which are presented via SAN LUNs. I am hoping to get some views/ideas as to the process to follow. I guess I have a couple of options here: Currently, the largest data disk in use on the system in question is 1073GB in size. For a vSphere 4.1 environment, this would mean it is comfortably within the 2TB minus 512 bytes maximum VMFS volume size (considering an 8MB block size formatting). The other data disks which are also presented via SAN LUNs are smaller in size and could fit on other datastores once P2V'd. Based on this info, I would say that it would be preferable to P2V everything and not worry about using RDM. I would like to present the option for RDM though, seeing as though the data disks are already being presented from LUN, or if not, at least get a good idea of the process for consolidation in this type of scenario. I have done my research and gathered data on performance metrics - CPU, Mem, network and disk. All are within scope for virtualisation - disk usage is fairly high though, with the average IOPS utilisation over a 24 hour period being 395 IOPS - (peak of 490 IOPS). What are your thoughts on the above two options? Which would you go for, and would someone be able to give me an idea on what they would do should they want to virtualise this system and use RDM for the data disks? - what would the high level process be? Thanks for any input
Hey Gregg, Not 100% sure if this answers your question but I'm pretty sure I have set both of these adv. options via PowerCLI script in the past. (on train now), but here is a link to the post... See more...
Hey Gregg, Not 100% sure if this answers your question but I'm pretty sure I have set both of these adv. options via PowerCLI script in the past. (on train now), but here is a link to the post I did in it. http://www.shogan.co.uk/?p=974
Hi Luc, Thanks - that would be the answer I was looking for. Surprised my search didn't turn that KB article up - I must have been using the wrong terms! Cheers, Sean
Hi all, Bit of a funny one this, and I haven't been able to find a concrete answer as to why (communities + google search). When I modify a standard virtual switch with PowerCLI, specifically ... See more...
Hi all, Bit of a funny one this, and I haven't been able to find a concrete answer as to why (communities + google search). When I modify a standard virtual switch with PowerCLI, specifically to modify the number of ports (example from 128 -> 1016), the switch seems to apply 1008, but not 1016. Any ideas as to why I am seeing this behaviour? Here is small bit of script I am using: $vSwitches = Get-VirtualSwitch | Where {$_.NumPorts -lt "1016"} foreach ($vSwitch in $vSwitches) {       Set-VirtualSwitch -VirtualSwitch $vSwitch -NumPorts "1016" -Confirm:$false       } Cheers, Sean Message was edited by: Shoganator, changed code highlighting to quote.
Nice. I am still trying to come to terms / get the hang of Github myself. I have the client installed and key pairing done, but that is about it so far :smileygrin:
Hi Joe, Thanks for posting this up. I for one will find it useful as I will soon be automating the deployment of a particular staging environment build I have been deploying lately. The portgr... See more...
Hi Joe, Thanks for posting this up. I for one will find it useful as I will soon be automating the deployment of a particular staging environment build I have been deploying lately. The portgroup creation here will come in handy as a reference Cheers! Sean
Also, is the 2.2 appliance still compatible with vCenter 5.0? I do not want to hassle with installing a whole new 2.3 version appliance after upgrading our vCenter to 5.0. I would rather wait for... See more...
Also, is the 2.2 appliance still compatible with vCenter 5.0? I do not want to hassle with installing a whole new 2.3 version appliance after upgrading our vCenter to 5.0. I would rather wait for the in-place update patch for 2.2 -> 2.3 migrations.
Hi there, I will be upgrading our vCenter 4.0 to vCenter 5.0 today and wanted to find out if anything needs to be changed for our vCloud Usage meter appliance? I know that it collects data eve... See more...
Hi there, I will be upgrading our vCenter 4.0 to vCenter 5.0 today and wanted to find out if anything needs to be changed for our vCloud Usage meter appliance? I know that it collects data every hour and compiles a monthly report that is emailed through once a month, but is there any compatibility that needs to be looked at between 4.0 and 5.0 of vCenter? We are currently using version 2.2 of the vCloud Usage meter. One additional detail: I will be migrating our vCenter Server to a new server (new name and IP Address) so I will obviously need to change the connection details that the vCloud usage meter uses to connect to vCenter. Anything else I should look into or watch out for? Cheers, Sean
CRad14's post explains a way of doing this. Alan Renouf has also blogged a script on how to shutdown VI before too - it goes a step further and will also shutdown your ESXi hosts too (unless you ... See more...
CRad14's post explains a way of doing this. Alan Renouf has also blogged a script on how to shutdown VI before too - it goes a step further and will also shutdown your ESXi hosts too (unless you are running your vCenter server(s) as VMs too though). Check it out here: http://www.virtu-al.net/2010/01/06/powercli-shutdown-your-virtual-infrastructure/ (it goes without saying, be careful playing with cmdlets that will shutdown anything - VMs, Hosts etc)! Finally, if you use any of the above for shutting down your VMs, if you have any which do not have VMware tools installed and do not shutdown with the above script, do something like this to get a list back of VMs still running which can then be manually powered down: $VM = Get-VM | Where {$_.PowerState -ne "PoweredOn"} If you would like a way of shutting down VMs with Windows guests which do not have VMware Tools installed for some reason, you could use the normal PowerShell Cmdlet Stop-Computer. This can shutdown remote computers too. Example below: Stop-Computer -Computerame MYSERVERNAME -Force Hope that helps! Sean
Thanks Alan, (and thanks for pointing out Switch to me). Hope to share more as I learn and create more.
Hi all, I made a fairly simple function for PowerCLI last night that will help you identify the version of ESX(i) that VMware Tools corresponds to. Usually it is easy enough to get the "Intern... See more...
Hi all, I made a fairly simple function for PowerCLI last night that will help you identify the version of ESX(i) that VMware Tools corresponds to. Usually it is easy enough to get the "Internal" build number of VMware Tools using PowerCLI (it can be exposed by using $var.ExtensionData.Config.Tools.ToolsVersion), however this is just a four digit internal build number of VMware Tools. This script aims to provide you with an extra column of data to show the version of ESX/ESXi it corresponds to using a Switch statement. You can read more on my blog post for this function at http://www.shogan.co.uk/?p=1219 Here is a link to the Script/Document here on the communities site: http://communities.vmware.com/docs/DOC-18645 Hope it is useful! Cheers, Sean
# Mapping file found at: http://packages.vmware.com/tools/versions # Content of mapping file as of 08/03/2012: Function Get -VMToolsMapped () { Get -VMToolsMapped -VM ... See more...
# Mapping file found at: http://packages.vmware.com/tools/versions # Content of mapping file as of 08/03/2012: Function Get -VMToolsMapped () { Get -VMToolsMapped -VM MYVMNAME .EXAMPLE PS F:\> Get -VMToolsMapped MYVMNAME .EXAMPLE PS F:\> Get-VM | Get -VMToolsMapped .EXAMPLE PS F:\> Get-Cluster "CLUSTERNAME" | Get-VM | Get -VMToolsMapped .LINK http://www.shogan.co.uk .NOTES Created by: Sean Duffy Date: 08/03/2012 #> [CmdletBinding()] param( [Parameter(Position=0,Mandatory= $true ,HelpMessage= "Specify the VM name you would like to query VMware Tools info for." , ValueFromPipeline= $true ,ValueFromPipelineByPropertyName= $true )] [String] $VM ) process { $Report = @() New -VIProperty -Name ToolsVersion -ObjectType VirtualMachine -ValueFromExtensionProperty 'config.tools.ToolsVersion' -Force $VMInfo = Get-VM $VM | Select Name, ToolsVersion Switch ( $VMInfo .ToolsVersion) {     8389 { $ESXMapping = "esx/5.0u1" }     8384 { $ESXMapping = "esx/5.0" }     8300 { $ESXMapping = "esx/4.1u2" }     8295 { $ESXMapping = "esx/4.1u1" }     8290 { $ESXMapping = "esx/4.1" }     8289 { $ESXMapping = "esx/4.1" }     8288 { $ESXMapping = "esx/4.1" }     8196 { $ESXMapping = "esx/4.0u4 or esx/4.0u3" }     8195 { $ESXMapping = "esx/4.0u2" }     8194 { $ESXMapping = "esx/4.0u1" }     8193 { $ESXMapping = "esx/4.0" }     7304 { $ESXMapping = "esx/3.5u5" }     7303 { $ESXMapping = "esx/3.5u4" }     7302 { $ESXMapping = "esx/3.5u3" }     default { $ESXMapping = "Unknown" }     } $row = New-Object -Type PSObject -Property @{         Name = $VMInfo .Name         ToolsVersion = $VMInfo .ToolsVersion         ESXMapping = $ESXMapping     } $Report += $row return $Report } }