jcsmith1 Absent Member.
Absent Member.
3000 views

"Pending" when using Recurring - When Device Refreshed

When you try to deploy software using Recurring - When device is refreshed it will many times place the install in a pending state and either not deploy or deploy when a you manually refresh the device. I've had to randomly call users and, yes, I've found a condition where some users do not reboot their PCs that often and they are stuck pending until they reboot, but many would not get the update even if you reboot and it would actually require you to manually refresh ZenWorks.

ZCM 10.3.0 with clients still at 10.2.2 but I've tested it against 10.3.0 clients.

Bundle example:
Bundle copies 2 small files to the root of C: then another bundle and a static Windows icon access these files. The day of the deployment users call in saying the icon linking to the files doesn't work. I check the status of the bundle's deployment and see they're stuck in "Devices Pending" for Overall Deployment Status. When I remoted them I simply refreshed and they got the file.

The only workaround I've found is to use ZenWorks Login (Windows Login doesn't seem to work), but then I'm not getting the employees who rarely reboot.

Any ideas?
Labels (2)
Tags (1)
0 Likes
18 Replies
Anonymous_User Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

jcsmith1,

>
>Bundle example:
>Bundle copies 2 small files to the root of C: then another bundle and a
>static Windows icon access these files. The day of the deployment users
>call in saying the icon linking to the files doesn't work. I check the
>status of the bundle's deployment and see they're stuck in "Devices
>Pending" for Overall Deployment Status. When I remoted them I simply
>refreshed and they got the file.


One guess that I would have is that a previous action isn't finishing.
Usually this is because a return code was return that wasn't 0 as the
bundle by default expects.

There could be other reasons, but that is the first that comes to mind.

--
Jared Jennings
Senior Systems Architect, Data Technique, Inc.
http://www.datatechnique.com

My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
Twitter@ jaredljennings
0 Likes
Highlighted
jcsmith1 Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

Jared,

Does this only apply to launching an executable? In this bundle I copy an exe and a bat file from a network share to c:\temp\, next I create a directory called ChangePassword in c:\Novell and finally I copy those files to c:\novell\ChangePassword\.

Currently there are 96 machines out of 1500+ who didn't receive the update, but so far my research shows these aren't machines used by users. It took a heck of a lot to get it out to everyone without users calling in. Next time we're just going to let it silently deploy for a good week then alert the users. 🙂

I love Zen 10...
0 Likes
jcsmith1 Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

This doesn't make any sense... in another Bundle 21 devices effective... 6 succeeded... 15 pending. Call a user, refresh their Zen and it deploys. Ask a user to reboot, nothing, then refresh and it deploys.
0 Likes
jcsmith1 Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

I just confirmed this also happens when using the ZenWorks login event unlike I previously thought.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

What happens if you manually launch the bundle?

--
Jared Jennings
Senior Systems Architect, Data Technique, Inc.
http://www.datatechnique.com

My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
Twitter@ jaredljennings
0 Likes
jcsmith1 Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

It installs without issue. This is what has me confused is what causes the "pending". I've even tried "Install Now" and pendings continue (even if I refresh all active workstations).

Jared Jennings;2053895 wrote:
What happens if you manually launch the bundle?

--
Jared Jennings
Senior Systems Architect, Data Technique, Inc.
Data Technique, Inc. | Information Technology Consulting Solutions

My Blog and Wiki with Tips, Tricks, and Tutorials
Main Page - ZENWorks Wiki
Twitter@ jaredljennings
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

jcsmith1,

>Does this only apply to launching an executable? In this bundle I copy
>an exe and a bat file from a network share to c:\temp\, next I create a
>directory called ChangePassword in c:\Novell and finally I copy those
>files to c:\novell\ChangePassword\.


Double-check, but I believe an error is thrown if the directory already
exists. I am 99% sure you need to check the box, continue on error. I was
going to check for you, but I didn't get to it.

--
Jared Jennings
Senior Systems Architect, Data Technique, Inc.
http://www.datatechnique.com

My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
Twitter@ jaredljennings
0 Likes
jcsmith1 Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

