How to change secure identifier request interval?

  • Thread starter Thread starter Dieter Fiebelkorn
  • Start date Start date
D

Dieter Fiebelkorn

My question is quite simply, how do I change the interval at which the
Windows 2000 and XP clients (Home as well as Pro), request a new secure
identifier from the server?

The background is that I have computers (running on Virtual PC and
vmware) which repeatly are UNDO this drives after test installtions
and experiences. The clients that changed it's SID (requested) are
leaving the domain, after UNDO it's drives and reboot.

This of cause also means that the new SID that the clients receive
from the server every so often is also deleted, so they cannot log on
to the network!

In Windows NT, I used to change the interval at which the clients
requested the new SID from the standard 90 days to 1,000,000 days,
thus solving the difficulties (mainly because no computer last for
such a long time ­ at the same time as this is the max. period of time
which can be entered in the interval)!

Thank you all for your answers in advance.
 
To put it quite simply, your question is way off topic in
microsoft.public.word.setup.networking.

Better luck in the Windows newsgroups to which you posted.

But a better place to post might have been microsoft.public.virtualpc

--
Please post any further questions or followup to the newsgroups for the
benefit of others who may be interested. Unsolicited questions forwarded
directly to me will only be answered on a paid consulting basis.

Hope this helps
Doug Robbins - Word MVP
 
Am 17.03.2004 9:00 Uhr schrieb "Doug Robbins - Word MVP - DELETE UPPERCASE
To put it quite simply, your question is way off topic in
microsoft.public.word.setup.networking.
SORRY!

Better luck in the Windows newsgroups to which you posted.
Click to expand...

I hope it! May be a special, not often used special ...
But a better place to post might have been microsoft.public.virtualpc
Click to expand...

Thanxs, have try it, but it is not a special virtualpc question, the same
problem is happened if a computer is restored with a version before last SID
request/change ...
 
Back
Top