RSS
 

Posts Tagged ‘OS’

Dell iDRAC 6 not responding

11 Jan

For our Dell R610 servers, we apply firmware, Bios, and hardware patches using the Unified Server Configurator and an SUU Bundle created from Dell’s Repository Manager software.

During a recent update, one of the servers returned the following error:
“Alert! iDRAC6 not responding. Power required may exceed PSU wattage.”

CAUSE:
This produced a somewhat erroneous error that required F1 to continue. The problem appears to come from the server not fully power cycling properly during the update. There are also some buggy versions of the USC that can cause an issue as well.

TO RESOLVE:
Completely disconnect power from the server, and hold the power button in for 10 seconds to dump any residual in the iDRAC module or PSU capacitors.

 
No Comments

Posted in IT

 

iTunes Option to Sync WI-FI not working.

30 Oct

I recently upgraded to iOS 5 on both my iPhone 3GS and iPAD 2. I selected the option in iTunes to sync wireless over Wi-Fi for both devices. However, only my iPhone would do this. The steps below resolved and fixed my issue:

** THIS ASSUMES you have verified any network issues to ensure the iTunes system and iOS device are on the same subnet.

1) Make sure the WI-FI sync is enabled via iTunes
2) Power Off the iPad by holding the sleep button for 3 secs and sliding the power bar.
3) Open iTunes (let it stablize if sync is taking place with other iOS devices).
4) Power iPad on.

If the problem is corrected…the iOS device will appear automatically in iTUNES.

The are several articles stating that the mobile device needs to be plugged into power. This is NOT NECESSARY or TRUE. As the statement above the SYNC NOW button on the device indicates, you must be plugged into “AUTOMATICALLY” sync. Manual sync from either the device or iTunes is possible while not cable in any way.

 
No Comments

Posted in IT

 

VirtualCenter Server will not start

01 Jun

Was working one minute…now its not! Welcome to the wonderful world of Windows Updates. I’m assuming this was broken by the unattended installation of Server 2008 R2 SP1 through our environment or some KB update prior.

It all started with this error when I tried to log into VCenter Server:

“vSphere Client could not connect to ‘{machine name}’ A connection failure occurred (Unable to connect to the remote server)”

After investigating this, I determined the VMware VirtualCenter Server Service was not running. However, trying to start it produced an Event 7000, Service Control Manager “The VMware VirtualCenter Server service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.”

After contacting VMware support, their suggestion was to uninstall and reinstall. Which frankly, is their answer to 90% of any issues – very frustrating for what has to be one of the most expensive OS support contracts out there. While this didn’t directly fix the problem, uninstalling and reinstalling produced this error:

The following port numbers are either invalid or already in use.
VMware VirtualCenter HTTPS Port: 443

As it turned out, Routing and Remote Services now employs SSTP protocol. That feature produces a listener on 80 and/or 443. I’m not sure if this was introduced when we did the Service Pack or when. But nevertheless, selecting RRAS>PORTS>WAN Miniport (SSTP) Configure, and disabling “Remote access connections (inbound only)”

For reference, here is the knowledge bulletin I eventually used to troubleshoot:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003926

 
No Comments

Posted in IT

 

Irish Goodbye to Mike Murphy

17 Mar

“Hey Pal!”

It’s a simple phrase.  Not Irish, per se.  Just a hallway greeting that will forever remind me of one of Kansas City’s greatest Talk Show hosts – Mike Murphy. 

I was fortunate early in my career to work with true “radio” professionals.  Defiantly something you don’t see much anymore.  But in the early 80′s, News Talk 81 – KCMO was full of them.  Mike Murphy was unique in his manner.  But his popularity left little doubt to his ability. 

By 1985 my path diverged, and I only saw Mike on occasion.  But not a single St. Patrick’s Day has gone by since then without churning memories of that time.  Today, like each of the past 25 years, I was reminded.  But unlike those, there wasn’t a thought of calling.  And for the first time, the “Mike Murphy Saint Patrick’s Day Parade” was held without its founder.

Mike - So long Pal!  May the wind be always at your Back! 

P.S.  Don’t let the Grigs talk you in to a game of Hearts.

 
No Comments

Posted in In the Studio

 

How to Whitelist a domain or email in Exchange 2010

04 Mar

If you have the Edge Transport Role installed on an Exchange 2010, mail may be rejected with the following error:

My.User@domain.com
mail.domain.com #<mail.domain.com #5.7.1 smtp; 550 5.7.1 Message rejected as spam by Content Filtering.> #SMTP#

Don’t ask me why Microsoft has buried this feature! From what I can tell, the only way to whitelist in Exchange 2010 is through the Powershell – not the GUI.  Thanks to Chris Caldwell for the fix.

Specific Address

$list = (Get-ContentFilterConfig).BypassedSenders
$list.add("new.mail@address.com")
Set-ContentFilterConfig -BypassedSenders $list

Entire Domain

$list = (Get-ContentFilterConfig).BypassedSenderDomains
$list.add("domain.com")
Set-ContentFilterConfig -BypassedSenderDomains $list

 Verfiy

Get-ContentFilterConfig

 Adding or Removing additional domains
You can enter several domains/addresses at one time by seperating with a common, as Fredrik notes in the comments below (i.e.  *.domain.com,*.domaina.com,*.domainb.com,*.domainc.com).  However, in certain circumstances you may wish to remove only one item from the entire list.  To do this, use the MULTIVALUED PROPERTY.   Here is an example:

Set-ContentFilterConfig -BypassedSenderDomains @{Remove="domain.com"}
 
14 Comments

Posted in IT

 

Goodbye Ol’ Pardner

26 Feb

Keeping up with Grigs in an airport was tough. He walked fast and with purpose. In fact, the more time we had, the faster he walked. By the time the rest of us arrived at the gate, Grigs was already best friends with the pilots and crew. And he was holding court with everyone waiting to board – and a few who weren’t.

It could have been the cab driver, or a fan waiting in line. A security guard; a receptionist; or a CEO. Everyone succumbed to the warmth and charisma of Grigs. And everyone who had the fortune to cross his path, would always remember fondly their brief encounter with the Grigs! He was after all infectious. He was…a friend to life itself.

He loved Lenny. And he loved Lamar Hunt.

Like so, so many others, I will always remember my time with Bill Grigsby. And just as before, I know he is at the gate…right now…holding court and making friends.

I can only imagine the smile on his face, as he was greeted by the Mentor and Lamar.

Goodbye Ol’ Friend! Until we meet again….

 
No Comments

Posted in Kansas City Chiefs

 
« Older Entries