Windows 10

Dekay
Beiträge: 29
Registriert: 04 Apr 2019, 15:20

Re: Windows 10

Beitragvon Dekay » 17 Jul 2019, 13:46

uncle_scrooge hat geschrieben:Das
[7] [Jul 17 12:47:21:908] X:\windows\system32>"o:\win10-x64\installfiles\setup.exe" /unattend:x:\unattend.xml
[7] [Jul 17 12:47:21:908] Access is denied.
hätte eher auffallen sollen.....
Auf der Serverconsole ein fröhliches opsi-set-rights absetzen. Noch einmal probieren.


Ich fresse den Besen..Wieso ist mir das nicht aufgefallen.. Ich habe die rechte für das win10-x64 dir neu gesetzt aber nicht diesen befehl global.. Ich teste gerade..

ob es was gebracht hat.. Ich melde mich wieder.. Schon mal vielen Dank. :)

Dekay
Beiträge: 29
Registriert: 04 Apr 2019, 15:20

Re: Windows 10

Beitragvon Dekay » 18 Jul 2019, 12:46

Also vielen Dank für deine Hile. Windows 10 Enterprise wird installiert.

Nur eine kleine sache hätte ich gerne noch geklärt. Ich musste jetzt am Clienten, bei der Windows installation, die Partitionen per Hand auswählen und erstellen. Wie kann ich diese sachen automatisiert dem clienten übergeben, dass ich nichts mehr machen muss als MAC-Adresse eintragen und das OS als Setup wählen was drauf soll und rest macht opsi ohne mein zutun ?

uncle_scrooge
Beiträge: 574
Registriert: 21 Feb 2012, 12:03
Wohnort: Mainz

Re: Windows 10

Beitragvon uncle_scrooge » 18 Jul 2019, 13:32

Welche unattend.xml benutzt Du?
Die im Paket mitgelieferte, oder eine selbstgehäkelte?
Inhalt hier einstellen.

Dekay
Beiträge: 29
Registriert: 04 Apr 2019, 15:20

Re: Windows 10

Beitragvon Dekay » 18 Jul 2019, 14:30

Code: Alles auswählen

