User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Imaging Toolkit 8.0 is now available to download!

We would like to thank all our BETA testers and partners for their feedback!

Highlights of this release are:

  • ZENworks Configuration Management 11.2.3 support
  • System Center 2012 Configuration Manager SP1 support
  • Windows 8 and Server 2012 deployment
  • Single instance driver storage
  • Driver analysis enhancements

For a complete list of changes view the Imaging Toolkit Release History.

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Imaging Toolkit 8 will help you to create and deploy a Windows 8 machine with either ZENworks (11.2.3a) or System Center Configuration Manager 2012 SP1

By default the Windows 8 build will contain a selection of new start menu apps that may or may not be appropriate for your users. These apps may also be slightly out of date.

Default

The normal power options (Shutdown, Restart and Log Off) are also hidden behind the [Windows Key] +C charms menu which takes a little bit of getting used to.

Charms


Many administrators will probably want to remove the Windows Store apps and also create suitable Shutdown, Restart and Log Off buttons on the new style start menu.

This is possible using some PowerShell scripts. What is even better is that Imaging Toolkit 8 allows you to run PowerShell scripts as phase scripts which lets you do these steps automatically during your build process.
For more information on phase scripts check out: https://www.engl.co.uk/documentation/imagingtoolkit/8.0/content/implementation-zcm-customhooks.htm

The scripts:

Remove Windows Store apps:


Import-Module Appx
Import-Module Dism
 
# Remove provisioned apps from logged in user.
 
Get-AppXProvisionedPackage -online | Remove-AppxProvisionedPackage -online
 
# Remove provisioned apps from all users
 
Get-AppXPackage | Remove-AppxPackage

 


Remove Windows Store shortcut: 


# Remove Windows Store shortcut link from the Start Menu
 
Remove-Item "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Windows Store.lnk" -force



Add Windows power icons to Start Menu: 


Import-Module C:\ztoolkit\CreateWindowsTile.psm1
New-OSCWindowsTile


The CreateWindowsTile.psm1 module can be downloaded from here: http://gallery.technet.microsoft.com/scriptcenter/Create-a-ShutdownRestartLog-37c8111d

Customise the Default User icon: 

# Set up Default User icons
 
Move-Item c:\ztoolkit\user.bmp "C:\ProgramData\Microsoft\User Account Pictures" -force
Move-Item c:\ztoolkit\user.png "C:\ProgramData\Microsoft\User Account Pictures" -force


Combine these files and commands into a phase0-before.ps1 file:


# Import modules
 
Import-Module Appx
Import-Module Dism
Import-Module C:\ztoolkit\CreateWindowsTile.psm1
 
# Remove provisioned apps from logged in user.
 
Get-AppXProvisionedPackage -online | Remove-AppxProvisionedPackage -online
 
# Remove provisioned apps from all users
 
Get-AppXPackage | Remove-AppxPackage
 
# Remove Windows Store shortcut link from the Start Menu
 
Remove-Item "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Windows Store.lnk" -force
 
# Add Windows power icons to Start Menu
 
Import-Module C:\ztoolkit\CreateWindowsTile.psm1
New-OSCWindowsTile
 
# Set up Default User icons
 
Move-Item c:\ztoolkit\user.bmp "C:\ProgramData\Microsoft\User Account Pictures" -force
Move-Item c:\ztoolkit\user.png "C:\ProgramData\Microsoft\User Account Pictures" -force

 

 

Save this as phase0-before.ps1 file and add to your Windows 8 project's Custom Files folder.

Add the CreateWindowsTile.psm1 extracted from the download link found here: http://gallery.technet.microsoft.com/scriptcenter/Create-a-ShutdownRestartLog-37c8111d then add to your project's Custom Files folder.

Make a custom version of the Default User icon files.
The originals can be found in "C:\ProgramData\Microsoft\User Account Pictures" on a Windows 8 machine.
Make a copy of these then update them as required. I have added a small ENGL logo to the images.

modified modified


When you are happy with the files add these into the project's Custom Files folder.



Once the project has been updated create a ztoolkit image for the project and then copy the resulting image file to the imaging server.

Now PXE boot your machine and restore the appropriate Windows 8 Project.
Once the machine has been built the Default User icons will now use the Custom Files.

Logon

The Start Menu only has a bare minimum of applications (which can of course be added to using ZENworks or System Center Configuration Management to deploy apps during your build)



There is also a Shutdown, Reboot and Log Off application shortcut available under "All apps" on the Windows 8 Start menu.

All

 

 

 

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

When using either Imaging Toolkit or Driver Manager drivers are delivered to a machine as it is being deployed.

Occasionally machines fail to deploy or install all the drivers correctly. The quickest way of reviewing what drivers are missing is to open Device Manager (devmgmt.msc) on the machine and check for unknown devices or those reporting an error.



