That's it! 

--
O'Reilly Active Directory Third Edition -
http://www.joeware.net/win/ad3e.htm 
 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Free, Bob
Sent: Wednesday, October 11, 2006 7:13 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Exchange in environment - reboot necessary
after a DC has been made a GC

>I can't for the life of me recall the name at the moment.  

NSPItool.exe ? 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: Tuesday, October 10, 2006 3:45 PM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Exchange in environment - reboot necessary
after a DC has been made a GC

The only other way I know to test if NSPI is working is to actually send
NSPI calls to the GC. There is a little unsupported command line tool
out there than can do that but I can't for the life of me recall the
name at the moment.  


--
O'Reilly Active Directory Third Edition -
http://www.joeware.net/win/ad3e.htm 
 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Wednesday, September 27, 2006 7:48 AM
To: ActiveDir@mail.activedir.org
Subject: RE: [ActiveDir] OT: Exchange in environment - reboot necessary
after a DC has been made a GC

I was misinformed, the rev of the DC is W2K, not W2K3 SP1. So that
clears up why Exchange is complaining about the GC needing a reboot
since it wasn't rebooted after it had been made a GC.

Interesting tool, RPC Dump, unfortunately I didnt get it to work just
yet.
It gave me an error: The NTVDM CPU has encountered an illegal
instruction, when I choose Ignore the Command.com or Cmd.exe starts
using 100% cpu.

Out of curiosity; is there another way to check if the "MS NT Directory
NSP Interface"
is listed?



-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of joe
Sent: zaterdag 23 september 2006 2:52
To: ActiveDir@mail.activedir.org
Subject: RE: RE: [ActiveDir] OT: Exchange in environment - reboot 
necessary
after a DC has been made a GC

What is the rev of the DC? Using RPC Dump do you see "MS NT Directory 
NSP
Interface" interfaces listed?

  joe


--
O'Reilly Active Directory Third Edition -
http://www.joeware.net/win/ad3e.htm 
 

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of victor-
[EMAIL PROTECTED]
Sent: Friday, September 22, 2006 11:07 AM
To: ActiveDir@mail.activedir.org
Subject: Re: RE: [ActiveDir] OT: Exchange in environment - reboot 
necessary
after a DC has been made a GC

Yeah, I thought so, thanks for the info.

The damn thing is that Exchange still throws event 9176:

Event ID 9176 from MSExchangeSA occurred 1 times (NSPI Proxy can contact
Global Catalog "servername" but it does not support the NSPI service. 
After
a Domain Controller is promoted to a Global Catalog, the  Global Catalog
must be rebooted to support MAPI Clients.  
Reboot "servernamerio" as  soon as possible.





----- Oorspronkelijk bericht -----
Van: joe <[EMAIL PROTECTED]>
Datum: vrijdag, september 22, 2006 4:38 pm
Onderwerp: RE: [ActiveDir] OT: Exchange in environment - reboot 
necessary
after a DC has been made a GC

> This is no longer necessary with current revs of AD. It was necessary 
> previously to get the NSPI functionality to fire up. Now it does that 
> automagically.
> 
> 
> --
> O'Reilly Active Directory Third Edition - 
> http://www.joeware.net/win/ad3e.htm
> 
> 
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of victor-
> [EMAIL PROTECTED]: Friday, September 22, 2006 10:31 AM
> To: ActiveDir@mail.activedir.org
> Subject: [ActiveDir] OT: Exchange in environment - reboot necessary 
> after a DC has been made a GC
> 
> A question came up wether or not a reboot is really necessary after a 
> DC has been made GC and Exchange would need to use this GC.
> 
> I have worked in a pretty large environment (at least to my standards 
> :- )). Where DC's did not get rebooted afther having been made GC's.
> The
> AD admins simply waited until event 1119 appeared.
> 
> I have read the following article which indicates a reboot is 
> necessary if you have Exchange in the environment.
> 
> http://support.microsoft.com/kb/304403/
> 
> But is this really still necessary with Exchange 2003 SP2 and Windows
> 2003 SP1?
> 
> Cheers,
> 
> 
> Victor
> List info   : http://www.activedir.org/List.aspx
> List FAQ    : http://www.activedir.org/ListFAQ.aspx
> List archive: http://www.activedir.org/ml/threads.aspx
> 
> List info   : http://www.activedir.org/List.aspx
> List FAQ    : http://www.activedir.org/ListFAQ.aspx
> List archive: http://www.activedir.org/ml/threads.aspx
> 
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx


List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx

List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx

Reply via email to