renaming workstations
mark
SBS windows 2003 network without causing any problems?
I'd like to bring up to date the names when viewed from the server which
have accumulated over the months and years and don't easily identify the
actual workstation when researching event problems.
If so, will it require server re-boot?
mark
--- news://freenews.netfront.net/ - complaints: ne...@netfront.net ---
Bob Lin (MS-MVP)
It is better to remove them from the domain and re-join them to the domain.
--
Bob Lin, Microsoft-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"mark" <no-on...@noads.com> wrote in message
news:hhcll4$bq2$1...@adenine.netfront.net...
Meinolf Weber [MVP-DS]
You can rename the domain machines normally without any problems. If DNS
is configured correct they will register themself with the new name. No server
reboot is required. Don't know what you like to achive with the dates, but
are you aware of the AD UC computer account properties that also contains
the date when the object was created in AD the first time and the last date
when something was modified on it?
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
Meinolf Weber [MVP-DS]
You don't have to take care about the date. I thought you would like to no
that date and add it to the name.
For the computer name keep in mind that not more then 15 characters are used,
as this is the limit of the NetBios name.
http://support.microsoft.com/kb/909264
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
> X-No-Archive: yes
>
> Meinolf Weber [MVP-DS] wrote:
>
>> Hello Mark,
>> You can rename the domain machines normally without any problems. If
>> DNS is configured correct they will register themself with the new
>> name.
>> No server reboot is required.
> Ah, thanks.
>
>> Don't know what you like to achive with
>> the dates, but are you aware of the AD UC computer account
>> properties that also contains the date when the object was created in
>> AD the first time and the last date when something was modified on
>> it?
> No. I had no idea. Is it something I need to be aware of?
> I'm not bothered about knowing when each workstation was first created
> on
> the network (if I've understood your comments correctly..) just want
> to
> re-name them all with something more comprehensively understandable.
> Not
> that it's an issue but there are only about 24 workstations on the
> network...
> best
Phillip Windell
know the role or position of the machine by the name.
I use the Serial Number (service tag) as the name. I then use the
Decsription field in the Active Directory Users and Computers to describe
the machine where I can be more thorough in decribing it than the machine
name can be. Plus if I need support on the machines and Dell asks for the
Service Tag I already know what it is without have to run to the machine and
write it down.
Another thing abotu using hte Serial Number is that it will always be unique
and it will never have to be changed.
--
Phillip Windell
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
Frankster
> unique and it will never have to be changed.
Unless you have machines from more than one manufacturer and/or more than
one model number of a machine.
-Frank
Falcon ITS
Check that the WS's are not running applications that rely on the NetBios
name. SQL Express based apps may stop running once you change the name and
also printers and drive mappings mapped to the name may have to be remapped.
--
Miguel Fra / Falcon ITS
http://www.falconits.com
"Frankster" wrote:
> .
>
Phillip Windell
I haven't run into problems yet. But I have had name conflicts by "making
up" names myself by forgettinging that I already named one that way,...or
come into an environment where someone else named them before I came along
and wasn't fully aware of all the names in use.
--
Phillip Windell
The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------
"Frankster" <fr...@SPAM2TRASH.com> wrote in message
news:t6ydncG7LsFhdabW...@giganews.com...
Lanwench [MVP - Exchange]
wrote:
>X-No-Archive: yes
>
>
>> "mark" <no-on...@noads.com> wrote in message
>> news:hhcll4$bq2$1...@adenine.netfront.net...
>>> Can I just rename any/all workststations (xp pro, some sp2,some sp3)
>>> on an SBS windows 2003 network without causing any problems?
>>> I'd like to bring up to date the names when viewed from the server
>>> which have accumulated over the months and years and don't easily
>>> identify the actual workstation when researching event problems.
>>> If so, will it require server re-boot?
>
>
>Bob Lin (MS-MVP) wrote:
>> It is better to remove them from the domain and re-join them to the
>> domain.
>
>Ah... thanks for that.
>So, to be sure, just work through the workstations by deleting them from the
>server... then rename the workstation individually before re-starting each
>one ( I think name change requires a re-start?) onto the network..
>Another poster has suggested that the AD UC account properties carry the
>object (workstation?) first created information but I'm not sure if that
>might cause issues... I'm not bothered about when the workstation was first
>created onto the network... I just want to be able to see the workstation
>name and *know* which workstation I am looking at easily (by a better
>naming scheme, that's all)..
>Thanks again for the helpful advice
>
>
>mark
Don't disjoin the domain. Log into a workstation as a domain admin. Go
to the network \advanced bit, and change the workstation name, provide
credentials if prompted, and reboot. Simple.
I like to add the user's name to the description field in ADUC (not
on the local workstation) so I know who uses what.
Phillip Windell
<lanw...@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:ums4k5pi3n1rr40kj...@4ax.com...
> Don't disjoin the domain. Log into a workstation as a domain admin. Go
> to the network \advanced bit, and change the workstation name, provide
> credentials if prompted, and reboot. Simple.
>
> I like to add the user's name to the description field in ADUC (not
> on the local workstation) so I know who uses what.
We think alike enough to scare me sometimes :-)
Yea, I too use the Desc field in ADUC to actually describe the machine
however I need to. I usually name the machine based on serial number or
Service Tag (Dells) so I don't have to hunt down the number if I ever call
Support,...and there is very little chance of a duplicate name
problem,...and I don't have to "dream up" a machine name and hope I haven't
already used it once. And lastly it makes it more difficult for an unwanted
guest to know what they are looking at over the network.