<div dir="ltr">Hi Joe,<div><br></div><div>I actually installed Windows cloud-init first, grabbed its unattend file and moved it to the sysprep dir under C:\Windows\System32\sysprep, then modified it to insert my SPLA keys. The unattend file that they provide automatically does the password prompt. Once you have moved the unattend file there, you'll want to open a command prompt, browse to C:\Windows\System32\sysprep, and run sysprep.exe /unattend:unattend</div>
<div><br></div><div>Here's what the unattend file looks like:</div><div><div><?xml version="1.0" encoding="utf-8"?></div><div><unattend xmlns="urn:schemas-microsoft-com:unattend"></div>
<div> <settings pass="generalize"></div><div> <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="<a href="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>"></div>
<div> <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls></div><div> </component></div><div> </settings></div><div> <settings pass="oobeSystem"></div><div> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="<a href="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State</a>"></div>
<div> <OOBE></div><div> <HideEULAPage>true</HideEULAPage></div><div> <NetworkLocation>Work</NetworkLocation></div><div> <ProtectYourPC>1</ProtectYourPC></div>
<div> <SkipMachineOOBE>true</SkipMachineOOBE></div><div> <SkipUserOOBE>true</SkipUserOOBE></div><div> </OOBE></div><div> </component></div><div> </settings></div>
<div> <settings pass="windowsPE"></div><div> <component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="<a href="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State</a>"></div>
<div> <UserData></div><div> <AcceptEula>true</AcceptEula></div><div> <ProductKey></div><div> <Key></Key></div><div> </ProductKey></div><div> </UserData></div>
<div> </component></div><div> </settings></div><div> <settings pass="specialize"></div><div> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="<a href="http://schemas.microsoft.com/WMIConfig/2002/State">http://schemas.microsoft.com/WMIConfig/2002/State</a>"></div>
<div> <ComputerName></ComputerName></div><div> <ProductKey>XXXXX-XXXXX-XXXXX-XXXXX-XXXXX</ProductKey></div><div> <RegisteredOrganization>Company</RegisteredOrganization></div>
<div> <RegisteredOwner>User</RegisteredOwner></div><div> <DoNotCleanTaskBar>false</DoNotCleanTaskBar></div><div> <TimeZone>Coordinated Universal Time</TimeZone></div><div>
</component></div><div> </settings></div><div></unattend></div></div><div><br></div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 16, 2013 at 2:04 PM, Joe Topjian <span dir="ltr"><<a href="mailto:joe.topjian@cybera.ca" target="_blank">joe.topjian@cybera.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Unless you plan on only having one instance of the Windows image running, sysprep should always be used as it removes all unique identifiers from the installation. The github repo I linked to involves running sysprep as the last step before uploading the image to Glance.<div>
<br></div><div>Jacob, can you share your sysprep procedure that prompts the user for a password and then sets it?</div><div><br></div><div>Thanks,</div><div>Joe</div></div><div class="gmail_extra"><div><div class="h5"><br>
<br><div class="gmail_quote">
On Thu, May 16, 2013 at 7:49 AM, Razique Mahroua <span dir="ltr"><<a href="mailto:razique.mahroua@gmail.com" target="_blank">razique.mahroua@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Thank you guys,<div>I'll definitely test all these solutions. If syspred does the job, then it's perfect :)</div><div><br></div><div>regards,</div><div>Razique</div><div><br><div>
<div>Le 15 mai 2013 à 12:58, Jacob Godin <<a href="mailto:jacobgodin@gmail.com" target="_blank">jacobgodin@gmail.com</a>> a écrit :</div><div><div><br><blockquote type="cite"><p dir="ltr">Hi Razique, </p>
<p dir="ltr">We used sysprep to auto prompt the user for a password when first booting their instance. This also allows you to do more Microsofty things to your instances on boot, like insert your SPLA product key automatically. </p>
<p dir="ltr">Cheers, <br>
Jacob</p>
<div class="gmail_quote">On 2013-05-15 5:36 AM, "Razique Mahroua" <<a href="mailto:razique.mahroua@gmail.com" target="_blank">razique.mahroua@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Joe, George, thank you for the answers!<div><br><div>I had a hard time as well making the cloudinit working with my Essex environment.</div><div>I'll give a shot on that one </div><div>
<a href="https://github.com/jordanrinke/openstack" target="_blank">https://github.com/jordanrinke/openstack</a></div><div><br></div><div>and let you know!</div><div><br></div><div>Regards,</div><div>Razique</div><div><br>
<div><div>Le 14 mai 2013 à 17:23, GMI <<a href="mailto:gmi68745@gmail.com" target="_blank">gmi68745@gmail.com</a>> a écrit :</div><br><blockquote type="cite">Hi Razique,<br><br>You can use the Windows cloudinit to set an admin password among other<br>
things (<a href="https://github.com/cloudbase/cloudbase-init" target="_blank">https://github.com/cloudbase/cloudbase-init</a>).<br><br>Recovery - use the VNC console and troubleshoot Windows boot problems as<br>normal<br>
<br>Disk attachment - it's not any different than any hot-pluggable device, so<br>the users have to learn how to use it<br><br>Updates - major updates (SP) should be incorporated in new versions of the<br>provided baselines, but for day to day instance OS patch and management, the<br>
users are responsible<br><br>Hope this helps,<br>George<br><br><br><br>-----Original Message-----<br>From: Razique Mahroua [mailto:<a href="mailto:razique.mahroua@" target="_blank">razique.mahroua@</a><a href="http://gmail.com/" target="_blank">gmail.com</a>] <br>
Sent: Tuesday, May 14, 2013 10:51 AM<br>To: <a href="mailto:openstack-operators@lists.openstack.org" target="_blank">openstack-operators@lists.openstack.org</a><br>Subject: [Openstack-operators] How do you manage your windows instances<br>
<br>Hi guys, <br>how do you manage the following items : <br><span style="white-space:pre-wrap"> </span>. User password (do you know if it's possible to configure the<br>instance so once the user spawn it for the first time, the user is asked to<br>
change his password)<br><span style="white-space:pre-wrap"> </span>. Recovery (do you have any way to debug your customers's<br>instances, how do you connect to them (same applies for Linux-based images<br>actually))<br>
<span style="white-space:pre-wrap"> </span>. Disk attachment (are your customers aware they need to go to the<br>disk manager after they added a disk if they want to start to use it?<br><span style="white-space:pre-wrap"> </span>. Updates (Are the updates managed by your user,or do you regularly<br>
update your images?<br><br>Thank you!<br>Razique<br><br><br>_______________________________________________<br>OpenStack-operators mailing list<br><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br><br></blockquote></div><br></div></div></div>
<br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div>
</blockquote></div></div></div><br></div></div><br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div></div></div><span class="HOEnZb"><font color="#888888">-- <br></font></span><div dir="ltr"><span class="HOEnZb"><font color="#888888">Joe Topjian<div>Systems Architect</div>
</font></span><div class="im"><div>Cybera Inc.</div><div><br></div><div><a href="http://www.cybera.ca" target="_blank">www.cybera.ca</a></div>
<div><br></div><div><font color="#666666"><span>Cybera</span><span> is a not-for-profit organization that works to spur and support innovation, for the economic benefit of Alberta, through the use of cyberinfrastructure.</span></font></div>
</div></div>
</div>
</blockquote></div><br></div>