dpomeroy's Posts

Im seeing this problem as well when AD is configured as "Windows Integrated - machine account". When I configure AD with SPN, I cannot add any users or groups as I get the "cannot load users from... See more...
Im seeing this problem as well when AD is configured as "Windows Integrated - machine account". When I configure AD with SPN, I cannot add any users or groups as I get the "cannot load users from this domain" message. If I configure AD via the AD as LDAP method then we get the "client cannot authenticate with inventory service" error. I don't have the solution (yet), but you are not alone, SSO 5.5 certainly has issues.
Just wanted to say Im having the exact same problem. You are not configuring it wrong, something is not working right. Adding our domain as "AD as LDAP" gives me a different set of errors. So far... See more...
Just wanted to say Im having the exact same problem. You are not configuring it wrong, something is not working right. Adding our domain as "AD as LDAP" gives me a different set of errors. So far Im not impressed with the new and improved SSO 5.5. I've had an SR open for about a week now, I'll update this if they find out what is going on.
Massimo, Do you ever get sick of doing the "Scale Up vs. Scale Out" presentations Don Pomeroy VMware Communities User Moderator
30, definately 30 Don Pomeroy VMware Communities User Moderator
Yeah, its called Google. :smileylaugh: Seriously though, I don't think I've ever seen one website that collects all this info, so it means going to each companies website and searching for th... See more...
Yeah, its called Google. :smileylaugh: Seriously though, I don't think I've ever seen one website that collects all this info, so it means going to each companies website and searching for the info. Unfortunately some companies like Microsoft seem to constantly change their licensing schemes in a virtual world. Here is one link to get you started on MS licensing Thanks, Don Pomeroy VMware Communities User Moderator
Ken is correct, vSphere is the generic umbrella name, kinda like "Virtual Infrastructure", but that doesnt mean that it wont be included in product names. Keep in mind, exact naming conven... See more...
Ken is correct, vSphere is the generic umbrella name, kinda like "Virtual Infrastructure", but that doesnt mean that it wont be included in product names. Keep in mind, exact naming conventions in documentation and as it appears in UI can change from beta to final release. It is not uncommon for VMware to have a mix of old/new names all over the place during betas. If I wasnt under NDA I would send you a screen shot clearly showing the name "VMware ESXi 4.0.0" woops, did I just say that but like I said, who knows what everything is going to look like when the final product launches. Don Pomeroy VMware Communities User Moderator
Maybe he was refering to this one: 44% Failure Rate Don Pomeroy VMware Communities User Moderator
Ya thanks, we finally found someone at HP support that had a clue and could supply us with a new ISO image. But alas, we have decided HP USB keys are not at all reliable and are switching to 3i i... See more...
Ya thanks, we finally found someone at HP support that had a clue and could supply us with a new ISO image. But alas, we have decided HP USB keys are not at all reliable and are switching to 3i installable. Don Pomeroy VMware Communities User Moderator
We also have the same issue. Running update2 (just finished updating the whole cluster to all the latest patches available in Update Manager) and running the HP 8.10 agents. I do no recall see... See more...
We also have the same issue. Running update2 (just finished updating the whole cluster to all the latest patches available in Update Manager) and running the HP 8.10 agents. I do no recall seeing this with the 7.x agents - but then we were running Update 1 at that time. I am going to remove the HP agents and confirm if the issue persists like in the other posts. If confirmed - ticket will be opened with VMware. Are you running this build, 110268? Don Pomeroy VMware Communities User Moderator
We are having issues getting HA to work with 3i (embedded). It seems that the setting changes (per the KB) only "stick" about 10% of the time. Set, reboot, set, reboot, eventually they will stick... See more...
We are having issues getting HA to work with 3i (embedded). It seems that the setting changes (per the KB) only "stick" about 10% of the time. Set, reboot, set, reboot, eventually they will stick. We still have problems with HA and 3i after this point. I'll update this if we ever get anything usefull from VMware on this issue. Don Pomeroy VMware Communities User Moderator
Review the KB before you do anything: http://kb2.vmware.com/kb/1006716.html Don Pomeroy VMware Communities User Moderator
Can someone please explain to me why a "FREE" product has a friggin expiration date? It just does NOT MAKE SENSE! Even worse, is a Licensed version one has paid for has this expiration "BUG... See more...
Can someone please explain to me why a "FREE" product has a friggin expiration date? It just does NOT MAKE SENSE! Even worse, is a Licensed version one has paid for has this expiration "BUG". YES IT IS A BUG! QA missed the big fat cock roach in their process. Here's what I want. I want install Enterprise binaries that has NO expiration. If our agency paid in excess of $15,000.00 to license our servers (Enterprise version) the friggin thing should never ever expire. I feel like VMware does not trust it's customers eventhough they have already spent their thousands of dollars on their product. MS 2003 Server does not expire does it? NO. Enough with this garbage about software piracy and protecting your product, the same old boring played out song. If we paid for it it should never expire. VMWare's method is basically saying "you're all pirates and eventhough you paid up the a(insert letters here), I still don't trust you worth doodoo". That's why this issue is here. Hmmmm.... This scenario should sound familiar to VMware, remember the "FREE" vmware server release?....tick....tick....tick.... Edit Just to clarify becuase there seems to be some confusion on this. The license expiration issue has nothing to do with how VMware sells or licenses its products and the reason this happened on a "Free" product is because the time expiration was left in from the Update 2 beta code. VMware puts a hard expiration date into their beta products, this has nothing to do with preventing people from stealing the product, but to ensure beta products that have bugs and different features don't stick around and end up in production. So again, this was a huge mistake on their part to not take that code out, and we all have a right to be mad about it, but lets be mad for the right reasons. That being said, lets try to keep this thread to a technical discussion of the patch. So far our experiance has been mixed, we have a large environment with a variety of different hardware as well as ESX and ESXi embedded and installable all running. Most of the issues we have seen involve ESXi, standard ESX patching with UpdateManager appear to be working fine. I believe there is a problem with this patch and ESXi and UpdateManager, more info to follow. Don Pomeroy VMware Communities User Moderator
Eric, I could not agree more. Over the last few years it seems VMware has become so focused on releasing new products and new features that QA has taken a big hit. I understand they are u... See more...
Eric, I could not agree more. Over the last few years it seems VMware has become so focused on releasing new products and new features that QA has taken a big hit. I understand they are under constant pressure to stay two steps ahead of Microsoft, Xen, and others, but not at the expense of stability and reliability. One of the major things that helped ESX spread in the Enterprise data center was its reliability and stability, and they need to make it priority #1 if they expect us large companies to continue to put our critical applications on top of their virtualization layer. Don Pomeroy VMware Communities User Moderator
Yes, if anyone has the HP part number for this CD it would be very helpfull. Don Pomeroy VMware Communities User Moderator
Unsupported disk controller would be my guess. Don Pomeroy VMware Communities User Moderator
HP seems to be clueless on how to support the VMware products they sell, such as 3i on their USB keys. Don Pomeroy VMware Communities User Moderator
We had already started the process of transitioning new hosts to 3i for the main reasons of ease of deployment/management, better security, and fits better with our overall data center strategy. ... See more...
We had already started the process of transitioning new hosts to 3i for the main reasons of ease of deployment/management, better security, and fits better with our overall data center strategy. Don Pomeroy VMware Communities User Moderator
What about the panel discussion they had last year on these forums? Is that going to happen again this year? I thought that panel was great. This is still on hold I believe. Don Pom... See more...
What about the panel discussion they had last year on these forums? Is that going to happen again this year? I thought that panel was great. This is still on hold I believe. Don Pomeroy VMware Communities User Moderator
My fear is that EMC is going to assert more controll over VMware, and mess up a good thing. Don Pomeroy VMware Communities User Moderator
The short version from where you are now: Click a host, select the Update Manager tab, attach a baseline, right click the host, select Scan for Updates, right click the host and select R... See more...
The short version from where you are now: Click a host, select the Update Manager tab, attach a baseline, right click the host, select Scan for Updates, right click the host and select Remediate if updates are needed. Don Pomeroy VMware Communities User Moderator