Where it is not obvious which device to use the Report Issue functionality, for example, the “Base System Device” in the image above, the Hardware IDs can be used in order to work out which device does not have a driver.
This involves displaying the properties for each device with an error, reviewing the Details tab, identifying all the Hardware IDs and searching through the machine XML files to find the matching device.

In order to simplify this process we have created a simple vbscript file that can be executed on a machine to gather information about the devices in error.

The output from the script can then be pasted into the Driver Issue Report in either Build Console or Driver Manager and gives us a lot more information to assist in identifying the missing drivers.

The sample script below logs the information to C:\Unknown-Devices.log.

on error resume next
Set objFSO = CreateObject("Scripting.FileSystemObject")
Set shell = CreateObject("Shell.Application")

'Option Explicit

Const ForAppending = 8

' set up logging
Set objLogFile = objFSO.OpenTextFile("c:\Unknown-Devices.log", ForAppending, True)
objLogFile.WriteBlankLines(2)

Dim oWMI, sComputerName, colItems, oItem
sComputerName = "."
Set objWMIService = GetObject("winmgmts:\\.\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_ComputerSystem")
For Each objItem in colItems
objLogfile.WriteLine "====================================================="
objLogfile.WriteLine " Hardware "
strmanufacturer = objItem.Manufacturer
objLogfile.WriteLine " Manufacturer: " & objItem.Manufacturer
objLogfile.WriteLine " Model: " & objItem.Model
objLogfile.WriteLine " Name: " & objItem.Name
Next

if strmanufacturer = "LENOVO" then
Set objWMIService = GetObject("winmgmts:\\.\root\cimv2")
Set colItems1 = objWMIService.ExecQuery("Select * from Win32_ComputerSystemProduct")
For Each objItem in colItems1
objLogfile.WriteLine " Lenovo Model: " & objItem.Version
Next
End If

Set oWMI = GetObject ("winmgmts:\\.\root\cimv2")
Set colItems = oWMI.ExecQuery ("Select * from Win32_PnPEntity where status = 'error'")
objLogfile.WriteLine "====================================================="
objLogfile.WriteLine " Script ran at " & Time & " on " & Date
objLogfile.WriteLine "====================================================="

For Each oItem In colItems
objLogFile.WriteBlankLines(1)
objLogfile.WriteLine "Name: " & oItem.Name
objLogfile.WriteLine "DeviceID: " & oItem.DeviceID
objLogfile.WriteLine "PNP Device ID: " & oItem.PNPDeviceID
objLogfile.WriteLine "Description: " & oItem.Description
objLogfile.WriteLine "manufacturer: " & oItem.Manufacturer
objLogFile.WriteBlankLines(1)
objLogfile.WriteLine "====================================================="
Next

objLogFile.WriteBlankLines(2)
objLogfile.WriteLine "If missing drivers have been found please paste the content of this file into the Driver Manager / Build Console driver issue report"
objLogFile.Close

wscript.echo "Processing complete. Review c:\Unknown-Devices.log file"
 

 

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

To coincide with the soon to be released ENGL Imaging Toolkit 8.0 which includes support for both System Center 2012 Configuration Manager and ZENworks 11 Configuration Management, ENGL is pleased to announce an optional Retro Imaging Pack.

The Retro Imaging Pack supports the import and deployment of Sinclair ZX Spectrum BASIC, Amiga Kickstart and Commodore BASIC. Based on demand from older customers who refuse to clear out their attics of old retro gaming machines will be delighted to purchase this expansion pack.



ENGL is working hard to support customers wishing to allow employees to bring in their own hardware. With the Retro Imaging Pack, corporate customers can now manage ZX Spectrum, Amiga and Commodore (VIC-20 and C-64 only at this time) along side their Windows hardware.

Proof of age will be required when placing an order together with a test on which 80's gaming machine is the best, which is clearly the Commodore C-64. Stay tuned for further details.

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

After months of scoping, we're gearing up for what could be Imaging Toolkit's biggest evolutionary leap so far - Microsoft System Center 2012 Configuration Manager support!

For 10 years we've given the ZENworks community the most advanced and feature rich Windows deployment solution. Don't panic! That will not change! We're committed to Novell ZENworks and will continue to support new ZENworks releases. Imaging Toolkit 8 includes new features for our ZENworks customers that make deployment configuration even easier.

If you're using or planning to move to System Center you too will have access to our industry leading driver management, Zim imaging front-end, and automated deployment process.

So, if you're using System Center 2012 or ZENworks 11 and would like to be involved in our closed BETA please complete the application survey below. Don't spend too long thinking it over, closing date for BETA applications is 31st August 2012.

Imaging Toolkit 8 BETA participation survey