WDS Import-WDSInstallImage Overview - Tips

I am studying for an upcoming Microsoft exam #70-411 and I was practicing the new WDS (Windows Deployment Services) features in the Windows Server 2012 R2 and I ran into a little problem.


Now, as Microsoft is pushing the new PowerShell, I thought, I would only use Microsoft PowerShell to setup the whole environment. So I've installed the WDS Role with the following command;

Install-WindowsFeature -Name WDS -IncludeManagementTools

Once the feature is installed. I decided to create 2 Image groups called "Server2012R2" & "Win8".

New-WDSInstallImageGroup -Name "Server2012R2"
New-WDSInstallImageGroup -Name "Win8"

Now, it's time to add a couple of install images. You can use any server 2012 or windows 8 setup media and use the "install.wim". The file is located under .\Sources folder. So, here it goes;

Import-WDSInstallImage -Path "D:\Sources\Install.wim" -ImageGroup "Server2012R2"

And... An unexpected error occurs.







Hmmm, OK! I'm smart enough to fool a computer with a fake image name :)

Import-WDSInstallImage -Path "D:\Sources\Install.wim" -ImageName "Server 2012 R2 Standard" -ImageGroup "Server2012R2" 


Nope! Looks like my trick didn't work either. So I had to investigate a little more. Let me look at that image first.

Get-WindowsImage -Image "D:\Sources\install.wim"



Now, everything makes sense. The install.wim I was trying to use has multiple image indexes with different versions of the Windows Server. I had to specify which index I wanted to import and it looks like the only way of doing that is getting the exact "image names" from the install.wim

So the final line here did the trick for me.

Import-WDSInstallImage -Path "D:\Sources\install.wim" -ImageName "Windows Server 2012 R2 SERVERSTANDARD" -skipverify

Enjoy,

Comments

Post a Comment

Popular posts from this blog

System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation (Public Queue create issue)

This is a weird issue that I don't fully understand why it would happen. But the symptoms are very persistent as we're able to reproduce these behavior easily. Issue: The MSMQ (Microsoft Message Queuing) fails to create Public Queues and throws  "the System.Messaging.MessageQueueException (0x80004005): A workgroup installation computer does not support the operation" exception.
Read more

Veeam Backup Error : Failed to prepare guest for hot backup. Error: VSSControl

Image
Problem Description; I had this issue on one of my backup jobs recently and I was able to fix the issue with the solution explained below. After a quick google search, I realized that I'm not the only one and neither you are :) Full Error Description; Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait tim eout 9 00 sec Error: VSSControl: Failed to prepare guest for freeze, wait timeout 900 sec
Read more

warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead - Chef Development Kit Update

Today, I needed to do some tests with a newer version of the Chef Client and test my cookbooks. To version 14.12.9-1 to be precise. I also upgraded my ChefDK on my workstation to the 4.2.0 version. I believe that upgrades Ruby version as well and now I have ruby version 2.6.3p62 Right after the upgrade, I tried with a basic knife node list command to see if I needed to reboot or anything was broke... Everything seems to be working fine, except I get this annoying "warning" message. As it's just a warning, I don't really care about it as it just seems to annonce something that is deprecated... Problem; You receive "warning: Win32API is deprecated after Ruby 1.9.1; use fiddle directly instead" warning when using ruby or chef knife commands. Solution; You need to comment out that warning message in Ruby lib scripts.
Read more