We're deploying a VM using cloudbase-init in Vcenter 5x. The original image/template has drive X: assigned to pagefile. When we provision a new image the pagefile is changed to drive E:. If we create a new VM without cloudbase-init, there is no change to the drive letter. Cloudbase-init was reinstalled on a clone of the original image with the same results. What could be the issue?
Hi Adrian, Thanks for your reply...
We used the msi installer.
Yes... we ran cloud init without sysprep and the drive did not change so I'm sure the error is with sysprep. This image was use with Drive E: before and now we would like to use X:. This there a configuration for sysprep or windows registry setting? We're using Windows 2008R2.
You can leverage Localscripts plugin from cloudbase-init and add a powershell or batch script in the LocalScripts folder, which will be run at boot time by cloudbase-init. The registry key you want to modify is: get-item 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\'
You can leverage Localscripts plugin from cloudbase-init and add a powershell or batch script in the LocalScripts folder, which will be run at boot time by cloudbase-init. The registry key you want to modify is: 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management\'
Hello,
Are you using Cloudbase-Init msi installer to install cloudbase-init and are you performing the sysprep step from the installer?
Thank you, Adrian Vladu
Asked: 2017-04-19 10:59:11 +0200
Seen: 349 times
Last updated: Apr 19 '17
© 2014-2023 Cloudbase Solutions Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
