New Question

# Scott's profile - activity

 2015-02-27 02:02:11 +0300 received badge ● Famous Question (source) 2015-02-04 02:36:09 +0300 received badge ● Notable Question (source) 2015-02-03 09:41:05 +0300 received badge ● Scholar (source) 2015-02-03 09:41:01 +0300 commented answer MaaS Windows PE Boot Images Thanks Gabriel, good to know, I will look for your update on the wiki for further information. I am excited to work towards getting this up and running. 2015-02-03 04:13:06 +0300 received badge ● Popular Question (source) 2015-02-02 02:31:51 +0300 commented answer MaaS Windows PE Boot Images Gabriel, Thanks for your reply, I have one question. When you say that MaaS doesn't need a generated PXE image for version 1.7, does this mean I can simply tar the .iso file in this case? or how would one go about doing it? Based on the later comment this feature seems not yet to be implemented? 2015-01-28 05:50:05 +0300 asked a question MaaS Windows PE Boot Images I need to create an image for use with MaaS. The only solution that seems to be working for various individuals is your solution located here: http://wiki.cloudbase.it/maas I have so far had to modify many variables throughout the deployment of these scripts to even get it to work as far as it has... its a bit frustrating to be honest. However that being said I wasn't able to figure out a solution this time. This is my setup... Additionally I have listed my changes to the scripts. And various things that are not mentioned during execution. ADK 8.1 Windows 8.1 Pro As you need to run these scripts in a powershell terminal you need to set up your computer to be able to do so. By default windows is set to a restricting policy and therefore the scripts will not run without changing this policy to allow the script to do so. This is because the scripts are unsigned. Set-ExecutionPolicy RemoteSigned Depending on your environment and the version's of software downloaded by the script you need to change variables in the first script by the name of BuildWinPE.ps1 [string]$ADKVersion = "8.1", [switch]$ForceADKInstall = $true Once that is finished the next issue is this should all be run under an administrator powershell. The$TFTPBlockSize variable did not seem to be passed correctly to the script bcdcreate.cmd and therefore needed to be set manually within the said script. Doing so however is tricky since the application creates that script when it runs. Which means you need to have the file opened/modified from a previous try and save it on top of the newly created file as soon as it appears. Changed: set TFTPBLOCKSIZE=%1 --> 8192 If the script has already run and failed once you will need to clear out your old BCD configs manually as the command %BCDEDIT% -create {ramdiskoptions} -d "will fail (although likely harmlessly) The following is where I am currently stuck at... How do I modify the current code, or if there is somewhere else I went wrong please let me know. C:\winpe\bin>for /f "tokens=3" %%a in ('%BCDEDIT% -create -d "Windows PE" -appli cation osloader') do set GUID=%%a %%a の使い方が誤っています。 (The use of %%a is incorrect) This is output from the set command showing what GUID was set to ... the meaning doesn't matter much its clearly set incorrectly which explains why my next commands failed. GUID=は正常に作成されました。 C:\winpe\bin>%BCDEDIT% -set %GUID% systemroot \Windows 指定されたエントリを参照中にエラーが発生しました。 (Error occurred during reference to the specified entry.) 指定されたファイルが見つかりません。 (Specified file cannot be found (What file??)) I greatly appreciate the help in advance.