Rename machine (or join/disjoin from domain) then reboot. Why?

[Guest Jim in Arizona]

One of my co-workers asked me the other day what it is excactly that forces

us to reboot a windows box after we change its name or join/disjoin it from

a domain. The question was "What services are affected so we can just

restart those instead of doing a reboot?".

 

Does anyone know an answer to this?

 

TIA,

Jim

[Guest Sharon Fink]

Re: Rename machine (or join/disjoin from domain) then reboot. Why?

 

In article <uslWVJ#cIHA.4144@TK2MSFTNGP05.phx.gbl>,

"Jim in Arizona" <tiltowait@hotmail.com> wrote:

> One of my co-workers asked me the other day what it is excactly that forces

> us to reboot a windows box after we change its name or join/disjoin it from

> a domain. The question was "What services are affected so we can just

> restart those instead of doing a reboot?".

>

> Does anyone know an answer to this?

>

> TIA,

> Jim

 

Many security choices and various policies load at startup only and

apply to that session. These are directly related to machine ID, user

ID, network relation and are applied to all resources (software, data,

hardware, network shares, etc). After changes of a a certain magnitude,

a restart is required to dump the old info and load the new. Why? No

idea if it's a limitation of XP or its security tools -OR- if it's due

to the security model that Microsoft chose to adopt for XP. I do know

that it takes more than stopping/starting a few services to effectively

propagate certain changes.

 

A very simplified and incomplete response but hope it's helpful

nonetheless,

--

Sharon F

Desktop User Experience - MVP

[Guest Sharon Fink]

Re: Rename machine (or join/disjoin from domain) then reboot. Why?

 

In article <sharonfDELETE-DCF7BA.10454421022008@msnews.microsoft.com>,

Sharon Fink <sharonfDELETE@THISmvps.org> wrote:

> In article <uslWVJ#cIHA.4144@TK2MSFTNGP05.phx.gbl>,

> "Jim in Arizona" <tiltowait@hotmail.com> wrote:

>

> > One of my co-workers asked me the other day what it is excactly that forces

> > us to reboot a windows box after we change its name or join/disjoin it from

> > a domain. The question was "What services are affected so we can just

> > restart those instead of doing a reboot?".

> >

> > Does anyone know an answer to this?

> >

> > TIA,

> > Jim

>

> Many security choices and various policies load at startup only and

> apply to that session. These are directly related to machine ID, user

> ID, network relation and are applied to all resources (software, data,

> hardware, network shares, etc). After changes of a a certain magnitude,

> a restart is required to dump the old info and load the new. Why? No

> idea if it's a limitation of XP or its security tools -OR- if it's due

> to the security model that Microsoft chose to adopt for XP. I do know

> that it takes more than stopping/starting a few services to effectively

> propagate certain changes.

>

> A very simplified and incomplete response but hope it's helpful

> nonetheless,

 

PS: Toss authentication and credentials in to the mix.

--

Sharon F

Desktop User Experience - MVP