mark_chuman's Accepted Solutions

Re: New-VIPermission Extremely Slow and Not working across domains
Doh!  Entity.Name!
You can apply permissions directly to the datastore. I don't have a need to go deeper than clusters in our environment, but what would really work well for you is to place datastores into folder... See more...
You can apply permissions directly to the datastore. I don't have a need to go deeper than clusters in our environment, but what would really work well for you is to place datastores into folders in storage view. Have the folders be the names of your clusters in hosts and clusters view. Then place the datastores for each cluster into the corresponding folder. Then you only have to apply permissions for datastores on the folder instead of going into each individual datastore. Off topic a bit, but one thing folders in datastore view lack is the "storage views" functionality, which I put in for a future request. Yes, if you assign permissision in the datastore view the user can flip the view and see them. Thorough testing of your permissions framework is warranted before pushing out to users. It sounds like you are already doing this.
You have a 14 day grace period in which to run without a license server. After 14 days certain features (power on VMs) become unavailable. My recommendations: 1. Determine what day the licen... See more...
You have a 14 day grace period in which to run without a license server. After 14 days certain features (power on VMs) become unavailable. My recommendations: 1. Determine what day the license server was retired. 2. View /var/log/vmkernel, /var/log/messages files on ESX servers to pinpoint the first message regarding no available license server. 3. Project out 14 days from date of license server being removed. If you decide to try and beat the clock, do nothing. If you decide to get flex license server back up perform below steps: 4. Alter DNS name of license server (name 3.5 ESX servers are pointing to for licensing) to your new 4.0 vCenter server. 5. Install the flex license manager on your 4.0 vCenter server. 6. Ensure 3.5 ESX servers are now licensed. 7. Remove flex license manager when 3.5 ESX servers are gone.
When you perform the add into vCenter you are logged into the local ESX and vCenter via the vSphere client? I don't think that would cause this problem, but if you are logged into both during th... See more...
When you perform the add into vCenter you are logged into the local ESX and vCenter via the vSphere client? I don't think that would cause this problem, but if you are logged into both during the add, drop the vSphere client connection into the ESX and try the add again. Also, if you can post logs during the time of the failure: ESX /var/log/vmkwarning /var/log/vmkernel /var/log/messages vCenter vpxd log Is this the only ESX add that causes the issue? Can you VMotion the vCenter server to another ESX and try to add the problem ESX again?
We use mainly use converter for conversions or "movement" of VMs from one region to another because it is a GUI based process. We have quite a few moves/conversions per week, so we standardized ... See more...
We use mainly use converter for conversions or "movement" of VMs from one region to another because it is a GUI based process. We have quite a few moves/conversions per week, so we standardized on the converter. If we run into problems with converter (multiple failures, etc..) we'll perform a back-end scp of the actual VM files. I agree that this method is quicker, but in our case we didn't want to open up the console for jobs like this, we felt it was a more dangerous process from the console (deletion of files etc..). We have used converter to convert physical to virtual, move virtual, clone virtual, convert virtual from one version to another (workstation to esx for example). I also like that the sysprep process can be automated in the process as well as some virtual machine configurations. If we say SCP'd a virtual machine to another location and we were creating a clone in the new location, we would have to scp, startup the VM and then process the sysprep (Windows) and the rename, ip configuration etc...
thx. see this in the logs. Failed to obtain connection: HY000:-2146893044 Failed to obtain connection: HY000:-2146893044 Failed to obtain connection: HY000:-2146893044 Failed to ... See more...
thx. see this in the logs. Failed to obtain connection: HY000:-2146893044 Failed to obtain connection: HY000:-2146893044 Failed to obtain connection: HY000:-2146893044 Failed to obtain connection: HY000:-2146893044 Failed to obtain connection: HY000:-2146893044 Failed to obtain connection: HY000:-2146893044 Failed to obtain database connection for the past 1800 seconds. Please ensure that the database server is up and is accessible Win32 exception: Access Violation (0xc0000005) run odbc connection again and test database connection. does it connect correctly?
netstat -a at command prompt should show you what is listening at port 80. netstat -bna at command prompt should show you what service. service might show up as SQLserver.exe. if so, loo... See more...
netstat -a at command prompt should show you what is listening at port 80. netstat -bna at command prompt should show you what service. service might show up as SQLserver.exe. if so, look in sql service configuration manager and stop SQL server reporting service. info on reporting service running on port 80 “Reporting Services no longer depends on IIS to provide access to the SOAP endpoint. URLs no longer include Web sites in IIS. Reporting Services uses HTTP.SYS directly to listen for requests on a specific port that you define for report server URLs.” if you need reporting service, change it's port to something else.
Double prompt is normal when VUM is enabled. In our environment we installed SSL certs for main vCenter (no prompt for main VC) and then just installed/ignored messages for VUM plugin. Reason... See more...
Double prompt is normal when VUM is enabled. In our environment we installed SSL certs for main vCenter (no prompt for main VC) and then just installed/ignored messages for VUM plugin. Reasoning is that only a few admins are going to enable the VUM plugin. Most users have no need for it. If you don't want to enable SSLs at all you can try this to disable them at the vSphere client level. You can right click on your viclient --> Properties --> find the Target: on my system is "C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe" add a switch "-i yes" to the end make it like: "C:\Program Files\VMware\Infrastructure\Virtual Infrastructure Client\Launcher\VpxClient.exe" -i yes From what I understand there is no way to disable alerts at the vCenter level. It must be done at the vSphere client or SSL certs need to be setup. That's of course your call regarding the security of your env.
This process worked for us when moving ESX servers from old VC(2.5) to new VC(4.0). 1. Unconfigure HA and DRS on farm. 2. Disconnect all ESX servers in farm. 3. Remove all ESX servers in ... See more...
This process worked for us when moving ESX servers from old VC(2.5) to new VC(4.0). 1. Unconfigure HA and DRS on farm. 2. Disconnect all ESX servers in farm. 3. Remove all ESX servers in farm. 4. Add ESX server to new cluster in VC (4.0). 5. Configure HA and DRS on new farm. Used for over 700 ESX servers with zero impact.