badazws6's Posts

I was having a similar problem.  My problem seemed to resolve after I changed the primary group for the account.  Even after I changed it back to the original primary group it continues to work.
So, just for testings sake I made my DA account's primary group "domain admins" again.  I can still log in...  I don't like problem resolutions that don't make sense and I can't replicate... ... See more...
So, just for testings sake I made my DA account's primary group "domain admins" again.  I can still log in...  I don't like problem resolutions that don't make sense and I can't replicate...  What am I missing here?
Ok, getting some love.  The test accounts primary group was set to "domain users", the DA account's primary group was set to "Domain Admins".  When I changed the DA's primary group to "domain use... See more...
Ok, getting some love.  The test accounts primary group was set to "domain users", the DA account's primary group was set to "Domain Admins".  When I changed the DA's primary group to "domain users" it was able to log in.  So...  Still somewhat confused here, why should it matter?  What is the difference?
Hmmm, so I added the test account to the same number of groups as well as adding it to a group that contains a "-".  It still works.  Maybe default group?
So it does appear that "-" is acii.  Another thought, my DA account is a member of 13 groups.  I wonder if I can break my test account by adding it to more groups?
Ok, bumping around trying different things.  I removed my domain admins account from a the one group with a "_", with no love.  I noticed that account is a member of about half a dozen accounts t... See more...
Ok, bumping around trying different things.  I removed my domain admins account from a the one group with a "_", with no love.  I noticed that account is a member of about half a dozen accounts that contain  "-".  I setup another account that is not a member of any of those "-" groups and added it to domain admins.  I get love on this new test account, it is not been assigned direct permissions.  So I am learning at least my in my instance it appears there are issues with "-"'s in group membership for SSO accounts.  Is "-" non-ascii?  Researching that now. So it appears I am having issues similar to the following thread. https://communities.vmware.com/message/2293089#2293089
Lots of SSO discussion here... Anyway, I seem to be having a slightly different problem than the others I have been seeing.  When I give admin rights to my vcenter instance to "domain admins",... See more...
Lots of SSO discussion here... Anyway, I seem to be having a slightly different problem than the others I have been seeing.  When I give admin rights to my vcenter instance to "domain admins", which my account is a direct member of, I can not log in.  When I give my domain admin account direct permissions to the vcenter instance I can log in no problem. Anyway, my environment is 2008r2, everything is up to 2008 functional levels, vCenter is installed into a fresh 2008r2 instance. Anyone else seeing this behavior?  Any suggestions?  I will be doing more testing. MR
It is mainly just "what if scenarios" nothing specific.  Mainly I would just expect as a matter of best practice that if the secondary node came up and the primary is not there that it would auto... See more...
It is mainly just "what if scenarios" nothing specific.  Mainly I would just expect as a matter of best practice that if the secondary node came up and the primary is not there that it would automatically pick up.  Obviously there would need to be something in place to protect against split brain but having the first available node automatically pick up seems like a fairly basic HA tenet to me.  Lots of things I could come up where the primary node is lost and the secondary is available would be simple accidental deletion or the VM's on different raid sets and you loose the raid set the primary is on.  I agree, somewhat unlikely but I have seen crazier things.
I have vCenter protected by Heartbeat in several environments and none appear to be allowing vCenter to automatically start from a cold state (where both nodes in heartbeat are powered off).  To ... See more...
I have vCenter protected by Heartbeat in several environments and none appear to be allowing vCenter to automatically start from a cold state (where both nodes in heartbeat are powered off).  To bring vCenter up I have to boot both nodes and then manually start the application (vCenter).  On top of that it appears that I always have to start the application (vCenter) on the same node it was on before both nodes where powered off. I suspect I have something misconfigured here, can anyone point me in the right direction? vCenter 5.0.2, heartbeat 6.5, both nodes are virtual Thanks, MR
Thanks JD, that is exactly what I have been updating to change the size and rotations during the testing.
Does anyone have any information on the max retention of size and number of of files for teh vCenter Syslog collector.  I have been experimenting and it appears the most I have been able to confi... See more...
Does anyone have any information on the max retention of size and number of of files for teh vCenter Syslog collector.  I have been experimenting and it appears the most I have been able to configure is 100 rotations of 10mb per host.  Does anyone have any information on expanding past that point? Thanks, Matt
Any luck with this?  I have the same problem, but not linked mode, I actaully moved vcenter from OS to another.
I had this problem and ran a compact and it completely wiped out all my systems and data... Beware!
I'm sure it is functional, but Gary's suggestion was much more simple. More then one way to skin a cat, but some things are easier then others and you may as well use the easiest. Thanks for th... See more...
I'm sure it is functional, but Gary's suggestion was much more simple. More then one way to skin a cat, but some things are easier then others and you may as well use the easiest. Thanks for the suggestion. MR
Ok, this seems like a really basic question but is there a way to expand the Virtual Center 2.0.x Event log listings to display a different date set or more events then the default? Basically I'... See more...
Ok, this seems like a really basic question but is there a way to expand the Virtual Center 2.0.x Event log listings to display a different date set or more events then the default? Basically I'm trying to track a problem another tech was working on over the weekend and some of the events are no longer displaying because they "fell off the bottom" of the event log. Is this possible or do you have to go straight to the local event logs through the service console?
results of the 1.log: Starting Pegasus CIMOM (cimserver)...^[[60G[ [[0;32mOK [[0;39m ]^M CIMOM not responding, sleeping... CIMOM not responding, sleeping... CIMOM not responding, sl... See more...
results of the 1.log: Starting Pegasus CIMOM (cimserver)...^[[60G[ [[0;32mOK [[0;39m ]^M CIMOM not responding, sleeping... CIMOM not responding, sleeping... CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. CIMOM not responding, sleeping... Specified provider module was not registered. "1.log" 1507L, 58189C
During boot I get the following errors. Everything seems to be working fine but I would like to get rid of the error. Any suggestions as far as troubleshooting? Processing /var/pegasus/vmw... See more...
During boot I get the following errors. Everything seems to be working fine but I would like to get rid of the error. Any suggestions as far as troubleshooting? Processing /var/pegasus/vmware/install_queue/1 ERROR: See log - /var/pegasus/vmware/install_queue/1.log Processing /var/pegasus/vmware/install_queue/1 ERROR: See log - /var/pegasus/vmware/install_queue/1.log Pegasus CIMOM (cimserver) is already stopped. Starting Pegasus CIMOM (cimserver)...
Anyone have any experience or solutions for backing up a NT 4.0 VM from the VMDK level with TSM? I have seen and followed the documenation that VMware, IBM and other third party's have out the... See more...
Anyone have any experience or solutions for backing up a NT 4.0 VM from the VMDK level with TSM? I have seen and followed the documenation that VMware, IBM and other third party's have out there for doing it in 3.0.x and it doesn't appear to be working. The TSM agent in the service console just does a core dump when it starts to scan the VMFS. MR
I removed the 3.0.2 host from the VC server and then readded with no luck. I then created a cluster and added it to the cluster with not luck.
I'm not sure what you are referencing but I didn't do an upgrade on my VC instance. I removed and "clean" install on the same server and then readded the hosts.