I recently became a contributor on TechTarget.com by answering the common question: How often should I conduct a disaster recovery test?
Feel free to swing on over to TechTarget.com and read what I have to say, here’s a link: http://searchservervirtualization.techtarget.com/answer/How-often-should-I-conduct-a-disaster-recovery-test
Thanks, and happy scripting!
I recently ran into an issue when installing SRM and thought I’d share. I didn’t get a screenshot, but the error was something like this:
Failed to Initialize – dbmanager could not initialize vdb connection – odbc error
If you click skip from there, it’ll fail to create the tables, and eventually get to the point where you’ll have to roll back.
As it turns out, it was due to a c0mp73x”P@s$w0rd! that caused the problem. I’m not sure what characters killed it, but going to a less complex pAs5w0rd worked fine. ODBC worked fine, user & permissions were set up properly, it just came down to SRM not being able to handle the special characters. What’s strange is a similarly complex password works for vCenter.
Hope this helps, have fun out there!
The hardware inventory file generated by the Auto Apply Drivers step is over 100k, which is the size limit for the MatchDriversSP process SCCM runs to provide the right drivers. The process then fails.
Create individual driver packages for each model and have a WMI query to apply those drivers as needed.
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… Read the rest of this entry »
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’ Read the rest of this entry »
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. Read the rest of this entry »
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!