Change the "full computer name" for an XP system (SP2) on ..

[Guest]

Archived from groups: microsoft.public.windowsxp.customize (More info?)

We do not have a Windows domain on our network - the PCs belong to a
workgroup. (Network administration is handled by our Novell servers.) If two
PCs have the same computer name, we get conflict messages. When I set up new
systems with Windows 2000, I can install all software with the random name
assigned by Windows setup, then change the computer name to match the old
system's name when I swap in the new system. Under Windows XP, trying to
change the "full computer name" prevented the system from booting. Mostly
leaving the name assigned by setup is acceptable. But in a few cases, we need
to maintain the same computer name because it is used for printing by our IBM
AS400 system. Is there a procedure for changing the name of a system running
XP Service Pack 2 (hardware configuration will vary) with no Windows domain
controller?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.customize (More info?)

Control panel->system applet. Go to the Computer Name tab. Hit change. Alter
the name in the top box and leave the 'member of' set as workgroup. Hit OK,
then apply and OK and let the system reboot.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


"SharonW" <SharonW@discussions.microsoft.com> wrote in message
news:167FD98B-AA9C-421B-9782-D29BBE91AB39@microsoft.com...
> We do not have a Windows domain on our network - the PCs belong to a
> workgroup. (Network administration is handled by our Novell servers.) If
> two
> PCs have the same computer name, we get conflict messages. When I set up
> new
> systems with Windows 2000, I can install all software with the random name
> assigned by Windows setup, then change the computer name to match the old
> system's name when I swap in the new system. Under Windows XP, trying to
> change the "full computer name" prevented the system from booting. Mostly
> leaving the name assigned by setup is acceptable. But in a few cases, we
> need
> to maintain the same computer name because it is used for printing by our
> IBM
> AS400 system. Is there a procedure for changing the name of a system
> running
> XP Service Pack 2 (hardware configuration will vary) with no Windows
> domain
> controller?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.customize (More info?)

Are you saying the "right clicking" on My Computer (Desktop), selecting
"properties", computer name tab, "change" button and replacing say
"IBM-78-RWCD" with "AS400 PRINT SVR 1" cause XP to become "unbootable" -
never heard of such, we do this all the time and we maintain close to 5000
network computers (servers, laptops, desktops, workstations) most running XP
SP1, but some Win2k SP3, across many trusted domains for our company
throughout the US, Alaska and Hawaii!

--
Star Fleet Admiral Q @ your service!
"Google is your Friend!"
www.google.com

***********************************************

"SharonW" <SharonW@discussions.microsoft.com> wrote in message
news:167FD98B-AA9C-421B-9782-D29BBE91AB39@microsoft.com...
> We do not have a Windows domain on our network - the PCs belong to a
> workgroup. (Network administration is handled by our Novell servers.) If
two
> PCs have the same computer name, we get conflict messages. When I set up
new
> systems with Windows 2000, I can install all software with the random name
> assigned by Windows setup, then change the computer name to match the old
> system's name when I swap in the new system. Under Windows XP, trying to
> change the "full computer name" prevented the system from booting. Mostly
> leaving the name assigned by setup is acceptable. But in a few cases, we
need
> to maintain the same computer name because it is used for printing by our
IBM
> AS400 system. Is there a procedure for changing the name of a system
running
> XP Service Pack 2 (hardware configuration will vary) with no Windows
domain
> controller?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.customize (More info?)