<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
    <!--
   ====================
   WINDOWSPE SETTINGS
   ====================
   The windowsPE configuration pass is used to configure settings specific to Windows PE as well as settings that apply to installation.
   For example, you can specify the display resolution of Windows PE, where to save a log file, and other Windows PE-related settings.
   -->
    <settings pass="windowsPE">
        <component name="Microsoft-Windows-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">
            <DiskConfiguration>
                <WillShowUI>OnError</WillShowUI>
                <Disk wcm:action="add">
                    <DiskID>#@diskindex*#</DiskID>
                    <WillWipeDisk>false</WillWipeDisk>
                    <ModifyPartitions>
                        #@modify_partitions*#
                    </ModifyPartitions>
                </Disk>
            </DiskConfiguration>
            <UserData>
                <ProductKey>
                    <WillShowUI>OnError</WillShowUI>
                    <Key>#@productkey*#</Key>
                </ProductKey>
                <AcceptEula>true</AcceptEula>
                <FullName>#@fullname*#</FullName>
                <Organization>#@orgname*#</Organization>
            </UserData>
            <ImageInstall>
                <OSImage>
                    <InstallFrom>
                        <MetaData wcm:action="add">
                            <Key>/IMAGE/NAME</Key>
                            <Value>#@imagename*#</Value>
                        </MetaData>
                    </InstallFrom>
                    <InstallTo>
                        <DiskID>#@installdiskindex*#</DiskID>
                        <PartitionID>#@windows_partition_number*#</PartitionID>
                    </InstallTo>
                    <WillShowUI>OnError</WillShowUI>
                </OSImage>
            </ImageInstall>
        </component>
        <component name="Microsoft-Windows-International-Core-WinPE" 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">
            <SetupUILanguage>
                <UILanguage>#@winpe_uilanguage*#</UILanguage>
                <WillShowUI>OnError</WillShowUI>
            </SetupUILanguage>
            <InputLocale>#@winpe_inputlocale*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@winpe_uilanguage*#</UILanguage>
            <UILanguageFallback>#@winpe_uilanguage_fallback*#</UILanguageFallback>
            <UserLocale>#@winpe_uilanguage*#</UserLocale>
            <LayeredDriver>1</LayeredDriver>
        </component>
        <component name="Microsoft-Windows-PnPCustomizationsWinPE" 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">
            <DriverPaths wcm:keyValue="1">
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path wcm:keyValue="1">c:\drvpe</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
   =====================
   GENERALIZE SETTINGS
   =====================
   The generalize pass of Windows Setup is used to create a Windows reference image that can be used throughout an organization.
   A setting in the generalize pass enables you to automate the behavior for all deployments of this reference image.
   In comparison, a setting associated with the specialize configuration pass enables you to override behavior for a single, specific deployment.
   When a system is generalized, specific configuration data for a given installation of Windows is removed.
   For example, during the generalize pass, the unique security ID (SID) and other hardware-specific settings are removed from the image.
   The generalize configuration pass runs only when you use the sysprep /generalize command.
   Answer file settings in generalize are applied to the system before sysprep generalization occurs. The system then shuts down.
   -->
    <!--
   <settings pass="generalize">
   </settings>
   -->
    <!--
   =====================
   SPECIALIZE SETTINGS
   =====================
   During the specialize pass of Windows Setup, machine-specific information for the image is applied.
   For example, you can configure network settings, international settings, and domain information.
   The specialize pass is used in conjunction with the generalize pass.
   The generalize pass is used to create a Windows reference image that can be used throughout an organization.
   From this basic Windows reference image, you can add further customizations that apply to different divisions
   within an organization or apply to different installations of Windows.
   The specialize pass is used to apply these specific customizations.
   -->
    <settings pass="specialize">
        <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">
            <ComputerName>#@pcname*#</ComputerName>
            <UserAccounts>
                <AdministratorPassword>
                    <PlainText>true</PlainText>
                    <Value>#@administratorPassword*#</Value>
                </AdministratorPassword>
            </UserAccounts>

        </component>

        <component name="Microsoft-Windows-RemoteAssistance-Exe" 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">
            <CreateEncryptedOnlyTickets>true</CreateEncryptedOnlyTickets>
            <fAllowToGetHelp>true</fAllowToGetHelp>
        </component>
        <component name="Microsoft-Windows-International-Core" 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">
            <InputLocale>#@system_keyboard_layout*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@system_language*#</UILanguage>
            <UILanguageFallback>#@system_language*#</UILanguageFallback>
            <UserLocale>#@system_language*#</UserLocale>
        </component>
        <component name="Microsoft-Windows-Deployment" 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">
            <RunSynchronous>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Enable Admin Account</Description>
                    <Order>1</Order>
                    <Path>cmd.exe /c net user #@adminName*# /active:yes</Path>
                </RunSynchronousCommand>
                <RunSynchronousCommand wcm:action="add">
                    <Description>Passwd Admin Account</Description>
                    <Order>2</Order>
                    <Path>cmd.exe /c net user #@adminName*# #@administratorPassword*#</Path>
                </RunSynchronousCommand>

            </RunSynchronous>
        </component>
        <component name="Networking-MPSSVC-Svc" 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">
            <DomainProfile_EnableFirewall>false</DomainProfile_EnableFirewall>
            <PrivateProfile_EnableFirewall>false</PrivateProfile_EnableFirewall>
            <PublicProfile_EnableFirewall>false</PublicProfile_EnableFirewall>
        </component>
    </settings>
    <!--
   =========================
   OFFLINESERVICING SETTINGS
   =========================
   Use the offlineServicing pass to apply unattended Setup settings to an offline Windows image.
   During this configuration pass, you can add language packs, updates, or other packages to the offline image.
   The offlineServicing pass runs during Windows Setup. Setup extracts and installs the Windows image, and then executes Package Manager (Pkgmgr.exe).
   Packages listed in the servicing section of the answer file are applied to the offline Windows image.
   The Unattend.xml settings in the offlineServicing pass are applied to the offline Windows image.
   Additionally, you can use Package Manager with an answer file to install packages.
   -->
    <settings pass="offlineServicing">
        <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" 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">
            <DriverPaths>
                <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                    <Path>c:\drv</Path>
                </PathAndCredentials>
            </DriverPaths>
        </component>
    </settings>
    <!--
   =====================
   AUDITSYSTEM SETTINGS
   =====================
   The auditSystem pass is an optional pass that enables you to add additional device drivers and applications to the image.
   This results in fewer required images because a reference image can be created with a minimal set of drivers.
   The image can be updated with additional drivers during the audit process.
   You can then test and resolve any operating system issues related to malfunctioning or incorrectly installed devices on the image.
   For example, you can install additional language packs, updates, or other applications, such as Microsoft Office.
   See Reseal mode in oobeSystem.
   -->
    <!--
   <settings pass="auditSystem">
   </settings>
   -->
    <!--
   =====================
   AUDITUSER SETTINGS
   =====================
   The auditUser pass is similar to the auditSystem pass.
   However, the auditUser pass processes these settings after users have logged on, not before they have logged on.
   Like the auditSystem pass, the auditUser pass is used to test the functionality of the Windows Vista image.
   See Reseal mode in oobeSystem.
   -->
    <!--
   <settings pass="auditUser">
   </settings>
   -->
    <!--
   =====================
   OOBESYSTEM SETTINGS
   =====================
   The oobeSystem pass configures settings that are applied during the first-boot experience for end users, also called Windows Welcome.
   oobeSystem settings are processed before a user first logs into Windows.
   Out-of-Box-Experience (OOBE) runs the first time the user starts a new computer.
   OOBE runs before the Windows shell or any additional software runs, and performs a small set of tasks necessary to configure and run Windows.
   -->
    <settings pass="oobeSystem">

        <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">

            <TimeZone>#@system_timezone*#</TimeZone>
            <AutoLogon>
                <Enabled>true</Enabled>
                <LogonCount>1</LogonCount>
                <Username>#@adminName*#</Username>
                <Password>
                    <PlainText>true</PlainText>
                    <Value>#@administratorPassword*#</Value>
                </Password>
            </AutoLogon>
            <FirstLogonCommands>
                <SynchronousCommand wcm:action="add">
                    <RequiresUserInput>false</RequiresUserInput>
                    <Description>Opsi tasks</Description>
                    <Order>1</Order>
                    <CommandLine>cmd.exe /c #@winpe_partition_letter*#:\opsi\postinst.cmd</CommandLine>
                </SynchronousCommand>
            </FirstLogonCommands>

            <OOBE>
                <HideEULAPage>true</HideEULAPage>
                <ProtectYourPC>3</ProtectYourPC>
                <HideOnlineAccountScreens>true</HideOnlineAccountScreens>
                <HideLocalAccountScreen>true</HideLocalAccountScreen>
                <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
            </OOBE>

        </component>
   <component name="Microsoft-Windows-International-Core" 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">
            <InputLocale>#@system_keyboard_layout*#</InputLocale>
            <SystemLocale>#@system_language*#</SystemLocale>
            <UILanguage>#@system_language*#</UILanguage>
            <UILanguageFallback>#@system_language*#</UILanguageFallback>
            <UserLocale>#@system_language*#</UserLocale>
        </component>

    </settings>
