Hostname change problem

[Guest Gaurav]

Dear Friends...

 

We have DC at our corporate office & each ADC at our site

location.there are 22 location & for each location OU is created in

AD.

We have single domain.There are nearly 3000 Desktops & servers in

whole domain.all desktops are member of OU respective of their site in

AD.

 

 

One Wsus server is installed for patch management & for each

site,respective container is created & for each location wsus policy

template is applied in AD,

 

Problem:-

 

 

When ever our desktop engineer on site location, format any desktop so

they also change the computer name [Host name].As they never think to

give the same old Hostname after installation of desktop.

 

& when they make server as a member of Domain the , Domain server make

the Desktop

As member of default container “computer”

 

But according to site name this should be the member of its

respective OU.

 

Similarly hostname is also not updated in WSUS

 

 

What should we do to sort out the issue.

 

Can we create any script or bat file & run file after the installation

of OS on desktop.

 

 

Waiting for response ..

 

Thanks in Advance…

 

Gaurav

[Guest Meinolf Weber]

Re: Hostname change problem

 

Hello Gaurav,

 

If the site admins add the new machines by hand to the domain, they will

be added to the computers container, that's default setting, so that new

machines will not directly get policies except the domain policy. When you

are using sysprep. for example with an image you can specify in the sysprep.inf

file, where the computer should be moved to.

WSUS will not compere the new name with the old one. The WSUS client gets

the server with the policy and the client just said the server "here am i",

do you have something for me. So the server doesn't connect to the client.

 

For scripts check out this ones:

scroll down to the end of the page:

http://www.experts-exchange.com/Programming/Languages/Visual_Basic/Q_21605648.html

 

http://www.wisesoft.co.uk/scripts/vbscript_move_the_current_computer_to_a_different_organizational_unit.aspx

 

Best regards

 

Meinolf Weber

Disclaimer: This posting is provided "AS IS" with no warranties, and confers

no rights.

** Please do NOT email, only reply to Newsgroups

** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> Dear Friends...

>

> We have DC at our corporate office & each ADC at our site

> location.there are 22 location & for each location OU is created in

> AD.

> We have single domain.There are nearly 3000 Desktops & servers in

> whole domain.all desktops are member of OU respective of their site in

> AD.

> One Wsus server is installed for patch management & for each

> site,respective container is created & for each location wsus policy

> template is applied in AD,

>

> Problem:-

>

> When ever our desktop engineer on site location, format any desktop so

> they also change the computer name [Host name].As they never think to

> give the same old Hostname after installation of desktop.

>

> & when they make server as a member of Domain the , Domain server make

> the Desktop

> As member of default container "computer"

> But according to site name this should be the member of its

> respective OU.

>

> Similarly hostname is also not updated in WSUS

>

> What should we do to sort out the issue.

>

> Can we create any script or bat file & run file after the installation

> of OS on desktop.

>

> Waiting for response ..

>

> Thanks in Advance.

>

> Gaurav

>

[Guest Lanwench [MVP - Exchange]]

Re: Hostname change problem

 

Gaurav <mathur.gm@gmail.com> wrote:

> Dear Friends...

>

> We have DC at our corporate office & each ADC at our site

> location.there are 22 location & for each location OU is created in

> AD.

> We have single domain.There are nearly 3000 Desktops & servers in

> whole domain.all desktops are member of OU respective of their site in

> AD.

>

<snipped for length>

 

Hi - in addition to Meinolf's reply, I wanted to add....if your

administrators are doing this wrong, they need to be re-trained or better

trained, so they stop. Your central IT should document the appropriate steps

in clear/simple language and ensure they all have it. There are seldom good

technological solutions to behavioral problems.