After a bit of searching I did not find any documentation on how to remove the NetApp® NFS Plug-in 1.0.21 for VMware® VAAI from an ESXi Host. If you have a need to uninstall this the process is pretty simple.
Place your host into Maintenance Mode. SSH to your ESXi Host
esxcli software vib list
You should get a list of all plugins on your system.
Name Version Vendor Acceptance Level Install Date
----------------------------- ------------------------------------ ------ ---------------- ------------
net-enic 220.127.116.11-1OEM.518.104.22.1688611 Cisco VMwareCertified 2014-04-23
NetAppNasPlugin 1.0-21 NetApp VMwareAccepted 2014-05-09
net-qlcnic 5.5.164-1OEM.522.214.171.1248611 QLogic VMwareCertified 2014-04-23
to remove the plugin use the following command:
esxcli software vib remove -n NetAppNasPlugin --dry-run
--dry-run will show you what the command will do, remove it to actually run the command:
~ # esxcli software vib remove -n NetAppNasPlugin
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Removed: NetApp_bootbank_NetAppNasPlugin_1.0-21
You will need to reboot your server to complete the removal.
If you are looking to install the plugin you can follow the Netapp Guide Located here:
Recently a Friend of mine got an error on his computer when booting.
Fatal error C0000034 applying update operation 282 of 117809 (_00000...)
After some digging i found out that there was an issue with the Windows 7 SP1 Upgrade that had recently ran on his computer. After some digging i found this Microsoft Article that seemed to solve the problem.
Short Notes are:
Download This VBS and Delete the ".txt" extension and place it on a usb drive.
1. Reboot the Computer while tapping F8 to enter advanced boot options.
2. Select Repair your Computer
3. Under System Recovery Options, make a note of the Windows 7 drive letter listed on the line below Choose a recovery tool. EX: Operating system: Windows 7 on (C:)
4. Select the command prompt option
5. Navigate to the USB drive Letter (Trial and error worked for me)
6. Run this command
7. You should get an output similar to this
2 POQ nodes removed. Script Completed
8. Reboot Computer and Updates should complete Normally.
Hope this helps.
I found some additional info on this forum post.
So before I can show you what I am doing to fix our scom environment, I need to tell you a little bit about what we did wrong, and what issues we are seeing because of it.
SCOM uses Management Packs for everything it does.
Management Packs (MP) contain predefined monitoring settings that enable agents to monitor a specific service or application in Operations Manager 2007. These predefined settings include discovery information that allows management servers to automatically detect and begin monitoring objects, a knowledge base that contains error and troubleshooting information, alerts, and reports.
In short MP's are a collections of rules and alerts for a specific object. Many MP's are provided from Microsoft for monitoring things like Windows 2008 Server OS, or SQl. Some third party vendors provide management packs as well. For example we have a lot of Dell Servers in our environment, so we installed the dell server MP. This MP monitors physical system health and alerts us when a failure has occurred.
When you First install SCOM it will install around 40 different default MPs. These MP's are a core part of SCOM. You then have the option to install additional MPs. These will be application specific, Windows, SQL, Exchange, ect. It is a best practice that you only install MPs that you need, and install them in a controlled manner, so they can be configured, and overridden in a controlled manner.
In my environment we have 140 MP's installed, with very minimal overrides configured. We have anything with a critical status to generate an email to the System Admins. This creates a large amount of garbage emails to be generated.
The Second big issue we have is Overrides. It is best practice to never place an override in the default management pack (by default it will automatically select to go there.) Instead each management pack should have its own custom build override pack. For example if the MP is "Active Directory Server 2008 (Monitoring)" you would create a custom override MP "Active Directory Server 2008 (Monitoring) - Override." Like most items in your environment, naming conventions are key here. If you dont come up with something that you follow for naming custom MP's you will end up with a mess.
In my environment the overrides we do have defined are all over the place, some are in "Default Management Pack" some "Test" or "Test MP" and very little follow any naming scheme.
Unfortunately before i can fix the email flooding issue, I needed to fix the Poor Location and Naming Scheme for our custom MP's.
So I have been tasked at work to clean up our scom environment. I have been spending a lot of time trying to organize and understand how scom works. Wikipedia Defines scom as:
System Center Operations Manager is a cross-platform data center management system for operating systems and hypervisors. It uses a single interface that shows state, health and performance information of computer systems. It also provides alerts generated according to some availability, performance, configuration or security situation being identified. It works with Microsoft Windows Server and Unix-based hosts.
In short its a health management tool. It sends out email alerts based on what you define, to notify you of issues, or pending issues within your environment. It will allow you to migrate from a reactionary department to a proactive department.
This tool when configured right and make your job much easier, but when not configured right... well you end up with what i have.
Currently i receive between 200 and 500 email's a day on "critical" issues within my environment.
"Critical" Issues Like:
Alert: Computer Browser Service Stopped Resolution state: New
Alert: Miscellaneous SAM Errors Resolution state: New
Alert: DC is both a Global Catalog and the Infrastructure Update master Resolution
Now don't get me wrong, i do get emails about actual critical issues within my environment, but when i get emails on issues like the above, it makes it near impossible for me to react within a timely manner.
So. Im going to start posting tips and tricks i have found for managing scom on here. Hopefully some of this stuff will help someone down the line, or even myself when I need to come back and reference something.
Hope you enjoy the Adventure.
I have been having an issue with wordpress just hanging on downloading, when trying to install an update through the internal auto update. After doing some research, I was able to find out that this feature requires php5 in order to function.
My web Host is 1and1.com, and inorder for your site to use php5 instead of php4 you must add a custom line in the .htaccess file in the root of your website. Simply add the below code to your .htaccess file, and you are good to go.
Today i upgraded my wordpress from 2.9.1 to 2.9.2 The upgrade process was pretty smooth. At first i had some trouble using the automatic update, so i ended up manually updating.
How to Manual Update:
The manual update process is quite simple. The wordpress website has full details on their website as to how to do this update. (http://codex.wordpress.org/Upgrading_WordPress) I will just go over the basics really fast.
Today while trying to update my blog to the new version, i received the following error: "Briefly unavailable for scheduled maintenance. Check back in a minute." any time I attempted to view the website. I was using the built in wordpress update functionality. After doing some research it appears that when an update is being performed wordpress places a file in the Root of the blog called “.maintenance”
This is actually a really simple fix. Just FTP into your web space and delete this file, and your blog should be back to normal, Provided the incomplete upgrade did not damage your blog in any way.
Why Does this happen?
During a wordpress update, WordPress creates this "dummy" file in the root, to block access to the website while the update is in progress. This is done so that if someone attempts to view your website while the upgrade is in progress, they may get ill desired results. If you are having problems using the auto update feature i suggest updating it manually, and researching why its not working. There can be many causes.
Hope this Helps!
This is my first posting, on my new and improved blog. Im not going to lie, i dont update it as often as i would like. Im going to do my best to put up as many posts as possible on here. Let me tell you a little about myself. I am a Systems Administrator for a major telecommunications company. I also work part time at bestbuys Geeksquad. Expect my posts here to be technical in nature, or based around a project i am currently working on. If any of my posts help you please feel free to leave a comment and let me know that doing this helped someone out.