Jump to content

myselfidem

Member
  • Posts

    2,515
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Switzerland

Everything posted by myselfidem

  1. Hello sjoerdhooft I think here is a solution, I've tried successfully! At first create the folders $OEM$ inside: %systemdrive%\Win7\sources 1 - With 7Customizer skip the key of your Windows version. You can see a key inside Autounattend.xml (généric I think. Don't deleete tis one: I think you know that!) 2 - Create a folder $OEM$ inside E:\Win7\sources\$OEM$ 3 - Inside the folder $OEM$ create a folder $$. 4 - And inside $$ create a folder SETUP and inside SCRIPTS. 5 - Use the cmd "SetupComplete.cmd" (gives you Admin rights at first run). 6 - If you want preserve the activation of your copy: copy/paste the file "Tokens.dat" and "pkeyconfig.xrm-ms" (for x64) inside SetupComplete.cmd Example for Windows x86 SetupComplete.cmd @echo off ::Install Product key and autoactivation TAKEOWN /F %SystemDrive%\Windows\System32\cmd.exe net stop sppsvc DEL /Q "%SystemDrive%\Windows\ServiceProfiles\NetWorkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\Tokens.dat" COPY /Y "%~dp0tokens.dat" "%SystemDrive%\Windows\ServiceProfiles\NetWorkService\AppData\Roaming\Microsoft\SoftwareProtectionPlatform\" net start sppsvc cscript %systemroot%\System32\slmgr.vbs -ipk XXXXX-XXXXX-XXXXX-XXXXX-XXXXX (your valid key) cscript %systemroot%\System32\slmgr.vbs -ato EXIT In this example the activation is preserving. For Windows x64 you need also copy/paste: For more information you can use: Run(you can see your partial valid key) %systemdrive%\Windows\System32\slmgr.vbs -dlv You can see at this time that your Key is registrated! And all is fine!
  2. Hello I've made a new 7Customizer French guide: version 7Customizer_0.4.4 7Customizer French guide
  3. Hello I've updated the Se7en_UA French guide: version 6.2.6 Here: French guide
  4. Hello You can add this Tweak: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System] "VerboseStatus"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced] "Start_ShowRun"=dword:00000001 "TaskbarSmallIcons"=dword:00000001
  5. I didn't burn it but used the ISO file in VMware... Hello I remember it happens to me one time - with the valid and correct key - but I don't really remember the reason ! You can try to make a new ISO file, but before deleete all the files inside the folder "work" except: mount; Themes; bootorder.txt; etfsboot.com; EXTRACT.EXE (originals files and folders). And at the section: unattend; write inside all fields, because if you live some fields blank, setup may fail. I hope that will help you Well, that didn't work either. I finally removed the key from the unattended setup and al doing it now without a key. It's too bad but I don't have another solution, especially since the key works when the installation is done. So weird... You said Hello Maybe you can try the tool MSKeyViewer for checking the key inside the registry: MSKeyViewer I've found some help here: http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/2dc49680-962e-403d-8c95-57b40891bcc1 Maybe you can contact Microsoft and asking what is the problem with Autounattend.xml? Help and support Microsoft: http://windows.microsoft.com/en-us/windows7/Windows-7-activation-error-invalid-product-key https://support.microsoft.com/oas/default.aspx?gprid=14019&st=1 I hope that will help you! An other way is to make changes inside Autounattend.xml and add at pass="specialize": You can use Windows System Image Manager (WSIM) and validate the file Autounattend.xml after changes. At first select your image Windows. Example for x86: <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> <RegisteredOrganization>MyOrg</RegisteredOrganization> <RegisteredOwner>myselfidem</RegisteredOwner> More help for Autounattend.xml: Maybe it's the solution.
  6. I didn't burn it but used the ISO file in VMware... Hello I remember it happens to me one time - with the valid and correct key - but I don't really remember the reason ! You can try to make a new ISO file, but before deleete all the files inside the folder "work" except: mount; Themes; bootorder.txt; etfsboot.com; EXTRACT.EXE (originals files and folders). And at the section: unattend; write inside all fields, because if you live some fields blank, setup may fail. I hope that will help you Well, that didn't work either. I finally removed the key from the unattended setup and al doing it now without a key. It's too bad but I don't have another solution, especially since the key works when the installation is done. So weird... You said Hello Maybe you can try the tool MSKeyViewer for checking the key inside the registry: MSKeyViewer I've found some help here: http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/2dc49680-962e-403d-8c95-57b40891bcc1 Maybe you can contact Microsoft and asking what is the problem with Autounattend.xml? Help and support Microsoft: http://windows.microsoft.com/en-us/windows7/Windows-7-activation-error-invalid-product-key https://support.microsoft.com/oas/default.aspx?gprid=14019&st=1 I hope that will help you!
  7. I didn't burn it but used the ISO file in VMware... Hello I remember it happens to me one time - with the valid and correct key - but I don't really remember the reason ! You can try to make a new ISO file, but before deleete all the files inside the folder "work" except: mount; Themes; bootorder.txt; etfsboot.com; EXTRACT.EXE (originals files and folders). And at the section: unattend; write inside all fields, because if you live some fields blank, setup may fail. I hope that will help you
  8. Hello Blue I see your message on Twitter for XP: I've tried successfully 7Customizer_0.4.4 with Windows XP Pro SP3 x86 and Unattended Install for Windows 7 Ultimate x86 (same architecture)! I use WAIK for Windows 7 (KB3AIK_FR.iso)-installed successfully. It takes more time but the result is all fine. Here is the log file: And all is fine with the test on VirtualBox. I've made also a new French.lng for 7Customizer_0.4.4: French.lng 0.4.4 Regards
  9. Yeah, I tried and worked like a charm. It's almost like the key is only valid for a manual install and not for an unattended... I'm totally clueless... Hello! Which is the software you use to burn your ISO file made by 7Customizer?
  10. @Blue Yes Blue, Because I see that some notes were missing and I've made images with French language. Yes, the guide inside the link (thread) is updated Regards
  11. Hello Blue Yes. I've updated the guide And if you want, I can add "The Table of Content" and "Functions and Features". Regards
  12. Hello Blue. I've made a new "French guide" for 7Customizer My link Regards
  13. Thanks johnhc. This image were found by MaxXPsoft and she's inside the "spwizimg.dll" and "imageres.dll" for x86 and x64 made by himself. I've just resized this image for 1024x768
  14. Hello Blue I see just some little errors in the file "French.lng". I give you the new one. My link Regards
  15. You can find some help for 7Customizer with Windows XP SP3 at he fisrt post: Extract: Regards
  16. Hello Blue Thanks for your answers. But it's not possible to modify the batch file during the exécution of this one because 7Customizer is running! Maybe there is a possibility to make changes? But at this time this is not an issue! Regards
  17. Hello Blue. Thank you very much for your good and nice software. I see the command line inside the batch works fine and "Everyone" is translated in my computer in french language "Tout le monde": However, I think the commands "rd" and "md" are working fine if I launch these one in my computer but not when some programs are running for theirs installations. However the folders inside "Themes" are really deleeted and all is fine! But I've made the experience and it's work fine if I change to: RMDIR /S /Q "work\Themes" MKDIR "work\Themes" I see just a little detail, inside the window when you click the tab Tweaks\Services at the top, in the left pane inside the word "serice" the letter v is missing. Regards
  18. @jslegers I think it's better to expand "7Customizer_0.4.4.rar" on a partition (C:\; H:\; F:\,...) and not on a temp folder. Regards
  19. @jslegers Hello. I think you have right, the problem is that you try to make an unattended installation for Windows 7 64 bits on a 32 bits laptop. When I've tried I had the same problem. I think it's needed to have the same architecture x64 installed for make an unattended Win7 x64 and the same for x86 (32 bits).
  20. You can find some help here: http://driverpacks.net/docs/beginners-guide-windows-xp Tutorial: http://users.telenet.be/jtdoom/basetute/Eng_tut6b.htm Extract: Caution Once the DriverPacks are integrated into your Windows source, you will not be able to integrate any patches or hotfixes without breaking the DriverPacks. This means that you should run nLite and the RyanVM Integrator before DriverPacks BASE! The recommended order is: 1.RyanVM Integrator 2.nLite 3.DriverPacks BASE When I try to slipstream IE8 inside Windows XP I have errors and it's the reason I integrate only IE7 with nLite 1.4.9.1. And all is fine like this! I think that jaclaz give you a good suggestion for your winnt.sif: In the section [Components] you can try to don't add these options or deleete: WDSearch=off WgaNotify=off BitLockerToGo=off You can also add this reg file for IE7, if you have slipstreamed this one with nLite. Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main] "RunOnceComplete"=dword:00000001 "RunOnceHasShown"=dword:00000001 [HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Main] "RunOnceComplete"=dword:00000001 "RunOnceHasShown"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Internet Connection Wizard] "Completed"=hex:01,00,00,00 I hope that will help you.
  21. Hello Blue I see that "S-1-1-0" is for Everyone ("Tout le monde") but this command don't work for localised versions: cacls "work\Themes" /e /t /p "S-1-1-0":F If I write "Tout le monde" it works; and if I write "S-1-1-0" don't work. And I don't know why? But this one works fine: icacls "work\Themes" /grant *S-1-5-32-544:F Here is the French.lng(zip) for 7Customizer_0.4.3. Regards
  22. No of course! If I use nLite I add these two rows, inside the section [unattended] of my winnt.sif: TargetPath=\WINDOWS OemFilesPath="..\$OEM$" I was saying that If you want use nLite and DriversPack, it's needed to launch DriversPack at last; in the end. But you must untouch your winnt.sif after that! If you don't use nLite it's the same for DriversPack: you can modify your winnt.sif only before to launch DriversPack; and after don't modify your "winnt.sif". It's seems that the problem is with Windows Update.
  23. @Escorpiom Thank you very much for your feedback!
×
×
  • Create New...