In order to create an image of your Windows virtual server by using the image archiving service, you must run Sysprep on the Windows virtual server of which you intend to create an image. The procedure is shown below for reference.
About this task
For details on Sysprep, refer to the Microsoft TechNet website (https://technet.microsoft.com/en-us/), and be sure you fully understand Sysprep before you actually run it.
Warning: Fujitsu does not take responsibility for any problems that are caused by running Sysprep. The customer takes full responsibility for carrying out this procedure.
Tip: We recommend that you take snapshots or create backups of system block storage before you start the procedure to run Sysprep.
Procedure
-
Taking a Snapshot
Take a snapshot of the system storage using the snapshot function.
Tip: Perform the subsequent procedures on Windows OS.
-
Allowing remote access to the computer
Remote access to the computer is allowed by default. If remote access is not allowed, change the setting to allow it by following the procedure below.
-
For Windows 2016 SE / 2012 SE
From the Start menu, click , and then select Allow remote connections to this computer (L) in the dialog box.
-
For Windows 2008 SE/EE
From the Start menu, click , and then select one of the following in the dialog box:
- Allow connections from computers running any version of Remote Desktop (less secure)(L)
- Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)(N)
-
Editing of the sysprep response file
Edit the sysprep response file as necessary. The sysprep response file is stored in the following location on the virtual server:
-
For Windows 2016 SE
C:\Windows\System32\Sysprep\ans_w2k16.xml
-
For Windows 2012 SE
C:\Windows\System32\Sysprep\ans_w2k12.xml
-
For Windows 2008 SE
C:\Windows\System32\Sysprep\ans_w2k8_se.xml
-
For Windows 2008 EE
C:\Windows\System32\Sysprep\ans_w2k8_ee.xml
-
Deleting the log file
Delete the Cloudbase-init log file. You can find the path to the Cloudbase-init log file at the following locations on a Windows OS:
-
Settings for the log file in cloudbase-init-unattend
<Location where Cloudbase-init is intalled>\conf\cloudbase-init-unattend.conf
- Location where the log exists: logdir in the [DEFAULT] section
- Log file: logfile in the [DEFAULT] section
Tip:
Normally, the path to the log file is as follows:
C:\Program Files (x86)\Cloudbase Solutions\Cloudbase-Init\log\cloudbase-init-unattend.log
-
Settings for the log file in cloudbase-init
<Location where Cloudbase-init is installed>\conf\cloudbase-init.conf
- Location where the log exists: logdir in the [DEFAULT] section
- Log file: logfile in the [DEFAULT] section
Tip:
Normally, the path to the log file is as follows:
C:\Program Files (x86)\Cloudbase Solutions\Cloudbase-Init\log\cloudbase-init.log
-
Deleting the registry information
Delete the Cloudbase-init registry information. Delete the following path by using the registry editor:
-
Starting the command prompt
-
For Windows 2016 SE / 2012 SE
On the desktop screen, right-click the Windows logo button and click Command Prompt (Admin).
-
For Windows 2008 SE/EE
- Click the Start button.
-
Click .
- Right-click Command Prompt and click Run as administrator.
-
Moving the current directory
Execute the following command to move the current directory:
cd C:\Windows\System32\sysprep\
-
Running of sysprep
Run the following batch file:
vsysprep.bat
Results
The virtual server will be shut down automatically after a few minutes. Make sure that the status of the virtual server is "SHUTOFF" before you create an image.
After creating an image, follow the procedure below on the virtual server:
-
Restoring a snapshot
Restore the snapshot of the system storage using the snapshot function.
-
Starting virtual servers
Start the virtual server.