vmware vcenter upgrade with cisco 1000v host disappears

Hopefully this helps people save a lot of time.

If you no longer see your VMware host in vCenter after you upgrade the host and you are using the cisco 1000v make sure your vCenter database has rows for that allow the version of your Host server.  We found that the only hosts that were allowed via the database were the original host version 4.1 thus we could not see the hosts under the 1000v distributed switch screen in vCenter until we added the rows and rebooted vCenter.

You need to add rows to this vCenter database table: VPX_DVS_COMPATIBLE

And you will need to look up the ID to enter in the first column of the above table in this table for the cisco 1000v switch: VPX_DVS

When you first open the VPX_DVS_COMPATIBLE table you will probably only see rows for the old versions of you host like this

ID of distributed switch             Description          Version
######                                             embeddedEsx         4.1+
######                                             esx                                  4.1+
……

You will need to add rows for the versions you want to be able to connect to your cisco 1000v distributed switch, so copy add the new rows with the versions you need.  The lines will  have the same data as above but with version different versions:5.0+, 5.1+, 5.5+

Example for version esxi 5.1
######                                             embeddedEsx         5.1+
######                                             esx                                  5.1+

We saw a message about a metadata error a few times while trying to upgrade as well as reload hosts.  We upgraded VIBs and VEMs on the host and verified many setting for to many hours before finding a reference to

We thought we did not have the correct licensing for the cisco 1000v, so we thought about changing to the free version of the cisco 1000v.    We upgraded from vCenter 4.1 to vCenter 5.5 which is not recommended when you have the cisco 1000v in the environment.  And the VMware updgrade simply does not update their database to support the newer esxi version thus the hosts do not show up under the distributed switch for the cisco 1000v until you add the rows above to the vCenter database.

 

Here are some of the steps we take to upgrade hosts:

Disconnected host from vDS in networking tab in vCenter

Go to host view in vcenter, configuration, security settings, enable SSH manually start

Then you can putty into the host

Deleted VEM/VIB from host  (vem-remove –d); then exit; stop SSH service in vcenter   (need to do this because when tried to upgrade without deleting VIB it gave error that VIB was conflicting and installer would not continue – no force migrate option like when went from 4.1 to 5.0)

Shut down host and use DVD to upgrade it to 5.5  (use upgrade, preserve datastore option)

Reconnect host in vcenter

Add Host to vDS in networking — This process automatically scanned host and invoked VUM to install VDS module on host, installed & remediated – all automatically!

Then went back to Host and VUM, scanned again, and installed 18 patches, which required a reboot

Exit Maintenance mode

Windows server how to change Public network to Private network

If you are cross connecting two servers or using a private internal network to connect your servers you will want to have the network identified as private.

Making network connection for backend connection / private IPs show as private instead of public.  Then you can change the firewall permissions on the private networks to allow access for applications like SQL server.

If you are using a backend connection to cross-connect two servers, you may want the network connection to show as a private connection and have different firewall rules than with your public connection. We have found that in Windows Server, when a default gateway isn’t entered for a backend connection, the network will display as “unidentified network” and windows will automatically define it as a public network for firewall profile purposes.

Solution

Windows Server 2008 R2 – One workaround is to change the default in Windows so that unidentified networks default to the private profile. Under Administrative Tools, Local Security, Policy, Security Settings, Network List Manager Policies, then on the right hand side you can change Unidentified Networks to Private.

 

Windows Server 2012 R2
Administrative Tools –> Local Security Policy –> Network List Manager Policies –> (in right window)  Unidentified Networks (double click).   Here you can change the location type to “Public” or “Private” and you can change the user permissions to allow them to change the type.

You should update your web.config now WordPress Permalinks

Are you trying to use Permalinks with WordPress to have a nice page name rather than www.domain…com/?p=3 and you see the message toward the top of your page that says “You should update your web.config now”?

You might be thinking what is a web.config. This means that you are running your WordPress site on a windows server like Windows 2012R2 server and the WordPress Admin can not add the code to the web.config file which is on your server under the default install folder for WordPress.

First you need to locate your web.config file.

  • You should find it in the default root where you installed WordPress. This folder will also have the folders “wp-admin”, “wp-content” and “wp-includes”
  • You can search your server for the web.config file. Note you may have more than one. So make sure this folder has these folders “wp-admin”, “wp-content” and “wp-includes”.

If you can’t access your file system to locate this file then you can’t user permalinks. If you are hosting with godaddy you want to use a Linux server. If you are using a dedicated server you should be fine running WordPress on a Windows Server. I know of several successful sites.

Once you find your web.config file you want to open it. You can open it in WordPad or Visual Studio if you have it loaded.

You need to add the code shown below and you can add it just below the line.


	<rewrite>
			<rules>
				<rule name="Main Rule" stopProcessing="true">
					<match url=".*" />
					<conditions logicalGrouping="MatchAll">
						<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
						<add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
					</conditions>
					<action type="Rewrite" url="index.php" />
				</rule>
			</rules>
		</rewrite>

Now Save your changes to the web.config file.