Yep - that's exactly what I'm saying. I didn't write down the error (duh),
but it was something along the lines of being unable to find a domain
controller (which I didn't expect to need on a workgroup...). I was able to
use "last known good" to salvage the system, but of course that put me back
to the original randomly generated name.

Please keep in mind that I am dealing with a network that DOES NOT CONTAIN
Microsoft domains.

"Admiral Q" wrote:

> Are you saying the "right clicking" on My Computer (Desktop), selecting
> "properties", computer name tab, "change" button and replacing say
> "IBM-78-RWCD" with "AS400 PRINT SVR 1" cause XP to become "unbootable" -
> never heard of such, we do this all the time and we maintain close to 5000
> network computers (servers, laptops, desktops, workstations) most running XP
> SP1, but some Win2k SP3, across many trusted domains for our company
> throughout the US, Alaska and Hawaii!
>
> --
> Star Fleet Admiral Q @ your service!
> "Google is your Friend!"
> www.google.com
>
> ***********************************************
>
> "SharonW" <SharonW@discussions.microsoft.com> wrote in message
> news:167FD98B-AA9C-421B-9782-D29BBE91AB39@microsoft.com...
> > We do not have a Windows domain on our network - the PCs belong to a
> > workgroup. (Network administration is handled by our Novell servers.) If
> two
> > PCs have the same computer name, we get conflict messages. When I set up
> new
> > systems with Windows 2000, I can install all software with the random name
> > assigned by Windows setup, then change the computer name to match the old
> > system's name when I swap in the new system. Under Windows XP, trying to
> > change the "full computer name" prevented the system from booting. Mostly
> > leaving the name assigned by setup is acceptable. But in a few cases, we
> need
> > to maintain the same computer name because it is used for printing by our
> IBM
> > AS400 system. Is there a procedure for changing the name of a system
> running
> > XP Service Pack 2 (hardware configuration will vary) with no Windows
> domain
> > controller?
>
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.customize (More info?)

Sorry, Walter - that's what I did, and on reboot got an error message along
the lines of being unable to find a domain controller (on a workgroup?!?) -
had to use Last known good to make the system usable again, but that returned
me to the original random name.

"Walter Clayton" wrote:

> Control panel->system applet. Go to the Computer Name tab. Hit change. Alter
> the name in the top box and leave the 'member of' set as workgroup. Hit OK,
> then apply and OK and let the system reboot.
>
> --
> Walter Clayton
> Any technology distinguishable from magic is insufficiently advanced.
>
>
> "SharonW" <SharonW@discussions.microsoft.com> wrote in message
> news:167FD98B-AA9C-421B-9782-D29BBE91AB39@microsoft.com...
> > We do not have a Windows domain on our network - the PCs belong to a
> > workgroup. (Network administration is handled by our Novell servers.) If
> > two
> > PCs have the same computer name, we get conflict messages. When I set up
> > new
> > systems with Windows 2000, I can install all software with the random name
> > assigned by Windows setup, then change the computer name to match the old
> > system's name when I swap in the new system. Under Windows XP, trying to
> > change the "full computer name" prevented the system from booting. Mostly
> > leaving the name assigned by setup is acceptable. But in a few cases, we
> > need
> > to maintain the same computer name because it is used for printing by our
> > IBM
> > AS400 system. Is there a procedure for changing the name of a system
> > running
> > XP Service Pack 2 (hardware configuration will vary) with no Windows
> > domain
> > controller?
>
>

 

[Guest]

Archived from groups: microsoft.public.windowsxp.customize (More info?)

Hmmm. I've changed computer names on VMs running SP2 without triggering a
domain add In fact, Just for grins I just renamed one to validate.

I can't quite figure out what you're doing that's triggering the domain add.
As long as you're doing nothing more than the steps I gave you, you'll stay
in workgroup mode.

What you may want to try is running the networking wizard first if you
haven't already.

--
Walter Clayton
Any technology distinguishable from magic is insufficiently advanced.


"SharonW" <SharonW@discussions.microsoft.com> wrote in message
news:60784534-2C49-498C-B6F1-3DE543E82D1E@microsoft.com...
> Sorry, Walter - that's what I did, and on reboot got an error message
> along
> the lines of being unable to find a domain controller (on a
> workgroup?!?) -
> had to use Last known good to make the system usable again, but that
> returned
> me to the original random name.
>
> "Walter Clayton" wrote:
>
>> Control panel->system applet. Go to the Computer Name tab. Hit change.
>> Alter
>> the name in the top box and leave the 'member of' set as workgroup. Hit
>> OK,
>> then apply and OK and let the system reboot.
>>
>> --
>> Walter Clayton
>> Any technology distinguishable from magic is insufficiently advanced.
>>
>>
>> "SharonW" <SharonW@discussions.microsoft.com> wrote in message
>> news:167FD98B-AA9C-421B-9782-D29BBE91AB39@microsoft.com...
>> > We do not have a Windows domain on our network - the PCs belong to a
>> > workgroup. (Network administration is handled by our Novell servers.)
>> > If
>> > two
>> > PCs have the same computer name, we get conflict messages. When I set
>> > up
>> > new
>> > systems with Windows 2000, I can install all software with the random
>> > name
>> > assigned by Windows setup, then change the computer name to match the
>> > old
>> > system's name when I swap in the new system. Under Windows XP, trying
>> > to
>> > change the "full computer name" prevented the system from booting.
>> > Mostly
>> > leaving the name assigned by setup is acceptable. But in a few cases,
>> > we
>> > need
>> > to maintain the same computer name because it is used for printing by
>> > our
>> > IBM
>> > AS400 system. Is there a procedure for changing the name of a system
>> > running
>> > XP Service Pack 2 (hardware configuration will vary) with no Windows
>> > domain
>> > controller?
>>
>>