Windows Instances Clean-up to Create OMIs
This topic lists the elements of a Windows instance you can clean up before creating an OMI, especially if you mean to share it with other users or to make it public.
An OMI created from an instance or a snapshot has the same characteristics as this instance or the instance the snapshot is created from. Moreover, an instance can contain sensitive information that you do not want to share.
We therefore strongly recommend cleaning up these elements from your instance, or the instance the snapshot is created from, before creating the OMI.
Creating multiple VM from an OMI that has not been clean up previously will make those VM instable in a Windows environment because they will share the same UUID that is suppose to be unique. |
You need to clean up your instance before executing the OMI Creating Launcher script or a sysprep. |
The table below gathers the elements you can clean up before creating an OMI:
Elements | Action | Method | ||
---|---|---|---|---|
Accounts configuration |
Guest account |
Disable the guest account |
Go to Computer Management > System Tools > Local Users and Group > Users and click Disable guest. |
|
Profile usage information |
Delete previous sysprep log files and clean AppData folder, history of registry and history of PowerShell ISE |
In a PowerShell prompt, run the following commands:
|
||
Start menu run history |
Clean the execute/run dialog box |
In a PowerShell prompt, run the following commands:
|
||
Explorer run history |
Clean the Windows Explorer history |
In a PowerShell prompt, run the following commands:
|
||
Internet Explorer history |
Clean the Internet Explorer history |
In a PowerShell prompt, run the following commands:
|
||
File shares |
Disable file share points that are accessible by unauthenticated users
|
Go to Computer Management > System Tools > Shared Folders > Shares and disable file shares. |
||
Windows domain |
Windows domain |
Ensure that your instance is not connected to any Windows domain |
Go to Control Panel > System and Security > System and check that your instance is on a workgroup and not on a domain. |
|
Instance configuration on OUTSCALE Cloud |
3DS OUTSCALE logs |
Clean OUTSCALE logs in C:\Windows\Outscale\logs\* |
In a PowerShell prompt, run the following command:
|
|
3DS OUTSCALE temporary files |
Clean OUTSCALE temporary files in C:\Windows\Outscale\tmp\* |
In a PowerShell prompt, run the following command:
|
||
User data script |
Clean the user data you specified for the instance, in C:\Windows\Outscale\userdata\* For more information, see Configuring an Instance with User Data and OUTSCALE Tags. |
In a PowerShell prompt, run the following command:
|
||
Logs |
Temporary files |
Clean the temporary files on your instance |
In a PowerShell prompt, run the following command:
|
|
Windows event logs |
Clear the Windows event logs
|
In a PowerShell prompt, run the following command:
|
Related Pages