</unattend>



An der Datei, wurde meines wissens nach, nichts verändert. Also die mit geliefert wurde.

Ich hätte auch gerne, dass er nach der Windows installation den OPSI-Agenten mit installiert. Noch macht er es nicht. Auch wenn es auf Setup steht. Auch nach einem Neustart macht er das nicht

Dekay
Beiträge: 29
Registriert: 04 Apr 2019, 15:20

Re: Windows 10

Beitragvon Dekay » 18 Jul 2019, 15:31

Wie kann es sein, dass in den ordner win10-x64 die unattend.xml von der x86 version liegt ?

Code: Alles auswählen

<component name="Microsoft-Windows-Setup" processorArchitecture="x86"

uncle_scrooge
Beiträge: 574
Registriert: 21 Feb 2012, 12:03
Wohnort: Mainz

Re: Windows 10

Beitragvon uncle_scrooge » 18 Jul 2019, 15:41

Die Frage solltest Du Dir vielleicht selber stellen.
Im Paket win10-x64 ist standardmäßig die AMD64-Variante drin.

uncle_scrooge
Beiträge: 574
Registriert: 21 Feb 2012, 12:03
Wohnort: Mainz

Re: Windows 10

Beitragvon uncle_scrooge » 18 Jul 2019, 15:48

