How to add Computer Description, Firewall (Enable/Disable), DNS Suffix

[srihariram]

Hi,

How to add the following in autounattend.xml?

1. Computer Description

2. Firewall (Enable/Disable)

3. DNS Suffix

4. DNS Search List

5. HTTP Proxy

Thanks...

[Tripredacus]

Firewall settings are per network profile.

http://technet.microsoft.com/en-us/library/cc766517%28WS.10%29.aspx

Here is DNSSuffixSearchOrder:

http://technet.microsoft.com/en-us/library/cc766454%28WS.10%29.aspx

This is info about HKLMProxyServer:

http://technet.microsoft.com/en-us/library/cc721933%28WS.10%29.aspx

Anything else (like Computer Description) may have to be done with a .reg file.

[srihariram]

Firewall settings are per network profile.

http://technet.microsoft.com/en-us/library/cc766517%28WS.10%29.aspx

Here is DNSSuffixSearchOrder:

http://technet.microsoft.com/en-us/library/cc766454%28WS.10%29.aspx

This is info about HKLMProxyServer:

http://technet.microsoft.com/en-us/library/cc721933%28WS.10%29.aspx

Anything else (like Computer Description) may have to be done with a .reg file.

Thank you..

I have query regarding RDP setting.

I am using Microsoft-Windows-TerminalServices-RDP-WinStationExtensions for enabling RDP

It has 2 fields - SecurityLayer and UserAuthentication

I am able to get what this two parameters mean. I need to enable RDP what should be the values of securitylayer and userauthentication.

Thanks..

[Tripredacus]

I ran into this problem with Windows Web Server 2008 Embedded. Of course it uses a different CLG, but it looks like there is an option to enable Remote Assistance, but not an option to enable RDP. You could add it during Serving with

<package action="configure">

But I checked the Windows 7 Packages list and there isn't one for RDP or Remote Assistance. Only remote admin for IIS.

[Gelob]

To enable Remote Desktop

        <component name="Microsoft-Windows-TerminalServices-LocalSessionManager" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <fDenyTSConnections>false</fDenyTSConnections>
        </component>

To allow Remote Desktop through the Windows Firewall

<component name="Networking-MPSSVC-Svc" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <FirewallGroups>
                <FirewallGroup wcm:action="add" wcm:keyValue="RDP">
                    <Active>true</Active>
                    <Group>Remote Desktop</Group>
                    <Profile>all</Profile>
                </FirewallGroup>
            </FirewallGroups>
        </component>

I don't think you can specify Computer Description in the unattended XML, it might pull that the OEM Information or something. If its anywhere its probably in Microsoft-Winodws-Shell-Setup.

[myselfidem]

Hello!

Like you, I've don't find explainations about "Computer description" for the "Autounattend.xml" file.

However I use this reg file:

Windows Registry Editor Version 5.00

; Computer description
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanServer\Parameters]
"srvcomment"="myselfidem's PC"

Cheers

Edited October 22, 2010 by myselfidem

[maxXPsoft]

Can also set that with

net config server /srvcomment:"machine comment"

[srihariram]

Hi,

Thanks for the replies.

Can someone tell me the difference between DNS Suffix and DNS Search List and how to configure them in Autounattend.xml?

Best wishes..

[Tripredacus]

I'm not sure. The DNS Suffix is a domain name that a DHCP server can send to a client. Not all networks do this, or most home networks do not by default either. This can be important only for a few reasons. Some networks will not resolve DNS requests if the DNS Suffix does not match the domain the system is on. I've only seen this happen on ISP's ISDN and DSL systems, but I imagine you could configure an enterprise domain to do this also.

I am not certain how this option is used with the XML, but likely this is also something you can do on a deployed system with the NET command? Does this mean this is the list it goes through for every request or just when it accepts the IP information it is given? Does this mean you can override DHCP information?

[srihariram]

I am trying to set static IP, but it is failing. Below is the snippet of the autounattend.xml. Please let me know if there is any error in below xml.. Thank you.

<component name="Microsoft-Windows-TCPIP" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<Interfaces>

<Interface wcm:action="add">

<UnicastIpAddresses>

<IpAddress wcm:action="add" wcm:keyValue="30">10.1.1.1/25</IpAddress>

</UnicastIpAddresses>

<Ipv4Settings>

<DhcpEnabled>false</DhcpEnabled>

</Ipv4Settings>

<Identifier>68-ef-bd-f6-72-18</Identifier>

<Routes>

<Route wcm:action="add">

<Identifier>35</Identifier>

<Prefix>0.0.0.0/0</Prefix>

<NextHopAddress>10.10.10.10</NextHopAddress>

</Route>

</Routes>

</Interface>

<Interface wcm:action="add">

<UnicastIpAddresses>

