MSFN Forum: Workgroup name change... - MSFN Forum

Jump to content



Unattended CD/DVD Guide Homepage · MSFN Forum Rules

If you have questions about customizing Windows XP that are nLite-specific, please post them in the nLite forum, not here. If you have questions regarding the unattended installation of Windows XP, please post them in the Unattended Windows 2000/XP/2003 section.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Workgroup name change... How can I change it via script? Rate Topic: -----

#1 User is offline   Yonderboy 

  • Senior Newbie
  • Pip
  • Group: Members
  • Posts: 85
  • Joined: 23-January 04

Posted 20 March 2004 - 02:18 PM

How can I change

the name of workgroup
the machine IP adress
the DNS adress
the gateway adress
the subnet mask



on standalone machine using VBS script or Batch file?

1/2 hour of googling did not help.


#2 User is offline   diesel_98a 

  • Spurz 4 Life....
  • PipPipPipPip
  • Group: Members
  • Posts: 532
  • Joined: 26-July 03

Posted 20 March 2004 - 11:07 PM

what os?

#3 User is offline   ballsup 

  • Newbie
  • Group: Members
  • Posts: 16
  • Joined: 16-November 03

Posted 21 March 2004 - 05:09 AM

the netsh command line tool can change ip / subnet / dns / wins settings

Nigel

#4 User is offline   Yonderboy 

  • Senior Newbie
  • Pip
  • Group: Members
  • Posts: 85
  • Joined: 23-January 04

Posted 21 March 2004 - 05:37 AM

XP pro

I suppose it should be irrelevant anyway, whether pro or home. :rolleyes:

Thanks for netsh... :)


And changing workgroup?

C'mon, not a single vbs guru here?

#5 User is offline   airmr 

  • Junior
  • Pip
  • Group: Members
  • Posts: 81
  • Joined: 21-October 03

Posted 21 March 2004 - 07:19 AM

You can change all the values with Registry settings.

I did that at work with W2K it works perfectly.

I am at work again at 28th of march, i got holidays unfortunately :)
i can post the settings then.

#6 User is offline   Yonderboy 

  • Senior Newbie
  • Pip
  • Group: Members
  • Posts: 85
  • Joined: 23-January 04

Posted 21 March 2004 - 07:35 AM

I got this one too...sometimes, to resolve a problem, all you need is a good sleep :D

I downloaded a tool called NETDOM.EXE, but not the newest one, you need specifically the version 1.8 that is a part of Microsoft Windows NT4 resource kit. You can download it here This version is the last one, that supports workgroup name change.
In Microsoft, they don't care about workgroup much more these days, only AD, those little sneaks.... :) it took me one hour to find out...

I put it into c:\windows\system32 folder

and used a following syntax in commandline

netdom member \\computername /joinworkgroup newworkgroupname


THANX ballsup for netsh..it works perfectly.
As I said in other thread before, I hope somebody will find this usefull... :rolleyes:

#7 User is offline   likuidkewl 

  • [Centos~]$
  • PipPipPipPipPip
  • Group: Members
  • Posts: 960
  • Joined: 16-September 03

Posted 21 March 2004 - 08:01 AM

That is a nice find, but my question is why not do it when you istall your OS?

#8 User is offline   Yonderboy 

  • Senior Newbie
  • Pip
  • Group: Members
  • Posts: 85
  • Joined: 23-January 04

Posted 21 March 2004 - 12:44 PM

Because this one is a specialized installation that requires to be installed and partly configured in network #1, and than, it is physically moved to various another locations - network #2 to #7 as a cloning master. And since it is not possible for me to travel to these locations, for each of these locations there is a preconfigured script, that contains literally hundreds of settings and reg changes and configs, in a form of a "magic button" (it really is one button - a shortcut to a that script).
They just run the appropriate button and everything will be done for them incl. that workgroup. :)

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy