Jump to content

jbusato

Member
  • Posts

    10
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Italy

Everything posted by jbusato

  1. Hi all, I made a syspreped Vista WIM image. I create a unattend.xml file with WSIM that use Microsoft-Windows-Shell-Setup\UserAccounts with only Administrator. All it's good but Windows ask me to create another user account. It's possible to have only Administrator? Thank you so much here is my xml file <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="offlineServicing"> <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"> <RegisteredOrganization>MYNAME</RegisteredOrganization> <RegisteredOwner>MYNAME</RegisteredOwner> <StartPanelOff>true</StartPanelOff> </component> </settings> <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"> <AutoLogon> <Enabled>true</Enabled> <LogonCount>5</LogonCount> <Username>Administrator</Username> </AutoLogon> <ComputerName>*</ComputerName> <RegisteredOwner>MYNAME</RegisteredOwner> <RegisteredOrganization>MYNAME</RegisteredOrganization> <ShowWindowsLive>false</ShowWindowsLive> <StartPanelOff>true</StartPanelOff> <TimeZone>W. Europe Standard Time</TimeZone> <ProductKey>xxxxxxxxxxxxxxxxxxxxxxxxx</ProductKey> </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>it-IT</InputLocale> <SystemLocale>it-IT</SystemLocale> <UILanguage>it-IT</UILanguage> <UserLocale>it-IT</UserLocale> </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"> <InputLocale>it-IT</InputLocale> <SystemLocale>it-IT</SystemLocale> <UILanguage>it-IT</UILanguage> <UserLocale>it-IT</UserLocale> </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"> <AutoLogon> <Enabled>true</Enabled> <LogonCount>5</LogonCount> <Username>Administrator</Username> </AutoLogon> <RegisteredOwner>MYNAME</RegisteredOwner> <RegisteredOrganization>MYNAME</RegisteredOrganization> <ShowWindowsLive>false</ShowWindowsLive> <StartPanelOff>false</StartPanelOff> <TimeZone>W. Europe Standard Time</TimeZone> <OOBE> <HideEULAPage>true</HideEULAPage> <NetworkLocation>Work</NetworkLocation> <ProtectYourPC>1</ProtectYourPC> </OOBE> <UserAccounts> <AdministratorPassword> <Value>QQBkAG0AaQBuAGkAcwB0AHIAYQB0AG8AcgBQAGEAcwBzAHcAbwByAGQA</Value> <PlainText>false</PlainText> </AdministratorPassword> </UserAccounts> </component> </settings> <settings pass="auditSystem"> <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"> <Reseal> <Mode>Audit</Mode> </Reseal> </component> </settings> <cpi:offlineImage cpi:source="wim://wvistaentita/wvistaitaent.wim#C-DRIVE" xmlns:cpi="urn:schemas-microsoft-com:cpi" /> </unattend>
  2. Adding XML package issue was solved
  3. Problem is my PE not my code. MS simple code (http://www.microsoft.com/technet/technetmag/issues/2006/09/WindowsPE/default.aspx) give me the same error.
  4. Hi, reading "WinPE 2.0 simple Ghost Menu HTA, a simple HTA to make Ghosting easy" topic I'm try to do an html application fontend to imagex in winpe. In my startnet.cmd I append a call to this file: <html> <head> <HTA:APPLICATION BORDER = No APPLICATION = Yes WINDOWSTATE = maximize INNERBORDER = No SHOWINTASKBAR = No SCROLL = No APPLICATIONNAME = "Imagex tool" NAVIGABLE = Yes> <style> td {color: black; font-size: 9pt;} </style> </head> <body bgcolor="#c8dcea" style="margin: 0px;"> <script language="vbscript"> '********************************* ' doTask '********************************* Sub doTask MsgBox "Helloworld" End Sub </script> <form name="osd"> <input type="button" id="task" onclick="doTask()" value="Just do it!"> </form> </body> </html> But it gives me a lot of script error without any info (no error no page no row and so on...) I'm using Windows PE 2.0 with HTA,Scripting and WMI support. Someone could help me please?
  5. Clear! you have a WIM with 2 images This is not clear! What do you mean for burn a wim file into a DVD? Yeah, now I understood! You want something like Recovery CDs vendors give us until few years ago. Maybe first of all you must understand if a file-based imaging tool (like imagex) is better for your businness then a byte-based one (like acronis, ghost and so on...) Usually you use imagex if you think you will change often it. If this will not occour maybe Acronis (or another) gives you less problems. It seems like the last one is your case but this is something YOU must decide. But than... what I give you is what you need (I'm talking about the 'tutorial') Build a recovery CD means make a bootable ISO image that run Windows PE that run cdmlines.txt that run imagex that explode the image from dvd to hd. If you read it again you see at the end the command oscdimg -n -b<destination>\etfsboot.com <destination>\ISO <destination>\winpe_x86.iso that build an iso image (winpe_x86.iso) starting from ISO folder content. It means that if you put your image into this folder it will be burned into the ISO image (so in your DVD too). That's easy (isn't it?) The hardest work is to customize Windows PE to automatically do the work (launch imagex and explode image into c:) AFAIK Acronis Loader is a customized version of Windows PE
  6. Maybe I understood your trouble Do you want to explode the RE image and append your C image to have an original restored image with your files? If yes make the work done for yourimage.wim 2 times so wpeinit format c: imagex /apply d:\yourfolder\winre.wim 1 C:\ imagex /apply d:\yourfolder\C_image.wim 1 C:\ and put them into \iso\yourfolder dir Other issues (CDROM and so on) still remain!
  7. You must have 2 .WIM images 1) your image captured from a (clean and syspreped should better) Windows Installation. This should be putted into a custom folder under the ISO directory so it will be accessible by the batch script 2) a clear Windows PE image (boot.wim) that you will customize and use for loading a live environment that do "cloning" job. This must be mounted into mount dir and customized; when finished copy it in \ISO\sources replacing the original one. When I say "customize" I mean edit cmdline batch script for automatically do all the work you want by shell. If you don't know enough on batch scripting this is another issue For Example: Maybe when PE is loaded your RAM DISK is X:, your HDD C: and CDROM D: X: is the content of boot.wim that is loaded in a ram drive and it's the windows pe os C: is your HD with your Windows (XP) installation D: is your DVD with the content of ISO folder (so with sources\boot.wim already loaded and yourfolder\yourimage.wim) A boot.wim customized with a cmdline batch file like this wpeinit format c: imagex /apply d:\yourfolder\yourimage.wim 1 C:\ will do what you want (OK, this is very simple;). But you can have other troubles like: 1) I'm sure that CDROM have D: drive letter? (if you have another HD partition for example windows will map the cdrom E:) 2) I'm sure that C: exist? If I have no partition?
  8. Use in-line parameters net use Z: \\YOURPC\YOURSHARE /user:YOUR_DOMAIN_OR_MACHINE_NAME\YOUR_USER_NAME YOUR_PLAINTEXT_PASSWORD
  9. Boot from Win PE and capture your XP installation (with imagex /capture command, you readed before) Once you have a WIM file 1-install Windows AIK 2-run Windows PE Tools Command Prompt 3-type : copype.cmd <arch> <destination> (where arch is x86 or amd64 and destination is a path to a work folder (i.e. c:\winpe)) imagex /mountrw <destination>\winpe.wim 1 <destination>\mount 4- create your own folders (and files) under <destination>\mount\ or <destination>\ISO\ (copy imagex.exe too!) Remember that what you put into mount dir will increase your boot.wim image and RAM usage; if you can use ISO instead (that will be store only on CDROM/DVD - you must put here your .WIM image) 5- add custom command-line scripts (like launch imagex and diskpart to put image onto destination) in Windows PE by using Startnet.cmd. By default, Windows PE includes a Startnet.cmd script located at %SYSTEMROOT%\System32 of your custom Windows PE image. Startnet.cmd currently starts Wpeinit.exe (don’t delete it, you need it for eth and pnp support! ) Remember that you can use %SYSTEMROOT% environment variable to windows folder path; to get cdrom path you should use a 3rd party tool like getcd (http://www.willowhayes.co.uk/); this you should put into MOUNT folder! 6- type: imagex /unmount /commit <destination>\mount (this will write changes) copy <destination>\winpe.wim <destination>\ISO\sources\boot.wim (this will replace original boot file) oscdimg -n -b<destination>\etfsboot.com <destination>\ISO <destination>\winpe_x86.iso (this will create a bootable iso image under your <destination> dir) copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim 7- Burn ISO image I made an unattended hardware indipendent Windows XP installation using this: http://technet2.microsoft.com/WindowsVista...3.mspx?mfr=true
  10. 1-install Windows AIK 2-run Windows PE Tools Command Prompt 3-type : copype.cmd <arch> <destination> (where arch is x86 or amd64 and destination is a path to a work folder (i.e. c:\winpe)) imagex /mountrw <destination>\winpe.wim 1 <destination>\mount 4- create your own folders (and files) under <destination>\mount\ or <destination>\ISO\ (copy imagex.exe too!) Remember that what you put into mount dir will increase your boot.wim image and RAM usage; if you can use ISO instead (that will be store only on CDROM/DVD - you must put here your .WIM image) 5- add custom command-line scripts (like launch imagex and diskpart to put image onto destination) in Windows PE by using Startnet.cmd. By default, Windows PE includes a Startnet.cmd script located at %SYSTEMROOT%\System32 of your custom Windows PE image. Startnet.cmd currently starts Wpeinit.exe (don’t delete it, you need it for eth and pnp support! ) Remember that you can use %SYSTEMROOT% environment variable to windows folder path; to get cdrom path you should use a 3rd party tool like getcd (http://www.willowhayes.co.uk/); this you should put into MOUNT folder! 6- type: imagex /unmount /commit <destination>\mount (this will write changes) copy <destination>\winpe.wim <destination>\ISO\sources\boot.wim (this will replace original boot file) oscdimg -n -b<destination>\etfsboot.com <destination>\ISO <destination>\winpe_x86.iso (this will create a bootable iso image under your <destination> dir) copy c:\winpe_x86\winpe.wim c:\winpe_x86\ISO\sources\boot.wim 7- Burn ISO image I made an unattended hardware indipendent Windows XP installation using this: http://technet2.microsoft.com/WindowsVista...3.mspx?mfr=true
×
×
  • Create New...