I added a bunch of cmdlets for VMware’s PowerCLI to the cmdlets array in the powershell.php file.
So you don’t have to export and copy & paste them in to yours, I attached it to this post.
This is for the WP-Syntax plugin for WordPress that uses GeSHi to highlight certain things in the pre tag.
Just thought I’d share…
I recently had this problem, but forgot to take a screenshot for the blog, sorry guys.
I was patching an HA/DRS cluster using VUM and none of the VMs would migrate off one specific host. The error it gave was “A general system error occured: Failed to start migration pre-copy Error 0xbad010d. The Esx host failed connect over the VMotion network”.
Trying to install a driver for old hardware, or otherwise unsupported hardware, on Windows 8? I bet you’ve run across something that kept you from actually install the drivers.
While playing with my Galaxy Nexus, I ran into an issue where I could not install the ADB driver found in the Galaxy Nexus Toolkit. It told me the driver was not digitally signed, and after trying to use it, it said windows encountered a problem.
This is because Windows 8 enforces driver signing. If it’s not signed, Windows 8 says tough! Well, I found a couple ways to get by this, keep reading to find out how…
So you’re still using ESX 3.5 and need to patch it manually? Bummer, I know, I’m in that boat right now, or was. I ran “esxupdate -a query” to find out the latest patch and saw, “ESX Server 3.5.0 Update 4”. Then went to VMware’s downloads site to download Update 5a, and when it prompted me to download all dependencies, I did.
What did that give me? Nineteen (19) bundles/depots/zip files, one of which was ‘ESX350-Update05a.zip’
Those of you with the 6R75 or 6R80 (Ford’s newer 6-speed auto transmission found in 2007+ Expedition and 2009+ F150) may have been slightly alarmed when you popped the hood for the first time and can’t find a transmission dip stick. A few Google searches may also leave you baffled and ready to get rid of your vehicle because of all the misinformation. Unfortunately, there’s a lot of it, too much, imo.
I bought a 2007 Expedition back in April and found it amusing that I couldn’t check my transmission fluid. It’s one of the ‘regular’ things you should always do, I still check my oil at almost every fuel-up, that’s pretty much just how I was raised. I pull a trailer from time to time, so not having something I can put my own eyes on worried me. I did some Googling and was met with such phrases as “sealed system”, “dealer only service”, but the gold medal winner wrote it was a ‘throw away transmission, just use it til it breaks and get another’. Seriously? How ignorant can one be? The manual states something along the lines of fluid change at 30k miles if you’re pulling a trailer 100% of the time, and was vague otherwise (or I simply ADD’d over it). My friend Google gave me a wide range of 100k to 150k miles.
I decided to do what I should have done before going to Google, and that was simply get personal with my vehicle.
If you’re using a 12th Generation Dell server, disable the SD Card in the BIOS. Keep reading for how I discovered this.
We recently received a handful of new Dell R720s and needed to lay down Windows Server 2008 x64. Got everything cabled, powered them up, PXE booted from our SCCM 2007 machine, it formatted the disks, and right when it went to deploy the OS, it failed with (taken from the SCCM Console, advertisement status):
The task sequence execution engine failed executing the action (Apply Operating System) in the group (Install Operating System) with the error code 2147942450
Action output: d-x64.xml”
Not a data image
ApplyOSRetry:
TSLaunchMode: PXE
OSDUseAlreadyDeployedImage: FALSE
Searching for next available volume:
Volume E:\ is a valid target.
Found volume E:!sSystemPart.empty(), HRESULT=80004005 (e:\nts_sms_fre\sms\framework\tscore\diskvolume.cpp,128)
Unable to locate a bootable volume. Attempting to make E:\ bootable.
volume.getDisk() == iBootDisk, HRESULT=80070032 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,680)
MakeVolumeBootable( pszVolume ), HRESULT=80070032 (e:\nts_sms_fre\sms\client\osdeployment\applyos\installcommon.cpp,759)
ConfigureBootVolume(targetVolume), HRESULT=80070032 (e:\nts_sms_fre\sms\client\osdeployment\applyos\applyos.cpp,364)
System partition not set
Volume E:\ is not on the boot disk and can not be made bootable.
Failed to make volume E:\ bootable. Please ensure that you have set an active partition on the boot disk before installing the operating system.
The request is not supported. (Error: 80070032; Source: Windows). The operating system reported error 2147942450: The request is not supported.
While upgrading my vShield Manager to 5.1, I ran into a little issue, it told me the file was invalid. I know it’s not, I checked the md5sum and it’s right, how dare you tell me it’s wrong, BAH! :-P
The file name listed on VMware’s site is correct:
But when it downloads, it’s named incorrectly:
Just rename it to .tar.gz and you’ll be good to go!
Happy upgrading!
I jumped right into the installation of vSphere 5.1 when it went GA a few days ago, and like most was surprised with the requirement to install vCenter Single Sign On (I’ll call it vCSSO from here). I think it’s great, but had several issues during the first few installation attempts, all around the database.
I did not want to use a locally installed SQL server, so I created a database on the same instance as my lab vCloud Director database. From there, I used the sql scripts that are included with the installation media (ISO\Single Sign On\DBScripts\SSOServer\schema\mssql). You do have to edit some of the sql files, though, but it’s simple. For instance, in rsaIMSLiteMSSQLSetupUsers.sql you simply need to set a Str0ngp@ssw0rd! and in rsaIMSLiteMSSQLSetupTablespaces.sql you need to specify where to place the database files.
I figured I’d step through creating the database using both routes, and even bypass the strong password requirement. Keep in mind, this is for home labs and likely not ‘best practice’ for the enterprise. Lets see how it goes…
I finished my VMworld 2012 schedule and figured I would throw it out there. I still may change it around to hit more vCloud stuff, we’ll see.
Anyway, look for me!
| INF-VSP1168 | Architecting a Cloud Infrastructure | 10:30 AM | 11:30 AM |
| INF-VSP1423 | esxtop for Advanced Users | 01:00 PM | 02:00 PM |
| INF-VSP1232 | Avoiding the 19 Biggest HA & DRS Configuration Mistakes – 2012 Edition | 02:30 PM | 03:30 PM |
| INF-NET2207 | VMware vSphere Distributed Switch – Technical Deep Dive | 04:00 PM | 05:00 PM |
| INF-VSP2825 | DRS: Advanced Concepts, Best Practices and Future Directions | 05:30 PM | 06:30 PM |
| INF-SEC2330 | How to Enable and Host Payment Card Industry-Compliant Applications in a Private Cloud Environment | 11:00 AM | 12:00 PM |
| INF-SEC2813 | Beyond the Hypervisor: Three Key Areas to Consider When Securing Your Cloud Infrastructure Platform | 12:30 PM | 01:30 PM |
| ITT1953 | Advice From Your Peers: How to Best Run and Manage a Cloud Environment | 02:00 PM | 03:00 PM |
| INF-SEC1282 | Automating Security and Compliance with Disaster Recovery Using VCM, vCOps, vShield, VIN and SRM | 03:30 PM | 04:30 PM |
| OPS-CSM1167 | Architecting for VMware vCloud Allocation Models | 04:30 PM | 05:30 PM |
| INF-STO1545 | Architecting Storage DRS Datastore Clusters | 08:30 AM | 09:30 AM |
| INF-BCO2382 | VMware vSphere HA Recommendations to Maximize Virtual Machine Uptime | 10:00 AM | 11:00 AM |
| INF-VSP1365 | Understanding VMware ESXi Security | 12:30 PM | 01:30 PM |
| INF-VSP1364 | Architecting Auto Deploy for Availability and Scalability | 02:00 PM | 03:00 PM |
| INF-VSP1196 | What’s New with vCloud Director Networking | 03:30 PM | 04:30 PM |
| INF-SEC1840 | VMware vSphere Hardening to Achieve Regulatory Compliance: Better, Faster, Stronger | 10:30 AM | 11:30 AM |
| ITT3240 | From Weeks to Hours: Automated Provisioning and Deployment | 12:30 PM | 01:30 PM |
| OPS-CIM1926 | 5 Must Know Design Considerations for Planning Capacity When You are 50% or More Virtualized | 02:00 PM | 03:00 PM |
I’m working on importing drivers for Dell’s new 12G servers into our SCCM server for OSD. I got everything imported yesterday, added them to my boot image, created a new boot iso for use in non-PXE enabled networks, and went home for the day.
I get to work today and boot from my ISO I created yesterday and am greeted with the error 80004005, and some nondescript text stating it couldn’t pull a list of tasks. You know, the typical error that you have no idea what it actually means.
I googled it and found 80004005 is “Failed to get client identity”, and some pointed out the time being off may be the cause. I rebooted, BIOS time was maybe 30s off, so I tried again, but exported the smsts.log located in X:\windows\temp\smstslog\ via net use to my workstation. I opened that in SMS Trace, and here’s what I found:
Right there in RED is my error, plain as day, but what wasn’t shown to me in WinPE was the “signature varification failed”. I think it’s worthwhile to note Microsoft misspelled vErification, yup, that’s an A in theirs.
Now, if you google that, I found This Post stating they saw the error after moving their SCCM server to new hardware. We didn’t move to new hardware, we actually went from hardware to virtual, in that we P2V’d our SCCM server last night, which indeed changed the signature of the server.
I updated the boot image’s distribution point, which rebuilds it, then did a refresh for posterity. When that was 100% complete, I recreated the task sequence media boot ISO and all is well again.
Just thought I’d share!