I'm going to check this and report back. I'll try more tests as well. I spoke with Novell about this once while working on another SR and they seemed to think it was a lag in the server finding out about the status of the bundle and I thought that was the case, but it seems not. Maybe I need to open an SR about this specifically?

Jared Jennings;2053894 wrote:
jcsmith1,

>Does this only apply to launching an executable? In this bundle I copy
>an exe and a bat file from a network share to c:\temp\, next I create a
>directory called ChangePassword in c:\Novell and finally I copy those
>files to c:\novell\ChangePassword\.


Double-check, but I believe an error is thrown if the directory already
exists. I am 99% sure you need to check the box, continue on error. I was
going to check for you, but I didn't get to it.

--
Jared Jennings
Senior Systems Architect, Data Technique, Inc.
Data Technique, Inc. | Information Technology Consulting Solutions

My Blog and Wiki with Tips, Tricks, and Tutorials
Main Page - ZENWorks Wiki
Twitter@ jaredljennings
0 Likes
jcsmith1 Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

I created a simple test bundle for my tests and it does the following:
Copy File M:\Software\Office2007\Updates\MAINWWsp2.msp to c:\temp\.
Remove File c:\temp\FileMAINWWsp2.msp.

Pointless, yes, but for a test I think it works. Here is an XML export of the bundle:

<?xml version="1.0" encoding="UTF-8"?>
<ns1:Bundle xmlns:ns1="http://novell.com/zenworks/datamodel/objects/bundles" xmlns="http://novell.com/zenworks/datamodel/objects/bundles">
<ns2:UID xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">2ea72734713d1ef8a061a09af44803ef</ns2:UID>
<ns2:Name xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">TestDeployPending</ns2:Name>
<ns2:InternalName xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">TestDeployPending</ns2:InternalName>
<ns2:ParentUID xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">1d6a16f87785c895a7f530d80b560da2</ns2:ParentUID>
<ns2:Path xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">/Bundles/TestDeployPending</ns2:Path>
<ns2:InternalPath xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">/~bundles~/TestDeployPending</ns2:InternalPath>
<ns2:AdminID xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">Bundles</ns2:AdminID>
<ns2:Description xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">Test</ns2:Description>
<ns2:PrimaryType xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">Bundle</ns2:PrimaryType>
<ns2:SubType xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">Windows Bundle</ns2:SubType>
<ns2:GeneralType xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">2</ns2:GeneralType>
<ns2:Deletable xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">true</ns2:Deletable>
<ns2:Undeletable xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">false</ns2:Undeletable>
<ns2:ErrorWarningStatus xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">1</ns2:ErrorWarningStatus>
<ns2:ComplianceStatus xmlns:ns2="http://novell.com/zenworks/datamodel/objects" xmlns="http://novell.com/zenworks/datamodel/objects">1</ns2:ComplianceStatus>
<ns2:IsEnabled xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">true</ns2:IsEnabled>
<ns2:Version xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">5</ns2:Version>
<ns2:Revision xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">0</ns2:Revision>
<ns2:ContentInfoVer xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">0</ns2:ContentInfoVer>
<ns2:ContentPriority xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">0</ns2:ContentPriority>
<ns2:NextRevision xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">0</ns2:NextRevision>
<ns2:Replication xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">2</ns2:Replication>
<ns2:Sandbox xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">false</ns2:Sandbox>
<ns2:SatelliteRep xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">2</ns2:SatelliteRep>
<ns2:Inheritance xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">15</ns2:Inheritance>
<ns2:ContentTypeTags xmlns:ns2="http://novell.com/zenworks/datamodel/objects/assignablecontent" xmlns="http://novell.com/zenworks/datamodel/objects/assignablecontent">Windows-Bundle</ns2:ContentTypeTags>
<ns2:ActionSets xmlns:ns2="http://novell.com/zenworks/datamodel/objects/actions" xmlns="http://novell.com/zenworks/datamodel/objects/actions">

To be continued in another post...
0 Likes
jcsmith1 Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed


