Quote:
Been there, done that, have the divorce

It apparantly does not work on all hardware configurations as advertised. I had to use a hack:
Quote:
The cfg.ini did not work for me. The install would not read it. If you have issues useing this way try this
As soon as you are greeted with the screen asking if you want a new install or to repair a previous one push Shift + F10 to bring up cmd.
Type "notepad.exe" without quotes then click file open and browse to sources/SKU/SERVERHOMEPREMIUM.def (you may have to select all files at the bottom so you can see the .def file).
From inside here you can change your amount of ram, number of cpu cores, HDD space, and processor speed to suit your needs. Save and close notepad.
Type "wpshell.exe" without quotes and hit enter => setup will restart with the new parameters. Hope this can help someone out and thanks again.
The cfg.ini did not work for me. The install would not read it. If you have issues useing this way try this
As soon as you are greeted with the screen asking if you want a new install or to repair a previous one push Shift + F10 to bring up cmd.
Type "notepad.exe" without quotes then click file open and browse to sources/SKU/SERVERHOMEPREMIUM.def (you may have to select all files at the bottom so you can see the .def file).
From inside here you can change your amount of ram, number of cpu cores, HDD space, and processor speed to suit your needs. Save and close notepad.
Type "wpshell.exe" without quotes and hit enter => setup will restart with the new parameters. Hope this can help someone out and thanks again.
Thanks to esullivan here: http://forums.connecteddigitalworld....__20#entry3618
I actually had to combine the two things, i.e. insert the USB stick with the cfg.ini file in the root as well as alter the hardware min requirement file (I changed HDD from 160 to 30 Gb). One without the other did not work for me. It did not run as an unattended setup, but it started up without having to choose OS disk etc.
You might also try adding [InitialConfiguration] to the cfg.ini file, if just having the WinPE lines doesn't work. And, like said earlier, try ALL USB ports before giving up...:
[WinPE]
ConfigDisk=1
CheckReqs=0
WindowsPartitionSize=MAX
[InitialConfiguration]
Language=en-US
Locale=en-US
Country=US
Keyboard=00000409
AcceptEula=true
AcceptOEMEula=true
ServerName=SERVER
PlainTextPassword=Password
PasswordHint=Password hint
Settings=All
Make sure you save it as an .ini file and not a cfg.ini.txt file ;-)
You wrote you saved it as a notepad file. That is a .txt file unless you choose "all file types" before saving!
Another important requirement:
Quote:
Its worth noting that for the above to work correctly, boot priorities must be correctly set up. I recently did a reinstall and kept hitting an error. The config file was being read as it was being edited to say it had, however install was failing. After a refresh (of my brain) I realised this cfg file hits a particular hard disk ID, for which for me it required it to be the PRIMARY boot device. I have a feeling this will really depend on which SATA port the install HDD is placed into, but haven’t had time to test properly.
Therefore, if you experience an issue where the INI file is identical to the above, and its definitely being read (you can tell by windows flag after read, which incidentally needs removing each time) then change your boot config. Also MAKE SURE ONLY THE HDD YOU WISH TO INSTALL TO IS IN THE PC (i.e. no data drives, add them after install) to make sure you don’t accidentally overwrite it!
Its worth noting that for the above to work correctly, boot priorities must be correctly set up. I recently did a reinstall and kept hitting an error. The config file was being read as it was being edited to say it had, however install was failing. After a refresh (of my brain) I realised this cfg file hits a particular hard disk ID, for which for me it required it to be the PRIMARY boot device. I have a feeling this will really depend on which SATA port the install HDD is placed into, but haven’t had time to test properly.
Therefore, if you experience an issue where the INI file is identical to the above, and its definitely being read (you can tell by windows flag after read, which incidentally needs removing each time) then change your boot config. Also MAKE SURE ONLY THE HDD YOU WISH TO INSTALL TO IS IN THE PC (i.e. no data drives, add them after install) to make sure you don’t accidentally overwrite it!
http://forums.connecteddigitalworld....0gb/#entry2963
Last, once you get it going, remember to remove the USB key when the installation restarts the machine the first time!
Good luck!




























