kesshin Posted October 13, 2010 Posted October 13, 2010 Hello everyone - I am a long time reader, first time poster.I have successfully created an unattended, bootable .iso for Server 2008 R2 using vLite. I have also played around with RT Server Customizer utility. However, I noticed that if I try to open the iso with MagicISO, modify the Autounattend.xml file, and save as a new iso, the new iso will no longer work even though I have not modified anything in the OSImage fields of the xml file. I get the following error message:"Windows could not collect information for [OSImage] since the specified image file [install.wim] does not exist."Even without using a utility such as vLite, I thought that all one has to do is create an Autounattend.xml file and save it in the root of the iso (or DVD) and it will work as long as the .xml format is correct. It appears however, when using vLite or RT Customizer the install.wim file is being modified so just saving a "working" Autounattend.xml file to the root of the iso or disc does not work.Is there a way to create an unattended, bootable .iso for Server 2008 R2 just using WAIK, a bootable Server 2008 iso, and MagicISO? Having to load the install media for every small modification and then saving a new iso is taking forever...Thanks in advance for your help!
jaclaz Posted October 13, 2010 Posted October 13, 2010 However, I noticed that if I try to open the iso with MagicISO, modify the Autounattend.xml file, and save as a new iso, the new iso will no longer work even though I have not modified anything in the OSImage fields of the xml file. The general idea about ISO is that they are READ ONLY..iso editors usually work, BUT, expecially with bootable .iso they often fail.The ONLY workaround you have (short of re-creating the .iso with OSCDIMG or mkisofs, which is what you should normally do) is to create a "padded" .xml file (i.e. a file with a number of spaces at the end) large enough to contain all possible modifications, and use any dd-like program or Winimage (Shareware) that has this feature, to replace this "fattened" UNATTENDED.XML with the edited file with the EXACT SAME size. In other words, supposing that your standard UNATTENDED.XML is 3487 bytes in size, you add to it, say 113 trailing spaces, so that it becomes 3600 bytes, then create your "master" .iso.When you modify the UNATEENDED.XML, you add or remove as many of the trailing spaces so that the size remains EXACTLY 3600 bytes, then you use a dd-like program or a hex editor or winimage to replace the file in the .iso image.jaclaz
Tripredacus Posted October 13, 2010 Posted October 13, 2010 Hoenstly, you should build your install media without the XML file in it. Then put your XML onto a USB key (in the root of course) and have it plugged in when you boot off the DVD. Server 2008, Vista and Windows 7 will look in the root of all drives for the Autounattend.xml file if it is not on the install source. This also gives you the ability to use different XML files with the same install media.
kesshin Posted October 14, 2010 Author Posted October 14, 2010 (edited) Thank you very much for your replies. Just to give you a little bit more background, I am using VMware ESX 4i and I wanted a way to install VMs using an .iso. I know about (and use) WDS and sysprep but there are certain situations in our environment where deploying a "standard" VM by iso is more convenient. For some reason however, I tried one more time and it worked. I must have mixed up an .xml file or the install media. I will retrace my steps and try to duplicate the success. I have .xml files and isos scattered all over the place so I need to clean up my test bed...@jaclaz - That is a great idea - I will give that a try!@Tripredacus - Unfortunately, the host machine that I am using for ESX 4i does not recognize the USB device that I have so I cannot add it to a VM. When it does work though, it is definitely a lot easier! Actually, I guess I could create an iso with just the Autounattend.xml and add another virtual CD to the VM - I will give that a try someday. Thank you again for your help. If I "discover" anything new or useful to contribute, I will make sure to post. Edited October 14, 2010 by kesshin
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now