Is there a problem in the usage?

edit

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.