Looking for:
Windows imaging and configuration designer download free |
Download and install the Windows ADK | Microsoft Docs.Windows imaging and configuration designer download free
Quickly create a provisioning package that you can use to customize devices without re-imaging. You can also build a customized Windows image for specific market segments downloac regions. Microsoft makes no warranties, express or implied, with respect to the information provided here. To determine if Windows ICD is the right tool for you, see the following table, which shows the scenarios that Windows 10 Technical Preview supports and the tool that you can use.
You can use Windows ICD to create a provisioning package. You can either apply the provisioning package to an image or share it as a standalone package that can be applied to a running system using the Provisioning Engine. Export a provisioning package if you want to reuse the customizations already configured in a different project or to share it as a standalone package that can imagkng applied to a running system during initial device setup or later.
You can use Windows ICD to create a new Windows 10 Technical Preview for desktop editions Home, Pro, and Enterprise image and customize it by adding drivers, apps, language packs, settings, and more.
Адрес can anr build the windows imaging and configuration designer download free media either to a folder or to a USB key. You diwnload use Windows ICD to configure the Windows device UI, connectivity settings, and user experience to better downloaad your brand, to meet mobile network requirements, to comply with IT department security requirements, or to fit market segments or regions where the device will ship. While running "ADKsetup. Windows ICD depends on other tools in order to work correctly.
If you have previously created projects that you want to modify, click "Open Project Provisioning Anx - Use this workflow to build a provisioning package that targets a Windows edition. A provisioning package allows you to customize an existing Windows image without re-imaging, or you can use this package to build rree Windows image. For more information, see Build and deploy a provisioning package and Export a configurxtion package.
Imaging - Use this workflow to create and build a new Windows image. From this workflow, you can use a:. This lets you build a deployment media either to a folder or to a USB key. For more information, see Build and deploy a Windows 10 image for desktop editions.
A provisioning package must apply to a specific Windows edition. In other words, you cannot create a generic provisioning package that applies imwging all Windows devices. When building an image for Windows 10 Technical Preview dosnload desktop editions Home, Pro, and Enterpriseyou can only build to a. Be aware that when adding apps and drivers, all files stored in the same folder will be imported and may cause errors during the build process. While you can open multiple projects at the same time within Windows ICD, you can only build one project at a time.
A best practice when using Windows ICD dowbload build projects or answer files that contains assets, such as apps configurration drivers, is to copy all necessary files to the local computer that is running Windows ICD. For example, when you add a driver to a provisioned package, you must copy the. If imxging windows imaging and configuration designer download free not do this, and attempt to use a copied version of this project on a different computer, Адрес страницы ICD might attempt to здесь the path to the files that point andd the original computer.
The supported host platform configuratin the operating system that can run Windows ICD. These platforms include:. Optionally, you can источник enter a freee Description to describe your project.
In the Choose Workflow window, select Provisioning Package from the list основываясь на этих данных available project workflows and then click Next. In the Select Windows Edition window, select the Windows edition for which you want to create the provisioning package and then click Finish. This loads all the customizations that you can configure based on the Windows edition that you selected. Once all the available windoas are loaded, you can see the Customizations Page.
In the Customizations Pageselect what you want to customize from the Available Customizations panel. This can include:. For more information about how to set the assets and settings, see Configure customizations using Windows ICD.
In the Downloadd Package Configuration screen, describe the provisioning package by filling windows imaging and configuration designer download free the following fields.
You can change продолжение здесь keep the default values for these fields. Package Name - This field is pre-populated with the imaginh name that you entered in the New Project wizard.
You can change this value by entering a different name in the Package Name field. Package Version - Optional. You can change the default package version by specifying designerr new value in the Package Version field.
Package Rank - Optional. You can select a value between 0 and 99, inclusive. The default package rank is 0. You cannot change this string and it's shown only for your reference. Specify the output location where you want the provisioning package to go once it's built. Click Browse to change the default location optional. Click Next. Click Build to start building the package. The project information is displayed in the build page and the progress bar indicates the build status. If you need to cancel the build, click Cancel.
This cancels the current build process, closes the wizard, and takes you back to the Customizations Windows imaging and configuration designer download free.
If your build fails, an error message will show up that includes a link www windows 10 software free download free the project folder. You can scan the logs to determine what windows imaging and configuration designer download free the error. Once you fix the issue, try building the package again.
If your build is successful, the name of the provisioning package, output directory, and project winows will be shown. If you are done, click Finish to close the wizard and go desugner to the Customizations Page. Select the provisioning package that you want to apply, double-click the file, and then allow admin privileges.
For example, you can downloar Windows Imaging and Configuration Designer ICD for image windows imaging and configuration designer download free and then build the model downlosd with its media.
You can then export the customizations done in the Customizations Page to a provisioning package before building the model image and media. You can also import the provisioning package in the New Desiggner wizard when starting another imaging project workflow to create a model image for a similar device model.
The assets and settings in the imported provisioning package will be pre-populated in the Customizations Page and you can add or change more assets and settings instead of redoing the customization tasks again before building the model image media.
Alternatively, you windows live for 8.1 download also use the Windows ICD command-line нажмите чтобы узнать больше to specify the provisioning package to build another model image with the media without further modifications to the current package contents.
This field is pre-populated with the ссылка на подробности name that you entered in the New Windows imaging and configuration designer download free wizard.
The value for the package dowwnload is pre-populated with the latest package version number or windosw. You can set downlaod Package Rank to a value between 0 and 99, inclusive. Configurstion Browse to change the default value and specify a different output location where you want the provisioning package to go once it's built.
In the Choose Workflow window, select Imaging from the list of available project workflows and then click Next. Search and locate the path to the Install. After you've selected the Install. By default, the first Windows image in the list is selected and the information about this image is displayed in the Image Information panel. This option allows you desiner build the media to a local folder on your PC or to a network share, or to create a bootable media on a USB drive. Folder Media - Creates a folder that contains the deployment media.
The resulting media is not a bootable media and is not guaranteed to work on windowws drives. If you selected Folder Media in the previous step, enter or select the path for the deployment media. Click Build to start building the image. Once you fix the issue, try building the image configudation. If your build is successful, the name of the image, output directory, and project directory will be displayed. Production Media - Use to create a production media of a desktop image.
This option is windows imaging and configuration designer download free by default. Recovery Media frfe Use to create a recovery media of a desktop image.
This can only be in the WIM image format. The Recovery Options page replaces the Select image format page that is displayed when you click the Build button. However, the rest of the workflow and pages remain the same. You can use Windows Imaging and Configuration Designer ICD to configure the Windows device UI, connectivity windows imaging and configuration designer download free, and user experience to better reflect your brand, to meet mobile network requirements, to comply with IT department security requirements, or to fit market segments or regions where the device will ship.
The following screenshot shows what you might see in the Customizations Page for a particular Windows edition. Project Нажмите для продолжения panel - Summarizes the information for the current project including the selected project workflow and the Windows edition that was selected for customization.
Available Customizations panel - Shows the assets and читать статью that you can customize for the selected project. Assets are configurable customizations that are not settings. These, and more information on how to configure them, windows imaging and configuration designer download free as follows:. The Settings group in the Available Customizations window shows the various settings that you can configure for a provisioning package or image.
For more information on how to configure them, see To customize OS settings. Customizations Editor panel - Displays information about the asset including the asset's name and path, shows the default OS value and description for a setting if availableand lets you set different values for these settings and assets.
Windows imaging and configuration designer download free will do most of your customization work in this panel. Configured Customizations panel - Shows the assets and settings that you have saved or set desginer the Customizations Windows imaging and configuration designer download free panel. The configured customizations is a list of customizations that will be included in the provisioning package.
Download and install the Windows ADK.Windows imaging and configuration designer download free
Cookies help us deliver better online services to you. By using our website, you agree to our use of cookies. Learn more.
You can use Windows ICD to do the following tasks:. To determine if Windows ICD is the right tool for you, see the following table, which shows the scenarios that Windows 10 supports and the tool that you can use. Windows 10 provides new deployment capabilities, scenarios, and tools by building on technologies introduced in Windows 7, and Windows 8.
Together, these changes require that you rethink the traditional deployment process. The following table provides an overview of the planning implications of the three Windows 10 servicing options so that IT administrators can be well-grounded conceptually before they start a Windows 10 deployment project. Product cycles and builds The Windows engineering team adds new features and functionality to Windows through product cycles comprised of development, testing, and release phases.
Each day during a product cycle, the team compiles the source code for Windows and assembles the output into a build that users can install on their devices.
The first recipients of builds are Microsoft employees who begin what Microsoft calls selfhost testing. Testing and release prior to Windows 10 Prior to Windows 10, Microsoft issued and extensively tested many builds internally before selecting one for testing outside Microsoft. After repeating the external test cycle several times against builds of progressively better quality, the engineering team selected a build to enter the release phase.
At the end of this phase, the team published the build as a new version of Windows — an event referred to as the Release to Manufacturing RTM milestone. In total, product cycles took between one and three years to complete, with testing and release processes taking up as much as half of the total investment in time. Additionally, new releases must be made available on a continual basis, and must be deployable with minimal impact on users.
Microsoft designed Windows 10 to meet these requirements by implementing a new approach to innovation development and delivery called Windows as a Service WaaS. The key to enabling significantly shorter product cycles while maintaining high quality levels is an innovative community-centric approach to testing that Microsoft has implemented for Windows The community, known as Windows Insiders, is comprised of millions of users around the world.
When Windows Insiders opt in to the community, they test many builds over the course of a product cycle, and provide feedback to Microsoft through an iterative methodology called flighting. Builds distributed as flights provide the Windows engineering team with significant data regarding how well builds are performing in actual use.
Flighting with Windows Insiders also enables Microsoft to test builds in much more diverse hardware, application, and networking environments than in the past, and to identify issues far more quickly. As a result, Microsoft believes that community-focused flighting will enable both a faster pace of innovation delivery, and better public release quality than ever.
Although Microsoft releases flight builds to Windows Insiders, Microsoft will publish two types of Windows 10 releases broadly to the public on an ongoing basis:. The cumulative nature of all Windows 10 releases It is important to note that, in order to improve release quality and simplify deployments, all new releases that Microsoft publishes for Windows 10 will be cumulative.
This means new feature upgrades and servicing updates will contain the payloads of all previous releases in an optimized form to reduce storage and networking requirements , and installing the release on a device will bring it completely up to date.
Also, unlike earlier versions of Windows, you cannot install a subset of the contents of a Windows 10 servicing update. For example, if a servicing update contains fixes for three security vulnerabilities and one reliability issue, deploying the update will result in the installation of all four fixes. As with earlier releases of Windows, Windows 10 includes support for the deployment of new releases using Windows Update, Windows Server Update Services, System Center Configuration Manager, and third-party configuration management tools.
Because of the importance of the Windows as a Service WaaS approach to delivering innovations to businesses, and the proven ability of Windows Update to deploy releases quickly and seamlessly to consumers and small businesses, several of the largest investments in Windows 10 focus on enabling broader use of Windows Update within enterprises. Since Microsoft introduced the first generation of Windows Update with Windows 95, Windows Update has evolved to become the standard way for consumers and small businesses to help keep devices running Windows secure and running reliably.
Almost one billion Windows devices communicate with the Windows Update service on a regular basis. The process of downloading and installing updates has evolved to be less and less obtrusive to users. More recently, Microsoft also has used Windows Update to deliver larger, feature-centric updates, such as the upgrade from Windows 8 to Windows 8.
Although Windows Update greatly simplifies and accelerates update deployment, enterprises are not using Windows Update as broadly as consumers and small businesses. This is largely because Windows Update maintains control over which updates are installed and the timing of installation.
This makes it difficult for IT administrators to test updates before deployment in their specific environment. Windows Server Update Services enables IT administrators to obtain the updates that Windows Update determines are applicable to the devices in their enterprise, perform additional testing and evaluation on the updates, and select the updates they want to install.
Windows Server Update Services also provides IT administrators with an all or nothing way to specify when they want an approved update to be installed. Because IT administrators ultimately select and install most updates identified by Windows Update, the role of Windows Server Update Services in many enterprises is to provide IT administrators with the additional time they need to gain confidence in the quality of updates prior to deployment.
To enable enterprises to manage more of their devices using Windows Update directly, Windows 10 provides IT administrators with a way to configure devices so that Windows Update will defer new feature upgrade installations until approximately four months after Microsoft first publishes them.
The additional time can be used to perform testing or enable releases to gain additional time in market prior to deployment.
At the end of each approximately four month period, Microsoft executes a set of processes that require no action from enterprise IT administrators. This reduces the time it can take to install a feature upgrade on a device. Although Windows 10 will enable IT administrators to defer installation of new feature upgrades using Windows Update, enterprises may also want additional control over how and when Windows Update installs releases.
Microsoft designed Windows Update for Business to provide IT administrators with additional Windows Update-centric management capabilities, such as the ability to deploy updates to groups of devices and to define maintenance windows for installing releases. This article will be updated with additional information about the role of Windows Update for Business in servicing Windows 10 devices as it becomes available.
Historically, because of the length of time between releases of new Windows versions, and the relatively low number of enterprise devices that were upgraded to newer versions of Windows during their deployment lifetimes, most IT administrators defined servicing as installing the updates that Microsoft published every month. Looking forward, because Microsoft will be publishing new feature upgrades on a continual basis, servicing will also include on some portion of an enterprise's devices installing new feature upgrades as they become available.
In particular, IT administrators can configure Windows 10 devices to:. When the development of a new Windows 10 feature upgrade is complete, it is initially offered to Current Branch computers; those computers configured for Current Branch for Business will receive the feature upgrade with additional fixes at a later date, generally at least four months later.
An additional deferral of at least eight months is available to organizations that use tools to control the update process. During this time, monthly security updates will continue to be made available to machines not yet upgraded.
The Defer upgrades setting needs to be configured, either manually through the Settings app , by using Group Policy, or by using mobile device management MDM. With Windows 10, this does not need to change; all updates are controlled through approvals or automatic deployment rules configured in those products, so new upgrades will not be deployed until the organization chooses.
The Defer upgrades setting can function as an additional validation check, so that Current Branch for Business machines that are targeted with a new upgrade prior to the end of the initial four-month deferral period will decline to install it; they can install the upgrade any time within the eight-month window after that initial four-month deferral period. For computers configured to receive updates from Windows Update directly, the Defer upgrades setting directly controls when the PC will be upgraded.
Computers that are not configured to defer upgrades will be upgraded at the time of the initial Current Branch release; computers that are configured to defer upgrades will be upgraded four months later. With Windows 10 it is now possible to manage updates for PCs and tablets that have a higher degree of mobility and are not joined to a domain. For PCs enrolled in a mobile device management MDM service, Windows 10 provides new update approval mechanisms that could be leveraged to delay the installation of a new feature upgrade or any other update.
Windows Update for Business will eventually provide these and other capabilities to manage upgrades and updates; more details on these capabilities will be provided when they are available later in You can use these images to upgrade existing machines or to create new custom images. These feature upgrades will also be published with WSUS to enable simple deployment to devices already running Windows Unlike previous versions of Windows, the servicing lifetime of Current Branch or Current Branch for Business is finite.
You must install new feature upgrades on machines running these branches in order to continue receiving monthly security updates. This requires new ways of thinking about software deployment.
It is best to align your deployment schedule with the Current Branch release schedule:. Some organizations may require more than 12 months to deploy Windows 10 to all of their existing PCs. To address this, it may be necessary to deploy multiple Windows 10 releases, switching to these new releases during the deployment project.
Notice how the timelines can overlap, with the evaluation of one release happening during the pilot and deployment of the previous release:. As a result of these overlapping timelines, organizations can choose which release to deploy. Note though that by continuing for longer with one release, that gives you less time to deploy the subsequent release to both existing Windows 10 PCs as well as newly-migrated ones , so staying with one release for the full lifetime of that release can be detrimental overall.
Once released, these will be supported with security and reliability fixes for an extended period; no new features will be added over its servicing lifetime. For apps from other ISVs including those published in the Windows Store , contact the ISV to confirm if they will provide long-term support for their specific apps.
As mentioned previously, there are few, if any, scenarios where an organization would use the Long-Term Servicing Branch for every PC — or even for a majority of them. During the development of a new Windows 10 feature update, preview releases will be made available to Windows Insider Program participants.
This enables those participants to try out new features, check application compatibility, and provide feedback during the development process. To obtain Windows Insider Program builds, the Windows Insider Program participants must opt in through the Settings app, and specify their Microsoft account. During the life of a particular PC, it may be necessary or desirable to switch between the available branches.
Depending on the branch you are using, the exact mechanism for doing this can be different; some will be simple, others more involved.
The remainder of this article focuses on the description of the three options outlined above, and their planning implications, in more detail. In practice, IT administrators have to focus on two areas when planning a Windows 10 device deployment:. The content that follows will provide IT administrators with the context needed to understand why these areas are pivotal, and the choices available to them.
Some figures in this article show multiple feature upgrades of Windows being released by Microsoft over time. Be aware that these figures were created with dates that were chosen for illustrative clarity, not for release roadmap accuracy, and should not be used for planning purposes.
When it is time to release a build as a new feature upgrade for Windows 10, Microsoft performs several processes in sequence. The first process involves creating either one or two servicing branches in a source code management system. These branches shown in Figure 4 are required to produce feature upgrade installation media and servicing update packages that can be deployed on different Windows 10 editions, running in different configurations. In all cases, Microsoft creates a servicing branch referred to in Figure 4 as Servicing Branch 1 that is used to produce releases for approximately one year although the lifetime of the branch will ultimately depend on when Microsoft publishes subsequent feature upgrade releases.
If Microsoft has selected the feature upgrade to receive long-term servicing-only support, Microsoft also creates a second servicing branch referred to in Figure 4 as Servicing Branch 2 that is used to produce servicing update releases for up to 10 years.
As shown in Figure 5, when Microsoft publishes a new feature upgrade, Servicing Branch 1 is used to produce the various forms of media needed by OEMs, businesses, and consumers to install Windows 10 Home, Pro, Education, and Enterprise editions. Microsoft also produces the files needed by Windows Update to distribute and install the feature upgrade, along with targeting information that instructs Windows Update to only install the files on devices configured for immediate installation of feature upgrades.
Approximately four months after publishing the feature upgrade, Microsoft uses Servicing Branch 1 again to republish updated installation media for Windows 10 Pro, Education, and Enterprise editions.
The updated media contains the exact same feature upgrade as contained in the original media except Microsoft also includes all the servicing updates that were published since the feature upgrade was first made available. This enables the feature upgrade to be installed on a device more quickly, and in a way that is potentially less obtrusive to users. Concurrently, Microsoft also changes the way the feature upgrade is published in the Windows Update service.
In particular, the files used by Windows Update to distribute and install the feature upgrade are refreshed with the updated versions, and the targeting instructions are changed so that the updated feature upgrade will now be installed on devices configured for deferred installation of feature upgrades. The time between releases of feature upgrades with long-term servicing support will vary between one and three years, and is strongly influenced by input from customers regarding the readiness of the release for long-term enterprise deployment.
Figure 5 shows the Windows 10 Enterprise LTSB edition being published at the same time as the other Windows 10 editions, which mirrors the way editions were actually published for Windows 10 in July of
Comments
Post a Comment