I tried to replicate this on my Windows 10 Pro (10.0.15063 Build) and it worked okay.

Which log file did you see that message in? Are you on 17.1?

I found the message in the C:\Program Files (x86)\Novell\ZENworks\logs\LocalStore\zmd-messages.log file. We are utilizing the 17.1 agent.

Windows Enterprise LTSB 2016 (10.0.14393)

CRAIGDWILSON;2467554 wrote:
Perhaps something about the bundles or the user name....Especially if there are non-English characters.

Maybe logon as a simple user "bob".
Make user only one bundle is assigned - "Notepad".

This way no odd characters anywhere....no "too long" bundle name causing an issue.
Again....those are not known issues either...but I could imagine those........

The feature normally works..........So it's kind of trying to guess what is going on here.....
All I can say is this is not a common problem. Fairly confident no open bugs around this feature.....

Our bundles and user names have always been very simple. But, I went ahead and created a brand new ZENworks 2017 Update 1 server, fresh out of the box. Downloaded the latest copy of Windows 10 Pro (10.0.15063) and setup a fresh PC to match strj500's build. I created one ZENworks Explorer Configuration Policy with "Allow the end user to pin bundles" set to "Yes". Interestingly, it gave me the following warning, "End User pinning is an experimental feature. Due to issues with the Windows APIs, random issues occur related to the placement of these shortcuts."

On the computer, I tried simple user names such as named bob, root, and admin. I create a simple windows launch executable bundle named "notepad" and assigned it to the computer. I made sure there were no caps in the bundle name and kept the default ZENworks bundle icon.

It still gave me the error message, "Pin_Failed_StartMenuTiles (Bundle Name)". The error message doesn't seem to stop it from pinning to the Start Menu. Unpinning and repinning the bundle again to the start menu doesn't exhibit the initial error message.

I have tried both Pro and Enterprise versions of Windows 10. Different update levels: Original Release, Anniversary Update, and Creators Update.

At this point, I am clueless as to why this doesn't work for me.

An SR would be recommended......
Sounds as if development could likely code in some type of retry since it works after a 2nd try.
If you are educational, it would most likely be refunded.
You can private message me the SR.

While I do not know if you are educational.........
One thing I try to stress not as a sales person but a former admin....
I strongly suggest getting at least a 5-pack of SRs.
At least from the ZEN team, they are often refunded resulting in far more than 5 incidents.
(School Admins tend to be top notch........and thus tickets opened are very real and thus worthy of refunds...)

I also do my best to monitor, assist, and track SRs for folks whom I redirect to Support Ticket support if they post their numbers back here.

It allows faster access to patches and resolution for your issues.
Cost-wise it may be close to 1-2 days of consulting from a local IT Company.
Money very well spent for an enterprise solution.....

Yes...I get the limits of school budgets........

CRAIGDWILSON;2467833 wrote:
An SR would be recommended......
Sounds as if development could likely code in some type of retry since it works after a 2nd try.
If you are educational, it would most likely be refunded.
You can private message me the SR.

While I do not know if you are educational.........
One thing I try to stress not as a sales person but a former admin....
I strongly suggest getting at least a 5-pack of SRs.
At least from the ZEN team, they are often refunded resulting in far more than 5 incidents.
(School Admins tend to be top notch........and thus tickets opened are very real and thus worthy of refunds...)

I also do my best to monitor, assist, and track SRs for folks whom I redirect to Support Ticket support if they post their numbers back here.

It allows faster access to patches and resolution for your issues.
Cost-wise it may be close to 1-2 days of consulting from a local IT Company.
Money very well spent for an enterprise solution.....

Yes...I get the limits of school budgets........

Yeah, you hit the nail on the head. We are Medical School and we have have a educational subscription, so I was hoping to exhaust all of my options before putting in an SR since it's not covered under the contract.

But, I talked to my manager and he is good with putting in an SR.

Thanks for all of your help,
Brandon

Support/Development confirmed that this feature is experimental and they cannot resolve the error:

Here is there official response on the status of this item:

I want to let you know where we are. Development is at point where they feel they can’t make further progress on this. Some background may help. The feature is experimental because it’s not based on any open-code from Microsoft and they figured out a way to do it based off a hack/round about method. It’s difficult for them to troubleshoot or remedy the issue without access to code. They currently want to leave the functionality in as it, experimental.

Pre-requisites:
-Windows 10
-ZENworks 2017 Update 1
-ZENworks Explorer Policy - Allow the end user to pin bundles - enabled.
-Application icon is not being pushed to start menu.

Steps to reproduce error:
1) Open ZENworks Application
2) Right-click on a bundle
3) Select Pin to Start

FYI - There is currently a Test FTF for this issue for ZCM 2017 Update 1 that appears to resolve the issue.
Pending more feedback, an official patch may be released.

FYI - There is currently a Test FTF for this issue for ZCM 2017 Update 1 that appears to resolve the issue.
Pending more feedback, an official patch may be released.

FYI - There is currently a Test FTF for this issue for ZCM 2017 Update 1 that appears to resolve the issue.
Pending more feedback, an official patch may be released.

Sorry, There is not a Test FTF yet...work continues....
There is another issue for which one was just made.

Sorry, There is not a Test FTF yet...work continues....
There is another issue for which one was just made.

Sorry, There is not a Test FTF yet...work continues....
There is another issue for which one was just made.

Sorry, There is not a Test FTF yet...work continues....
There is another issue for which one was just made.