user001's questions

I have the TS setting the registry keys in the HKEY_Local_Machine no problem.

My issue is that I want to, by default, set a key for the HKEY_Current_User. I want to have the "Automatically detect settings" in Internet Properties LAN settings unchecked, for anyone logging in.

I think that the correct key is

Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\DefaultConnectionSettings

but as it is in the Current User I am finding it hard to have it set by default, through the OSDeploy TS. Want it set by default for a no-touch build of all our machines.

Any help would be appreciated.

I have been told that it is possible to run Powershell directly from the Unattend.xml during an OS install.

I am trying to set the ComputerName to (A + "SerialNumber") but not matter how I write the file it keeps being stepped over.

Currently I have the XML as below

<settings pass="specialize">
        <component name="Microsoft-Windows-International-Core" 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">
            <InputLocale>en-IE</InputLocale>
            <SystemLocale>en-IE</SystemLocale>
            <UILanguage>en-IE</UILanguage>
            <UserLocale>en-IE</UserLocale>
            <UILanguageFallback></UILanguageFallback>
        </component>
        <component name="Microsoft-Windows-Deployment" 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">
            <RunAsynchronous>
                <RunAsynchronousCommand wcm:action="add">
                    <Path>powershell.exe –ExecutionPolicy Bypass -File "\\server\store\Software\Powershell\UnattendedInstallComputerName.ps1"</Path>
                    <Description>Use script to rename computer with Serial number</Description>
                    <Order>1</Order>
                </RunAsynchronousCommand>
            </RunAsynchronous>
        </component>
    </settings>
    <settings pass="oobeSystem">
        <component name="Microsoft-Windows-International-Core" 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">
            <InputLocale>en-IE</InputLocale>
            <SystemLocale>en-IE</SystemLocale>
            <UILanguage>en-IE</UILanguage>
            <UserLocale>en-IE</UserLocale>
        </component>
    </settings>

With the script being called simply as

$Serial = Get-WmiObject win32_bios | select -expand serialnumber
$CompName = "A" + $Serial
Rename-Computer $CompName

Now I have done loads of variants of the above in different pass runs but no luck. I've honestly just thrown the "powershell.exe –ExecutionPolicy Bypass -File " as a Hail Mary.

Any help would be appreciated

I'm trying to disable NetBIOS and need to do this over SCCM to multiple clients.

I am trying to do this through compliance settings and have the following in place (and they work when run locally)

Discovery Script

$adapter=(gwmi win32_networkadapterconfiguration | where {$_.ipenabled -eq "1"})
Foreach ($nic in $adapter) {if ($adapter.TcpIPNetBiosOptions -ne "2") {[System.Environment]::Exit(1)}} [System.Environment]::Exit(0)

Remediation script

$adapter=(gwmi win32_networkadapterconfiguration | where {$_.ipenabled -eq "1"})
Foreach ($nic in $adapter) {
$adapter.settcpipnetbios(2)
}

So running the script works on each machine locally and, if already compliant, SCCM is giving correct response

BUT

If the registry values returns as $adapter.TcpIPNetBiosOptions -ne "2" then the configuration compliance shows "error" when evaluated in Configuration Manager and the remediation does not trigger automatically. If I run the script myself then the configuration returns as compliant.

Is there something which I am missing?

Edit I see the following error being reported

Setting Discovery Error 0x80070001 Incorrect function. Windows

Anyone know why I am getting this on a server Win 2012 R2?

FTP is not an enabled feature, on the server. It's a very old CVE and very (no) info about it on searching.