And now your web.config probably looks very much like the following.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
	<system.webServer>
		<rewrite>
			<rules>
				<rule name="Main Rule" stopProcessing="true">
					<match url=".*" />
					<conditions logicalGrouping="MatchAll">
						<add input="{REQUEST_FILENAME}" matchType="IsFile" negate="true" />
						<add input="{REQUEST_FILENAME}" matchType="IsDirectory" negate="true" />
					</conditions>
					<action type="Rewrite" url="index.php" />
				</rule>
			</rules>
		</rewrite>
		<staticContent>
			<remove fileExtension=".svg" />
			<mimeMap fileExtension=".svg" mimeType="image/svg+xml" />
		</staticContent>
        <defaultDocument>
            <files>
                <remove value="index.aspx" />
                <add value="index.php" />
            </files>
        </defaultDocument>
	</system.webServer>
</configuration>

Credit for the code goes to Jeff Clark NOTE his code does not have the correct double quotes for the asp.net web.config file found

iDRAC error Secure Connection Failed

iDRAC6 error “Secure Connection Failed” when trying to access several iDRAC cards.

If you access several iDRAC cards for remote administration of your Dell servers you may have seen the dreaded “Secure Connection Failed” message.

If you are using Firefox and have been clicking the “Add Exception” when accessing an iDRAC card over a https:// which doesn’t have a SSL cert loaded you can do the following to fix the issue.

Solution

…. Go to the IP or domain of the iDRAC card.
When you see the page saying “This Connection is Untrusted”
Click the “Add Exception” button at the bottom. This opens a window. If you uncheck the box at the bottom of the add security exceptions screen that says “permanently store this exception” so that it isn’t permanently stored.

Then you can go to both drac IPs using firefox without issue as long as you close & restart the browser between using each drac IP (but you can’t have both drac IPs open at one time in firefox).

Don’t permanently save iDRAC IP exceptions anymore. (note: I did clear out the exceptions and Dell idrac certificate from the past at à Firefox, options, options, advanced tab, certificates, view certificates, server tab (deleted IP address) and authorities tab (deleted Dell idrac default certification).

 

Can I delete files in the WERReportQueue folder on Windows Server 2008R2

If you have noticed that your windows server has a lot of files in the folder ProgramDataMicrosoftWindowsWERReportQueue you can delete them to free up space on your drive.

It is recommended using “Disk Cleanup” to free up the space.

To disable the files from accumulating you can turn Windows Error Reporting off.

On a Windows 2008R2 server open “Server Manager”
Open “Resources and Support”
Click “Configure Windows Error Reporting”
In the “Windows Error Reporting Configuration” box
Select “I don’t want to participate, and don’t ask me again”

 

See the steps from Microsoft below

http://technet.microsoft.com/en-us/library/cc754364.aspx#BKMK_enableWER_RMT

WordPress error Windows Server HTTP Error 403.14 Forbiden

If you see the following error after a successful install of wordpress on a IIS 7.5 on a Windows Server the fix might be to change your default document to index.php    In the case of the following error we found the default document set to index.aspx since it was inherited from the parent website, in this case a asp.net website.

Solution change your default document for your WordPress website. 

To change your default document in IIS 7.5 open IIS select/highlight/click the WordPress website (folder)

Then scroll down in the middle panel and double click the “Default Document” icon under the IIS section.  Here you can verify the default document(s) for your WordPress website and check to see if it is set to “index.php”

Actual Errors displayed in web browser
Error Summary HTTP Error 403.14 – Forbidden

The Web server is configured to not list the contents of this directory.

403 – Forbidden: Access is denied.

You might see the full error is you are viewing your wordpress website on the actual server via a browser which would like this

Server Error in Application “RIPTIDEHOSTING.COM/BLOG”

Internet Information Services 7.5

Error Summary HTTP Error 403.14 – Forbidden

The Web server is configured to not list the contents of this directory.

Detailed Error Information

Module DirectoryListingModule

Notification ExecuteRequestHandler

Handler StaticFile

Error Code 0x00000000

Requested URL http://www.riptidehosting.com:80/blog/

Physical Path C:inetpubwwwrootRiptideHositng.comblog

Logon Method Anonymous

Logon User Anonymous

Most likely causes: •A default document is not configured for the requested URL, and directory browsing is not enabled on the server.

Things you can try: •If you do not want to enable directory browsing, ensure that a default document is configured and that the file exists. • Enable directory browsing using IIS Manager. 1.Open IIS Manager. 2.In the Features view, double-click Directory Browsing. 3.On the Directory Browsing page, in the Actions pane, click Enable.

•Verify that the configuration/system.webServer/directoryBrowse@enabled attribute is set to true in the site or application configuration file.

Links and More InformationThis error occurs when a document is not specified in the URL, no default document is specified for the Web site or application, and directory listing is not enabled for the Web site or application. This setting may be disabled on purpose to secure the contents of the server. View more information »

Windows Server 2008 R2 stuck on windows update at 32%

Last week we had a customer who’s Windows 2008 R2 server stopped responding after selecting to restart the server.  If updates are allowed to be applied when rebooting your server will try updating.  In this case the server started applying server updates and was stuck at 32% for several hours and displayed the following

Please do not power off or unplug your machine

With the customers permission we did reboot the server and it came back to the same screen but proceeded to finish the updates after a few minutes.

A reboot may not fix your server but after several hours or days you will need to take action to proceed.  You may end up needing to repair windows or remove certain files if the reboot does not work.