Comments on: Fix: Intel PROSet for Windows Device Manager missing tabs

By: Jay

Jay — Wed, 22 Sep 2010 02:48:19 +0000

Wow, thanks dude, been banging my head on the wall for 2 days about this one! Why can’t they just include that in the README.txt file? Sheesh!!!

By: Noof

Noof — Thu, 01 Apr 2010 21:08:42 +0000

OMG, thank you, thank you, thank you!!!

By: Brian

Brian — Thu, 17 Dec 2009 16:11:15 +0000

I was another stumped person. Wasted hours on this and it never crossed my mind to remote desktop to console.

Thanks

By: Brian

Brian — Wed, 09 Dec 2009 22:20:10 +0000

Thank you,

made me feel stupid but at the same time saved my butt.

By: Muhammad Khan

Muhammad Khan — Fri, 23 Oct 2009 15:45:09 +0000

Great post. Thanks a bunch.

By: NM

NM — Tue, 01 Sep 2009 17:35:20 +0000

That is absolutely friggin absurd. I had an enterprise support ticket open with Dell trying to figure out why the dell package drivers weren’t working on the intel 10gb nics. And no mention of this? They couldn’t leave a tab saying “Not available – open from local console” ?? Bloody amazing.

Thanks for the post – appreciated.

By: Michael

Michael — Mon, 31 Aug 2009 10:16:34 +0000

Thanks a load guys… i reinstalled the intel software about 5 times and it was driving me crazy!

(who came up with that “feature”???)

By: Vincent

Vincent — Fri, 03 Apr 2009 14:46:18 +0000

Thank you!! I just spent a considerable part of my morning trying to figure out what was going on and why the usual teaming software was not there!!! I will pass this along.

By: MetroCS

MetroCS — Sun, 22 Feb 2009 20:13:25 +0000

After working on this for a while because it’s not possible to have physical access for all my systems.
This issue is ANS uses COM+/DCOM and it’s default security rights only allows access from a “interactive user”

I found the following solution on the Intel Website:

http://www.intel.com/support/network/sb/cs-020166.htm

Change the default user account from “interactive user” to a user with administrative rights.

For Windows* 2000:

On the target system, click the Start menu and click Run.
Type “dcomcnfg” in the text field, click OK. The DCOM configuration properties window will open.
In the Applications tab, highlight NCS2Prov and click Properties.
In the NCS2Prov Properties window, click the Identify tab. Change the user account to “the launching user”
Click OK to exit the NCS2Prov Properties window. Click OK to exit DCOM configuration.

For Windows* XP and Windows* 2003 Server:

On the target system, click the Start menu and click Run.
Type dcomcnfg in the text field and click OK. The Component Services Console Root window will open.
In the left pane, double-click Component Services, Computers, My Computer, and DCOM Config.
In either pane, right-click NCS2Prov and select Properties. The DCOM configuration properties window will open.
In the NCS2Prov Properties window, click the Identify tab. Change the user account to “the launching user.”
Click OK to exit the NCS2Prov Properties window. Close the Component Services window.

By: Jason

Jason — Sat, 21 Feb 2009 16:04:28 +0000

There is a fix that will allow you to see the options through RDP. Jus tfollow this below for your OS and you no longer need a console.

Solution:
Change the default user account from “interactive user” to a user with administrative rights.

For Windows* 2000:
On the target system, click the Start menu and click Run.
Type “dcomcnfg” in the text field, click OK. The DCOM configuration properties window will open.
In the Applications tab, highlight NCS2Prov and click Properties.
In the NCS2Prov Properties window, click the Identify tab. Change the user account to “the launching user”
Click OK to exit the NCS2Prov Properties window. Click OK to exit DCOM configuration.
For Windows* XP and Windows* 2003 Server: