HyperV wallpaper1 anyway to remove the Server 2008 reference on the can the robot is holding? i tried to do it ages ago but i made a right mess of it, and i gather photoshop can do a better removal/hiding of that area?
MRP 100.1 is at RC stage (soon to be 101.0 RC1) Query Tool 74.0 is in final testing and so far all seems to be running ok, apart from a few spelling mistakes which have now been sorted.
Hi again, I made it work correctly using sysprep putting thos files in C:\Windows\Setup\Scripts which is the equivalent to the OEM folder in the ISO, so I have the branding and activation working but it seems the MRPConfig.ini is not applied... Anyone would have a pointer? I have looked at the log setupact.log and there are no trace of MRP anywhere. What is actually calling MRPConfig.ini when it's in the ISO? Is the OOBE.cmd actually executing all executables from the Scripts folder? Or just the DeCompile.exe which in turn search for MRPConfig.ini?
decompile.exe uses the MRPConfig.ini to action any options used. Without the ini file MRP will just auto brand the OS, (if it can via DMI entries), and attempt OEM activation if possible. MSDM/HWID (Digital License) is done via online m$ servers.
OOBE.cmd starts Decompile.exe, Decompile.exe creates the scripts and one of them looks for MRPconfig.ini
If the ini file is in the Scripts folder where decompile.exe and oobe.cmd is then it should of 'seen' the ini file...
If mrp had run, there will be a Project.log on the C:\ (root of the system drive)... The oobe.cmd has entries that are 'run' in sequence which calls decompile, which extracts the required MRP files, this in turn runs the install part etc - this also checks for the config ini file and takes action on any options the user has used.
Yes! So it appears to run correctly! You could add this to the "features" that it can also run sysprep OOBE mode once Windows is already installed!
It will have run MRP time you got to the desktop in audit mode, which would of branded etc 'that' pc it was audited on. The branding would only be for that one pc so if it was a 'Acer' for example and then you had set audit to reseal to oobe so it asks the usual user username/password and other oobe related settings for another pc, it would still only be 'Acer' branding as the project had already been run. So installing that sysprepped install on another brand/pc would not re-brand it to the other pc's DMI it would be preset to Acer in this example. MRP was not designed to be used in that way and it may not be possible without a bit of a hassle. Unless the newly sysprepped install.wim could be mounted and the project files added to the \Windows\Scripts folder and unmounted which i dont think is possible as DISM/ImageX would report that the wim is not serviceable and you end up with a shafted installation.