<Id>1e2b11587e2474bd3750e4cab9594944</Id>
<Type>Distribution</Type>
<Version>1</Version>
<Modified>false</Modified>
<Actions>
<Id>674e9c3c802f33b507bbc1eb7b53827e</Id>
<Type>Distribute Action</Type>
<ContinueOnFailure>false</ContinueOnFailure>
<Enabled>true</Enabled>
</Actions>
</ns2:ActionSets>
<ns2:ActionSets xmlns:ns2="http://novell.com/zenworks/datamodel/objects/actions" xmlns="http://novell.com/zenworks/datamodel/objects/actions">
<Id>2aa92e5374962761b03e94698a4f26a2</Id>
<Type>Uninstall</Type>
<Version>1</Version>
<Modified>false</Modified>
<Data>
<ns1:Uninstall xmlns:ns1="http://novell.com/zenworks/apps/appSchema">
<Enabled xmlns="http://novell.com/zenworks/apps/appSchema">false</Enabled>
<AllowManual xmlns="http://novell.com/zenworks/apps/appSchema">false</AllowManual>
<DaysBeforeUninstallWhenNotUsed xmlns="http://novell.com/zenworks/apps/appSchema">-1</DaysBeforeUninstallWhenNotUsed>
<IgnoreChainedDependencies xmlns="http://novell.com/zenworks/apps/appSchema">false</IgnoreChainedDependencies>
</ns1:Uninstall>
</Data>
<Actions>
<Id>3b3871c9743470e1fdde6f7f560072e6</Id>
<Type>Undo Install</Type>
<ContinueOnFailure>false</ContinueOnFailure>
<Enabled>true</Enabled>
</Actions>
</ns2:ActionSets>
<ns2:ActionSets xmlns:ns2="http://novell.com/zenworks/datamodel/objects/actions" xmlns="http://novell.com/zenworks/datamodel/objects/actions">
<Id>5291a948ef0744cc8b40d7f9f2b5fb22</Id>
<Type>Launch</Type>
<Version>1</Version>
<Modified>false</Modified>
<Data>
<ns1:Launch xmlns:ns1="http://novell.com/zenworks/apps/appSchema" />
</Data>
</ns2:ActionSets>
<ns2:ActionSets xmlns:ns2="http://novell.com/zenworks/datamodel/objects/actions" xmlns="http://novell.com/zenworks/datamodel/objects/actions">
<Id>548730dd93bb7e4a4d937881c2b7a6cd</Id>
<Type>Install</Type>
<Version>2</Version>
<Modified>false</Modified>
<Data>
<ns1:Install xmlns:ns1="http://novell.com/zenworks/apps/appSchema">
<InstallOption xmlns="http://novell.com/zenworks/apps/appSchema">InstallPerMachine</InstallOption>
<AllowedPostpones xmlns="http://novell.com/zenworks/apps/appSchema">3</AllowedPostpones>
</ns1:Install>
</Data>
<Actions>
<Id>86596d7fb0449199188b4e43e240b403</Id>
<Name>Copy File(s)</Name>
<Type>Copy Files Action</Type>
<Data>
<ns1:CopyFilesData xmlns:ns1="http://www.novell.com/ZENworks/Actions/v1.0">
<File xmlns="http://www.novell.com/ZENworks/Actions/v1.0">
<FileName>MAINWWsp2.msp</FileName>
<DestDir>c:\temp\</DestDir>
<CreateFilesAsLinks>false</CreateFilesAsLinks>
<FileAttributes>
<FileAttribute Name="Hidden" default="false">false</FileAttribute>
<FileAttribute Name="ReadOnly" default="false">false</FileAttribute>
</FileAttributes>
<DestFileName>MAINWWsp2.msp</DestFileName>
<SourceDir>M:\Software\Office2007\Updates\</SourceDir>
<CopyOption>CopyAlways</CopyOption>
</File>
<ImpersonateCopy xmlns="http://www.novell.com/ZENworks/Actions/v1.0">USER</ImpersonateCopy>
</ns1:CopyFilesData>
</Data>
<ContinueOnFailure>false</ContinueOnFailure>
<Enabled>true</Enabled>
</Actions>
<Actions>
<Id>c907fd771a2b9faee03b6e1b07978f62</Id>
<Name>File Removal</Name>
<Type>File Removal Action</Type>
<Data>
<ns1:FileRemovalActionData xmlns:ns1="http://www.novell.com/ZENworks/Actions/v1.0" deleteFolderIfEmpty="false" includeSystemFiles="false" retryCount="3" retrySecondsInterval="5">
<File xmlns="http://www.novell.com/ZENworks/Actions/v1.0">c:\temp\MAINWWsp2.msp</File>
</ns1:FileRemovalActionData>
</Data>
<ContinueOnFailure>false</ContinueOnFailure>
<Enabled>true</Enabled>
<Properties>Impersonation=SYSTEM;</Properties>
</Actions>
</ns2:ActionSets>
<ns2:ActionSets xmlns:ns2="http://novell.com/zenworks/datamodel/objects/actions" xmlns="http://novell.com/zenworks/datamodel/objects/actions">
<Id>6debad7191c0f2154b14c7ac686935f8</Id>
<Type>Terminate</Type>
<Version>1</Version>
<Modified>false</Modified>
<Data>
<ns1:Terminate xmlns:ns1="http://novell.com/zenworks/apps/appSchema">
<Enabled xmlns="http://novell.com/zenworks/apps/appSchema">true</Enabled>
</ns1:Terminate>
</Data>
<Actions>
<Id>1748d755505da6dd0709f57dfc0c9d57</Id>
<Type>Terminate Action Prompt</Type>
<ContinueOnFailure>false</ContinueOnFailure>
<Enabled>true</Enabled>
</Actions>
<Actions>
<Id>4aaa9cd6040b29516bce7c3acf5ed96e</Id>
<Type>Terminate Action</Type>
<ContinueOnFailure>false</ContinueOnFailure>
<Enabled>true</Enabled>
</Actions>
</ns2:ActionSets>
<ns2:ActionSets xmlns:ns2="http://novell.com/zenworks/datamodel/objects/actions" xmlns="http://novell.com/zenworks/datamodel/objects/actions">
<Id>6fe4105a0de6e1a09d5aace8675c35f3</Id>
<Type>Verify</Type>
<Version>1</Version>
<Modified>false</Modified>
<Actions>
<Id>fbe5bcb29d3940b5d2f005cbd9f72cd4</Id>
<Type>Verify Install</Type>
<ContinueOnFailure>false</ContinueOnFailure>
<Enabled>true</Enabled>
</Actions>
</ns2:ActionSets>
<DisplayName>TestDeployPending</DisplayName>
<CreationDate>2010-12-08T07:33:28</CreationDate>
<Data><ns1:ApplicationBundleData xmlns="http://novell.com/zenworks/datamodel/objects/bundles" xmlns:ns1="http://novell.com/zenworks/datamodel/objects/bundles"><AlwaysShowIcon>false</AlwaysShowIcon><ShowProgress>true</ShowProgress></ns1:ApplicationBundleData></Data>
</ns1:Bundle>


