1. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,412
    15,485
    210
    Preparing for ToolKit v1.03 release. A lot of features awaited are added to the ToolKit. just wanted a help about these things

    I want to Import Registry Settings from File to WIM, I know about the reg load, add and unload method. it's easy for a single line registry key import. but for a registry file, is there any easy method or do I have to make changes in the registry file to reflect the reg load <path> and then can I import the registry file to the wim.
     
  2. btf-tribal

    btf-tribal MDL Junior Member

    Jul 9, 2009
    70
    12
    0
    Hello MSMG,
    I have the same problem as dante96.
    I select integrate ga rollup it says that 'the folder is empty', but the updates are in there.
    OS: Windows 8.1 German x64

    is it possible that the command Administrators (in german Versions it`s called Administratoren) caused the Problems?
     
  3. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,412
    15,485
    210
    Well toolkit saying getting os architecture : x86, this is not for effect. but it really detects the working os architecture. but the batch file to exe packer am using always does display the os architecture as x86 even when working on x64 os. this is the bug of the packer not the toolkit. am just working on it.

     
  4. btf-tribal

    btf-tribal MDL Junior Member

    Jul 9, 2009
    70
    12
    0
    No log file in log Folder.

    Output test1:

    Output test2
     
  5. btf-tribal

    btf-tribal MDL Junior Member

    Jul 9, 2009
    70
    12
    0
    i`m using the MSDN Images

    de_windows_8_1_x64_dvd_2707227.iso
    de_windows_8_1_x86_dvd_2707398.iso
     
  6. dante96

    dante96 MDL Junior Member

    Nov 1, 2013
    60
    9
    0
    #70 dante96, Dec 13, 2013
    Last edited by a moderator: Apr 20, 2017
    Log (test1):
    Code:
    
    Deployment Image Servicing and Management tool
    Version: 6.2.9200.16384
    
    
    Details for image : C:\MSMG\DVD\sources\install.wim
    
    
    Index : 1
    Name : Windows 8.1 Pro x86
    Description : Windows 8.1 Pro
    Size : 8.370.058.901 bytes
    Architecture : x86
    Hal : acpiapic
    Version : 6.3.9600
    ServicePack Build : 16384
    ServicePack Level : 0
    Edition : Professional
    Installation : Client
    ProductType : WinNT
    ProductSuite : Terminal Server
    System Root : WINDOWS
    Directories : 13197
    Files : 62457
    Created : 22/08/2013 - 16.04.51
    Modified : 04/12/2013 - 16.03.20
    Languages :
    it-IT (Default)
    
    
    The operation completed successfully.
    log (test2):
    Code:
    
    Strumento Gestione e manutenzione immagini distribuzione
    Versione: 6.2.9200.16384
    
    
    Dettagli per l'immagine: C:\MSMG\DVD\sources\install.wim
    
    
    Indice: 1
    Nome: Windows 8.1 Pro x86
    Descrizione: Windows 8.1 Pro
    Dimensioni: 8.370.058.901 byte
    Architettura : x86
    HAL : acpiapic
    Versione : 6.3.9600
    Build Service Pack : 16384
    Livello Service Pack : 0
    Edizione : Professional
    Installazione : Client
    Tipo prodotto : WinNT
    Famiglia di prodotti : Terminal Server
    Radice sistema : WINDOWS
    Directory : 13197
    File : 62457
    Data creazione : 22/08/2013 - 16.04.51
    Data modifica : 04/12/2013 - 16.03.20
    Lingue :
    it-IT (valore predefinito)
    
    
    Operazione completata.
     
  7. btf-tribal

    btf-tribal MDL Junior Member

    Jul 9, 2009
    70
    12
    0
    test1 english:

    test 2 german:

     
  8. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,412
    15,485
    210
    Ok, did the program output displayed "GA Updates found at <MSMG\Updates\GA\x86> Folder". the next release of toolkit will fix these issues..

     
  9. dante96

    dante96 MDL Junior Member

    Nov 1, 2013
    60
    9
    0
    #73 dante96, Dec 13, 2013
    Last edited by a moderator: Apr 20, 2017
    test 1:
    Code:
    
    Source File <DVD\sources\install.wim> Exists...
    
    
    Thank You...
    
    
    
    
    Windows 8.1 and Server 2012 R2 GA Rollup Updates Folder is Empty...
    Copy the Rollup Updates to C:\MSMG\Updates\GA\ Folder...
    
    
    Sorry...
    
    
    
    
    
    
    Premere un tasto per continuare . . .
    test2:
    Code:
    
    Source File <DVD\sources\install.wim> Exists...
    
    
    Thank You...
    
    
    
    
    Windows 8.1 and Server 2012 R2 GA Rollup Updates Folder is Empty...
    Copy the Rollup Updates to C:\MSMG\Updates\GA\ Folder...
    
    
    Sorry...
    
    
    
    
    
    
    Premere un tasto per continuare . . .
     
  10. RickSteele

    RickSteele MDL Addicted

    Nov 12, 2009
    833
    483
    30
    I attempted to use MSMG to integrate Windows Media Center, but, several errors occured.

    1) It does not recognise anything but Windows 8.1 x86
    2) No index choice dialogue popped up
    3) It does not recognise my Windows 8.1 ADK installation, so, forces me to quit because I won't download and install. (It already is installed)

    I am running Windows 8.1 Pro x64 (Full Retail). I placed MSMG at the root of C: (C:\MSMG). My retail Windows 8.1 DVD was copied to the MSMG DVD folder.
    I integrated Windows Media Center successfully myself using DISM, but, when I go to use it in a fresh install I get a fatal error "image not found". Therefore I'm hoping your program will eliminate this so I can install ".....with Media Center Edition".

    Thanks very much
     
  11. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,412
    15,485
    210
    First of all I have tested the ToolKit several times with both x86 and x64 OS. For every new version, I do test all the features properly so that their is no error. In your case "Integrate windows media center add-on"

    1) I have tested and used both the x86/x64 version of windows 8.1 pro to integrate wmc add-on. it works flawlessly.

    2) In Next version of Toolkit there will be a option to choose the wim index, when the OS source is a Windows 8.1 AIO.

    3) I have put every condition to check for existence of WADK Installation. The ToolKit checks for the default installation folder for the presence of WADK.
    C:\Program Files\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools
    or
    C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools

    If you have installed WADK to a different folder, then Toolkit will not function or else you have to remove the existing WADK Install and allow the Toolkit to install the WADK.

    In Next version of Toolkit, I will add a option to make the ToolKit Portable so that the WADK Tools can be placed in the ToolKit Bin Folder.

    4) You can keep the ToolKit files in any drive or folder, I have made the ToolKit to function to work in any folder expect there should not be a space in between folder names.

    5) MSMG ToolKit v1.03 is ready and will be uploaded in a while. so test this new version and see what happens.


     
  12. luke7

    luke7 MDL Novice

    Jul 29, 2009
    49
    8
    0
    Thanks for your program.
    I have integrated WMC to my windows 8.1 install and it works fine.
    However, I cannot get the Pre-Activation to work.
    Are you sure you can auto activate windows 8.1 with your Data.dat, Tokens.dat, cache.dat, when it is a backup from online activation?
    Have you tested a clean install without network?
    If yes, how does it work?
    Must I manuel copy the 3 token files to your MSGN tool folder? And what is the location I must copy the 3 files to (folder name)?
     
  13. RickSteele

    RickSteele MDL Addicted

    Nov 12, 2009
    833
    483
    30
    Thanks for the reply and info, but, unfortunately I will not allow ADK to be installed anywhere else but where I want it. (Just one of those things I'm very particular about :eek: ) Please understand I am not trying to be rude or anything; this is a great program and I have every confidence you test it thoroughly. Therefore, until MSMG can recognise my ADK installation I will be unable to use it.

    Thanks very much again. :worthy:
     
  14. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,412
    15,485
    210
    Yes I have Tested the Pre-Activation without network and its Works. you have to manually copy the pre-activated tokens files "data.dat", "tokens.dat" from \Windows\System32\spp\store\2.0 and the "cache.dat" from \Windows\System32\spp\store\2.0\cache folder to <MSMG Folder>\Packs\PreAct Folder.

    Make sure you have activated the os with all the necessary drivers installed and then copy the tokens files.

    Note: If there is any changes in the hardware after the activation then the Activation will break.


     
  15. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,412
    15,485
    210
    No issues, i have made the necessary changes to the next version to make the ToolKit portable so u don't have to install WADK Installation every time on a clean OS. it will take some time for testing the next version. but right now am posting a new version without the above changes. so you have wait for the next version.

     
  16. MSMG

    MSMG MDL Developer

    Jul 15, 2011
    6,412
    15,485
    210
    Updated MSMG ToolKit to v1.03

    Changelog:

    v1.03
    + Added a New Main Menu Item - Integrate Custom Packs.
    > Moved the Main Menu Item - Integrate Custom Patches to Main Menu Item - Integrate Custom Packs.
    + Added a Feature to Integrate Windows Vista & Windows 7 Games Pack.
    + Added a Feature to Integrate Custom Windows Recovery Environment (WinRE.wim).
    + Added a New Main Menu Item - Remove/Customize Metro Apps.
    + Added a Feature to Remove Default Metro Apps.
    + Added a Feature to Delete Default Metro Apps Association.
    + Added a Feature to Import Default Metro Apps Assoication from XML File.
    + Added a Feature to Export Default Metro Apps Association to XML File.
    + Added Missing Terminal Server Patch Registry Settings.
    + Updated CleanUp Tool.
    + Added Better Display to Show List of WIM Images Available to Service.
    + Fixed the Bug - "GA/HotFixes Updates Folder is Empty" when the Host OS is a Non-English OS.