Nachschlag:
Ich würde an dieser Stelle einen cut machen.
Dein Paket komplett entfernen.
Und von hier https://download.uib.de/opsi_stable/pro ... .0-16.opsi neu installieren.
Und wieder mit den Windows-Quellen und Deinem WinPE bestücken.

Dekay
Beiträge: 29
Registriert: 04 Apr 2019, 15:20

Re: Windows 10

Beitragvon Dekay » 18 Jul 2019, 16:26

uncle_scrooge hat geschrieben:Die Frage solltest Du Dir vielleicht selber stellen.
Im Paket win10-x64 ist standardmäßig die AMD64-Variante drin.


Diese Frage stelle ich mir gerade.


uncle_scrooge hat geschrieben:Nachschlag:
Ich würde an dieser Stelle einen cut machen.
Dein Paket komplett entfernen.
Und von hier https://download.uib.de/opsi_stable/pro ... .0-16.opsi neu installieren.
Und wieder mit den Windows-Quellen und Deinem WinPE bestücken.


Danke das werde ich machen. :)

Dekay
Beiträge: 29
Registriert: 04 Apr 2019, 15:20

Re: Windows 10

Beitragvon Dekay » 19 Jul 2019, 09:21

Du glaubst garnicht wie sehr du mir geholfen hast. Vielen Vielen Dank. :D :D :D

uncle_scrooge
Beiträge: 574
Registriert: 21 Feb 2012, 12:03
Wohnort: Mainz

Re: Windows 10

Beitragvon uncle_scrooge » 19 Jul 2019, 11:25

Vielleicht hierzu
...Ich hoffe das mir jemand helfen kann und das ohne supportvertrag....
noch ein Wort.
Die Menschen von uib weisen gerne und häufig auf die angebotenen Supportleistungen hin. Wenn man kurz innehält, und darüber nachdenkt, wohl auch aus gutem Grund. Von irgendetwas müssen die ganzen Lambo, Ferrari und Bentley bezahlt werden. Von Niko Wenselowskis Fahrrad gar nicht zu reden.
Aber sie sind trotzdem, wenn es die Zeit erlaubt, hier im Forum helfend unterwegs.
Die anderen Forumsteilnehmer haben neben ihrer Arbeit noch andere Hobbies (Frau und Kinder schlagen, Katze des Nachbarn quälen, ...). Und opfern hier ihre Freizeit.
Worauf ich mit dem ganzen Sermon hinaus will ist, Geduld ist eine Tugend.
Manches kann und wird schnell erledigt. Weil es gerade passt. (Genug Leute mit Langeweile und Expertise unterwegs.)
Aber manchmal dauert es halt auch ein paar Tage. Wegen Häh? und verwirrtem Kopfkratzen. Und weil die Hälfte der Menschen hier in Urlaub ist.