The above yeilds the same result. For instance I associated that bundle to a test user, rebooted and it did not deploy. I refreshed Zen manually and it deployed. I version stamped the bundle, rebooted three times in a row and it would not deploy, but when I refreshed Zen it deployed. Each time I checked the bundle in ZCM and it would be Pending, also in the ZenWorks Properties it would only be listed as available.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: "Pending" when using Recurring - When Device Refreshed

jcsmith1,

>The above yeilds the same result. For instance I associated that
>bundle to a test user, rebooted and it did not deploy. I refreshed Zen
>manually and it deployed. I version stamped the bundle, rebooted three
>times in a row and it would not deploy, but when I refreshed Zen it
>deployed.


Actually this is what I would expect. Unlike in the previous versions of
ZEN, bumping the version number of a bundle does not cause it to
re-install. It will only perform installations if any of the actions
actually changed.

Try this please - Created a bundle with a launch action, like launches
calc or notepad or such. Set the bundle to whatever schedule you prefer
for launch. Like user login or refresh , etc. See if you get the same
results as before.

--
Jared Jennings
Senior Systems Architect, Data Technique, Inc.
http://www.datatechnique.com

My Blog and Wiki with Tips, Tricks, and Tutorials
http://jaredjennings.org
Twitter@ jaredljennings
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.