SP3 and unattended network settings

[jeffd]

I'm finally moving my unattended/images to SP3 ... experiencing some greif re: the network settings. For some reason, the Microsoft Client and File/Printer Sharing are being installed no matter what the configuration of the answer file. This was not the case with previous builds - these components could be excluded using the following:

[Networking]

InstallDefaultComponents=No

[NetAdapters]

Adapter1=params.Adapter1

[params.Adapter1]

INFID=*

[NetClients]

[NetServices]

[NetProtocols]

MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]

DNS=Yes

UseDomainNameDevolution=No

EnableLMHosts=No

AdapterSections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]

SpecificTo=Adapter1

DHCP=Yes

WINS=No

NetBIOSOptions=2

Note that we're largely a Novell shop so there's no need for the Microsoft Client or File/Printer Sharing. The preference is that they not be installed. Is this a change with SP3? I've looked through ref.chm that's included with SP3 and didn't note any significant changes to the answer file configuration options.

Thoughts?

EDIT:

I generated a new answer file using setupmgr.exe included with SP3. I specifically removed the Microsoft Client and File/Printer sharing in the Wizard then used the resulting answer file with my unattended - same result. Both the Microsoft Client and File/Printer sharing are installed. So, either something (undocumented) is missing from the answer file or something has changed re: SP3 setup that prevents exclusion of these two components. Note that the new answer includes:

[Networking]

InstallDefaultComponents=No

[NetAdapters]

Adapter1=params.Adapter1

[params.Adapter1]

INFID=*

[NetProtocols]

MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]

DNS=Yes

UseDomainNameDevolution=No

EnableLMHosts=No

AdapterSections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]

SpecificTo=Adapter1

DHCP=Yes

WINS=No

NetBIOSOptions=2

Edited April 15, 2010 by jeffd

[jeffd]

Worked around the problem ... tossed a script in Cmdlines.txt that uses snetcfg to uninstall the offending components. Shouldn't have to IMO, but...

Edited April 16, 2010 by jeffd