A beta version of Hyper-V was shipped with certain x86-64 editions of Windows Server 2008. The finalized version was released on June 26, 2008 and was delivered through Windows Update. 'We officially do not support Windows Server 2008 on this W500 series.' Is there anyone who success to recognize network card? Windows Server 2008 and Network Driver. In the device manager on the ethernet controller I choose 'let me pick from a list of device drivers on my computer' then i select (C: DRIVERS Vista ETHERNET PRO1000 Winx64. Free Download Intel Network Adapter Driver 18.5 for Server 2008 R2 (Network Card). - Removed driver and software support for Microsoft Windows Server 2008 R1. - Intel 82567 Gigabit Ethernet Controller - Intel 82571EB Gigabit Ethernet Controller.
August 6, 2012
Install_Win7_7061_07272012.zip
5.8 MB
Windows 7
Networking
23,932
Communications Network ICs 10/100/1000M Gigabit Ethernet PCI Express
Supported Products:
Supported OS:
-->
Applies To: Windows Server 2016
Important
Starting in Windows Server, version 1709, Nano Server will be available only as a container base OS image. Check out Changes to Nano Server to learn what this means.
This topic covers information you need to deploy Nano Server images that are more customized to your needs compared to the simple examples in the Nano Server Quick Start topic. You'll find information about making a custom Nano Server image with exactly the features you want, installing Nano Server images from VHD or WIM, editing files, working with domains, dealing with packages by several methods, and working with server roles.
Nano Server Image Builder
The Nano Server Image Builder is a tool that helps you create a custom Nano Server image and bootable USB media with the aid of a graphical interface. Based on the inputs you provide, it generates reusable PowerShell scripts that allow you easily automate consistent installations of Nano Server running either Windows Server 2016 Datacenter or Standard editions.
Obtain the tool from the Download Center.
The tool also requires Windows Assessment and Deployment Kit (ADK).
Nano Server Image Builder creates customized Nano Server images in VHD, VHDX or ISO formats and can create bootable USB media to deploy Nano server or detect the hardware configuration of a server. It also can do the following:
If any of these are unfamiliar to you, review the remainder of this topic and the other Nano Server topics so that you'll be prepared to provide the tool with the information it will need.
Creating a custom Nano Server image
For Windows Server 2016, Nano Server is distributed on the physical media, where you will find a NanoServer folder; this contains a .wim image and a subfolder called Packages. It is these package files that you use to add server roles and features to the VHD image, which you then boot to.
You can also find and install these packages with the NanoServerPackage provider of PackageManagement (OneGet) PowerShell module. See the 'Installing roles and features online' section of this topic.
This table shows the roles and features that are available in this release of Nano Server, along with the Windows PowerShell options that will install the packages for them. Some packages are installed directly with their own Windows PowerShell switches (such as -Compute); others you install by passing package names to the -Package parameter, which you can combine in a comma-separated list. You can dynamically list available packages using the Get-NanoServerPackage cmdlet.
Note
When you install packages with these options, a corresponding language pack is also installed based on selected server media locale. You can find the available language packs and their locale abbreviations in the installation media in subfolders named for the locale of the image.
Note
When you use the -Storage parameter to install File Services, File Services is not actually enabled. Enable this feature from a remote computer with Server Manager.
Failover Clustering items installed by the -Clustering parameter
File and storage items installed by the -Storage parameter
Installing a Nano Server VHD
This example creates a GPT-based VHDX image with a given computer name and including Hyper-V guest drivers, starting with Nano Server installation media on a network share. In an elevated Windows PowerShell prompt, start with this cmdlet:
Ethernet ControllerImport-Module <Server media location>NanoServerNanoServerImageGenerator; New-NanoServerImage -DeploymentType Guest -Edition Standard -MediaPath PathToMediaserver_en-us -BasePath .Base -TargetPath .FirstStepsNano.vhdx -ComputerName FirstStepsNano
The cmdlet will accomplish all of these tasks:
All of this results in an image of .FirstStepsNano.vhdx.
The cmdlet generates a log as it runs and will let you know where this log is located once it is finished. The WIM-to-VHD conversion accomplished by the companion script generates its own log in %TEMP%Convert-WindowsImage<GUID> (where <GUID> is a unique identifier per conversion session).
As long as you use the same base path, you can omit the media path parameter every time you run this cmdlet, since it will use cached files from the base path. If you don't specify a base path, the cmdlet will generate a default one in the TEMP folder. If you want to use different source media, but the same base path, you should specify the media path parameter, however.
Note
You now have the option to specify the Nano Server edition to build either the Standard or Datacenter edition. Use the -Edition parameter to specify Standard or Datacenter editions.
Once you have an existing image, you can modify it as needed using the Edit-NanoServerImage cmdlet.
If you do not specify a computer name, a random name will be generated.
Installing a Nano Server WIM
To create a Nano Server image to serve as a Hyper-V host, run the following:
New-NanoServerImage -Edition Standard -DeploymentType Host -MediaPath <path to root of media> -BasePath .Base -TargetPath .NanoServerPhysicalNanoServer.wim -ComputerName <computer name> -OEMDrivers -Compute -Clustering
Where
You will be prompted to enter an administrator password.
For more information, run
Get-Help New-NanoServerImage -Full .
Boot into WinPE and ensure that the .wim file just created is accessible from WinPE. (You could, for example, copy the .wim file to a bootable WinPE image on a USB flash drive.)
Once WinPE boots, use Diskpart.exe to prepare the target computer's hard drive. Run the following Diskpart commands (modify accordingly, if you're not using UEFI & GPT):
Warning
These commands will delete all data on the hard drive.
Diskpart.exe
Select disk 0 Clean Convert GPT Create partition efi size=100 Format quick FS=FAT32 label='System' Assign letter='s' Create partition msr size=128 Create partition primary Format quick FS=NTFS label='NanoServer' Assign letter='n' List volume Exit
Apply the Nano Server image (adjust the path of the .wim file):
Dism.exe /apply-image /imagefile:.NanoServer.wim /index:1 /applydir:n:
Bcdboot.exe n:Windows /s s:
Remove the DVD media or USB drive and reboot your system with Wpeutil.exe Reboot
Editing files on Nano Server locally and remotely
In either case, connect to Nano Server, such as with Windows PowerShell remoting.
Once you've connected to Nano Server, you can edit a file residing on your local computer by passing the file's relative or absolute path to the psEdit command, for example:
psEdit C:WindowsLogsDISMdism.log or psEdit .myScript.ps1
Edit a file residing on the remote Nano Server by starting a remote session with
Enter-PSSession -ComputerName '192.168.0.100' -Credential ~Administrator and then passing the file's relative or absolute path to the psEdit command like this:psEdit C:WindowsLogsDISMdism.log
Installing roles and features online
Note
If you install an optional Nano Server package from media or online repository, it won't have recent security fixes included. To avoid a version mismatch between the optional packages and base operating system, you should install the latest cumulative update immediately after installing any optional packages and before restarting the server.
Installing roles and features from a package repository
You can find and install Nano Server packages from the online package repository by using the NanoServerPackage provider of the PackageManagement PowerShell module. To install this provider, use these cmdlets:
Note
If you experience errors when running Install-PackageProvider, check that you have installed the latest cumulative update (KB3206632 or later), or use Save-Module as follows:
Once this provider is installed and imported, you can search for, download, and install Nano Server packages using cmdlets designed specifically for working with Nano Server packages:
You can also use the generic PackageManagement cmdlets and specify the NanoServerPackage provider:
To use any of these cmdlets with Nano Server packages on Nano Server, add
-ProviderName NanoServerPackage . If you don't add the -ProviderName parameter, PackageManagement will iterate all of the providers. For more details on these cmdlets, run Get-Help <cmdlet> . Here are some common usage examples:
Searching for Nano Server packages
You can use either
Find-NanoServerPackage or Find-Package -ProviderName NanoServerPackage to search for and return a list of Nano Server packages that are available in the online repository. For example, you can get a list of all the latest packages:
Running
Find-Package -ProviderName NanoServerPackage -DisplayCulture displays all available cultures.
If you need a specific locale version, such as US English, you could use
Find-NanoServerPackage -Culture en-us orFind-Package -ProviderName NanoServerPackage -Culture en-us or Find-Package -Culture en-us -DisplayCulture .
To find a specific package by package name, use the -Name parameter. This parameter also accepts wildcards. For example, to find all packages with VMM in the name, use
Find-NanoServerPackage -Name *VMM* or Find-Package -ProviderName NanoServerPackage -Name *VMM* .
You can find a particular version with the -RequiredVersion, -MinimumVersion, or -MaximumVersion parameters. To find all available versions, use -AllVersions. Otherwise, only the latest version is returned. For example:
Find-NanoServerPackage -Name *VMM* -RequiredVersion 10.0.14393.0 . Or, for all versions: Find-Package -ProviderName NanoServerPackage -Name *VMM* -AllVersions
Installing Nano Server packages
You can install a Nano Server package (including its dependency packages, if any) to Nano Server either locally or an offline image with either
Install-NanoServerPackage or Install-Package -ProviderName NanoServerPackage . Both of these accept input from the pipeline.
To install the latest version of a Nano Server package to an online Nano Server, use either
Install-NanoServerPackage -Name Microsoft-NanoServer-Containers-Package or Install-Package -Name Microsoft-NanoServer-Containers-Package . PackageManagement will use the culture of the Nano Server.
You can install a Nano Server package to an offline image while specifying a particular version and culture, like this:
Install-NanoServerPackage -Name Microsoft-NanoServer-DCB-Package -Culture de-de -RequiredVersion 10.0.14393.0 -ToVhd C:MyNanoVhd.vhd
or:
Install-Package -Name Microsoft-NanoServer-DCB-Package -Culture de-de -RequiredVersion 10.0.14393.0 -ToVhd C:MyNanoVhd.vhd
Here are some examples of pipelining package search results to the installation cmdlet:
Find-NanoServerPackage *dcb* | Install-NanoServerPackage finds any packages with 'dcb' in the name and then installs them.
Find-Package *nanoserver-compute-* | Install-Package finds packages with 'nanoserver-compute-' in the name and installs them.
Find-NanoServerPackage -Name *nanoserver-compute* | Install-NanoServerPackage -ToVhd C:MyNanoVhd.vhd finds packages with 'compute' in the name and installs them to an offline image.
Find-Package -ProviderName NanoserverPackage *nanoserver-compute-* | Install-Package -ToVhd C:MyNanoVhd.vhd does the same thing with any package that has 'nanoserver-compute-' in the name.
Downloading Nano Server packagesSave-NanoServerPackage or Save-Package allow you to download packages and save them without installing them. Both cmdlets accept input from the pipeline.
For example, to download and save a Nano Server package to a directory that matches the wildcard path, use
Save-NanoServerPackage -Name Microsoft-NanoServer-DNS-Package -Path C: In this example, -Culture wasn't specified, so the culture of the local machine will be used. No version was specified, so the latest version will be saved.
Save-Package -ProviderName NanoServerPackage -Name Microsoft-NanoServer-IIS-Package -Path C: -Culture it-IT -MinimumVersion 10.0.14393.0 saves a particular version and for the Italian language and locale.
You can send search results through the pipeline as in these examples:
Find-NanoServerPackage -Name *containers* -MaximumVersion 10.2 -MinimumVersion 1.0 -Culture es-ES | Save-NanoServerPackage -Path C:
or
Find-Package -ProviderName NanoServerPackage -Name *shield* -Culture es-ES | Save-Package -Path
Inventory installed packages
You can discover which Nano Server packages are installed with
Get-Package . For example, see which packages are on Nano Server with Get-Package -ProviderName NanoserverPackage .
To check the Nano Server packages that are installed in an offline image, run
Get-Package -ProviderName NanoserverPackage -FromVhd C:MyNanoVhd.vhd .
Installing roles and features from local source
Though offline installation of server roles and other packages is recommended, you might need to install them online (with the Nano Server running) in container scenarios. To do this, follow these steps:
Customizing an existing Nano Server VHD
You can change the details of an existing VHD by using the Edit-NanoServerImage cmdlet, as in this example:
Edit-NanoServerImage -BasePath .Base -TargetPath .BYOVHD.vhd
This cmdlet does the same things as New-NanoServerImage, but changes the existing image instead of converting a WIM to a VHD. It supports the same parameters as New-NanoServerImage with the exception of -MediaPath and -MaxSize, so the initial VHD must have been created with those parameters before you can make changes with Edit-NanoServerImage.
Additional tasks you can accomplish with New-NanoServerImage and Edit-NanoServerImageJoining domains
New-NanoServerImage offers two methods of joining a domain; both rely on offline domain provisioning, but one harvests a blob to accomplish the join. In this example, the cmdlet harvests a domain blob for the Contoso domain from the local computer (which of course must be part of the Contoso domain), then it performs offline provisioning of the image using the blob:
New-NanoServerImage -Edition Standard -DeploymentType Host -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .JoinDomHarvest.vhdx -ComputerName JoinDomHarvest -DomainName Contoso
When this cmdlet completes, you should find a computer named 'JoinDomHarvest' in the Active Directory computer list.
You can also use this cmdlet on a computer that is not joined to a domain. To do this, harvest a blob from any computer that is joined to the domain, and then provide the blob to the cmdlet yourself. Note that when you harvest such a blob from another computer, the blob already includes that computer's name--so if you try to add the -ComputerName parameter, an error will result.
You can harvest the blob with this command:
djoin
/Provision /Domain Contoso /Machine JoiningDomainsNoHarvest /SaveFile JoiningDomainsNoHarvest.djoin
Run New-NanoServerImage using the harvested blob:
New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .JoinDomNoHrvest.vhd -DomainBlobPath .PathToDomainBlobJoinDomNoHrvestContoso.djoin
In the event that you already have a node in the domain with the same computer name as your future Nano Server, you could reuse the computer name by adding the
-ReuseDomainNode parameter.
Adding additional drivers
Nano Server offers a package that includes a set of basic drivers for a variety of network adapters and storage controllers; it's possible that drivers for your network adapters might not be included. You can use these steps to find drivers in a working system, extract them, and then add them to the Nano Server image.
Note
In the folder where you keep your drivers, both the SYS files and corresponding INF files must be present. Also, Nano Server only supports signed, 64-bit drivers.
Injecting drivers
Nano Server offers a package that includes a set of basic drivers for a variety of network adapters and storage controllers; it's possible that drivers for your network adapters might not be included. You can use this syntax to have New-NanoServerImage search the directory for available drivers and inject them into the Nano Server image:
New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .InjectingDrivers.vhdx -DriverPath .ExtraDrivers
Note
In the folder where you keep your drivers, both the SYS files and corresponding INF files must be present. Also, Nano Server only supports signed, 64-bit drivers.
Using the -DriverPath parameter, you can also pass a array of paths to driver .inf files:
Ethernet Controller Driver Windows 7New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .InjectingDrivers.vhdx -DriverPath .ExtraDriversnetcard64.inf
Connecting with WinRM![]()
To be able to connect to a Nano Server computer using Windows Remote Management (WinRM) (from another computer that is not on the same subnet), open port 5985 for inbound TCP traffic on the Nano Server image. Use this cmdlet:
New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .ConnectingOverWinRM.vhd -EnableRemoteManagementPort
Setting static IP addresses
To configure a Nano Server image to use static IP addresses, first find the name or index of the interface you want to modify by using Get-NetAdapter, netsh, or the Nano Server Recovery Console. Use the -Ipv6Address, -Ipv6Dns, -Ipv4Address, -Ipv4SubnetMask, -Ipv4Gateway and -Ipv4Dns parameters to specify the configuration, as in this example:
New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .StaticIpv4.vhd -InterfaceNameOrIndex Ethernet -Ipv4Address 192.168.1.2 -Ipv4SubnetMask 255.255.255.0 -Ipv4Gateway 192.168.1.1 -Ipv4Dns 192.168.1.1
Custom image size
You can configure the Nano Server image to be a dynamically expanding VHD or VHDX with the -MaxSize parameter, as in this example:
New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .BigBoss.vhd -MaxSize 100GB
Embedding custom data
To embed your own script or binaries in the Nano Server image, use the -CopyPath parameter to pass an array of files and directories to be copied. The -CopyPath parameter can also accept a hashtable to specify the destination path for files and directories.
New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .BigBoss.vhd -CopyPath .tools
Running custom commands after the first boot
To run custom commands as part of setupcomplete.cmd, use the -SetupCompleteCommand parameter to pass an array of commands:
New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .NanoServer.wim -SetupCompleteCommand @('echo foo', 'echo bar')
Running custom PowerShell scripts as part of image creation
To run custom PowerShell scripts as part of the image creation process, use the -OfflineScriptPath parameter to pass an array of paths to .ps1 scripts. If those scripts take arguments, use the -OfflineScriptArgument to pass a hashtable of additional arguments to the scripts.
New-NanoServerImage -DeploymentType Host -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .NanoServer.wim -OfflineScriptPath C:MyScriptscustom.ps1 -OfflineScriptArgument @{Param1='Value1'; Param2='Value2'}
Support for development scenarios
If you want to develop and test on Nano Server, you can use the -Development parameter. This will enable PowerShell as the default local shell, enable installation of unsigned drivers, copy debugger binaries, open a port for debugging, enable test signing, and enable installation of AppX packages without a developer license:
New-NanoServerImage -DeploymentType Guest -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .NanoServer.wim -Development
Custom unattend file
If you want to use your own unattend file, use the -UnattendPath parameter:
New-NanoServerImage -DeploymentType Guest -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .NanoServer.wim -UnattendPath pathtounattend.xml
Specifying an administrator password or computer name in this unattend file will override the values set by -AdministratorPassword and -ComputerName.
Note
Nano Server does not support setting TCP/IP settings via unattend files. You can use Setupcomplete.cmd to configure TCP/IP settings.
Collecting log files
If you want to collect the log files during image creation, use the -LogPath parameter to specify a directory where all the log files are copied.
New-NanoServerImage -DeploymentType Guest -Edition Standard -MediaPath PathToMediaen_us -BasePath .Base -TargetPath .NanoServer.wim -LogPath C:Logs
Note
Some parameters on New-NanoServerImage and Edit-NanoServerImage are for internal use only and can be safely ignored. These include the -SetupUI and -Internal parameters.
Installing apps and driversWindows Server App installer
Windows Server App (WSA) installer provides a reliable installation option for Nano Server. Since Windows Installer (MSI) is not supported on Nano Server, WSA is also the only installation technology available for non-Microsoft products. WSA leverages Windows app package technology designed to install and service applications safely and reliably, using a declarative manifest. It extends the Windows app package installer to support Windows Server-specific extensions, with the limitation that WSA does not support installing drivers.
Creating and installing a WSA package on Nano Server involves steps for both the publisher and the consumer of the package.
The package publisher should do the following:
Next, the package consumer should follow these steps:
Additional resources for creating apps
WSA is server extension of Windows app package technology (though it is not hosted in Microsoft Store). If you want to publish apps with WSA,these topics will help you familiarize youself with the app package pipeline:
Installing drivers on Nano Server
You can install non-Microsoft drivers on Nano Server by using INF driver packages. These include both Plug-and-Play (PnP) driver packages and File System Filter driver packages. Network Filter drivers are not currently supported on Nano Server.
Both PnP and File System Filter driver packages must follow the Universal driver requirements and installation process, as well as general driver package guidelines such as signing. They are documented at these locations:
Installing driver packages offline
Supported driver packages can be installed on Nano Server offline via DISM.exe or DISM PowerShell cmdlets.
Installing driver packages online
PnP driver packages can be installed to Nano Server online by using PnpUtil. Online driver installation for non-PnP driver packages is not currently supported on Nano Server.
Joining Nano Server to a domainTo add Nano Server to a domain online
Alternate method to join a domain in one step
First, harvest the data blob from another computer running Windows Threshold Server that is already in your domain using this command:
djoin.exe /provision /domain <domain-name> /machine <machine-name> /savefile .odjblob
Open the file 'odjblob' (perhaps in Notepad), copy its contents, and then paste the contents into the <AccountData> section of the Unattend.xml file below.
Put this Unattend.xml file into the C:NanoServer folder, and then use the following commands to mount the VHD and apply the settings in the
offlineServicing section:
dismdism /Mount-ImagemediaFile:.NanoServer.vhd /Index:1 /MountDir:.mountdir
dismdismmedia:.mountdir /Apply-Unattend:.unattend.xml
Create a 'Panther' folder (used by Windows systems for storing files during setup; see Windows 7, Windows Server 2008 R2, and Windows Vista setup log file locations if you're curious), copy the Unattend.xml file to it, and then unmount the VHD with these commands:
md .mountdirwindowspanther
copy .unattend.xml .mountdirwindowspanther
dismdism /Unmount-Image /MountDir:.mountdir /Commit
The first time you boot Nano Server from this VHD, the other settings will be applied.
After you have joined Nano Server to a domain, add the domain user account to the Administrators group on the Nano Server.
Working with server roles on Nano ServerUsing Hyper-V on Nano Server
Hyper-V works the same on Nano Server as it does on Windows Server in Server Core mode, with two exceptions:
Ethernet Controller Driver Windows Xp
In this release, these features of Hyper-V have been verified:
If you want to perform a live migration of virtual machines, create a virtual machine on an SMB share, or connect resources on an existing SMB share to an existing virtual machine, it is vital that you configure authentication correctly. You have two options for doing this:
Constrained delegation
Constrained delegation works exactly the same as in previous releases. Refer to these articles for more information:
CredSSP
First, refer to the 'Using Windows PowerShell remoting' section of this topic to enable and test CredSSP. Then, on the management computer, you can use Hyper-V Manager and select the option to 'connect as another user.' Hyper-V Manager will use CredSSP. You should do this even if you are using your current account.
Windows PowerShell cmdlets for Hyper-V can use CimSession or Credential parameters, either of which work with CredSSP.
Using Failover Clustering on Nano Server
Failover clustering works the same on Nano Server as it does on Windows Server in Server Core mode, but keep these caveats in mind:
Note
Additionally, certain features are not supported in this release:
Ethernet Controller For Windows 7
You'll find these Windows PowerShell cmdlets useful in managing Failover clusters:
You can create a new cluster with
New-Cluster -Name <clustername> -Node <comma-separated cluster node list>
Once you've established a new cluster, you should run
Set-StorageSetting -NewDiskPolicy OfflineShared on all nodes.
Add an additional node to the cluster with
Add-ClusterNode -Name <comma-separated cluster node list> -Cluster <clustername>
Remove a node from the cluster with
Remove-ClusterNode -Name <comma-separated cluster node list> -Cluster <clustername>
Create a Scale-Out File Server with
Add-ClusterScaleoutFileServerRole -name <sofsname> -cluster <clustername>
You can find additional cmdlets for failover clustering at Microsoft.FailoverClusters.PowerShell.
Using DNS Server on Nano Server
To provide Nano Server with the DNS Server role, add the Microsoft-NanoServer-DNS-Package to the image (see the 'Creating a custom Nano Server image' section of this topic. Once the Nano Server is running, connect to it and run this command from and elevated Windows PowerShell console to enable the feature:
Enable-WindowsOptionalFeature -Online -FeatureName DNS-Server-Full-Role
Using IIS on Nano Server
For steps to use the Internet Information Services (IIS) role, see IIS on Nano Server.
Using MPIO on Nano Server
For steps to use MPIO, see MPIO on Nano Server
Using SSH on Nano Server
For instructions on how to install and use SSH on Nano Server with the OpenSSH project, see the Win32-OpenSSH wiki.
Appendix: Sample Unattend.xml file that joins Nano Server to a domain
Note
Be sure to delete the trailing space in the contents of 'odjblob' once you paste it into the Unattend file.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |