Skip to content

add a warning on how to work with sysprep #671

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
YuzuruUeda wants to merge 1 commit into
base: master
Choose a base branch
from
Open

add a warning on how to work with sysprep #671

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions end-user/en/source/pages/templating/appliance-installprofile.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,3 +81,5 @@ You can define the following as part of a Windows-based appliance install profil
* ``Welcome Message``: You can enter a welcome message.

.. image:: /images/install-profile-windowsfp3.png

.. warning:: For now, please do not select to run sysprep, if the target cloud platform injects CloudBase-Init during its import process, for example, on K5. If you want to run sysprep, run sysprep after the import process has finished.
Copy link
Contributor

@emuus emuus Mar 13, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To avoid possible conflicts we recommend you avoid running sysprep, particularly if the target cloud platform injects CloudBase-Init during its import process (this is the case for example on K5).

Copy link
Contributor

@thachmai thachmai Mar 14, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For K5 platform, running sysprep is not recommended due to a conflict with CloudBase-Init. You can run sysprep on the instance after publication if needed.

Copy link
Contributor Author

@YuzuruUeda YuzuruUeda Mar 14, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To avoid possible conflicts we recommend you avoid running sysprep, particularly if the target cloud platform injects CloudBase-Init during its import process (this is the case for example on K5). You can run sysprep on the instance after publication if needed.

Copy link
Contributor

@thachmai thachmai Mar 16, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe you can make another commit directly? I think the wording is a bit long but it's fine :)

Copy link
Contributor

@emuus emuus Mar 18, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your last proposition is ok for me