V
Vanessa
The environment. W2K DC and W2K Terminal Servers with NT
4.0 resource domains. We're going to put LS in our NT
4.0 resource domains so that our W2K TS will find the
LS. (Our W2K TS's must reside in the resource domains
because of SMS.)
Will someone point me in the right direction to find
documentation from Microsoft that says:
1. amount of time a windows 2000 terminal server will
accept connections before it must find a licensing server
or it starts refusing connections. (90 days - We've
found lots of documentation on this.)
2. This is the importatn question. You have a LS in
your NT 4.0 domain with a reg hack that points the Win2K
TS to the LS. What happens if the LS goes down - after
the 90 server grace period? How much time do you have to
get the LS back online before your users start to have
problems?
4.0 resource domains. We're going to put LS in our NT
4.0 resource domains so that our W2K TS will find the
LS. (Our W2K TS's must reside in the resource domains
because of SMS.)
Will someone point me in the right direction to find
documentation from Microsoft that says:
1. amount of time a windows 2000 terminal server will
accept connections before it must find a licensing server
or it starts refusing connections. (90 days - We've
found lots of documentation on this.)
2. This is the importatn question. You have a LS in
your NT 4.0 domain with a reg hack that points the Win2K
TS to the LS. What happens if the LS goes down - after
the 90 server grace period? How much time do you have to
get the LS back online before your users start to have
problems?