-
Posts
600 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Events
Posts posted by myselfidem
-
-
Just add the same password for: user1
-
Using "Apply Unattend": Applies an Unattend.xml file to the image:
http://technet.microsoft.com/en-us/library/dd744522(WS.10).aspx
Applies an unattend.xml file to an image.
If you are updating device drivers using an unattended answer file, you must apply the answer file to an offline image and specify the settings in the offlineServicing configuration pass.
If you are updating packages or other settings using an unattended answer file, you can apply the answer file to an offline or online image. Specify the settings in the offlineServicing configuration pass.
-
I think I'm in the heart of the problem!
My example above is to show how works AutoLogon with an Autounattend.xml file fully unattended!
Using Username : Administrator - inside AutoLogon - activate the built-in Administrator and not the Admin User, to log on automatically!
The best way is to create a simple XML Creator with the needed values!
-
Works fine for me if I change like this, example:
<AutoLogon>
<Enabled>true</Enabled>
<LogonCount>9999999</LogonCount>
<Username>Antoine</Username>
<Password>
<Value>Same Password</Value>
<PlainText>false</PlainText>
</Password>
</AutoLogon>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Home</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<PlainText>false</PlainText>
<Value>Same Password</Value>
</Password>
<Group>Administrators</Group>
<DisplayName>Antoine</DisplayName>
<Name>Antoine</Name>
</LocalAccount>
<LocalAccount wcm:action="add">
<Password>
<PlainText>false</PlainText>
<Value>Other Password</Value>
</Password>
<Group>Users</Group>
<DisplayName>Josiane</DisplayName>
<Name>Josiane</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>Image Accounts:
-
@Legolash2o
About XML Creator!
It's possible to merge inside Autounattend.xml files (anyCPU) for x86/x64 file, like this:
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[url="http://schemas.microsoft.com/WMIConfig/2002/State"]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url="http://www.w3.org/2001/XMLSchema-instance"]http://www.w3.org/2001/XMLSchema-instance[/url]">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="[url="http://schemas.microsoft.com/WMIConfig/2002/State"]http://schemas.microsoft.com/WMIConfig/2002/State[/url]" xmlns:xsi="[url="http://www.w3.org/2001/XMLSchema-instance"]http://www.w3.org/2001/XMLSchema-instance[/url]">
<SetupUILanguage>
<UILanguage>en-US</UILanguage>
</SetupUILanguage>
<InputLocale>0409:00000409</InputLocale>
<SystemLocale>en-US</SystemLocale>
<UILanguage>en-US</UILanguage>
<UserLocale>en-US</UserLocale>
</component>Regards
*Edit: Using this option AnyCPU the ei.cfg file must be removed for AIO (x86/x64) to display the Edition the user wants to install!!
-
Fine, if it's OK for you!
Yes, you are right about trying to move post install!
However, useful info:
http://www.msfn.org/...043#entry960043
*Edit: I'm not sure the files and folders moved will be more secure!!!
-
@Etz
I see inside your Autounattend.xml file:
<FolderLocations>
<ProfilesDirectory>D:\Users</ProfilesDirectory>
<ProgramData>D:\ProgramData</ProgramData>
</FolderLocations>Warning:
ProfilesDirectory
The ProfilesDirectory setting specifies the path to the user profile folder.
Caution:
- This setting should be used only in a test environment. If you change the default location of the user-profile directories or program-data folders to a volume other than the system volume, you cannot service your image. Any updates, fixes, or service packs will not be applied to the installation.
For a list of known issues with this setting, see Description of known issues with the FolderLocation settings.. - Using this setting to redirect folders to a drive other than the system volume blocks upgrades. Using ProfilesDirectory to point to a directory that is not the system volume will block SKU edition upgrades and upgrades to future versions of Windows®. For example, if you use Windows 7 Home Premium with ProfilesDirectory set to D:\, you will not be able to upgrade to Windows 7 Ultimate or to the next version of Windows. The servicing stack does not handle cross-volume transactions, and it blocks upgrades.
Use this setting to move the user-profile folder (typically %SYSTEMDRIVE%\Users) to another location during Setup or when Sysprep is running. The destination path can be on a volume other than the system drive, as long as it meets the following requirements:
- It must be on an NTFS volume.
- It must not be the path of another operating system user-profile folder.
- It must not contain any serviceable components.
This setting can be used to keep system data separate from user data. If Windows® is re-installed on the system volume, a user with administrative rights can manually recover data from this location.
ProgramData
The ProgramData setting specifies the path to the program-data folder.
Important: This setting should be used only in a test environment. If you change the default location of the user-profile directories or program-data folders to a volume other than the system volume, you cannot service your image. Any updates, fixes, or service packs will not be applied to the installation.
For a list of known issues with this setting, see Description of known issues with the FolderLocation settings..
Use this setting to move the program-data folder (typically %SYSTEMDRIVE%\Program Files) to another location during Setup or when Sysprep is running. The destination path can be on a volume other than the system drive, as long as it meets the following requirements:
- It must be on an NTFS volume.
- It must not be the path of another operating system program-data folder.
- It must not contain any serviceable components.
- This setting should be used only in a test environment. If you change the default location of the user-profile directories or program-data folders to a volume other than the system volume, you cannot service your image. Any updates, fixes, or service packs will not be applied to the installation.
-
Remember XML Creator needs to be improved...Use the Autounattend.xml file I gave you!
Check first your Autounattend.xml file for Windows x86 and after duplicate the values for x64 and merge the files, and check with WSIM...You will see ONLY ONE error: missing the last line...But this is not needed!
Example, two Accounts:
<LocalAccounts>
<LocalAccount wcm:action="add">
<Name>Antoine</Name>
<Group>Administrators</Group>
<Password>
<Value>xxxxxxx</Value>
<PlainText>false</PlainText>
</Password>
<DisplayName>Antoine</DisplayName>
<Description>Antoine</Description>
</LocalAccount>
<LocalAccount wcm:action="add">
<Name>Josiane</Name>
<Group>Users</Group>
<Password>
<Value>xxxxxxxxx</Value>
<PlainText>false</PlainText>
</Password>
<DisplayName>Josiane</DisplayName>
<Description>Josiane</Description>
</LocalAccount>
</LocalAccounts> -
Your are using an Autounattend.xml file AIO x86/x64 right?
You can't validate this file with WSIM, but only see if there is some errors!
Give me your Autounattend.xml file and I will try to add the users you want!
Attach this one.
Thanks
*Edit: If the integrated keys aren't the good ones you may have errors!!
SetProductKey.cmd is useful if you don't want enter a key during the silent installation!!
Please read carefully my posts here:
-
Remember, always check your Autounattend.xml file with WSIM to see if there is errors !!!!!!!!
<OEMInformation>
<Manufacturer /> ???????
<SupportHours /> ??????
<SupportPhone /> ??????
<SupportURL />????????
<Model /> ????????
</OEMInformation>etc...
unnecessary....
-
Why you don't use the Autounattend.xml file I gave you and working fine?
Remember, you have only ONE VALID key matching the Windows 7 you bought!!!
If you have saved your activated files you will see 3 days and after you must validate your windows 7 version...Using on a virtual machine...!!
The default keys are useful to install silently any Windows 7 version...But you need to buy a different VALID KEY for each version!
And I see an error inside your Autounattend.xml file:
<Value /> ??????
Remember Legolash2o is working to improve XML Creator!!
Regards
-
My advice is to not use: Skip User Creation, but to associate the AutoLogon's User name with the User account who have privileges to start automatically as administrator!
Don't use: Skip User Creation for Windows 7
I hope my english is understandable!
Regards
-
I think many people believe they have the full power of their computers!
A friend of mine was unable to restore his computer because he was the only Administrator (in fact built-in Administrator) of his computer!!
-
Found some infos:
http://www.msfn.org/...810#entry891810
I think it's not recommended to: Skip User Creation for Windows 7!
Regards
Using AutoLogon like this works:
<AutoLogon>
<Password>
<Value></Value>
</Password>
<Enabled>true</Enabled>
<LogonCount>2</LogonCount>
<Username>Administrator</Username>
</AutoLogon>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value></Value>
<PlainText>true</PlainText>
</Password>
<DisplayName>Administrator</DisplayName>
<Name>Administrator</Name>
<Group>Administrators</Group>
</LocalAccount>
</LocalAccounts>
</UserAccounts> -
Very fast reply! Thanks Rick
-
If we use only::
<AutoLogon>
<Password>
<Value></Value>
</Password>
<Enabled>true</Enabled>
<LogonCount>9999999</LogonCount>
<Username>Administrator</Username>
</AutoLogon>If a password is specified in AdministratorPassword, then use the same password in Autologon.We can enable the built-in Administrator without creating a User account!
But I think it's not a good silent installation!
Silent installation can fails on WMware virtual Machine using only AutoLogon like shown above!
*Edit:
New test made with (Test4) and I see if I select: Skip User Creation, some values are set!
<UserAccounts>
<AdministratorPassword>
<Value>qwertzuiop</Value>
<PlainText>true</PlainText>
</AdministratorPassword>
</UserAccounts> -
Thanks Rick!
Here is the language pack for French (x86):
http://www.microsoft...8d-0df2d76e24a8
Module linguistique Microsoft .NET Framework 4 Full (x86/x64):
http://www.microsoft.com/downloads/fr-fr/details.aspx?FamilyID=6fd7e428-0aa8-40e3-a48d-0df2d76e24a8
Regards
-
I would like to create a user named user1 in administrators group with Autounattended.xml and apply autologon to user1
is that possible?
Yes like Legolash2o answered it's possible, but take care with built-in Administrator Auto Logon and User Account!
Simply creates 2 or more Uer accounts!
-
I would like to create a user named user1 in administrators group with Autounattended.xml and apply autologon to user1
is that possible?
We must take care about built-in Administrator and Auto Logon!
Using your name as Auto Logon and User Account seems correct and works fine for me!
-
Extract: Unattended Windows Setup Reference for Windows 7.chm
AutoLogon
AutoLogon specifies the account to use to log on to a computer automatically. Autologon credentials are deleted from the unattended installation answer file after Windows® Setup is complete.
Important: Make sure Autologon is disabled on computers that are delivered to customers.
By default, the built-in administrator account is disabled in all default, clean installations.
For Windows® 7 and Windows Vista®, you can enable the built-in administrator account during unattended installations by setting Username to Administrator (only the English word, Administrator, automatically enables the account). This enables the built-in administrator account, even if a password is not specified in AdministratorPassword. If a password is specified in AdministratorPassword, then use the same password in Autologon.
For Windows Server® 2008 and Windows Server® 2008 R2, the built-in Administrator account must have a password, and that password must be changed at first logon. This prevents the built-in Administrator account from having a blank password by default. Use the same password that was used in AdministratorPassword.
Both Microsoft-Windows-Shell-Setup | Autologon and Microsoft-Windows-Shell-Setup | UserAccounts | AdministratorPassword sections are needed to auto logon to a computer in audit mode. Both of these settings should be added to the auditSystem configuration pass.
Regards
*Edit: my Autounattend.xml file seems correct and works fine!
-
At this time XML Creator needs to be improved!
Some values are missing to have a full unattended answer file!
You can find help to create your own Autounattend.xml file, here:
http://www.msfn.org/...seven-xml-here/
As example, my customized Autounattend.xml file:
<?xml version="1.0" encoding="utf-8"?>
<unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<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>fr-FR</UILanguage>
</SetupUILanguage>
<InputLocale>100c:0000100c</InputLocale>
<SystemLocale>fr-CH</SystemLocale>
<UILanguage>fr-FR</UILanguage>
<UserLocale>fr-CH</UserLocale>
</component>
<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">
<Diagnostics>
<OptIn>false</OptIn>
</Diagnostics>
<DiskConfiguration>
<WillShowUI>Always</WillShowUI>
</DiskConfiguration>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1280</HorizontalResolution>
<VerticalResolution>1024</VerticalResolution>
<RefreshRate>60</RefreshRate>
</Display>
<DynamicUpdate>
<Enable>false</Enable>
<WillShowUI>OnError</WillShowUI>
</DynamicUpdate>
<ImageInstall>
<OSImage>
<InstallFrom>
<MetaData wcm:action="add">
<Key>/IMAGE/NAME</Key>
<Value>Windows 7 ULTIMATE</Value>
</MetaData>
</InstallFrom>
</OSImage>
</ImageInstall>
<UserData>
<AcceptEula>true</AcceptEula>
<FullName>Your Full Name</FullName>
<Organization>customer</Organization>
<ProductKey>
<Key>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</Key>
<WillShowUI>OnError</WillShowUI>
</ProductKey>
</UserData>
<EnableFirewall>true</EnableFirewall>
</component>
</settings>
<settings pass="offlineServicing">
<component name="Microsoft-Windows-LUA-Settings" 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">
<EnableLUA>false</EnableLUA>
</component>
</settings>
<settings pass="generalize">
<component name="Microsoft-Windows-PnpSysprep" 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">
<PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-IE-InternetExplorer" 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">
<Home_Page>http://www.bluewin.ch/index.html.fr</Home_Page>
<BlockPopups>yes</BlockPopups>
<CompanyName>Se7en_UA</CompanyName>
<FavoritesOnTop>true</FavoritesOnTop>
<FilterLevel>High</FilterLevel>
<Help_Page>http://people.consolidated.net/veeger/</Help_Page>
<DisableFirstRunWizard>true</DisableFirstRunWizard>
<DisableWelcomePage>true</DisableWelcomePage>
<PlaySound>false</PlaySound>
<ShowInformationBar>true</ShowInformationBar>
<SearchScopes>
<Scope wcm:action="add">
<ScopeDefault>true</ScopeDefault>
<ScopeDisplayName>Google</ScopeDisplayName>
<ScopeKey>Search1</ScopeKey>
<ScopeUrl>http://www.google.com/advanced_search?hl=fr</ScopeUrl>
</Scope>
</SearchScopes>
<LockToolbars>true</LockToolbars>
<ShowLeftAddressToolbar>true</ShowLeftAddressToolbar>
<ShowMenuBar>true</ShowMenuBar>
<SuggestedSitesEnabled>true</SuggestedSitesEnabled>
</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">
<fAllowFullControl>false</fAllowFullControl>
<fAllowToGetHelp>false</fAllowToGetHelp>
</component>
<component name="Microsoft-Windows-Security-SPP-UX" 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">
<SkipAutoActivation>true</SkipAutoActivation>
</component>
<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>Se7en</ComputerName>
<ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey>
<RegisteredOwner>myselfidem</RegisteredOwner>
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1280</HorizontalResolution>
<VerticalResolution>1024</VerticalResolution>
<RefreshRate>60</RefreshRate>
</Display>
</component>
</settings>
<settings pass="oobeSystem">
<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">
<UILanguage>fr-FR</UILanguage>
<UserLocale>fr-CH</UserLocale>
<InputLocale>100c:0000100c</InputLocale>
</component>
<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">
<Display>
<ColorDepth>32</ColorDepth>
<HorizontalResolution>1280</HorizontalResolution>
<VerticalResolution>1024</VerticalResolution>
<RefreshRate>60</RefreshRate>
</Display>
<RegisteredOwner>Your Full Name</RegisteredOwner>
<TimeZone>W. Europe Standard Time</TimeZone>
<AutoLogon>
<Enabled>true</Enabled>
<LogonCount>9999999</LogonCount>
<Username>myselfidem</Username>
<Password>
<Value>xxxxxxxxx</Value>
<PlainText>false</PlainText>
</Password>
</AutoLogon>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<Order>1</Order>
<Description>Password never expires</Description>
<CommandLine>cmd /C wmic useraccount where "name='myselfidem'" set PasswordExpires=FALSE</CommandLine>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
<SynchronousCommand wcm:action="add">
<Order>2</Order>
<Description>Installation des applications avec WPI</Description>
<CommandLine>cmd /c for %i in (C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %i:\wpi\wpi.exe start %i:\wpi\wpi.exe</CommandLine>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>
</FirstLogonCommands>
<OEMInformation>
<Logo>%WINDIR%\System32\oemlogo.bmp</Logo>
<Manufacturer>Se7en_UA</Manufacturer>
<Model>Seven Titan</Model>
<SupportHours>A tout instant, consultez les Forums</SupportHours>
<SupportPhone>BR549</SupportPhone>
<SupportURL>http://www.msfn.org</SupportURL>
</OEMInformation>
<OOBE>
<HideEULAPage>true</HideEULAPage>
<NetworkLocation>Home</NetworkLocation>
<ProtectYourPC>1</ProtectYourPC>
<HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE>
</OOBE>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<PlainText>false</PlainText>
<Value>xxxxxxx</Value>
</Password>
<Group>Administrators</Group>
<DisplayName>myselfidem</DisplayName>
<Name>myselfidem</Name>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<VisualEffects>
<FontSmoothing>ClearType</FontSmoothing>
</VisualEffects>
<BluetoothTaskbarIconEnabled>true</BluetoothTaskbarIconEnabled>
<WindowsFeatures>
<ShowInternetExplorer>true</ShowInternetExplorer>
<ShowMediaCenter>true</ShowMediaCenter>
<ShowWindowsMediaPlayer>true</ShowWindowsMediaPlayer>
</WindowsFeatures>
</component>
<component name="Microsoft-Windows-Sidebar" 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">
<Gadget1>%PROGRAMFILES%\Windows Sidebar\Gadgets\Clock.Gadget</Gadget1>
<Gadget2>%PROGRAMFILES%\Windows Sidebar\Gadgets\Calendar.Gadget</Gadget2>
<Gadget3>%PROGRAMFILES%\Windows Sidebar\Gadgets\Weather.Gadget</Gadget3>
</component>
</settings>
</unattend>Adapt to your needs. Always check your answer file with WSIM to see if there is errors!
I hope that can help!
*Edit: Using new Test3: removing components Speech and Natural Language and WinSxS\Backup successfully!
-
Look inside the file:
C:\Windows\Logs\DISM\dism.log
You will see the errors!
Could you post your new Settings.txt file?
Maybe it seems W7T.exe can't create properly the files on another partition than C:\ !
-
It seems the error is with the temp folder: sMountTemp=D:\WTMount
It's not like mine:
Settings.txt
fAddons=
fDrivers=
fGadgets=
fSilents=
fThemes=
fTweaks=
fUpdates=
fWallpapers=
sAICommands=True
sAIOSave=True
sCheckForUpdates=True
sDLogging=True
sFreeRAM=True
sGroups=True
sHotkeys=True
sLastWIM=C:\Win7\sources\install.wim
smCheck=False
sAIOPM=True
sMountTemp=C:\W7T\Mount
sQuickMerge=False
smVerify=False
sSolDownload=C:\W7T130-38B_Test\SoLoR\
sTransparency=100
sTransparencyAll=False
sW7TDISM=Normal
sW7TExt=Normal
sW7TPRI=Normal
sW7TTemp=C:\W7T
sShowAntiV=True
sSkipDCheck=True
sUploadLogs=True
sLastISO_Folder=
sLastISO_ISO=
sMountLog=True
sUSBPrepLog=True
sWelcomeTab=True
sDownloadTab=True
sToolsTab=True
sRegistryLog=False
-
Try to use: W:\Win7\sources\install.wim
sLastWIM=W:\0Wins\7\Ultimate\Sources\install.wim
@Legolash2o
Removing components with the new version (Test)= No errors! Windows 7 Ultimate x86
I will make more tests...
Regards
Unattended not working
in Win Toolkit
Posted
Try with the same password for: user1 !!!