Jump to content

Unable to set workgroup name


Recommended Posts

Hi all, I have encountered a little problem while trying an unattended installation. The workgroup name doesn't seem to change to the one I set in the winnt.sif. I really have no idea where did I do wrong. Can someone please enlighten me.

[Data]    AutoPartition=0

    MsDosInitiated="0"

    UnattendedInstall="Yes"

    AutomaticUpdates=1

[unattended]

    UnattendMode=FullUnattended

    OemSkipEula=Yes

    OemPreinstall=Yes

    UnattendSwitch="Yes"

    TargetPath=\WINDOWS

    WaitForReboot="No"

    DriverSigningPolicy=Ignore

[GuiUnattended]

    AdminPassword=*

    EncryptedAdminPassword=NO

    OEMSkipRegional=1

    TimeZone=215

    OemSkipWelcome=1

[userData]

    ProductKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

    FullName="myname"

    OrgName="myname"

    ComputerName=MY-PC

[Display]

    BitsPerPel=32

    Xresolution=1024

    YResolution=768

    Vrefresh=75

[RegionalSettings]

    LanguageGroup=7,10,9,1

[Networking]

    InstallDefaultComponents=Yes

[identification]

    JoinWorkgroup=HOME

[Components]

    AccessOpt=Off

    Clipbook=Off

    Dialer=Off

    Freecell=Off

    Hearts=Off

    Hypertrm=Off

    Media_clips=Off

    Minesweeper=Off

    Mousepoint=Off

    Msmsgs=Off

    Msnexplr=Off

    Mswordpad=Off

    Pinball=Off

    Solitaire=Off

    Spider=Off

    TerminalServer=Off

    Zonegames=Off

[shell]

    DefaultThemesOff=Yes

[WindowsFirewall]

    Profiles = WindowsFirewall.TurnOffFirewall

[WindowsFirewall.TurnOffFirewall]

    Mode = 0

Link to comment
Share on other sites


Hmmm, thats the default workgroup when one isn't specified.

*looks over winnt.sif again*

Yeah, thats right. The only difference that shows up on mine is that I have

[identification]    JoinWorkgroup=mshome

And it's in lowercase and not in capitals. I suppose you could also try putting the name in quotes.

The only time that I've seen something like that was when I specified all settings in the winnt.sif file and was installing the OS off of our RIS server. RIS uses the ristndrd.sif file in the i386\template dir as the answer file and not the winnt.sif file.

Paul

Link to comment
Share on other sites

Ok, I went back and took a good look at my winnt.sif file. Try this, move the Identification portion above the networking stuff so that it looks like this:

[identification]    JoinWorkgroup=mshome

[Networking]

    InstallDefaultComponents=Yes

Maybe if it hits the Networking part for default stuff first, it doesn't mess with the identification part at all because the default workgroup is already specified.

Paul

Link to comment
Share on other sites

Ok, I went back and took a good look at my winnt.sif file. Try this, move the Identification portion above the networking stuff so that it looks like this:

[identification]

    JoinWorkgroup=mshome

[Networking]

    InstallDefaultComponents=Yes

Maybe if it hits the Networking part for default stuff first, it doesn't mess with the identification part at all because the default workgroup is already specified.

Paul

I had tried all that you had mention, but none of them is successful. I have run out of ideas now.

Link to comment
Share on other sites

I've seen this happen when identification was "outside" networking, as pthomas suggested, which is not your original case.

leaving off the installdefaultcomponents, and mannualy specifying protocols, bindings and services. works for me, hope it helps

[Networking]

[Identification]
JoinWorkgroup="Home"

[NetAdapters]
Adapter1=params.Adapter1

[Homenet]
InternetConnectionFirewall = Adapter1
ShowTrayIcon = Yes

[params.Adapter1]
INFID=*

[NetClients]
MS_MSClient=params.MS_MSClient

[NetBindings]
Disable = "MS_PSched , Adapter1" ;Disable Qos

[NetServices]
;MS_SERVER=params.MS_SERVER

[NetProtocols]
MS_TCPIP=params.MS_TCPIP


params.MS_TCPIP]
UseDomainNameDevolution=No
EnableLMHosts=No
AdapterSections=params.MS_TCPIP.Adapter1
DeadGWDetectDefault = No
;DNSDomain = "Your domain"
;DNSSuffixSearchOrder = "Your domain"
DontAddDefaultGatewayDefault = No
EnableICMPRedirect = No
EnableSecurity = Yes

[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP=No
DisableDynamicUpdate = yes
EnableAdapterDomainNameRegistration = No
DefaultGateway = 192.168.200.2
DNSServerSearchOrder = 192.168.200.2
IPAddress = 192.168.200.4
NetBIOSOptions = 2
SubnetMask = 255.255.0.0
WINS = No
;WINSServerList = 192.168.200.2

Link to comment
Share on other sites

Couldn't it be because your network card isn't recognised by windows XP during the install

I've had the problem with a graphic card, and the resolution wasn't what I asked because it was for Windows to do it without the right driver...

Link to comment
Share on other sites

Use setupmgr.exe to edit winnt.sif:

On the network screen change from "Default settings" to "Custom Settins", that's all.

If you thing is your network card not being instaled add

[Unattended]
OemPnPDriversPath="Instalar\Drivers\nForce510;Instalar\Drivers\nForce510\PreNRM;Instalar\Drivers\VIAHyperion453"

And for this example your driver go to $oem$\$1\Instalar\Drivers

Link to comment
Share on other sites

Couldn't it be because your network card isn't recognised by windows XP during the install

That also sounds like another idea. Are you sure that the network card is installed during the install? Or does it get picked up like the first time you logon?

Paul

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...