- OK (Default for all new tickets)
1. The Microsoft App-V 5.0 (SP3) sequencer fails to package application if that application contains "relationship part" (.rels) file.
2. This is a known limitation in App-V 5.0
3. The error message:
"An error was encountered while trying to finalize the package. Please check the event log for more details".
4. Relationship part can be identified by the presence of a file with a ".rels" file extension in a folder named "_rels".
5. To work around the limitation, all relationship files (.rels) needs to be deleted from the package source folder prior to saving the package.
6. Delete the file(s) when reaching the Create Package page in the new package wizard, just prior to clicking the Create button.
7. One of such application we have recently worked is:
8. This application has ".rels" files associated, so couldn't sequence the application as after deleting the files application was not working properly;
hence we have proceeded with MSI packaging.
9. More details on this can be found in this below KB article:
Quality section with RayQC
Command Line Snapshotting
As a Dell Partner we have now had the privilege of taking somewhere in the region of 750 Dell KACE customers through the Jumpstart training program. On occasions we are lucky enough to then work with some of those customers again, or through the course of our business and events such as the Dell Software user forum we get to renew friendships and acquaintances made during Jumpstart. I am constantly reminded that every customer is different. Different in their attitude, different in their approach to Dell KACE and different in their capabilities, and as hard we try to set our Jumpstart customers up in the best way to use their Dell KACE appliances, the paths that customers then travel are many and varied.
So we started to wonder, Jumpstart training is a great foundation, and for the areas of expertise that each customer selects, we do our best to get the customer to a certain level of competence. If we assume a certain level say 2 out of 5, is there a way of measuring where the average Dell KACE customer is at today and what is the average skill level across the customer base?
So we decided to see if we could introduce a simple process that enables us to measure how any individual customer is doing. We would then be able to compare that with the standard that we know KACE Jumpstart customers should be at the end of their Jumpstart program, and then use those scores to evaluate the Dell KACE community as a whole by setting a Benchmark.
What is the Survey
The survey is a simple questionnaire of 75 questions, that asks questions about your usage of all the functions within both K1 and K2 appliances.
The survey takes approx. 10 mins to complete
Once completed your scores are recorded and we then format a benchmark report, which is emailed to you, to show how you scored
Benchmark Maturity Survey
Challenge: Mimecast is an E-Mail risk management application that has a different installer for each version bitness of Microsoft Outlook, either x86 and x64, not the Windows architecture installed.
Requirement: Identify which version bitness of Outlook is installed on each computer to then install the proper version of Mimecast using the appropriate installer.
Solution: The architecture or version bitness of Microsoft Outlook is not gathered as a part of the standard inventory. Use Custom Inventory Rules to find what version of Outlook is installed, then create a Smart Label to group the similar machines together to then install the corresponding version of Mimecast against the label.
1. Identifier: Determine the architecture of Outlook installed. There is a registry to identify the architecture.
a. For example, Outlook 2013 has the following key/value name: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Outlook\Bitness and its value will be x86 or x64
2. Custom Inventory Rule
a. Go to Inventory -> Software and create a New Software
i. Define Name, Version and Publisher at a minimum
ii. Select OS versions to investigate
iii. Define Custom Inventory Rule
1. If you only have on version of Outlook installed, say 2013, you only need one entry for the rule: RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Outlook, Bitness, REG_SZ)
2. However, if you have more than one version or the possibility of more than one version, define the rule as follows:
Bitness, REG_SZ) OR
RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\11.0\Outlook, Bitness, REG_SZ) OR
RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Outlook, Bitness, REG_SZ) OR
RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\14.0\Outlook, Bitness, REG_SZ) OR
RegistryValueReturn(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\Outlook, Bitness, REG_SZ)
a. Create a Smart Label to group together all 32bit versions of Outlook and another label to group together all 64 bit versions of Outlook.
Installation of Mimecast
a. Create a Managed Install or Script to install the x86 version of Mimecast and target your “Microsoft Outlook Bitness x86 Installs” label.
b. Create a Managed Install or Script to install the x64 version of Mimecast and target your “Microsoft Outlook Bitness x64 Installs” label.