User Rating: 5 / 5

Star ActiveStar ActiveStar ActiveStar ActiveStar Active

When a DLU policy is configured and associated to all workstations in an environment with multiple user sources but is not needed on Active Directory builds the policy can cause issues on login. A requirement can be applied to the policy to ensure that the policy is only applied to machines with the Novell Client installed and that are not Domain members.

Scenario:

  • ZENworks 11.x configured with an AD and an eDirectory user source.

  • Multiple ENGL projects configured (AD only, eDirectory only and AD + eDirectory)

  • DLU policy configured and associated to all workstations but is not needed on AD builds

Solution:

Apply a requirement to ensure that the DLU policy is active when required.

Note: ENGL recomends that policies are disabled during the build process. The filter being described here is in addition to this requirement.

Steps:

  • Login to ZENworks Control Center

  • Open the policy to be edited

  • Select "Requirements" tab

    There should be a filter defined already as defined in our documentation: https://www.engl.co.uk/documentation/imagingtoolkit/7.0/content/proc-prerequisites-config.html#Disable



  • Check the "Combine Filters" option is set to "and"

  • Click "Add Filter"

    Define the following parameters:

    • Filter type : Novell Client Installed

    • Operators : Yes

  • Click "Add Filter"

    Define the following parameters:

    • Filter type : Environment Variable Value

    • Value : USERDOMAIN

    • Operators : Not equal to

    • Value: e.g. ENGLLAB



  • Click Apply

  • Increment version of policy (ZCM10.3.x)

  • Publish new version of policy (ZCM11.x)

The policy will now no longer apply during the ENGL build process and will only apply post build if the Novell client is installed and the USERDOMAIN environment variable does not match the AD domain.

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

Scenario:

I have used the latest version of the ENGL Driver Manager (latest internal BETA) software to create driver packages and application packages in my SCCM 2012 RC test server.
The appropriate packages have been created successfully and are visible within the SCCM 2012 Console.
The packages were distributed to the distribution point then added to an existing task sequence

Error:

The Task sequence reports an error when attempting to deploy it:

This task sequence cannot be run because the
program files for SCO00015 cannot be located on a distribution point.

Resolving the error:

To review the actual error message within the WinPE environment:

  • Press F8 to launch a command window (this needs to be configured in the appropriate boot image properties page)



  • Launch cmtrace.exe from the command prompt.



    (cmtrace.exe is a replacement for trace32.exe and is included by default in the WinPE boot image)

  • Accept the prompt to make this the default log viewer.

  • Open x:\windows\temp\SMSTSLog\smsts.log file. This gives all the information about the task sequence and any errors.

Reviewing the log file I get the following error(s)

Failed to resolve selected task sequence dependencies. Code(0x80040102)


A google search on this error code gave some useful information but nothing that appeared to help resolve the issue.

I then switched back to the System Center 2012 Configuration Manager Console. SCCM 2012 has a different look and feel to SCCM 2007 which makes things interesting when tracking things down.

The console has a "Monitoring" section. This has several options that let you check the status of different SCCM 2012 components.
Selecting Overview -> Distribution Status -> Content Status allows you to check the status of individual packages.



Select the Package that is reporting an error. In this case SCO00015

Right Click on the package then select View Status



Four tabs are now visible

Success Status information is currently unavailable for this deployment
In Progress Waiting for prestaged content
Error Status information is currently unavailable for this deployment
Unknown Status information is currently unavailable for this deployment


Reviewing the "In Progress" Asset Details the description says:

Distribution Manager is waiting for the package SCO00015 content to be prestaged on the distribution point. 
You must manually prestage the package SCO00015 on the distribution point before the content will be available.

This confirms that the package has not been updated on the distribution point.

Switching back to the Software Library > Overview > application Management > Packages > VMware, Inc.



I can view the packages created by Driver Manager.

Right click on the VMware-Virtual-Platform-Win7-x86-2 package (SCO00015)
Select Properties
Review the package details.


Distribution settings has the setting "Manually copy the content in this package to the distribution point" set.

Change this option to "Automatically download content when packages are assigned to distribution point"
Click apply.
Right click on the package.
Select "update distribution point".
The distribution point now updates successfully.
Reviewing the content status for the package it shows

Content was distributed to distribution point

PXE booting the virtual machine I now have a task sequence that deploys successfully.

I have reviewed other packages that were created by Driver Manager or created manually. These default to "Automatically download content when packages are assigned to distribution point" and as expected distribute successfully to the distribution point when assigned.

At some point when initially reviewing the package properties I must have been changed the distribution setting without noticing!

SCCM2012 looks different to SCCM2007 which makes troubleshooting issues interesting until you find your way around the console.
Prestaging content is also a useful feature to have if you are aware that it exists and don't enable it on a package by mistake!

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

When you use Zclonewiz to create a clone of a built machine (more information on Zclonewiz here: https://www.engl.co.uk/documentation/imagingtoolkit/7.0/content/cloning.htm ) you will need to deploy the clone image to machines.

We have published a TID that talks you through setting up a Clone menu within Zim.

This TID will give you the ability to do the following:

  • Configure a clone master machine as an img multicast master.

  • Create a server image of a clone master machine.

  • Configure a clone target machine as an img multicast client machine .

  • Restore a clone image from the ZENworks imaging server to the target machine.

  • Populate ZISD with the computername and other appropriate attributes.

For more information check out TID 2012003

User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

We have had reports that the Windows 7 unattend process can stall at the "completing installation" screen.

This can occur in the following scenario:

  • VMWare virtual machine
  • Windows 7 iso attached to virtual machine
  • USB pendrive containing unattend files attached to virtual machine

Solution:
Remove the USB pendrive once the Windows 7 installation process has rebooted for the first time.



User Rating: 0 / 5

Star InactiveStar InactiveStar InactiveStar InactiveStar Inactive

When deploying an Imaging Toolkit project to a machine we expect to have administrator rights in order for the deployment process to complete successfully.

ZENworks DLU and GPO policies can be inherited by the machine as soon as it is registered. These policies may then impact on the local user the build is using when then may cause problems with phase 3 of the build process.

We recommend that any policies that are inherited by the deployment process (Machine or Installer user) have a requirement set on them to ensure that they are not active while a build is in process.

This requirement is detailed in our product documentation : https://www.engl.co.uk/documentation/imagingtoolkit/7.0/content/proc-prerequisites-config.html#Disable

It is possible to identify if a policy is being picked up by a machine by reviewing the deployment process log file (ztoolkit.log) on the machine:

[06-Mar-12 11:06:03] [ZapphookZcm] [Debug] ActionSet processing BEGIN 
[06-Mar-12 11:06:03] [ZapphookZcm] [Debug] Current Task: PolicyManager
[06-Mar-12 11:06:03] [ZapphookZcm] [Debug] Current Task Status: Downloading
[06-Mar-12 11:06:12] [ZapphookZcm] [Debug] ActionSet processing END

As you can see there is a policy being processed but there is no indication which policy is being processed.

We have just published a TID that shows how to list the ZENworks policies that are picked up during the deployment process.

For more information check out https://www.engl.co.uk/kb/tid-2012005.htm