Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

According to NCR, the largest ATM supplier in the U.S., over 90% of the world's cash machines are powered by Windows XP. A further 4% are running Windows 3.11 [for Workgroups] which according to several hacking groups, have had Windows XP wallpaper installed to avoid paying license fees.

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Today we have released the latest versions of Imaging Toolkit and Deployment Monitor, which are available to download.

Imaging Toolkit 9.0.2

This release includes the following:

  • Support for Windows 8.1 with Update (Nov'14) media
  • Support for Windows Server 2012 R2 with Update (Nov'2014) media
  • Status updates now include Zim and Ztoolkit log files (requires Deployment Monitor 1.0.4)
  • Ability to prepare a master VDI image using ZcloneWiz
  • Base Image partition size is now 60GB by default for new projects
  • Improved driver downloads from slow connections
  • Improved support for long file paths in Build Console
  • WinPE imaging now handles network adapters that are slow to initialise
  • Zim logging is now enabled by default (zimrun.s and zimpeget.cmd)
  • Bug fixes since Imaging Toolkit 9.0.1

Imaging Toolkit release history

One of the most exciting changes in 9.0.2, is support for Deployment Monitor's log viewing capability. If you have ever tried to analyse imaging and Windows build process log files, you are going to love this feature. See the next section for more details.

Deployment Monitor 1.0.4

This release includes the following:

  • Ability to display build process log files (requires Imaging Toolkit 9.0.2)
  • Mobile App compatible (to be released at later date)
  • Bug fixes since Deployment Monitor 1.0.3

Deployment Monitor release history

Deployment Monitor 1.0.4 includes a lot of engineering effort, most of which you won't see until we release the Deployment Monitor Mobile App. The Mobile App on Android and iOS, will give you a real time view of machines whether they are in-progress, successful, or failed. We'll be talking more about the Mobile App in the near future when it's available to download.

The 1.0.4 release includes the ability to view deployment log files created by Imaging Toolkit. Until now, it has been painful to retrieve log files from the imaging environment. Using Imaging Toolkit 9.0.2, log files for imaging and the Windows build process will be automatically sent to the Deployment Monitor 1.0.4 server (provided a Deployment Monitor server has been configured in Build Console). Using the Deployment Monitor Web Console, you can now view the log files, which opens a window with a conbined Zim and Ztoolkit log. Furthermore, the log files can be saved to a single text file and sent to ENGL to help with troubleshooting.

Check out the Deployment Monitor home page for screenshot heaven.


Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Following on from TID-2015001 we have just published a second TID on site-specific build customisation. This time we used the octets of the subnet IP address to identify the site location. The example is very simple but the method can be applied to complex architectures and if necessary a second (or even third) layer of drill down choices can be applied.

For example you could select a site and then within that site select a building and within the building a department.

Here is the link to the new TID-2015002: Site-specific build customisation (using the subnet)

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Have you ever wanted to know which of your PCs were built using the ENGL deployment process, and when they were last built? Deployment Monitor is great for tracking builds as they happen and it has a history function, but if you want a snapshot of all your PCs, then we can turn to ZENworks Asset Inventory. See TID-2015003: Adding ENGL build information to ZENworks Asset Inventory

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

We have published a TID that talks you through how a single project can be amended  
to read in site-specific information so it can be delivered on multiple sites to maintain consistency. 
There are many ways to identify the site-specific information and the best way for you is dictated by your own environment.  The guidelines in the TID can easily be modified to meet your own needs.  In this TID we have used the IP address of the ZENworks server (PROXYADDR) to determine the machine's "site" characteristics. Please take a look at this new TID 2015001.

If you have any comments on this TID then we would love to hear from you.