egami's profile - activity

Hi cmiN,

Thanks a lot. I'm sorry for my bad question. Your expectation is correct.

I tried to execute the cloudbase-init at hand using Cloudbase-init.exe and cloudbase-init.conf files. Cloudbase-init restarted the Windows OS (Windows Server 2012 R2) and set all parameter. But registry "HKEYLOCALMACHINE\SOFTWARE\Wow6432Node\Cloudbase Solutions\Cloudbase-Init" was not set. I thought that my operation was not correct.

However, I get your answer and execute same operation. I find in registry "HKEYLOCALMACHINE\SOFTWARE\Cloudbase Solutions\Cloudbase-Init". I think that my operation is correct and my recognition maybe old.

I created the Windows Server 2012 R2 Server Core image by Cloudbase IT's guide. I find the warning message(*), but I created the image success.

• I get the followning message
  Resource files missing from E:\windows\boot\Resources. These files are required for some editions of windows...

I registered the image to OpenStack and I created the instance by Windows Server 2012 R2 Server Core image. Then the instance is not start normally and displays a status 0xc0000001 error.

Can I create Server Core image by Cloudbase IT's guide?

When Cloudbase-init is used, it becomes the following flows. ()Adhering is a part that operates by the automatic operation.

1. Make the Windows instance.
2. Install Cloudbase-init.
3. Execute Sysprep.
4. Shutdown
5. Image collection
6. Make the Windows instance by using the image of operation 5.
7. (Boot the instance)
8. (Sysprep minisetup operates. )
9. (Cloudbase-init is executed by extending sysprep minisetup (Cloudbase-init-unattend.conf is used). )
10. (Starts Windows OS. )
11. (Cloudbase-init starts as service (Cloudbase-init.conf is used). )

I think the following use. I want you to teach if there is a problem.

1. Make the Windows instance.
2. Make the response file of Sysprep (Unattend.xml).
3. Execute Sysprep.
4. Shutdown
5. Image collection
6. Make the Windows instance by using the image of operation 5.
7. (Boot the instance)
8. (Sysprep minisetup operates. )
9. (Starts Windows OS. )
10. login in Windows.
11. Install Cloudbase-init.
12. Start Cloudbase-init.
13. (Start restart Windows OS)
14. (Starts Windows OS. )
15. (Cloubase-init starts as service (Cloudbase-init.conf is used). )

When I tried, this operation seems no problem. (The setting that need restart OS is excluded. e.g. Hostname) I want you to teach the content of the problem if there is a problem.

I think as follows.
I want to use the same image in Cloud and local environment. (KVM not openstack). On Cloud, I setup by Cloudbase-init. On local environment, I setup by other method. Therefore, I do not want to install Cloudbase-init in the Windows image.