Did you know that when you delete an Azure Resource Group, it deletes all the resources in that group?
You have built a Resource Group in Azure that contains your infrastructure resources including:
- Virtual Network
- Network Security Groups (NSG)
- Storage account to hold diagnostic logging for the NSGs
The subnets may host your IaaS Virtual Machines, maybe define your DMZ and your reverse proxy. So questions around risk need to be asked including:
- How easy is it to delete a Resource Group?
- Who can delete a Resource Group?
- What can be done to protect a Resource Group?
The Windows-To-Go creator tool (Wtgcreator.exe) is responsible for imaging a Windows-To-Go USB drive with a Windows Image (WIM) file.
This WIM file may be:
- Taken from a Windows 8.1 original ISO image
- A customised WIM image created using Configuration Manager or the Microsoft Deployment Toolkit (MDT)
To use the tool you simply:
- Plug in your certified USB device
- Start the Windows-To-Go Wizard
- Highlight your USB key and click Next
- Click ‘Add Search Location’ and provide a directory where the WIM file lives
- Select the correct WIM and begin the imaging process
When running through the Windows-To-Go creator wizard, no custom WIM files (even though they exist) are listed which prevents imaging.
Selecting a stock WIM file from the original ISO however works.
Use the DISM command to mount the WIM image to a temporary directory:
"DISM.exe /Mount-Wim /WimFile:C:\images\myimage.wim /index:1 /MountDir:C:\images\mount"
Close the WIM with the commit flag:
DISM.exe /Unmount-Wim /MountDir:C:\images\mount /commit
I don’t know why this works yet, but it does solve the immediate issue.
One interested thing to note is that the WIM file is now around 10MB larger.
Just a quick post.
I had a PDF file containing scanned pages (with signatures). There was a need for me to remove a page and replace it with an updated version.
Enter ‘PDF Rider’ to the rescue. A free Open Source programme that performed the job for me in less than a minute.
Awesome. And no cost!
When attempting to install KMS onto a Windows 2003 SP2 x86 server, I received a ‘Setup Error’ when running the command line ‘KMSW2K3.exe /l:c:\kmsinst.log’.
The installation then failed and rolled back without any further explanation.
Even the log file failed to shed any real light on the problem.
Turns out that I had to re-register my WMI components!
The following commands came from this link.
cd /d %windir%\system32\wbem
for %i in (*.dll) do RegSvr32 -s %i
for %i in (*.exe) do %i /RegServer
Obscure, but may hopefully help someone!