Erik_Gross's Posts

It appears this issue is only related to Server 2003 64bit.  The PerfOS registry setting has a subkey under 'Performance' named 'Disable Performance Counters'.  The 'Disable Performance Counters'... See more...
It appears this issue is only related to Server 2003 64bit.  The PerfOS registry setting has a subkey under 'Performance' named 'Disable Performance Counters'.  The 'Disable Performance Counters' should be set to 0 (zero) to enable the 64bit counters. Full details in http://support.microsoft.com/kb/2554336. I'm still unclear how this subkey was added since it doesn't appear it should even exist (at least it doesn't in any other 'Perfxxx' registry entry keys. Hopefully this helps someone else having the same problem. Regards, E.
Has anyone else seen the issue with the standard Windows perfmon.exe 'Processor' counter being missing after upgrading the VM tools on a Server 2003 system to 4.1 U3?  (screen shot below) We n... See more...
Has anyone else seen the issue with the standard Windows perfmon.exe 'Processor' counter being missing after upgrading the VM tools on a Server 2003 system to 4.1 U3?  (screen shot below) We now have about 5 reported servers that are missing this counter.  The new 'VM Processor' (and 'VM Memory') counters are present, but the standard Windows counter is missing. I'm working through http://support.microsoft.com/kb/300956 now on one of the systems to attempt to recover/recreate the counter, but if anyone has a faster method and/or ideas of why the counter went missing, it would be appreciated. Thanks for your time. Erik G.
That worked for me.  (No service restart needed) I looked and our was set to already generate individual alerts, so i tried turning that off (for infrastructure and vm alerts), exiting out of ... See more...
That worked for me.  (No service restart needed) I looked and our was set to already generate individual alerts, so i tried turning that off (for infrastructure and vm alerts), exiting out of the configuration window and then reloading the page. That did clear the red 100 fault count message.  I went back into the configuration and re-enabled and then reloaded page again and the fault count was still cleared. Thanks for the quick response. EG
Has there been any resolution to this?  We are having the same issue... Thanks, EGross
I did finally figure this out. It turns out our problem was due to the fact that we did not have a DNS on the same subnet as we had defined for the vAPP IP addresses (in the IP Pool). Once ... See more...
I did finally figure this out. It turns out our problem was due to the fact that we did not have a DNS on the same subnet as we had defined for the vAPP IP addresses (in the IP Pool). Once we had the DNS on the same subnet, all the problems went away.  I reported this up through our account reps and the issue was confirmed. Hope this helps. Erik G. (Marking this as 'answered' even though i found the answer myself).
I have confirmed that both VMs are able to resolve each other (internal and external interfaces) as well as the vCenter server. I've also confirmed both have only about 1% usage on the /data v... See more...
I have confirmed that both VMs are able to resolve each other (internal and external interfaces) as well as the vCenter server. I've also confirmed both have only about 1% usage on the /data volume. EG
I first had this error after attempting to update from 5.0.0 to 5.0.1. I've since tried powering off and deleting the vApp from disk and redeploying from the OVA but get the same error.  The A... See more...
I first had this error after attempting to update from 5.0.0 to 5.0.1. I've since tried powering off and deleting the vApp from disk and redeploying from the OVA but get the same error.  The Analytics VM loads and boots with no issues, but the UI VM fails when starting the 'vami-sfcbd'.  Actual messages are: Starting vami-sfcbd: done. Checking vami-sfcbd status: ^........... failed, restarting vami-sfcbd. Shutting down vami-sfcbd: failed. Starting vami-sfcbd: done. Checking vami-sfcbd status: ............ failed, restarting vami-sfcbd. Shutting down vami-sfcbd: failed. Starting vami-sfcbd: done. Checking vami-sfcbd status: ............ failed, restarting vami-sfcbd. Shutting down vami-sfcbd: failed. Starting vami-sfcbd: done. Checking vami-sfcbd status: ........ This repeats about 15 times and finally fails, at which time the boot completes, but the console displays: Any help is greatly appreciated. Erik G.
Ok, looks like my way actually does work better (there's a first for everything)... Try using the following: get-snapshot * | format-list -property * That will show you all the propertie... See more...
Ok, looks like my way actually does work better (there's a first for everything)... Try using the following: get-snapshot * | format-list -property * That will show you all the properties actually being retrieved by the get-snapshot command. Be carefull if you have a lot of snapshots out there. This can take a while to walk through them all. Substitute and actual snapshot name for the '*' (asterisk) if you know one. You can use something like: get-snapshot * | sort-object SizeMB -descending | format-table -property VM,SizeMB,Created,IsCurrent -auto to get a pretty decently formatted report with most of the important information. Obviously you could easily tweak around what you are sorting on and what you want to display and even easily output to some formatted output (CSV, HTML, etc.). One other note, remember powershell has (and you can create your own) alias' for commands (get-alias * to see them all). You could sub 'sort' for 'sort-object' and 'ft' for 'format-table'. Later. Erik Gross This message and/or attachments may include information subject to GDC4S O.M. 1.8.6 and GD Corporate Policy 07-105 and are intended to be accessed only by authorized recipients. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Wow, guess I should re-read your email before sending... Just realized that I sent your command back to you... DOH!!! I did some digging, thought I came up with a great way, and even tested it... See more...
Wow, guess I should re-read your email before sending... Just realized that I sent your command back to you... DOH!!! I did some digging, thought I came up with a great way, and even tested it and sent it back to you... I need to go drink something with caffeine... Your command does work for me. Are you getting anything back at all? Erik Gross This message and/or attachments may include information subject to GDC4S O.M. 1.8.6 and GD Corporate Policy 07-105 and are intended to be accessed only by authorized recipients. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Rich - You can iterate the properties and methods of any PowerShell command by using the following... get-command get-snapshot | get-member Another way (I use a lot when trying to decide wh... See more...
Rich - You can iterate the properties and methods of any PowerShell command by using the following... get-command get-snapshot | get-member Another way (I use a lot when trying to decide what to display when looking at VMs or hosts or datastores) is to use the regular get-... command and then pipe it to format-list and show all properties. Example: "get-vmhost |fl -property *" This doesn't show methods but it does show all properties. Take care, Erik Gross This message and/or attachments may include information subject to GDC4S O.M. 1.8.6 and GD Corporate Policy 07-105 and are intended to be accessed only by authorized recipients. Use, storage and transmission are governed by General Dynamics and its policies. Contractual restrictions apply to third parties. Recipients should refer to the policies or contract to determine proper handling. Unauthorized review, use, disclosure or distribution is prohibited. If you are not an intended recipient, please contact the sender and destroy all copies of the original message. NOTE: Regardless of content, this e-mail shall not operate to bind CSC to any order or other contract unless pursuant to explicit written agreement or government initiative expressly permitting the use of e-mail for such purpose.
Rich - I had tried the uninstall/re-install route myself but had same results as your confirmed. I guess I should probably send a copy of these posts to our TAM and see if he can kick it up to t... See more...
Rich - I had tried the uninstall/re-install route myself but had same results as your confirmed. I guess I should probably send a copy of these posts to our TAM and see if he can kick it up to the engineers to tweak the next version of the installer. Keep on shelling... :smileygrin:
Nope... at least not unless the multiple-personality meds are wearing off and he, I mean I, didn't realize it.
Found the problem. There was an old registry entry at 'HKLM\SOFTWARE\VMware, Inc.' named 'VMware Infrastructure Update Manager - PowerShell Library' that had a key name 'Installedversion' with t... See more...
Found the problem. There was an old registry entry at 'HKLM\SOFTWARE\VMware, Inc.' named 'VMware Infrastructure Update Manager - PowerShell Library' that had a key name 'Installedversion' with the old version number there. For some reason, the installer does not check the version number to determine if it you are installing a newer version. The installer saw the existing key (that had a value of '1.something') and decided it was going to quit. Hopefully this will help others who may fight the old version issue. Good luck. Erik Gross erik.gross@gdc4s.com
Has anyone else had an issue installing the Update Manager PowerCLI? I tried the install and got an error first that vSphere PowerCLI wasn't installed (i had the older version 'vi toolkit'),... See more...
Has anyone else had an issue installing the Update Manager PowerCLI? I tried the install and got an error first that vSphere PowerCLI wasn't installed (i had the older version 'vi toolkit'), so i grabbed the latest vSphere PowerCLI and got that installed and going, but now i'm getting an error that the UM PowerCLI is already installed, but i'm not seeing the commandlets when i 'get-command...' I'm guessing the first install attempt set a pointer that the UM PowerCLI was installed, but when it failed, it didn't clear the pointer. (I've checked the 'add/remove software' and don't see the UM PowerCLI there either.) Any help is appreciated. Erik Gross
JDL - Probably not the answer you want (or that I wanted...) but when I called support about this, they told me the only way to remove old/superseded/un-needed patches was to totally uninstall ... See more...
JDL - Probably not the answer you want (or that I wanted...) but when I called support about this, they told me the only way to remove old/superseded/un-needed patches was to totally uninstall the update manager and then re-install. I brought this up to our TAM and he did some research and claimed the same. After I calmed down, I expressed my dismay that there was no way to better manage the available patches and asked this be looked at and submitted as a request for enhanmencement in future versions. My issue started when we decide to not use VUM for patching the VMs themselves, unfortunately, my system had already downloaded patches for Windows & Linux. I'm actually in the middle of the re-install now and will post more info after completed. Erik G.
Same problem but service restarts and/or reboots have not cleared issue. I even get the same error when logged into the VC Server itself and trying to connect to '.' or 'localhost'.... See more...
Same problem but service restarts and/or reboots have not cleared issue. I even get the same error when logged into the VC Server itself and trying to connect to '.' or 'localhost'. Any help is appreciated. Erik G.