<IpAddress wcm:action="add" wcm:keyValue="31">20.2.2.2/25</IpAddress>

</UnicastIpAddresses>

<Ipv4Settings>

<DhcpEnabled>false</DhcpEnabled>

</Ipv4Settings>

<Identifier>68-ef-bd-f6-72-19</Identifier>

<Routes>

<Route wcm:action="add">

<Identifier>36</Identifier>

<Prefix>0.0.0.0/0</Prefix>

<NextHopAddress>20.20.20.20</NextHopAddress>

</Route>

</Routes>

</Interface>

</Interfaces>

</component>

<component name="Microsoft-Windows-DNS-Client" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<Interfaces>

<Interface wcm:action="add">

<DNSServerSearchOrder>

<IpAddress wcm:action="add" wcm:keyValue="40">1.1.1.1</IpAddress>

<IpAddress wcm:action="add" />

</DNSServerSearchOrder>

<Identifier>68-ef-bd-f6-72-18</Identifier>

</Interface>

<Interface wcm:action="add">

<DNSServerSearchOrder>

<IpAddress wcm:action="add" wcm:keyValue="41">2.2.2.2</IpAddress>

</DNSServerSearchOrder>

<Identifier>68-ef-bd-f6-72-19</Identifier>

</Interface>

</Interfaces>

</component>

[Tripredacus]

        <component name="Microsoft-Windows-TCPIP" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

I believe that Windows Setup will ignore this code you posted. Did you build it with WSIM? The reason I am asking is because you are missing a few things. Compare the above quoted code to the following:

<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

Setup looks at the answer file to match the arch of the install to the XML. So since you do not specify an arch, it will skip those components. I do not know if Setup requires all of the information that WSIM puts in, but anytime you are having trouble with an Answer File, you should check it in WSIM after loading the appropriate CLG.

Now, from the documentation it appears you can only use thes options in WindowsPE and Specialize passes.

Source

[srihariram]

Thank you.. None of the examples explain about assigning static IP address (IPv4) and if there are more adapters, then to assign IP to each adapter based on MAC ID.

None of the examples talk about <Identifier>68-ef-bd-f6-72-18</Identifier> (MAC ID).

Below is the snippet that i used.

<component name="Microsoft-Windows-TCPIP" processorArchitecture="amd64" language="neutral" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Interfaces>
                <Interface wcm:action="add">
                    <UnicastIpAddresses>
                        <IpAddress wcm:action="add" wcm:keyValue="30">10.1.1.1/25</IpAddress>
                    </UnicastIpAddresses>
                    <Ipv4Settings>
                        <DhcpEnabled>false</DhcpEnabled>
                    </Ipv4Settings>
                    <Identifier>68-ef-bd-f6-72-18</Identifier>
                    <Routes>
                        <Route wcm:action="add">
                            <Identifier>35</Identifier>
                            <Prefix>0.0.0.0/0</Prefix>
                            <NextHopAddress>10.10.10.10</NextHopAddress>
                        </Route>
                    </Routes>
                </Interface>
                <Interface wcm:action="add">
                    <UnicastIpAddresses>
                        <IpAddress wcm:action="add" wcm:keyValue="31">20.2.2.2/25</IpAddress>
                    </UnicastIpAddresses>
                    <Ipv4Settings>
                        <DhcpEnabled>false</DhcpEnabled>
                    </Ipv4Settings>
                    <Identifier>68-ef-bd-f6-72-19</Identifier>
                    <Routes>
                        <Route wcm:action="add">
                            <Identifier>36</Identifier>
                            <Prefix>0.0.0.0/0</Prefix>
                            <NextHopAddress>20.20.20.20</NextHopAddress>
                        </Route>
                    </Routes>
                </Interface>
            </Interfaces>
        </component>
        <component name="Microsoft-Windows-DNS-Client" processorArchitecture="amd64" language="neutral" versionScope="nonSxS" publicKeyToken="31bf3856ad364e35" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
            <Interfaces>
                <Interface wcm:action="add">
                    <DNSServerSearchOrder>
                        <IpAddress wcm:action="add" wcm:keyValue="40">1.1.1.1</IpAddress>
                        <IpAddress wcm:action="add" />
                    </DNSServerSearchOrder>
                    <Identifier>68-ef-bd-f6-72-18</Identifier>
                </Interface>
                <Interface wcm:action="add">
                    <DNSServerSearchOrder>
                        <IpAddress wcm:action="add" wcm:keyValue="41">2.2.2.2</IpAddress>
                    </DNSServerSearchOrder>
                    <Identifier>68-ef-bd-f6-72-19</Identifier>
                </Interface>
            </Interfaces>
        </component>

Edited November 17, 2010 by Tripredacus
use code tags

[Tripredacus]

I'm not sure about this part, but your Prefix is different than the documentation.

In the future use the CODE tags for posting XML.